Zwave is fine. SmartThings is flaky.
Multiple people reporting similar issues right now, unfortunately.
Version
0.24.11
Hub Target
Samsung SmartThings Hub (Hub V2 and Hub V3)
Release Date
US - between Thursday, October 11 at 10:00 am to 9:00 pm EDT
EU - between Thursday, October 11 at 4:00 pm to Friday, 12 October at 3:00 am BST
Release Notes
Local execution support for the Everspring Flood Sensor. See here for more information.
Firmware updates on the following devices. For more information, please see here .
SmartThings Multi and Motion Sensors (2015)
Cree LED Bulb
Other bug fixes and stability improvements.
To troubleshoot, put the devices back on Vivint. If they work fine there, you’ve identified the issue.
One other possibility…you didn’t give the model number for the Remotek. It may not support beaming. SmartThings is finicky about that, so a different model zwave pocket socket might also solve things for you. See the following FAQ (this is a clickable link).
This question comes up a lot. Suppose you have a Z wave lock, but the status doesn’t seem to update or commands don’t always seem to work. Typically someone in the community will recommend that you add another beaming repeater within 10 feet or so of the lock. So the question is why would you need that if the lock is already pretty close to the hub?
The short answer is that the hub is busy, and it takes some load off of it if you have a separate beaming repeater near your lock.
The long answer is in the following thread (this is a clickable link)
Also, since I get asked all the time what’s an inexpensive Zwave plus beaming repeater, for the US hub the Minoston miniplug is often on sale for right around $20. It should not require any custom code, it’s just a very simple one socket on/…
2 Likes
