Hub disconnect issues

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

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

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.

@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

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…

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.

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…

@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.

HI Tom,

I now have 2 Xiaomi sensors that goes inactive. In between they do not start reporting battery. They were right next to the hub. What can it be. See the log of event. After one hour of no-motion they go inactive, I assume eventually will be declared off-line?
Date Source Type Name Value User Displayed Text
2017-12-10 10:12:37.087 AM GMT
1 hour ago DEVICE motion inactive Extension Motion motion is inactive
2017-12-10 10:10:37.478 AM GMT
1 hour ago DEVICE motion active Extension Motion detected motion
2017-12-10 10:10:37.497 AM GMT
1 hour ago DEVICE lastMotion 2017 Dec 10 Sun 10:10:37 AM Extension Motion last motion is 2017 Dec 10 Sun 10:10:37 AM
2017-12-10 10:10:37.470 AM GMT
1 hour ago DEVICE lastCheckin 2017 Dec 10 Sun 10:10:37 AM Extension Motion last checkin is 2017 Dec 10 Sun 10:10:37 AM
2017-12-10 9:58:45.057 AM GMT
1 hour ago DEVICE motion inactive Extension Motion motion is inactive
2017-12-10 9:56:45.819 AM GMT
1 hour ago DEVICE lastMotion 2017 Dec 10 Sun 9:56:45 AM Extension Motion last motion is 2017 Dec 10 Sun 9:56:45 AM
2017-12-10 9:56:45.794 AM GMT
1 hour ago DEVICE lastCheckin 2017 Dec 10 Sun 9:56:45 AM Extension Motion last checkin is 2017 Dec 10 Sun 9:56:45 AM
2017-12-10 9:56:40.175 AM GMT
1 hour ago DEVICE motion active Extension Motion detected motion

I am also experiencing disconnects and reconnects every 1 minute and I can’t find any method to resolve this.

Grateful for any advice to help stop this problem

I seem to be having the same issues for the last couple of weeks on my V1 hub. I thought it was a bad router or something with my internet and after eliminating those I started looking at the hub…

It connects and disconnects continuously and is driving me nuts. Ive been in the IDE, read the events, rebooted, shut everything off, unplugged everything and currently do not have any idea what to do next.

Do we know what version of firmware I should have for V1? Do I need to open a support ticket?

Thanks in advance for any help.

Hi. I managed to reset my hub (V2) yesterday and so far, all is working fine and no disconnects. Not an ideal fix though as it is hard starting from scratch again

After suffering through that for too long, I can confirm that the hub disconnects have been fixed or at least largely mitigated in the next release of the hub firmware.

1 Like

Did they bump you to the 0.20.11 firmware already as part of the Z-Wave firmware upgrade they performed on your hub the other day?

Yes they did. They also pushed a firmware update to the Z-Wave module. I had to reconnect about 2 dozen Z-devices afterward but I don’t believe that’s directly attributable to the either firmware upgrade.

I believe the loss of devices was more due to the very frequent power cycling that had been happening for days as well as the ST the cloud outage last week.

The update is impressive in terms of performance anyhow. One of the more significant I’ve seen so far.

Z-Wave devices respond faster than they ever have. I have also completed upgrading firmware on all 44 Iris SmartPlugs too. That was a long process as each had to be paired with Iris and left overnight but the result is the Z-Wave repeaters in these pair more reliably than before and stay connected afterward.

1 Like

Looks like having my V1hub unplugged for a day did the trick for me. I also think that I had a device on the network creating an unstable situation that was handled when I took everything offline and began adding one by one.

Not sure what was creating the havoc but at least my hub is stable.

My Hub(v2.0) has been disconnecting several times a day for the last several days. I think it started on Thursday 1/25. Is anyone else having an issue?

Dave

I am having the same on my V1 hub.I also have problem pairing again all my 4 fibaro door/window sensors.
FYI: European V1 kickstarter backed hub 868MHz

The firmware update caused some kind of communication issue with my
router…I rebooted it and have not had an issue.

Dave

Agree with David. Rebooting with the hub utility certainly quieted things down. Been getting lots of disconnect messages and losing connections with z wave devices ever since setting up my hub last week. After the reboot, all is well. Using a v2 hub.