Long delays in ZWAVE

[Neo Andersson 230]

Guys, anyone noticed something similar?

I am having randomly some really long delays between sensor detection and perfromed actions.

I havent changed anything in my system quite a long time, so this is not related to any new device or whatsoever. (before there was never any such issue)

I noticed this i think after the latest Beta update, but i am not sure if its related.

It is not like all the time, but it happens..and when happens, the delay is like 4-5 seconds, or even more..

Anyone noticed some similar behaviour?

Thanks

[awlieser 19]

Same here - scenes that have run for months flawlessly suddenly stopped working. I did not update to the Beta-version, but … strange enough! ☹️
 

P.S. All of the scenes no longer working properly include devices added via the Hue Plugin to HC3 - maybe the Plugin needs to be updated to mirror any potential changes in the Hue Bridge firmware. Stranger even, that voice commands via Amazon Alexa still work for these devices. I‘m at a total loss here ☹️

Edited March 5, 2025 by awlieser

[Sjakie 156]

@Neo Andersson,  no I don't have that delay. 

It can happen if there is a kind of "loop" in a QA when a trigger is followed shortly after execution and revert back. This proces only stops by restart or another trigger break that "loop".

[SmartHomeEddy 1,005]

All running well overhere also (on the stable version). 

[Brors94 115]

15 hours ago, Sjakie said:

@Neo Andersson,  no I don't have that delay. 

It can happen if there is a kind of "loop" in a QA when a trigger is followed shortly after execution and revert back. This proces only stops by restart or another trigger break that "loop".

 

Hmm, what type of loop are you thinking of here? 🤔 
 

Would love an example so I understand and can avoid this 😅 
 

[akatar 208]

Use zniffer to see what is going on. 

 

 

i had once: see picture  @Neo Andersson

Please login or register to see this attachment.

[Sjakie 156]

@Brors94, I had 2 GV who are continues changing from one value into another and back. This made memory usage up and was slowing down response time hc3.

This is visible in debug.

 

@akatar good idea!

 

[Brors94 115]

GV short for Global Variable? 😅🤔

 

 

[Sjakie 156]

Yes

[Neo Andersson 230]

I forgot to mentioin that i am running on Beta

 

@akatar Yeah, if i only knew when to check it. If the delay happens, i cant rush that moment to my PC. Maybe once i will be lucky enough to catch it ..

 

@Sjakie If it was a loop in a QA, i suppose it would have happened back in time too, not only after the beta udpate..thats why it is strange..It never happened before..And i have not touched my system long long time..On the other hand, if it was a QA loop, or a GV change, it would be nice, if i could somehow find the QA where it is originating from.

 

 

Thanks

Edited March 7, 2025 by Neo Andersson

[Sjakie 156]

@Neo. in case of QA or scenario you should see it in debug. In debug reset and see which trigger(s) stays rolling over your screen.

FW 5.171