Well, the majority of users didn’t encounter this issue with 2.2.4 either ...
1 Like
Yeah, moving up to 2.2.5 would be the recommended course of action. There will be no more fixes to version 2.2.4.
2 Likes
Do your logs say anything? Can you reach port 8081 when it crashes? do you have any 3rd party apps installed or community apps/drivers installed? If it continues to crash after the update, I would start by disabling anything 3rd party and then turning things on one by one to see when it crashes. I know it's tedious but process of elimination works.
- Nothing appears in the logs I can observe in the web interface (under logs or system events)
- Reviewing the system events just pointed out to me that I was, in fact, already running 2.2.5 when the daily crashing behavior began (see attached log snippet). I've edited the main post to reflect that.
- I'll check 8081 next time it crashes
- I'll try disabling various apps
My question is: is there some way to get at lower level system logs to debug a crash like this?
FYI (via direct reply) turns out I'm seeing this on 2.2.5
do you happen to have 3210-L zw/zig plugs in use?
How would I determine that? Is that the chipset or the name of the plug?
do you happen to have 3210-L zw/zig plugs in use?
I just had another crash after 84 hours (which is better than it was doing before).
Unpingable on the network when in the crashed state. Came up quickly after a power cycle.
I'll throw my hat into the rig as my first post. I have a C5 hub as well that has been locking up nightly, usually overnight, after recent updates. I don't remember which update it started on but it was the past few weeks. Currently running the latest 2.2.5.131.
When it's locked up I have verified I cannot reach it on port 8081. My only solution is to go and power cycle the box. The only new addition to my system was an Enbrighten wall toggle switch.
I looked through my system event logs and it appears the lock ups started after I upgraded from 2.2.4.158 to 2.2.5.124.
There is a known issue with these if you enable the Zwave repeater capability in addition to the default zigbee.
2 Likes
Do you have a link to where this has been written about by the staff?
Don't recall one directly commented on by staff, although I'm sure that there probably is, but if you do a search on 3210-L and Zwave issues or device lockups you'll end up with a few pages of threads.
2 Likes
Yup. To add to this, my recollection is that the issue crops up dependent on the fw version on the the 3210-L outlets.
1 Like
I've been having the same crashes since upgrading to 2.2.5. I'm also on a c5. The crashes happen intermittently, sometimes after a few days, mostly every day, and one time an hour after unplugging and plugging it back in.
Did you figure out what caused it, or did you get a response from support?
Just an update here: the hub was fairly stable (making it multiple days without crashing) for a few weeks.
In the past couple of days, it's started crashing multiple times a day. (No device or config changes)
I'm rolling back to 2.2.4 to see if that helps.
