kpine

The server [checks](https://github.com/zwave-js/zwave-js-server/blob/1595c0d76c1be6a5d73c747f2d99e078514d91bf/src/lib/forward.ts#L167) the `node.ready` flag and ignores any value/metadata events prior to the flag being true. That should prevent any incomplete values from being created within HA?

The logs are now missing due to pastebin expiration, but was the original problem that the notification CC values have the wrong metadata ("any")? If so, isn't it the same...

Just to add on here with another example, I track my furnace off/on state and visualize it with this panel. If the furnace is on and the time range includes...

There is an issue logged in https://github.com/OpenZWave/qt-openzwave/issues/103. If you weren't using the Addon you could install the official docker image and there is an option to show a dot for...

The config params are defined by XML files. https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices#creating-configuration-variables I think I misread your ask. Adding the parameter index as a column in the config UI would be useful.

The command topics are all lowercase with a trailing slash: `OpenZWave/1/command/setvalue/`

Neither `32` nor `00100000` are valid values for a BitSet (according to the [docs](https://github.com/OpenZWave/qt-openzwave/blob/master/docs/MQTT.md#setvalue)), and you probably are getting some kind of error back as a response. The value is...

It does not exist yet.

No way to disable it currently, but it would be nice to have.

I can confirm the same with my thermostat. My light switch does not have this behavior though. I notice there is a difference between the controls. The light switch Level...