This is one of the built-in problems with an asynchronous design. Interestingly, in some cases turning something on that you think is already on is harmless. In other cases not so good. So with ST if the state of a device is lost for a moment, things depending on that state being correct will fail.
It is possible to work around some of this with custom apps, but not all of it. Some of this behavior is intrinsic to the architecture of ST even when it is working properly. Toss in some ST server / comms issue, and itās gonna fail.
Guys if you do improve upon the code do let us know, For now the code is working. I have incorporated in Binder for dual relay and virtual switches and the relay (1 & 2) are able to stay in sync.
Just one problem though. I am not able to catch the event for physical throw of switch, I do not know if the switch is generating it, it should. Noting in
def parse(String description) {
log.debug "Parsing desc => '${description}'"
def result = null
def cmd = zwave.parse(description, [0x60:3, 0x25:1, 0x32:1, 0x70:1])
log.debug cmd
if (cmd) {
result = createEvent(zwaveEvent(cmd))
}
log.debug "Parsing result => '${result}'"
return result
I just installed a Linear WS15Z wall switch and a Linear WT00Z accessory switch.
I was planning to use Big Switch so the WT00Z controlled the WS15Z via ST per JDRobertsā suggestion.
However, Big Switch is no longer on the list of Officially Published Apps. Can someone tell me where to find it? Or it is no longer working? If so, is there a replacement with similar functionality.
I didnāt want to use the minimote to associate the switches since JDRoberts said that ST will not know the status of the switches if they talk directly to each other.
It worked very well for months. But last weekend all of a sudden the 2 switches ping pong each other indefinitely so I had to remove it, any idea what may have caused it?
This has happened to me off and on. I guess it is due to occasional
network delays. I either reboot the hub or throw the breake on the device
to reset it. Hope it helps.
Hi, I also had the two switches āping pongā yesterday. And I checked the code of @tslagle13 and found out that the code does not help prevent loop, it worked because of how smartthing works as @JDRoberts explained. So if something goes wrong, it may loop.
(the āifā lines were useless 'cause it check the status of the active device it self)
So I did change the code and it still works and I believe it will not cause any looping.
I still leave the credit to @tslagle13 in the code. Cheers.
Btw, I think this code can be done simplier with WebCoRe, but I still use this code to work with my multi-switches device after some modification.