Moritz Heusinger

> But maybe rewritable to use doc too? Yes, but then we cannot remove it from backup creation process yet without breaking backward compatibility, see my latest edit.

> There might be incompatibilities with the settings you put in [.eslintrc.js](https://github.com/ioBroker/ioBroker.js-controller/blob/master/.eslintrc.js), resulting in this failure. There should be no, @AlCalzone is working with VSCode too and it is all...

Would be fixed by porting binary states to a unique namespace as currently planned. Then a getState would not return contents of a binary state and thus all fine (assumption...

I have mixed feelings about this, for some, it may be useful, however, it can break something w/o really noticing, because of various reasons. Unfortunately, devs sometimes introduce breaking changes...

We can catch and log a more user friendly error but as discussed we should not start.

Or we can discuss about bringing non-instance-specific custom attributes to `custom` too by using the adapter name without the instance id. Additionally we allow the current properties like `smartName` but...

Are there any use cases for this filter functionality? Why should I ignore a whole state change of the related state?

For this to work, we would need to create the alias as real state (write it in db) because when value is filtered out and now someone wants to get...

The only possibility I see is to enhance the existing state object with its current alias state. Otherwise we cannot stay 100 % in sync, and we simply need to...

So here we should decide if we want aliases to be really stored instead of being just a transform function as it is currently. If we keep aliases as transformers,...