Ditto. Mine occurred at 18:42 UTC today (30 minutes ago)…with no notice.
Yelp, mines updated as well.
i dont think im on a beta test. already emailed support. how do we go about in updating our hubs. ???
Yep, mine updated (v2). I have never been in a beta.
Ditto… just happened at 3:00 PM EST.
Looks like mine updated on 12/7. Had no idea.
2018-12-07 12:59:21.168 PM MST
3 days ago HUB hub updater action: apply, result: SUCCESS, target: FFFFFFFF, version: FFFFFFFF, hardwareInfo: 000F hub updater action: apply, re… hub updater action: apply, result: SUCCESS, target: FFFFFFFF, version: FFFFFFFF, hardwareInfo: 000F
2018-12-07 12:58:50.158 PM MST
3 days ago HUB hub updater action: notify, status: SUCCESS, target: FFFFFFFF, version: FFFFFFFF, hardwareInfo: 000F hub updater action: notify, s… hub updater action: notify, status: SUCCESS, target: FFFFFFFF, version: FFFFFFFF, hardwareInfo: 000F
2018-12-07 12:58:45.474 PM MST
3 days ago HUB index:04, ip:7F000001, port:0BB8, requestId:324c2b56-272c-44b1-ae8f-2540a000bdf7, headers:SFRUUC8xLj index:04, ip:7F000001, port:0… index:04, ip:7F000001, port:0BB8, requestId:324c2b56-272c-44b1-ae8f-2540a000bdf7, headers:SFRUUC8xLjEgMjAwIE9LDQpTZXJ2ZXI6IFZp…
2018-12-07 12:58:35.105 PM MST
3 days ago HUB zwNwk zw network:F2C761B5, node:01, suc:01
2018-12-07 12:58:35.087 PM MST
3 days ago HUB zwStatus ready Z-Wave is ready
2018-12-07 12:58:35.086 PM MST
3 days ago HUB index:02, ip:7F000001, port:0BB8, requestId:b816b49c-50f1-4dc4-9f98-bc1548affdbc, headers:SFRUUC8xLj index:02, ip:7F000001, port:0… index:02, ip:7F000001, port:0BB8, requestId:b816b49c-50f1-4dc4-9f98-bc1548affdbc, headers:SFRUUC8xLjEgMjAwIE9LDQpTZXJ2ZXI6IFZp…
2018-12-07 12:58:28.040 PM MST
3 days ago HUB hubStatus zb_radio_on
2018-12-07 12:58:28.032 PM MST
3 days ago HUB hubInfo hardwareID:000F, version:16, … hardwareID:000F, version:16, mac:24:FD:5B:02:15:B6, localip:192.168.0.129, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWM…
2018-12-07 12:58:25.785 PM MST
3 days ago HUB ping ping ping
2018-12-07 12:58:25.755 PM MST
3 days ago HUB hubStatus zb_radio_off
2018-12-07 12:58:25.746 PM MST
3 days ago HUB hubInfo hardwareID:000F, version:16, … hardwareID:000F, version:16, mac:24:FD:5B:02:15:B6, localip:192.168.0.129, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWM…
2018-12-07 12:58:22.772 PM MST
3 days ago HUB register register register
2018-12-07 12:58:22.754 PM MST
3 days ago HUB ENTITY_UPDATE HubUpdated Hub ‘Home Hub’ updated
2018-12-07 12:58:22.682 PM MST
3 days ago HUB hubStatus active Your SmartThings Hub at Home is now active.
2018-12-07 12:57:48.739 PM MST
3 days ago HUB hubStatus disconnected Your SmartThings Hub at Home is now disconnected. Please check your internet connection.
2018-12-07 12:54:03.140 PM MST
3 days ago HUB ping ping ping
2018-12-07 12:53:09.660 PM MST
3 days ago HUB hub updater action: notify, status: SUCCESS, target: FFFFFFFF, version: FFFFFFFF, hardwareInfo: 000F hub updater action: notify, s… hub updater action: n
just got updated as well… is this a good thing or a bad thing? hopefully a good thing… my hub has been acting crazy recently…again…
Whether it’s a good thing or not, it’s unacceptable to auto-update, especially without any notice or warning. I know of no other technology product that takes this approach. It’s your device, not Samsung’s. Not even Apple, famous for their tight control of their “ecosystem”, does this.
My Internet router, smart speakers, TV, PC etc all give me a polite notice that new firmware is available, and ask whether would I like to upgrade, or perhaps prefer to wait for a more convenient time…
This attitude is enough, on it’s own, to make me consider an alternative platform.
I’m not defending ST here but Nest puts out updates automatically and without notice and so does Amazon with their Alexa devices. I am sure I can think of others if I try.
2 Likes
After a reboot of the hub I now seem to get every time this set of lines. ZWave is ready and then ZWave power cycle has started.
Is anyone else seeing this after a hub reboot?
the z-wave power cycle is caused by the zwBadNode preceding it
Windows 10.
1 Like
Mine too.
Maybe they fixed the battery drain issue?! My presence sensor go through batteries like candy on Halloween! Wishfully thinking I know, but one can dream.
Do a zwave replace on that dining room dimmer switch to see if that stops.
Oh the bad node causes the zwave power cycle? What does bad node mean? When I am home again I can do a replace on the dinning room light, I guess. The last event from the dinning room dimmer was last night. Did the device have a hardware failure? Did the firmware update corrupt the entry for this device?
Regarding the v2 Hub firmware update, please see Hub Firmware Release Notes - 24.20
What kind of sensor updates? Does this fix the battery drain and or incorrect battery reporting?
It’s more like a restart. I don’t remember when, but those messages started a while back with another firmware release.
It just means it can’t be reached for some reason. Could be interference, dead, or just a very busy mesh.
Probably not. See my reply for the other potential reasons.
It shouldn’t have. Doing a replace, or even power cycling the switch via an air gap switch or a breaker, could do the trick too.
Mine updated at 2018-12-07 7:01 PM UTC
and I just noticed that my Philips bulbs are no longer responding, Ikea ones seem to be ok.
I haven’t touched this stuff for over a year, apart from pulling the battery to reset a motion sensor which stops working every so often, it’s been relatively stable.
According to the Devices log they stopped responding about about 9am UTC 2018-12-10, or much later than the hub said it updated, but I’m sure the 2 events are related as they have been running fine for so long.
I’m still running them as Kudled and ZLL Dimmer bulb devices. Am I going to have to repair them all? They are model LWB010.
Pulling the air gap on the dimmer resolved my issue.
Thanks for the help!!
1 Like