Max Hauser

is it correct like this or recent change? If it was a recent design change, then we should avoid having properties with free chooseable names and fixed names on the...

Edit: ah it is a non promise method without callback so this throws yeah.

> Ok @foxriver76 for "get" we might return null like "state noch defined" in such case ... no idea what we could do on set? Just catch in adapter. I...

Umgehen schon aber er gibt einen Fehler zurück weil er den Befehl nicht ausführen kann, da alias der ins leere linkt -> State wird nicht geschrieben und das wird mitgeteilt.

Für get mag das Sinn machen wie Ingo sagt convenience null Objekt aber für set nicht

Which means warning that we might throw in the future, not really hurting doing it already for these cases as it is done for quite a while now and this...

I am not that familiar with CUXD but aren't you able to define the datatype when creating devices there? The object `hm-rpc.0.CUX2801500.1.SET_STATE` probably has `NATIVE.TYPE` defined as a number like.

> `{ "_id": "hm-rpc.0.CUX2801500.1", "type": "channel", "common": { "name": "Schlafzimmer Bettbeleuchtung" }, "native": { "ADDRESS": "CUX2801500:1", "AES_ACTIVE": 0, "FLAGS": 1, "VERSION": 1, "TYPE": "VIR-LG-RGBW-DIM-CH", "PARENT": "CUX2801500", "PARENT_TYPE": "VIR-LG-RGBW-DIM", "DIRECTION": 0,...

And what is written to the State when the Adapter Logs the Warning?

And the warning is logged by hm-rpc itself?