For those who are part of the 0.25.x beta test, we are releasing new firmware:
Version
0.25.18
Hub Targets
Samsung SmartThings Hub (Hub V2)
Samsung SmartThings Hub (Hub V3) (2018)
Release Date
2/15/2019
Release Notes:
Fix a rare scenario where local Z-Wave polling functionality was not enabled
Turn on blue LED earlier on reboot for Hub V2
Fix factory reset functionality for a subset of affected Hub V2s (PGC431-E). Formerly the factory reset process for these hubs would just result in the hub booting with a green LED and no factory reset was occurring
Fix a Hub V2 reboot issue which resulted in unresponsive state with red LED
Even though I’m still on 25.17, I just submitted these 2 bug reports:
BUG-0034 : Can’t change the hub setting “Allow Unsecure Rejoin”
BUG-0035 : Can’t change the hub setting “ZigBee OTA”
Both of these settings were set to enabled, but now they’re disabled and I can’t change them at all. I have no idea when those settings changed, but I didn’t do it.
EDIT: My device polling issue popped up again overnight, but it could be related to another ticket being worked on to get Classic and Connect apps to sync.
The polling issue was related to local devices being polled by the cloud, not the hub. That caused a ton of delay, or you had to tap on the Refresh tile for an update. It went away the last few days.
What I’m seeing now is that the device works fine, like a switch, but the tile won’t update until I move out of the device page back to a Room or Things view, or vise versa. Both in Classic and new apps btw.
This is likely unrelated to this firmware but it does to be somewhat worse so I’ll ask…
I have 3 Schlage Zwave locks that have a varying degree of slowness in reporting their lock status… or so it seems… as when I look in the app it appears to be instantaneous but I often get the “door open / closed” audio alert with an extreme delay. I currently use Echo Speaks for this functionality however I believe this was also happening when I was playing messages using a Sonos.
Also, this always happens when I can’t immediately dig into the logs… Any suggestions on how to troubleshoot this would be appreciated, but if definitely unrelated to this firmware revision, and they take this thread off topic I can glad to start another thread.
The update should have already gone out to everyone this morning. It looks like your hub did update to 25.18 but Graph isn’t displaying the correct version. I’m adding your instance to the ticket we’ve created for the cloud team to investigate this.
Hmmm, I just tested my August lock, and I’m not getting lock/unlock status updates until I tap on refresh, but I can still control the lock. I’ll have to do some more testing today.
(just messing with you)
