kpine

Light level value which works fine: ```json { "Label": "Level", "Value": 0, "Units": "", "ValueSet": false, "ValuePolled": false, "ChangeVerified": false, "Min": 0, "Max": 255, "Type": "Byte", "Instance": 1, "CommandClass": "COMMAND_CLASS_SWITCH_MULTILEVEL",...

@matejdro You can use [MQTT](https://github.com/OpenZWave/qt-openzwave/blob/master/docs/MQTT.md#setvalue) to set the value. Publish `OpenZWave/1/command/setvalue/` Data: ```json { "ValueIDKey": key, "Value": value, } ``` But as I mentioned in #68 your problem is that...

This seems like it might be a problem with the device XML file. Also open-zwave is failing to properly validate input. As mentioned, the [definition](https://github.com/OpenZWave/open-zwave/blob/b0afd4c60b38065fdbc57835cb3eb6035afcc00f/config/aeotec/zw096.xml#L140 ) of this value (and...

The HEM Gen5 config params don't specify a min and max, so it probably has a similar issue. If you look in your ozwcache file you'll see how that gets...

FYI, none of the network commands are implemented in OZW Admin yet.

Same as existing problem in HA core zwave https://github.com/home-assistant/core/issues/31253. The discovery schema needs to be updated for that device type.

Pretty sure, but I'll try again.

I can reproduce. I was definitely on 0.0.13, in fact I upgraded to 0.0.14 to reproduce again. > BTW: In the log snippet you've sent there are no errors. I...

Yes, I did refresh. The bigger problem is the creation of the entities though, they are stored before the device name is seen apparently.

I tried again and can't really say this is fixed because after adding the node there is no new Device entry or entities **at all**, even after refreshing (F5) the...