4.100 still slow starting scenes

[wienog 107]

A few months ago I posted a similar message as this one saying that especially scenes triggered by (often Fibaro-) motion sensors were starting erratically , sometimes after 1 sec sometimes after 4 sometimes after 15 seconds only.

Several items to check were given to me: look for some endless loop, check for VD's with buttons that have magically disappeared, check out Lua-scenes for errors or typo's, reconfigure every device, rebuild your mesh;....

Well,I have spent the last two months doing just that. I have cleaned up my whole operation, removed unused scenes, rewrote scenes that looked suspicious , etc..

Guess what: HC2 is STILL responding very erratically to Fibaro motion sensors (and other triggers but that is less obvious because you can not literally SEE when they are triggered).

So what happens:

A scene that is triggered by a motion sensor takes sometimes 1 second, sometimes 5 or 6 seconds, sometimes 10 to 15 seconds before it starts. There is absolutely no other factor that changes with this behavior (like: it happens only when it's cold or when the cat is outside or aunt Anna is visiting).

THE SAME SCENE started from the webinterface or the (IOS-)app executes 100 % of the time IMMEDIATELY, without ANY delay.

 

So, i see the led of the motion sensor coming on and have to wait patiently what will happen this time: will the light go on immediately or only after 15 seconds, after i broke my legs in the dark on the stairs ?

 

So, somehow HC2 for some reason that I just can not find, AND ONLY SINCE 4.09x reacts slowly and erratically to triggered motion sensors.

 

Any ideas ? PLEASE ???

 

P.S.: 99% of my motion sensors are in direct contact with the HC2. Increasing sensitivity of the sensor doesn't help a bit: the sensor triggers, it's the HC2 that responds erratically to the trigger...

Edited November 23, 2016 by wienog

[AutoFrank 372]

Hi,

This sounds like an exact mirror image of my experience and I too have weeded out all the poor code quality at this stage.

I have deleted and rewrote scenes, converted some to VD's, offloaded http requests to VD's and use press button, disabled some scenes to reduce the load, switched off bridges to reduce the load, doubted myself several times and even went through a week where I rebooted the HC2 every morning at 3am (to clear out any gremlins that may have built up).. but like Wienog above I am out of ideas at this stage.

 

I have one simple scene - ("turn on porch light when door sensor if triggered") that will sometimes trigger immediately and sometimes take 3-4 or 5 seconds to trigger.

 

I also have observed delays in other scenes that I manually activate. These mainly contain a number of sequenced steps and could be something like the following.

• Turn on light A
• Turn off light B
• Pause music in room A
• Turn on TV in room B

The code at this stage is rock solid and the annoying thing is that I have some 'poor quality" code that pre-dates 4.090 that I know for a fact worked every time reliably but not my well honed code is still not reliable

 

To me it looks like that scenes are sometime slow to start but once they start, they then execute as one would expect 

This is consistent whether it is a triggered scene or a manually driven scene and is not limited to the same scene each time

 

-frank

 

[devfern24 10]

4 hours ago, wienog said:

A few months ago I posted a similar message as this one saying that especially scenes triggered by (often Fibaro-) motion sensors were starting erratically , sometimes after 1 sec sometimes after 4 sometimes after 15 seconds only.

Several items to check were given to me: look for some endless loop, check for VD's with buttons that have magically disappeared, check out Lua-scenes for errors or typo's, reconfigure every device, rebuild your mesh;....

Well,I have spent the last two months doing just that. I have cleaned up my whole operation, removed unused scenes, rewrote scenes that looked suspicious , etc..

Guess what: HC2 is STILL responding very erratically to Fibaro motion sensors (and other triggers but that is less obvious because you can not literally SEE when they are triggered).

So what happens:

A scene that is triggered by a motion sensor takes sometimes 1 second, sometimes 5 or 6 seconds, sometimes 10 to 15 seconds before it starts. There is absolutely no other factor that changes with this behavior (like: it happens only when it's cold or when the cat is outside or aunt Anna is visiting).

THE SAME SCENE started from the webinterface or the (IOS-)app executes 100 % of the time IMMEDIATELY, without ANY delay.

 

So, i see the led of the motion sensor coming on and have to wait patiently what will happen this time: will the light go on immediately or only after 15 seconds, after i broke my legs in the dark on the stairs ?

 

So, somehow HC2 for some reason that I just can not find, AND ONLY SINCE 4.09x reacts slowly and erratically to triggered motion sensors.

 

Any ideas ? PLEASE ???

 

P.S.: 99% of my motion sensors are in direct contact with the HC2. Increasing sensitivity of the sensor doesn't help a bit: the sensor triggers, it's the HC2 that responds erratically to the trigger...

 

+1

 

I have also noticed over the last couple months that my motion triggered lighting scenes have been erratic. They sometimes trigger perfectly, sometimes it takes 5-6 seconds or more. I have tried going through all my code as well. Like you say, I am not sure if this is an issue with the motion sensors (which, by the way, have never updated their battery level once since being installed) or the HC2 because any delay triggering of other scenes is not as noticeable as when your lights don't turn on for you...

[Alex 32]

Similar to my topic:

Please login or register to see this link.

 

 

[AutoFrank 372]

@Alex

Thanks for spotting and sorry for the ovelap.

I'll continue my contribution there

 

-frank

[Alex 32]

No problem. I am glad there are other people around having the same problem (but not having the problem  ).

You might be right that it has started with 4.10. I am not sure about this, but now after thinking about this I believe you  are right.

[Sankotronic 2,370]

My HC2 is on FW 4.100 and everything was fine until last reboot when 141 devices became not configured. Restoring backup helped and everything get back expect last work which I always have backed up on my computer anyway. So, after restoring all was OK but just for curiosity and to check if all devices working fine I ticked options "Pooling dead devices" and "Mark nodes dead" on configuration Z-wave network panel and saved change:

 

 

 

Thanks to that I found that I have problem with 3 door/window sensor that has problem with wake up and exchanging data with controller. But that is also when I noticed that some scenes has delay, also that sometimes GUI is not refreshed properly and also Philips HUE lamps again sometimes has wrong status on GUI. LED on HC2 for z-wave also was more active than before.

 

So now I again removed tick for "Polling dead devices" and also individually removed "Mark nodes as dead" on those 3 door/window sensors. After that it seems that now scenes react properly on triggers but let me see for next few days.

 

Maybe that is not source of this problem with delays, but for now it looks to me that it is. Can you check if you have ticked this options, especially first one "Polling dead devices"?

Edited May 2, 2017 by Sankotronic
Attachment quota filled up / deleting older stuff sorry :-(

[Alex 32]

51 minutes ago, Sankotronic said:

Maybe that is not source of this problem with delays, but for now it looks to me that it is. Can you check if you have ticked this options, especially first one "Polling dead devices"?

I have 159 devices and these two options checked.

Right now I have no dead devices.

But I will test it this evening.

[Sankotronic 2,370]

I think that my door/window sensors are faulty because they are just few meters away from HC2 and still unable to transfer data during wake up period while status is correctly reported. On both I had to replace batteries. I'm testing my scenes and for now looks good, but let's wait till at least tomorrow to be sure.

[AutoFrank 372]

I have these also options check.  Will uncheck and see if this improves things 

 

Thx

[Sankotronic 2,370]

@AutoFrank

 

It seems that this system with marking nodes as dead is buggy on HC. How it is really working? I expected if I tick "Mark dead devices" in configuration of z-wave network that all devices will have this option tick which actually happened. Then if I want just some devices not to be marked dead that I can untick it on their advanced tab what I did. But now when I checked, again all devices have unticked this option??

 

Pooling is on other hand working only with devices that are powered from power grid. Battery devices can't be pulled since they are sleeping and not listening to THE BOX. But even then, how can system pull dead device? Probably only after power loss and when power is back on?

 

Still for me it is difficult to understand how it is possible that battery powered sensor is regularly reporting state change and it is unable to establish reliable communication with controller during wake up time??

 

Or maybe we have some other problem? Anyway, for now with this options unticked no delays with scenes.

[AutoFrank 372]

sorry to post a bad result

 

I unchecked the two options listed above earlier today and rebooted the HC2

Unfortunately I am still seeing the delay in my scenes...