I'm having an issue that has me scratching my head.
I have a remote virtual switch, Switch 118, which is set in my remote Hub (hub#1). The piston below (on Hub#2) is triggered by the remote virtual switch (Hub#1) BUT the Piston doesn't recognize the State change.
Are device states , time sensitive - meaning is there a time limit of when a device "is on" vs "changed to on"
Perhaps try setting up a simple rule in rule machine or something similar on hub#2, say to send you a notification, triggered off the switch changing state, just to confirm they pick up on the state change. Then you can work out where to focus your efforts in trying to solve the issue.
Or perhaps an even quicker thing to check is the events listed against the device
ok thanks for the idea.. what i did do is set the switch in Hub 2 manually... in which case all is good.... then the state change on switch is recognized in Hub 1.
However the switch is set by a piston on Hub 1 (not manually) in which case, the state change triggers the piston in Hub2 but the switch state change is not recognized..
Ok i tried something which is demonstrating strange behaviour.. I put a wait of 1 sec before the condition of the virtual switch state is tested - it does not recognize the state.. without the wait it does.
So either this is a webcore issue or a Hubmesh issue
Unfortunately that didnt make a difference in my case... there definitely appears to be an issue in webcore in recognizing device state change from a hubmesh device..