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

  • Fixed a memory leak that was causing some user’s hubs to reboot
  • Fixed a problem causing the LED not to blink when hub was powered on when not connected to Ethernet
  • Fixed a bug causing lighting automations to slow down when the hub is not connected to the Internet
  • Changes in status of devices connected to Hue hubs will be retreived much more quickly
  • The current version of firmware on ZigBee devices is now shown on the device details page in

Brilliant. Anyone verify this yet?

PS: This update feels like a good one towards stability and reliability.


How much more quickly are we talking about? Cause five minutes is an eternity… So is ten seconds… J/s

Just did, I had to check twice if I really disconnected the ethernet! Great work guys!

And if the memory leak fixed my occasional reboot, these two alone are really BIG improvements…


I presume this is an enhancement just to the DTH embedded in the firmware?

Is the DTH code the same for cloud executed Hue Bulbs / Hue Connect?

Nope. Has to do specifically with firmware improvements themselves. The hue code doesn’t live on the hub.

1 Like

So, what kind of a difference should we see? Right now I have automations compensation for that issue and it gives me almost instant updates.

I just got home and tested this… My hue bulbs, triggered with motion, updated in the app almost instant. Definitely under a second. Great job!


Ah! Well… does this imply that the V1 Hub may still have an unfixed bug or missing feature that results in degraded functionality with Hue Bridges?

It sounds like a few of you are excited but to me it doesn’t look like much of an update if that is all that was in there. How frequent are tubes updates? This seems like the kind of stuff that should come out every two weeks.

My hub seems ok except not reporting the firmware version.

Quality software takes time. I’m ok waiting. Updates used to be slightly faster and more surprising (not the good kind of surprise necessarily). :slight_smile:


I work in the software world. We do frequent releases for several apps. Sometimes bi weekly sometimes monthly. I’m not saying they are the same complexity as ST. However to me this seems like a featureless update and the only thing I got out of it was a 1-2 hours of outage / instability.

Just wondering how often these updates go in.

I guess I wish they would charge a monthly fee so I know that they will have a large enough team and they will also be here tomorrow.

1 Like

Cloud software running thousands of homes in production? I work with cloud software. Breaking stuff in production has never been so easy… :grimacing:

Sometimes updates only address sets of users or lay groundwork for the future. This is a good thing IMHO.

1 Like

Actually, cloud makes it easier. The hub here causes issues. is one of the largest SaaS and PaaS providers and they do weekly updates in a lot of cases.

Easier to fix and easier to break. I’m all too familiar with SF. They have practically unlimited resources. Ask me how I know. :wink:

1 Like

ST must be monitoring this thread. My system is down again. Great update!

Different system sold for a different purpose. Since every SmartThings update takes the hub off-line for some period of time, and the customer cannot postpone them, frequent updates are not a great idea for system sold for security monitoring. It would be even worse if they were scheduled, so that the entire world knew that every Monday morning the system would be off-line. :scream:

Just sayin’… :wink:


My point is if they are this infrequent maybe they should be more meaningful.

Actually, I found this to be very meaningful. To finally update the system so that Phillips Hub connected devices update status almost instant instead of every 5 minutes means a lot.

I have a piston that used 12 motion sensors. Every time one of those sensors goes active it ran a refresh on 5 devices in my home. 3 of those devices triggered a status update from the Phillips bridge, which in turn cause 27 devices in my home to be polled and updated. So, for every motion sensor going active there was the traffic of 32 devices being polled. That occurred literally hundreds of times a day.

That one piston creates a massive amount of traffic on my system. But, it was necessary for my system to be responsive.

Now, that piston will only update 2 GE smart switches (I use physical press on those two).

Then, when the internet goes down I have a lot of local running automations that ran like crap. Now, that is supposed to be fixed.

What I see from this update is a faster, more responsive, and more stable system within my home. I’m sure I’m not the only one.

So, as @JDRoberts is fond of saying… “Your use case may not necessarily be another’s use case”.


How much more quickly are we talking about? Cause five minutes is an eternity… So is ten seconds… J/s

With this release, the hub firmware will poll the hue bridge for changes once every ~2 seconds, so you should see updates (round trip to the cloud/mobile app) in the 0 - 5 second range typically (depending on when the last poll was and other latencies on the ST and hue side of things). To test this, you can pull up the hue app and live logging on Graph and change settings on the hue side. You should events in graph in that time window.