Hub Firmware Release Notes - OTA - 16.9 - V2


(Bob) #405

After reading this and something in another thread, I decided to power down my hub for 20 mins and power it back up again.
Apparently this causes the zigbee devices to re-associate/rebuild the zigbee network.
I would be interested if someone would confirm/deny this.
Anyway, after doing this things do seem to have quickened up their response times to motion etc.
Well that’s my perception anyway. :slight_smile:


(Joe) #406

Did you update it to the latest firmware from osram?


#407

This is true of any certified zigbee coordinator, which the SmartThings hub is. When you remove the coordinator from the network by powering it off (including removing any batteries) and leave it off for at least 20 minutes while leaving the other certified zigbee devices powered on, the other devices will go into “panic mode” because they can’t find the coordinator.

Then when the coordinator comes back online, each of the other zigbee devices will rebuild their individual neighbor tables.

This was originally intended to let you move an entire network without having to reset each individual device, but it also just cleans up any issues from missing or bad repeaters on a network.

It can take awhile for all of the tables to get rebuilt, so you may not see improvements until the next day.

This process is called a “network heal” in Zigbee.

It will not affect your Z wave devices. For those you have to run the “zwave repair” utility to rebuild the individual device tables.

As I mentioned, this is just part of the zigbee standard, all zigbee home automation devices should work this way.

@tpmanley should be able to say if there’s anything weird about the SmartThings zigbee implementation of a network heal, but I don’t think there is. Many people have been doing a zigbee heal in this manner for the two years that I’ve been in the community. :sunglasses:


(might be my fake name?) #408

No. I don’t have a hub to do that. One thing that I would like to know is if these OTA updates are for official ST devices only, then why are my Lightify strips, and gardenspots, and iris contact sensors being checked daily for firmware?


(Joe) #409

I bought a hub for like 20 bucks and updated all my current ones and first thing I do if I add a new one. I have 10 lights and strips and none have had an issue. Not saying that is the reason for issues. But I was having a few issues here and there which was the reason for the hub and the updates eliminated all issues when they were updated. The other it may check all ZigBee devices but nothing to check against so it will report that but that all it will do is report it check and there is nothing to update but something ST would have to answer definitively.


(might be my fake name?) #410

My issues with the Osram products started when the OTA firmware updates were enabled. The random turn on’s happen at the exact same time that their firmware is checked; according to the Smartthings IDE.

For this reason, I can’t justify buying an Osram hub at this time. I may disable OTA updates to see if this solves my problem.


(Paul Osborne) #411

Hi Eric, this is how ZigBee OTA works (you can find the spec online if you are sufficiently interested). At a high level, the hub advertises itself as an OTA server to all devices. Devices which can act as OTA clients then periodically check with the OTA server for updates.

I’ll see if we have some Lightify strips around (or we’ll get some at our main engineering office) to see if we can reproduce the issue next week. My best guess at present is that there is an issue with the Lightify firmware that we might need to work around or tell them to fix, but we probably can’t say more until we do the engineering work. For now, disabling OTA might make sense.

If you haven’t already, please report the issue to support so they can categorize how widespread the problem is and involve the appropriate users in other communication/test programs down the road.


(Joe) #412

All my osram products have the latest firmware and I had no issues. It might be an issue they already addressed but of course people without a lightify hub they can’t get it.


(might be my fake name?) #413

Ok thanks. Will do!


(Eric) #414

You can get the osram/lightify hubs for $20-$30. You might want to update them that way…


(Carlos) #415

Hi, I got the update, enabled OTA updates Ave noticed that my multi purpose sensor has a target target firmware different than the current (which means I need to update it) how do I do that?

Thank you


(Wayne) #416

If you’ve enabled OTA on the hub then just reseat the battery and preferably leave it close to the hub. Should update within the hour.


(Larry) #417

My lughtify strip and spots are working fine. I’ve got 5 multi sendors. None have updated.
It did check.

Version Published
Zigbee Id
Device Network Id 7429
Status ACTIVE
Hub Nh Hub
Group Family Room
Last Activity At 2016-12-03 11:46 PM EST
Date Created 2015-09-18 3:26 AM EDT
Last Updated 2016-12-01 11:25 AM EST
Data
endpointId: 01
Raw Description 01 0104 0302 00 07 0000 0001 0003 0020 0402 0B05 FC45 02 0003 0019
Firmware
Current Version: 0x10025100
Target Version: 0x10025100
Last Updated: N/A
Last Checked: 2016-12-03 9:56 PM EST
Current States
temperature: 70 F
humidity: 40 %
battery: 56


(Tom Manley) #418

This looks like a Temp/Humidity sensor which doesn’t have a firmware update available yet. If there was an update available the target version would be different than the current version.


(Larry) #419

That is one of your multi sensors, which I thought you said have firmware updates.


(Tom Manley) #420

Can you double check that you’re looking at one of the multi’s? The info you pasted in is definitely a Temp/Humidity sensor. I can tell because of the raw description 01 0104 0302 00 07 0000 0001 0003 0020 0402 0B05 FC45 02 0003 0019. The raw description for a multi sensor should look like this: 01 0104 0402 00 08 0000 0001 0003 0020 0402 0500 0B05 FC02 01 0019.


#421

@tpmanley,

FYI. Ticket #286581 opened for me. I’ve have 11 zigbee devices drop since the firmware update where I needed to manually reset, including a couple Keen vents that I needed to visit twice. All have been GE bulbs, Iris motion sensors, Iris open/close sensors, and Keen vents.

What use to be a very stable zigbee mesh for me has been turned upside down. This is very concerning. Hub version 16.9


Leaksmart Sensors - quit working - 6 of them within 2 hours of each other
(Wayne) #422

I’ve had a complete reversal of fortunes in regards to zigbee for myself. My non smartthings zigbee devices like orvibo seem to have become extremely reliable whilst my smartthings branded ones have become unreliable.


(Lighty) #423

I had issues but I took the advise from support removed the batteries and power for 30 minutes. It all came back to life except some camera’s, which I never got to work yet.


#424

That’s what I’ve done in the past. It’s unfortunate that we have to do that. Things were working so well for such a long time for me until this particular firmware release.