#Hmmm good point What would be the best
robust abyss
@wild patio So I looked at a lot of stuff and found something odd - when I push the up (ON) switch on the light switch, neither the history nor the logbook reflect anything. However, I see these 2 events come in through the z-wave JS control panel:
2022-10-29T20:48:46.813Z - VALUE UPDATED
Arg 0:
└─commandClassName: Binary Switch
└─commandClass: 37
└─property: currentValue
└─endpoint: 0
└─newValue: true
└─prevValue: true
└─propertyName: currentValue
2022-10-29T20:48:46.992Z - VALUE UPDATED
Arg 0:
└─commandClassName: Binary Switch
└─commandClass: 37
└─property: currentValue
└─endpoint: 0
└─newValue: true
└─prevValue: true
└─propertyName: currentValue
Would there be any way to use this data for anything?
wild patio
You can use event triggers, but ideally you want #zwave-archived to be reporting the state change as a sate change
Also, I get notifications when you reply, you really don't need to tag me
robust abyss
Hmmm any chance you could link an example of a trigger that could ingest these kinds of values?
Also, I tried running the Z-wave JS debug console and got the same thing so I know at least Z-wave is reporting the same-same state changes:
2022-10-29 16:56:06.937 INFO Z-WAVE: Node 4: value updated: 37-0-currentValue true => true
2022-10-29 16:56:09.097 INFO Z-WAVE: Node 4: value updated: 37-0-currentValue true => true
2022-10-29 16:56:11.131 INFO Z-WAVE: Node 4: value updated: 37-0-currentValue true => true
wild patio
#zwave-archived can likely help you better than I can, I don't use Z-Wave JS