For those who are part of the 0.25.x beta test, we are releasing new firmware:
Version
0.25.19
Hub Targets
Samsung SmartThings Hub (Hub V2)
Samsung SmartThings Hub (Hub V3) (2018)
Release Date
2/22/2019
Release Notes:
Fix: Z-Wave sleepy devices were not being assigned a default wake up interval at join time. If you have added a sleepy device in the beta, the device was most likely not assigned a default wake up interval by the hub firmware at join time, however many DTHs do set the wake up interval in the configuration. The symptom of this issue is that the device may appear offline while reporting the events properly. Our suggestion would be that if you have added a sleepy Z-Wave device (i.e. sensors) during the beta, you should exclude the device and add the device again to ensure that there is a wake up interval set.
Fixed issues with Zigbee configuration persistence that manifested itself by setting the insecure rejoin and OTA configurations to default values.
if anybody else is using the new app, did you have to reboot the hub after the update to get devices to load their status? I had to do this with the first 25.X update and now this one.
I don’t think that’s a beta issue. I’m not on the beta (just enjoy following the conversation), but I had something similar happen today and yesterday when configuring smartapps in the classic app. Usually, I can wait a few seconds and try again and it works, assuming your issue is the same as mine.
Yup, just checking. Adding a bunch of GE Zigbee Switches right now, and it’s annoying.
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
11
Something I’ve been noticing for the past few weeks. The platform tends to run slow on weekend and times out a lot. Our mailboxes fill up on the weekend questions from users related to errors saving SmartApps, slow responses etc and things fix themselves on Monday.
I was removing device ID 7C and eventually 6F. It did both, but then that’s when I noticed 3 devices instead of 2 were gone from my list, and then within less than a minute, a new device popped up called “Z-Wave Switch” (I’ve seen that odd behavior a while back if I remember right)
No matter what I do I’m not able to add that zwave switch back (that my removed on it own), It tries, and it will join, but it’s not controllable.
Something is really odd with joining this zwave device. Like I said above, it was working fine until the hub decided to remove it, and now it won’t add it back correctly.
Could this be related to the fix in the release note, and something not working right?
Based on the radio logs, 4C is failing to receive any message from the hub. The join method went fine, the radio is failing to get an acknowledgement from the device that the message sent to it was received.
I wonder if some message corrupted over the air that something became 3F… But that would require us the checksum to pass which can happen but we have seen this very rarely.
