lucky for you lot being able to update your sensors, my hub has been Zigbee nil for 5 days now and I finally get an email saying that my hub is one of the few affected by a dodgy update, did i want to wait or have a new hub. well i’ve asked for a new hub, lets face it, if it’s one of a few that doesn’t take updates well then i want to change it. In the meantime though, before i’d realised it was the firmware failure that caused this, i’d managed to snap 2 battery clips on my sensors by continually switching batteries in and out, very poor design. For now i have to wait to see if a new hub turns up, some confirmation that one is on the way would be nice.
With the constant false alarms i’m getting on upgraded motion sensors, i’m not sure i’m feeling very lucky right now.
How do I get the hub to stop checking the software version on my Lightify Spots? Whenever it checks the software version, it’s like a power-on condition. Lights turn on to full brightness at the power up color. I have turned OFF OTA , but it is still checking once per day. Frustrating.
The same thing was happening to me. I disabled my OTA updates and it stopped.
I recommend letting support now. So they can keep track of these instances. That’s what I did.
Please do. We are pulling logs and looking into this
@Mike_Maxwell look forward to your resolution on this. Also tagging @einars on this conversation, he’s spent countless hours trying to figure out why suddenly his hub started rebooting. Working through for a few days have narrowed it down to some SmartApp API’s which when called are probably causing the reboot, no sure exactly which one yet. @Aaron
I threw this at support, there’s no practical way for me to correlate the reboots to an SA’s API call…
@aron huge amount of elimination and a patient family. Roughly twice a day it reboots, and status on z-wave units gets lost. All automation on lights from movement and such get fuzzy. Mine problem is pre and post hub update. FYI.
Elimination, remove all your SA’s and then add them on one a day is what einars did. Painful process.
There is no way in effin hell I’m going to do that.
With over 200 devices and 110 SA’s it’s never going to happen…
…I dread the day my hub dies as there’s no migration or restore process still.
Yea, I already did this when I got my V2 hub, that took two days, and I had half the stuff I have now…
Another one i got last night was this one, never seen that before:
HUB, zwStatus, ready, Z-Wave is ready
HUB, zwStatus, power cycle, Z-Wave power cycle started
HUB,Err 120: Z-Wave send timed out, Err 120: Z-Wave send timed out
A couple updates:
- I changed the title of this thread to reflect we released Hub firmware version 16.9.
- We have identified two unique Zigbee issues with the update:
2a. Some Zigbee devices will not connect until the Hub is power cycled for 5-10 minutes.
2b. Some Zigbee mesh network maps did not fully migrate with the update.
2c. Sensor OTA updates take longer than expected and cause false-positive events.
Note, these are both edge-cases and may not be what is actually affecting you. If you think are are experiencing this issue, please try power cycling your Hub or disabling the OTA feature.
Like a broken record, I don’t understand why ST calls it a community platform when they don’t test their firmware and mobile releases on the popular community apps before releasing it. Whenever anyone contacts support their only answer is it’s a community app and not a stock ST app so we can’t debug or look into it. So why the heck do they publish API’s and claim to have a community developed apps platform when they don’t want to test their releases against it?
So you’re saying (definitively) that hub reboots are being caused by custom code (SA/DTH) ?, or is this just what you suspect at this point…
Strong suspicion as when all the apps are uninstalled it doesn’t reboot and when reinstalled it reboots (ofcourse event driven reboots). I suspect it’s a SA as the reboots happen with stock DH’s also. Anyways ST support has been made aware of this but since it’s was only one user I aware of, I was interested when you also said that it rebooted.
Same here, my hub goes offline once a day since the update.
TLDR; I skimmed through the new bugs on this update, and found mostly zigbee related. I would like to include a new Z-wave issue as well.
- Z-wave replace no longer functions, just spins. Work around is force delete via IDE, zwave general exclude, disable and enable z-wave radio, then add device and re associate to all smart apps.
- Z-wave force remove no longer functions. Workaround is IDE remove (“delete”).
- Adding a new Z-wave device after a force delete disables or locks up the z-wave module. 908.4mhz stops transmitting all together. workaround is to disable and enable Z-wave module from the IDE to get it to start transmitting again.
Please don’t tell me this is specific to my hub, I’m already on my 4th smartthings hub in a little over 1 year on this platform. I have done the cold boot multiple times, until I discovered the disable/enable z-wave module work around.