Further re-enforcing my much earlier statement that communication is hard, the wrong set of change notes went out with the notification email again. The differences aren’t super significant, but we did want to provide some more detail up front. These are the notes that should have gone out:
Faster boot times and local automations
Increased reliability and performance for Zigbee devices
Fix for problem with some Schlage Z-Wave locks not reporting lock status
Firmware updates for some SmartThings sensors and outlets, Sengled Classic bulbs, Iris sensors and the Halo smoke alarm
Actually the two sets of changes are completely independent of each other, so the decision was made to avoid downtime events on multiple days for people.
I can’t exclude you from the cloud downtime, but we are not planning to update beta users (those on 18.20) during the Thursday release.
Beta users on 18.20 have the same Hub firmware as 18.21, but have the newer version of the ZigBee radio firmware with an extra change recommended by the radio manufacturer. In the end, our confidence wasn’t high enough to use the new ZigBee firmware + patch in production, but keeping that firmware on beta allows us to work with the community members to eventually get to true root cause.
Theories, but nothing I would call conclusive yet. On our side we’ve worked to try and get a clear set of steps to reproduce the issue, and that’s been difficult too since this occurs at an extremely low rate.
At this point everyone should have been notified of the update via email.
My only notification was following this thread. And I know my e-mail address is correct as I received all the notifications about the 17.12 update. Also, I have checked my e-mail and spam folders and I have received nothing. Who do I check with to find out why I am not getting notifications?
I’m so glad I had the wisdom to disable OTA updates for ZigBee devices right before leaving on holidays for the last 3 weeks. Will make sure to follow this practice from now on. If only I could do the same for the hub’s firmware updates…
It looks like a different (not correct) method was used for pulling emails to notify of this release and they may not have been sent to people that unsubscribed to marketing emails (which is fine). We’re looking to determine who might not have received notification that should have and get that notification sent to that subset of people.