Hub disconnect issues


(Steve) #1

Anyone else having issues with notifications that your hub is disconnected? I’ve been getting them frequently, followed by another saying it is active again (sometimes within a minute or so of each other). But it is not really disconnected, as I can still use controls, routines still run (mostly) and my internet is not down. Very frustrating throughout the night. Just another ST “bonus”, or is the issue fixable?


(Steve White) #2

Check your event logs in the IDE and see if your hub it actually rebooting. It likely is, there are a few of us experiencing the issue right now. If it is, you’ll see the hub disconnect message followed by some other messages like zb_radio_on and zw_radio_on

I can consistently crash my hub by running the Goodnight routine.


(Tom Manley) #3

Thanks for report. We are actively investigating this problem but please contact support if you haven’t already to we can make sure we understand your particular situation.

Also you should now be able to tell the difference between full hub reboot and a reconnection by looking at Last Booted in graph. This replaced Uptime which was very confusing because it wasn’t updated as frequently as you’d expect. If you still see Uptime then you just need to reboot your hub once or wait for it to reconnect on its own.


Hub Firmware Release Notes - 19.17
#4

Yes I’ve been experiencing the same with one of the three Samsung Connect hubs that I just installed. For the meanwhile I temporarily disabled the ST hub feature (and have 3 other ST hubs that are active.)


#5

@tpmanley:

Support request #452193 emailed in just now. I caught this hub disconnect issue at 2:30’ish today, along with many of these for quite some time:

image

image


(Tom Manley) #6

In case you missed it, there will be a release on Monday that fixes some of the things that have been causing the largest number of hub disconnects.


(Steve White) #7

There is no mention of hub disconnects in the announcement.

Fix frequent disconnects for users with an offline Hue bridge
Fix disconnect issues for some users with video cameras

It would be outstanding if this were fixed in todays release! My hub crashed twice last night trying to run the Goodnight scene; it took almost 10 minutes to get all of the night actions to complete correctly.


(Tom Manley) #8

I guess we could have been more clear with those release notes but the disconnects mentioned are the hub disconnecting from the cloud. We have looked at your hub and hope that this does clear up the problems you’re seeing but if it doesn’t please let us know and we’ll keep digging.


(Steve White) #9

Thank you!! I’m eagerly awaiting the update. I’ll be able to test it tonight since the Goodnight routine reliably kills the hub just about every night.


(Steve White) #10

A side note: My hub was updated about 10 minutes ago, Fingers crossed! Thanks to everyone involved!


(Steve) #11

It does not. Hub went inactive Mon am 3:56 and active 4:15 am prior to update. Was updated Mon. Went inactive Tue 4:20 am and active 4:56 am. During this “inactive” period, I was able to trigger devices normally (both local and cloud based). Thought I would let you know, now that I am awake. On a side note, how about giving us the azbility to disable this specific notification, if the actual issue cannot be resolved…


(Steve White) #12

The tech gods giveth, and the tech gods taketh…

Hub crashes seem to be fixed in this release. That’s good!

Z-Wave seems to have reverted back to a steaming pile of dung. It took a solid 5 minutes to get the Goodnight routine to control all devices due to numerous Z-Wave power cycle events.

I see 16 Z-wave reboot events over the past 4 hours in the event logs!!!


(Steve) #13

And another disconnect/connect at 7:35/7:36. Obviously, the issue remains.


(Steve) #14

Yet another at 6:17/6:18 pm. Will stop repeating myself now. The “fix” seems to have made these episodes even more frequent.


(Steve White) #15

It just took me 14 minutes to complete the Good Night routine due to 7 Z-Wave power cycle events and a hub crash.

Sorry to report the hub crashing is not fixed and Z-wave is back to being broken to the point where it’s almost unusable.

I’m afraid I am going to have to consider other home automation systems. At this point the Z-Wave stack is horribly broken on SmartThings and I doubt they’ll be able to fix it.

Edit: After testing, I can confirm that my system is unable to run even the most basic routine or automation as Z-wave reboots and/or the hub crashes. I’m now forced to go room by room and make sure devices switched, doors locked, etc.


(Steve White) #16

@tpmanley, My hub is basically turned into Swiss cheese with this update. I would really like to have it rolled back to 19.17 as 19.19 made it worse. 16 Z-Wave power cycle events and numerous hub “crashes” with the Zigbee & Z-wave radios turning on. Here’s a synopsis of major events over the past 12 hours. Not every reboot or crash is shown below.

After running Goodbye this morning (after presence detection failed and left the house unlocked for hours):

2017-12-06 10:51:28.069 AM EST
moments ago	HUB		hubStatus	zw_radio_on		
2017-12-06 10:51:28.065 AM EST
moments ago	HUB		hubStatus	zb_radio_on		

After running Goodnight last night:

2017-12-06 1:10:03.600 AM EST
10 hours ago	HUB		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:04, mac:4C72B9F8B735, h...		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 1:08:11.695 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:08:07.573 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 1:07:42.982 AM EST
10 hours ago	HUB		ping	ping		ping
2017-12-06 1:07:40.078 AM EST
10 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:58a6cdfd-cbd0-48f1-bd85-594d3aa29f4a,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:58a6cdfd-cbd0-48f1-bd85-594d3aa29f4a, headers:SFRUUC8xLjEgMjAwIE...
2017-12-06 1:07:35.900 AM EST
10 hours ago	HUB		ping	ping		ping
2017-12-06 1:07:05.654 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:07:01.610 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 1:06:53.769 AM EST
10 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:a7cff8ac-6c51-4571-88c7-09ecd07a69cc,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:a7cff8ac-6c51-4571-88c7-09ecd07a69cc, headers:SFRUUC8xLjEgMjAwIE...
2017-12-06 1:06:43.749 AM EST
10 hours ago	HUB		hubStatus	zw_radio_on		
2017-12-06 1:06:43.745 AM EST
10 hours ago	HUB		hubStatus	zb_radio_on		
2017-12-06 1:06:43.741 AM EST
10 hours ago	HUB		hubInfo	hardwareID:000D, version:14, ...		hardwareID:000D, version:14, mac:D0:52:A8:91:0D:6C, localip:192.168.7.30, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa...
2017-12-06 1:06:24.484 AM EST
10 hours ago	HUB		ping	ping		ping
2017-12-06 1:06:01.731 AM EST
10 hours ago	HUB		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:01, mac:4C72B9F8B735, h...		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 1:04:53.792 AM EST
10 hours ago	HUB		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:01, mac:4C72B9F8B735, h...		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 1:03:53.508 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:03:49.472 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 1:03:36.071 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:03:31.986 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 1:03:13.440 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:03:09.420 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 1:02:49.883 AM EST
10 hours ago	HUB		ping	ping		ping
2017-12-06 1:01:11.605 AM EST
10 hours ago	HUB		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:05, mac:4C72B9F8B735, h...		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 1:00:37.634 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 1:00:33.648 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 12:59:37.638 AM EST
10 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-06 12:59:33.519 AM EST
10 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-06 12:57:49.622 AM EST
10 hours ago	HUB		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:01, mac:4C72B9F8B735, h...		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 12:57:47.573 AM EST
10 hours ago	HUB		ping	ping		ping

More evidence of the hub “crashing”

2017-12-06 12:18:51.641 AM EST
11 hours ago	HUB		index:02, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:02, mac:4C72B9F8B735, h...		index:02, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-06 12:17:42.099 AM EST
11 hours ago	HUB		hubStatus	zw_radio_on		
2017-12-06 12:17:42.095 AM EST
11 hours ago	HUB		hubStatus	zb_radio_on		
2017-12-06 12:17:42.092 AM EST
11 hours ago	HUB		hubInfo	hardwareID:000D, version:14, ...		hardwareID:000D, version:14, mac:D0:52:A8:91:0D:6C, localip:192.168.7.30, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa...
2017-12-06 12:17:31.629 AM EST
11 hours ago	HUB		ping	ping		ping

Random instability not attributed to a specific device:

2017-12-05 11:07:03.829 PM EST
12 hours ago	HUB		ping	ping		ping
2017-12-05 11:06:17.991 PM EST
12 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-05 11:06:13.932 PM EST
12 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-05 11:04:59.913 PM EST
12 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-05 11:04:56.026 PM EST
12 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-05 11:03:30.119 PM EST
12 hours ago	HUB		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:05, mac:4C72B9F8B735, h...		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-12-05 11:02:01.928 PM EST
12 hours ago	HUB		ping	ping		ping
2017-12-05 11:00:37.913 PM EST
12 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-05 11:00:34.150 PM EST
12 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-12-05 10:59:37.789 PM EST
12 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-12-05 10:59:33.966 PM EST
12 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started

(Lourenss) #17

I have not been able to get my Zigbee or Xiaomi motion sensors to work consistently since the new firmware. I did reset my hub as my son couldn’t log on as another user through his own Samsung account. Now it’s all gone to pot. I reset all the sensors a few times. At first the Xiaomi worked then went off line after a few hours. Since resetting again it’s not working at all. I am using code from github. The Zigbee sensor never worked other than reporting temp.

What the…


(Tom Manley) #18

Make sure you’re joining the Xiaomi sensors close to the hub and leaving them there until they start reporting battery. Once it starts joining reporting battery you should be able to move it to where you want it. If you still have issues I suggest bringing it up in one of the Xiaomi threads like [RELEASE] Xiaomi Sensors and Button (beta) since it’s likely not related to the firmware release or hub disconnect issues.

I think by Zigbee motion you’re talking about a SmartSense Motion Sensor. Sounds like you’ve repaired that a few times and it’s still not working so I’d definitely suggest contacting support.


Will the Samsung Connect Hub get a firmware upgrade?
(Lourenss) #19

thanks I tried placing the sensors right by the hub reset a few times, they didnt start reporting battery or motion for that matter. I did see illumination counts in the event log, but that’s it for Xiaomi…


(Alwas) #20

@tpmanley has all the feedback regarding 19.19 made you guys start to ask the question of a firmware rollback back yet or are you going to persevere with this one? I’ve been looking at a blue light for most of the day now.