Replies: 1 comment 4 replies
-
Why not just subscribe to single values update? I don't understand what you are trying to archieve here |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on decoding the "node_value_updated" payloads.
They are HUGE, the worst is for a TKB TZ56D dual wall switch at 269984 chars.
Most of that is 255 pairs of scene configuration.
Is there any way to get just the device values? (like zigbee2mqtt)
The log shows what has changed, and publishes a basic message -
Wall switch -
2021-11-06 16:08:25.677 DEBUG MQTT: Publishing to zwave2mqtt/Study/WallSwitch-2/37/0/currentValue: { time: 1636214905676, value: false } with options { qos: 1, retain: true }
2021-11-06 16:08:25.679 INFO ZWAVE: Node 59: value updated: 37-0-currentValue false => false
Motion sensor -
2021-11-06 16:08:20.539 DEBUG MQTT: Publishing to zwave2mqtt/nodeID_60/48/0/Motion: { time: 1636214900538, value: true } with options { qos: 1, retain: true }
2021-11-06 16:08:20.540 INFO ZWAVE: Node 60: value updated: 48-0-Motion false => true
Beta Was this translation helpful? Give feedback.
All reactions