Hub Firmware Release Notes 08/15/16 (Hub V2) - 15.3

[N8XD (I got a hair cut from Alexa)]

I have 7 or 8 zigbee temperature sensors…2 of them went flaky a few weeks ago, I was just getting ready to replace them…but they magically work now after this update.

[AVGeek66 (Steve)]

My hub goes “inactive” every 10 minutes after a Hard Boot. You can ping it but it is inactive

[Aaron (Aaron S)]

We are looking into reports of reboots with the 15.3 firmware update. If you are having an issue, please submit a ticket so we can pull the logs and track down the issue.

[bamarayne (Jason "The Enabler" as deemed so by @Smart)]

Ticket submitted.

[jcalex22 (John Alex)]

I have the same hub disconnect issues since the new firmware update, as well.

I have tried the soft reboot (red button) & hard reboot (removing batteries, Ethernet and power cables for 15 minutes and still it disconnects and remains unresponsive until another reboot. Very disappointing, but at least someone else is experiencing the same issues, so I don’t feel alone.
There is my logs for those that can make any sense of it: Whether it is an internet connectivity issue or something else it has happened since this last update. Once rebooted it works like a champ until disconnecting with all my 84 devices. FYI.

Date Source Type Name Value User Displayed Text
2016-08-17 8:35:52.718 AM PDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:b… devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:52.711 AM PDT
moments ago HUB ssdpTerm uuid:2f402f80-da50-11e1-9b23-… devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:52.703 AM PDT
moments ago HUB ssdpTerm upnp:rootdevice devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:52.039 AM PDT
moments ago HUB ssdpTerm uuid:2f402f80-da50-11e1-9b23-… devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:52.035 AM PDT
moments ago HUB ssdpTerm upnp:rootdevice devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:52.032 AM PDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:b… devicetype:04, mac:00178819E995, networkAddress:C0A8018F, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpU…
2016-08-17 8:35:21.213 AM PDT
moments ago HUB hub has disconnected hub has disconnected hub has disconnected
2016-08-17 8:34:22.243 AM PDT
moments ago HUB hubInfo hardwareID:000D, version:9, m… hardwareID:000D, version:9, mac:D0:52:A8:A6:5B:75, localip:192.168.1.121, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa…
2016-08-17 8:34:22.238 AM PDT
moments ago HUB ENTITY_UPDATE HubUpdated
2016-08-17 8:34:21.669 AM PDT
moments ago HUB hubInfo hardwareID:000D, version:9, m… hardwareID:000D, version:9, mac:D0:52:A8:A6:5B:75, localip:192.168.1.121, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa…
2016-08-17 8:34:21.664 AM PDT
moments ago HUB ENTITY_UPDATE HubUpdated
2016-08-17 8:34:20.367 AM PDT
moments ago HUB ping ping ping
2016-08-17 8:34:19.090 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.943 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.943 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.943 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.943 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.936 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.934 AM PDT
moments ago HUB register register register
2016-08-17 8:34:18.934 AM PDT
moments ago HUB register register register
2016-08-17 8:33:30.031 AM PDT
moments ago HUB ping ping ping
2016-08-17 8:32:44.209 AM PDT
moments ago HUB hub has disconnected hub has disconnected hub has disconnected
2016-08-17 8:31:46.109 AM PDT
moments ago HUB hubInfo hardwareID:000D, version:9, m… hardwareID:000D, version:9, mac:D0:52:A8:A6:5B:75, localip:192.168.1.121, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa…
2016-08-17 8:31:46.103 AM PDT
moments ago HUB ENTITY_UPDATE HubUpdated
2016-08-17 8:31:44.642 AM PDT
moments ago HUB hubInfo hardwareID:000D, version:9, m… hardwareID:000D, version:9, mac:D0:52:A8:A6:5B:75, localip:192.168.1.121, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWMa…
2016-08-17 8:31:44.637 AM PDT
moments ago HUB ENTITY_UPDATE HubUpdated
2016-08-17 8:31:43.356 AM PDT
moments ago HUB ping ping ping
2016-08-17 8:31:42.114 AM PDT
moments ago HUB register register register

[robertn78 (Robert Nuno)]

I looked mine up in the web management.
graph.api.smartthings.com

Mine says 15.3 under my hubs.

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@SBDOBRESCU

The bulbs are deemed ‘unreachable’ by Hue, it’s a Hue problem.

My “unreachable” bulbs work justfinethankyouverymuch.

It’s a bogus status, and my V1 Hub has no problems controlling all my Hue and GE Link … except not reporting their dim levels.

[JDRoberts]

It’s not a bogus status. The bulbs are not reporting back to the bridge. They may still accept a command sent to them, but not responding is a real issue for some use cases. If only because you can’t get the status in the app.

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@JDRoberts

The bulbs are not reporting back to the bridge. They may still accept a command sent to them, but not responding is a real issue for some use cases.

Sure… but from what I’ve heard, prior to this update, V2 handled this in a “fail-safe” manner and now doesn’t. I don’t know the details; but if true, that is a deprecation of functionality that would really p**s me off.

So I’m fine with my Hub V1 for now; even if … or maybe because, I have defective GE Link bulbs that it is able to control.

[Dlee]

I have certain smatapps and routines that execute but fail to turn on lights or lock locks. Manual control of same ZigBee and zwave devices still work.

Started after hub update AFAICT. Examples, Goodbye executes successfully and changes mode, but locks didn’t lock. Some local smartapps trigger with motion but light doesn’t actually turn on. Seems to be execution fail. Hub reboot and zwave repair no help.

[Bryan_Fleming]

@Aaron

We are looking into reports of reboots with the 15.3 firmware update. If you are having an issue, please submit a ticket so we can pull the logs and track down the issue.

Ticket submitted - I’m experiencing 1-2 reboots per hour currently.

[a4refillpad (Wayne)]

Omg. I thought my stability was bad before. I’m getting dozens of frozen zigbee devices that need repeated resetting to bring back online now. Absolutely crud.

[Jimxenus]

@a4refillpad

Omg. I thought my stability was bad before. I’m getting dozens of frozen zigbee devices that need repeated resetting to bring back online now. Absolutely crud.

Same thing is happening to me. It seems to affect only Zigbee devices.

[SBDOBRESCU (Bobby)]

Update: it seems like the ‘unreachable’ issue has been corrected. All my automations involving the GE bulbs are running fine tonight. Very interesting to say the least…

This one bulb that caught my attention because wasn’t taking any actions on Monday night, is now following ST automation. Strange, but I am happy…

[whoismoses (Eric)]

I’ve noticed that all of the exceptions in my logs have an @ line number at the end. This used to happen occasionally, if I was lucky. Now I see them all the time. Is this new or was I just missing them before? I seem to remember wishing the exception always included the line number.

[vlad]

There was a bug that caused line numbers to not appear - this was fixed with a recent cloud deployment. You can also now log an exception which will print out the line number where it occurred (Was requested on the dev Slack)

See: http://docs.smartthings.com/en/latest/tools-and-ide/logging.html#logging-exceptions

[U3gRJLfQiF9C (ecksomperudenlign)]

Anybody encountered this problem after the update? Or any suggestion of fixing this? Thanks.

D-Links cameras stopped working after last week Hub update

Hi, All 4 of my D-Link cameras stopped working in SmartThings after last week Hub update. It is showing “Inactive” in all of them since the Hub upgrade. Removed all the cameras from SmartThings Hub Restarted my wifi router Restart the SmartThings Hub by pressing the red button Reset 1 D-Link camera to the factory default Connect that camera to the router by using a wired connection with factory settings Use SmartThings Hub to add that camera. Multi phones still exhibited the same problem. I had already reached out to the support and I am not sure how bad is the backlog nowadays. Hopefully I can get faster help from community than support as always. Thanks

[kippers]

Similar issue for me. Any recent improvements for you @Dlee ?

[Dlee]

@kippers

Similar issue for me. Any recent improvements for you @Dlee ?

I figured out the official Enhanced Auto lock door smartapp was broken and unlocking 2 of 4 z-wave locks after the hub update. Device status issue I think since that app forces you to use the unlock when open function. Setting unlock when open timer timer to 9999 didn’t prevent from unlocking after Goodnight or Goodbye routines locked up even though the zigbee smart sense multis reported status as closed. The other two locks not using SS Multi sensors for open/close did not have this bug.

Switching to the old “Lock it after awhile” smartapp fixed my locks problem. But still have fail issues and delays with lights attached to certain zigbee motion sensors.

[David_Steele]

My hub went INACTIVE as well on August 15th. I’ve been out of town so only noticed it a couple of days ago. After trying various things, I finally contacted support today. They ultimately asked me to temporarily unplug my Phillips Hue bridge - and suddenly my SmartThings Hub came fully back online.

They said:

“There’s a Hue Bridge connected to your SmartThings. While normally that is not a problem, our engineers have identified that as the cause of Hubs unable to connect. Try disconnecting the Hue bridge from your network briefly, and see if your Hub comes back online. If that fixes it, then we’ll let you know the moment our engineering team has this resolved and the Bridge can be used again in SmartThings.
I see lots of Hue bulbs on your account, and I understand the disconnect is frustrating. Please bear with us as we work to fix the Hue integration. I am very sorry for the breakage.”

When I responded back asking for an ETA on the fix, I was told:

“We do not currently have an ETA on a fix for the Hue Bridge issue, however it is one of our top priorities so it should be resolved soon. We have gone ahead and attached your support request to the open ticket we have investigating this and will follow up with you once we’ve confirmed it has been resolved. Thank you for your patience.”

Just wanted to share here in case someone else has the same issue…