It appears when a Leviton Vizia RF+ switch is toggled (assume 4 times in 7 seconds and that the node id is 19), the VRC0P will show the following (provided the associations are set properly):
<N019:130,001
<N019:130,001
<N019:130,001
<N019:130,001
<N019S000,094,000
The <N019S000,094,000 is always delayed about 1.5 seconds (presumeably to give the user time to re-toggle the switch before sending the status update to the VRC0P). This information is really only useful for updating a lights status. Yes, you could use it to turn on a neighboring light, but this would always result in a 1.5 second delay for turning this other light on.
However, <N019:130,001 is much more reliable and always comes in if a switch is toggled on/off or a bright/dim button is pressed multiple times in a quick sequence (but with about a .75 second delay inbetween presses). It seems on all of my Vizia RF+ dimmers/switches, <Nxxx:130,001 shows up from the VRC0P in less than a second!
I'm thinking about using this information to count the number of switch presses and actuate things depending on the toggle count over a time period. For example, if someone toggles a light at the front door 3 times in 5 seconds, it would turn everything off in my home and set my alarm to away mode. A user would have to be careful and wait a second before toggling the switch, but 3 or more toggles could always result in some action. In other rooms, the toggle could be used to disable an occupancy timer for 4 hours (for those times when you don't want to rely on door/motion sensors to keep the lights on).
I'm curious if anyone else is using this status update to do similar things and if so, how reliable is it? This seems a lot cheaper than placing scene controllers throughout a home.
PS: I plan to add this capability to the free opensource Premise VRC0P module (newest beta is found here): http://www.cocoontech.com/forums/index.php?showtopic=18200&view=findpost&p=151266
Premise is also free, so you might give it a try
: http://www.cocoontech.com/wiki/Premise
<N019:130,001
<N019:130,001
<N019:130,001
<N019:130,001
<N019S000,094,000
The <N019S000,094,000 is always delayed about 1.5 seconds (presumeably to give the user time to re-toggle the switch before sending the status update to the VRC0P). This information is really only useful for updating a lights status. Yes, you could use it to turn on a neighboring light, but this would always result in a 1.5 second delay for turning this other light on.
However, <N019:130,001 is much more reliable and always comes in if a switch is toggled on/off or a bright/dim button is pressed multiple times in a quick sequence (but with about a .75 second delay inbetween presses). It seems on all of my Vizia RF+ dimmers/switches, <Nxxx:130,001 shows up from the VRC0P in less than a second!
I'm thinking about using this information to count the number of switch presses and actuate things depending on the toggle count over a time period. For example, if someone toggles a light at the front door 3 times in 5 seconds, it would turn everything off in my home and set my alarm to away mode. A user would have to be careful and wait a second before toggling the switch, but 3 or more toggles could always result in some action. In other rooms, the toggle could be used to disable an occupancy timer for 4 hours (for those times when you don't want to rely on door/motion sensors to keep the lights on).
I'm curious if anyone else is using this status update to do similar things and if so, how reliable is it? This seems a lot cheaper than placing scene controllers throughout a home.
PS: I plan to add this capability to the free opensource Premise VRC0P module (newest beta is found here): http://www.cocoontech.com/forums/index.php?showtopic=18200&view=findpost&p=151266
Premise is also free, so you might give it a try
: http://www.cocoontech.com/wiki/Premise