You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This device does not support Associations, so it is unable to report the changed state on its own. It has to be polled regularly for its state to get updated.
Since that is only necessary for a handful of legacy devices and can have severe negative influences on a Z-Wave network if not done correctly, iobroker.zwave2 does not poll on its own. You can use the javascript adapter however to do this, e.g. to poll those two states every minute:
// Poll every minute, see https://github.com/ioBroker/ioBroker.javascript/blob/master/docs/en/javascript.md#time-schedule for detailsschedule("* * * * *",()=>{sendTo("zwave2.0","sendCommand",{nodeId: 2,// The target nodecommandClass: "Binary Switch",// Which command class to usecommand: "get",// Which command should be sent},({ error, result })=>{//});sendTo("zwave2.0","sendCommand",{nodeId: 2,// The target nodecommandClass: "Thermostat Mode",// Which command class to usecommand: "get",// Which command should be sent},({ error, result })=>{//});});
Versions:
The states of BinarySwitch and ThermostatMode did not change in ioBroker when the device changes its state.
https://products.z-wavealliance.org/products/1618
Device:
Logfile of an interview:
zwavejs_2023-06-19.log
The text was updated successfully, but these errors were encountered: