Hub Firmware Release Notes - OTA - 16.9 - V2

Could well be just this. The outside temperature might be affecting the efficiency of the coin cell. I was getting a huge number of false alarms on my mailbox sensor until I replaced the battery. I initially thought it was a spider or some other insect until I replaced the battery.


What is a healthCheck()?

I do not think I have ever seen SmartThings provide notification if a device is not responding.

If a battery powered sensor goes completely offline, battery dead or whatever, does SmartThings provide any feedback?

Yes, I know there are community authored apps for this, but what is this SmartThings authored healthcheck() function?

1 Like


Thanks, that explains stuff. I am comparing my graph/ide to this explanation and see those statuses.

And look one of my osram garden spots has gone AWOL, offline!


My kitchen motion sensor seemed to be stuck for hours in motion so I finally replaced the battery with another brand new one though it was showing 89%

Now misfires are back in full on misbehaviour

Is anyone interested in ST motion sensors in the UK? I am about to rip them all out and replace them with Fibaro sensors - might even switch to the complete system thinking about it as I am tired of these issues and ST not getting a handle on them. If you are intereted in sensors please PM me.

@r4nd0m What brand batteries are you using? At present, this (combined with the 5-minute reports) is still the best theory we have on why this is happening for some users.

To add some more meat to this, here are some facts based on details of the hardware and observations we have made:

  1. (Observation) When the battery has been exhausted somewhat, there is a period when the battery will have sufficient voltage to power the radio (and communicate) but there is a power drop to the PIR sensor. With a low battery, I can often cause a motion event by doing a “refresh” on the sensor. We still need to scope the voltage to the PIR during this to confirm what is going on for certain.
  2. (Fact) A peak current event like a transmission on the Zigbee radio can cause a drop in the output voltage for the device.
  3. (Fact) When the PIR sensor is powered on it may need up to 200s to “stabilize” (figure out baseline infrared levels, etc.) and during this time it may “falsely” trigger multiple times.

@tpmanley and other team members have been discussing different ideas for how we might address this problem. I do think that there is something different with your batteries as compared to most users that is exacerbating this issue. In addition, the multiple false motion triggers will, of course, drain the battery even faster.

I, of course, cannot guarantee that this is what is affecting you but based on the information you have provided and our own observations it seems like a plausible match. We are continuing to do some research to confirm a few parts of our root cause analysis.


Thanks for the information @posborne. What would be great is a way for us to enable/disable or at the very least adjust the health check interval. This should give us a bit of a respite from the false alarms we’re getting. I have been able to confirm for some time now that all of my false alarms occur at or just after a 5minute report.

Just for completeness I was using the recommended Panasonic ones the sensors come with one fresh out of a spare sensor the other out of the package …

Sensors are now removed and sold and will be replaced by Fibaro sensors which I have working in some areas already which never gave me any issues … which in fact leads to everything ST has been removed and replaced with other available options except the hub …

Offline online feature already active via IDE.

Evergreen batteries I got from battery source fit perfect. I can’t comprehend the size difference for the same type of battery. It’s would be like some AA batteries are shorter then others.

My sensors are sold mate, wont be an issue for me from here onwards the replacements are working perfectly fine in other areas of the house already and I expect the true replacements any minute thanks to amazon prime so I dont expect any trouble here to be honest …

Some good information here unfortunately when I logged a case I wasnt told any of this but people wanted to do ‘tests’ or implement changes I didnt see as a valid solution while my sensors were going off lighting the kitchen and hall way all the time and potentially triggering alarms in my absence if I hadnt disabled the alarms …
So easy but expensive fix for me was to move to Fibaro sensors thats I use in other areas already where I wanted lux measures in addition …

All in all it seems that your pre-prod testing might be too short and you may want an option for people to allow beta code to be adapted rather than pushing it to the masses and then seeing all the complaints in the forum … my system was stable for months which was a relief for a change prior to the recent changes - and I believe I have seen this comment multiple times before …

Dont test on customer site unless the customer agrees or is aware of potential issues with the option to revert back to last known good state - cant be too difficult to support 2 hub versions or even 3 - current/previous/beta …


I have been having various issues documented at this link and hopefully fixed as per this link
In summary - was having issues with a multi-purpose sensor, which led me to reset zigmee mesh, which screwed everything up, which led me to factory reset hub, after which reset sensors would not get discovered and then finally fixed as per procedure in above links.

Some points to note - I have a case open with support on checkinterval going from 720 to 7260 seconds for certain sensors which then leads to them being stuck in open/close/active/inactive and eventually going offline. Support was not very helpful on this and had no idea on checkinterval issues. After the firmware update these issues probably worsened which led me to resets. etc detailed in my links above. The offending sensors shipped with LIXING batteries, however switching to panasonic after the issues has not helped. Putting lixing batteries into working sensors screwed them up as well. However now after the full reset and rebuild, things seem fine. Did have an osram led bulb in my network, which I got rid off before the rebuild!

1 Like

new user here… enabled OTA and all my zigbee sensors weren’t working correctly (motion sensors not detecting motion, light bulbs not responding)

disabled OTA and all seems to be fine again… guess i’ll leave it off… if it works, don’t fix it eh…

They won’t work while they are updating.

I have had ST replace a motion sensor that went faulty after this upgrade.
All has been working well but reading the reports in this thread I decided to disable OTA to see what would happen.
Oh dear. Since then the new motion sensor has either shown permanent motion or fails to detect motion.
I have tried resetting the sensor numerous times.
I have just reset again and enabled OTA to see how things go now.
Happy days. :smile:

Well hmmm… I have also disabled OTA per the suggestions and am continuing to have all my ST ZigBee devices get “stuck” reporting. I haven’t tried re-enabling OTA as I was getting so many false positives that way.

However last night was a real doozy. We had multiple false positives that the lights in the house made it look like a disco and the garage door kept sending SMS texts.

With the fact that the z-wave devices have started acting flaky now as well, I’m at a loss of how to salvage the hub. Even when the timer was sooo broken and states were being lost the hub was still a bit useful as it would still control local activities. This is beyond what anyone is willing to put up with.

It isn’t all just batteries. I have several screw in light bulbs that are ZigBee that quit responding as well.

In my ST motion sensors, of which 10 very routinely get “stuck” or give false positives, the batteries are all what came with the ST device. It isn’t only those 10 devices that are having problems they are just the most troublesome. The other 10 or so ST motion sensors will occasionally give a false positive or get stuck but only about once every 2 days as opposed to every few hours.

I have noticed that when I set the mode to good night, it will trigger a false positive from 3 sensors every single time. Those are the tilt sensor on the garage, and two of my bathroom motion sensors. I haven’t actually put a stop watch to it, but it appears to be 1-2 minutes after the mode change that it triggers the sensor…

1 Like

Wonder why this is isolated.

1 Like

Oh well.
The ‘new’ ST motion sensor supplied by ST to replace my dead one is now dead as well.
I have tried changing the battery, removing it, re-associating etc. etc. and it is now a paperweight.
I did vow never to buy any of these again 9 months ago when I had issues but I relented as a newer version came out. Oh how wrong I was.
Top of my list for motion sensors is the Phillips Hue. Does Motion/Lux/Temp. Same dimensions as the ST.
2nd is the golf ball. The Fibaro Motion/Lux/Temp sensor.
Followed by the Orvibo. Works OK but I do not like the look of it. Just me.
I will not bother to contact support with the dead motion sensor as I do not want another one. Just put it down to experience.

It might be bigger than reported here on the forum to be fair - to me it almost looks like its the same people on the forum all the time with hardly new ones …