Use q=0x40 during the interview to be able to detect in scripts if the update was part of the interview

[alcalzone]

Use q=0x40 during the interview to be able to detect in scripts if the update was part of the interview

[easybeat]

Hi

I'm not sure if this is the right issue to add my comments but you will tell me if not.

I did install zwave2 adapter yesterday on my system and moved my rules to the new endpoints of the zwave2 devices. This did work without any problems. Then I restarted my system at some point and after a few minutes, I think when each device did send his status report, all my rules connected to a physical switch were triggered. You can imagine that my house was like a disco! Lights went on and off, shutters went up and down, music started, stopped and started again.

I couldn't believe so I started debugging and realised that on the first status report of a switch each scene endpoint updated the value, for example for a switch on button 1 value 0 was sent. This triggered my rules as this is like a physical button pressed.

My investigation did bring up that state "ready" is changed when the device sends first report. What I now built in my rule is a check on state "ready" when an event is triggered. If state "ready" is lastchanged less than 5 seconds before then my rule stops. Like this I was able to stop this startup disco.

I think this is a bug and you should look at this.

If you need more information please let me know.

Kind regards

Beat

[AlCalzone]

Yeah, this might be related. Could you share an example of your scripts so I can see how you use the triggers?

[easybeat]

I'm using NodeRed for my rules. In fact I have a ioBroker node pointing the topic to the Scene state of a switch. Whenever there is a change on that state the rule is triggered.

Does that make sense for you?

[AlCalzone]

Whenever there is a change on that state the rule is triggered.

Does that rule check if the state was actually changed or does it trigger whenever the value is updated (not necessarily changed)?

[AlCalzone]

Kinda depends on https://github.com/AlCalzone/node-zwave-js/issues/987

[AlCalzone]

In the upcoming version this will be fixed. Please check the new FAQ how to avoid triggering after a restart:
https://github.com/AlCalzone/ioBroker.zwave2/blob/master/docs/en/FAQ.md

[AlCalzone]

The mentioned change should resolve most of these problems (at least for all values that are read from the cache file). For all other updates that happen during the interview, I first need to solve https://github.com/AlCalzone/node-zwave-js/issues/987.

[easybeat]

Thank you! I will send you the log file about the other bug tomorrow.