[2.2.4.139] Woke up to Slowwwww world - delays & non-responsive

kahn-hubitat · December 5, 2020, 3:57pm

when i briefly testing on .151 the ecolinks would sucessfully send the open and the rule would fire but the light would not turn on or turn on delayed.. after sending the open the ecolinks appared to temporarily drop off the net and start a packet storm for some reason.
ie

no such issue in 2.2.3

this occured intemittantly with two different ecolink contact and one ecolink motion... but not every time. so it was not just one bad device or i would have tried replacing it.

Since i have gotten the zniffer running so if i ever try upgrading again i can look at it.

JasonJoel · December 5, 2020, 4:00pm

Interesting. I don't see anything in the zwave logs when my contract sensor open/closes, so I can't comment on what mine does (well, I guess I could go look at my sniffer logs, but no time right now).

OT, but I find that the zwave log only shows what it feels like showing, and DEFINITELY (as shown by sniffer logs) does not show all zwave events/commands that the hub sees.

672southmain · December 5, 2020, 7:13pm

It would be nice if the built-in drivers and apps included version numbers on the Devices and Apps pages.

Rxich · December 6, 2020, 3:16am

Hello Victor, That's specifically for the z-wave firmware? Is there anyway to force a downgrade to a previous hub firmware? Hub only holds 3 previous versions, and I'm concerned about upgrading past my stable 2.2.0.126, with all the incremental releases will remove 2.2.0 for me(on my C4).

velvetfoot · December 6, 2020, 3:32am

Here are some z-wave details on the four Ecolink door sensors.

gopher.ny · December 6, 2020, 12:17pm

There's a way to download latest iteration of 2.2.3 directly: /hub/advanced/download223
It doesn't install it, but it gets downloaded locally and you can switch to it.

velvetfoot · December 6, 2020, 12:57pm

I bagged two today. Now 6 for 6.

Woke up to upstairs bathroom 8 second delay.
Went downstairs: same for basement.
Did battery thing on basement Ecolink: snappy.
Went upstairs; still slow (interesting)
Did battery thing: snappy

Unfortunately, I totally forgot to set debug logging.

velvetfoot · December 7, 2020, 1:32am

Fooling around with the Basic ZWave tool.
Removing the case on the Ecolink wakes it up.

Here is version report:

Two parameters available:

Three nodes available for association in Group 2 (I'd like to try this, but haven't figured out how without a driver):

velvetfoot · December 7, 2020, 1:35am

Here is the advanced manual for the Ecolink contact sensor.

velvetfoot · December 7, 2020, 1:39pm

Woke up to snappy world.
Was it my fooling around with the parameter tool (I changed nothing)?
Maybe .158?
Probably just have to wait for it to happen again, but always hopeful.

velvetfoot · December 7, 2020, 2:22pm

I take it back.
Went upstairs to super slowww world.
Wouldn't start working with usual trick.
Couldn't pursue. Maybe later.
I'm going to look at the behavior of the led on the sensor a little more.
This sucks.

velvetfoot · December 7, 2020, 4:22pm

I just excluded/included all five of my Ecolink contacts.
We'll see how that goes.

lewis.heidrick · December 7, 2020, 4:39pm

Sounds like there's something else going on and it's not related to the ecolinks imo. What do your rules look like?

velvetfoot · December 7, 2020, 5:30pm

Nothing fancy:

lewis.heidrick · December 7, 2020, 5:56pm

What about your hub stats?

http://hubitat.local/hub/enableStats (Run this to start stat collection and let it collect for about 5 minutes)
http://hubitat.local/hub/stats (Run this after the 5 minutes has elapsed to view the stats)
http://hubitat.local/hub/disableStats (Run this to stop stat collection)
For Winodws PC's Shift + Windows Key + S is an easy way to take a cropped screenshot.

You can use these links to track down the apps and devices by putting the id's from stats
http://hubitat.local/installedapp/configure/APPIDHERE
http://hubitat.local/device/edit/DEVICEIDHERE

Any issues with memory?
http://hubitat.local/hub/advanced/freeOSMemoryHistory

velvetfoot · December 7, 2020, 5:57pm

I think you commented that they didn't look back last time I ran them.

lewis.heidrick · December 7, 2020, 5:58pm

Things change between builds and even device pairings it's good to check.

lewis.heidrick · December 7, 2020, 6:00pm

Memory may be a culprit seeing how it comes and goes. Database might be doing a bunch of garbage collection.

http://hubitat.local/hub/advanced/freeOSMemoryHistory

danabw · December 7, 2020, 6:04pm

Would the database backup/immediate restore help to ID where the problem is? As in, do that in the morning before trying anything and see if the problems persist at that time?

lewis.heidrick · December 7, 2020, 6:04pm

Depends on if its a corruption issue or not. I doubt it is but maybe. Seems more like it's getting bogged down by something maybe mesh maybe hub.