To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/45036810-9d8d-4133-99c5-0ef2d7a6ce17%40googlegroups.com.--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
In the US, the Cooper Industries switches also have the Instant Status/HAIL functionality.
With the switches that rely upon the ApplicationUpdate ("I've changed") messages, the controller has to do a callback to get the actual status ("What are you set to"). These are still better than having to rely upon a pure Poll operation ... esp for the health of your Z-Wave Network @40kbits in larger networks
In some cases, like the Leviton DZ series, that callback has to be delayed (by ~2-3 seconds) or the device indicates it's busy and the call fails.So it depends upon how important this Instant Status feature is to you. In my case, I use it to trigger other Scenes (via the Controller) but also via local Z-Wave Scene Controllers (it's handled between devices, and the Controller isn't involved) so speed is important, but others get away without it.
Good luck on your hunt, and the new house build-out, HA definitely isn't cheap!
In the US, the Cooper Industries switches also have the Instant Status/HAIL functionality.With the switches that rely upon the ApplicationUpdate ("I've changed") messages, the controller has to do a callback to get the actual status ("What are you set to"). These are still better than having to rely upon a pure Poll operation ... esp for the health of your Z-Wave Network @40kbits in larger networksIn some cases, like the Leviton DZ series, that callback has to be delayed (by ~2-3 seconds) or the device indicates it's busy and the call fails.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/30a8e3d2-255e-49ef-b40c-c5556693de92%40googlegroups.com.
Not sure what price you saw, but I'll tell you that you can get them for ~$50/switch (RF9501).
Fair enough, I'm going by my experiences helping another user "simulate" the callBack in MiOS/Vera for the DZS15 Switches, and a more general comment on the Busy response.That user also had different backoffs needed for the Leviton DZ Dimmer model, than the DZ Switch model (through experimentation).Q: Is a default "wait" applied upon receipt of all ApplicationUpdate messages (eg. 2s) or are the Status enquiries fired off immediately and then re-fired (after wait) when/if the Busy is received?
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/8d36e273-1af0-46a5-a536-7830065ff094%40googlegroups.com.
Yes the patent thing sucks, made it harder for us and made association enabled equipment more expensive. To your question, the delayed query is only if we receive a busy message with a "try again latter" payload. So the sequence starting from the switch (-->) is
"Update" --> , <--"Get Status", "Busy, try again latter" -->, (2 seconds) ,<--"Get Status".
If we get another busy message, we would keep repeating. With the Leviton switches I have only seen the busy message with a "try again later" payload. The other options are "try again in x seconds" which I think I support, and "busy, don't try again" which we respect, but I have not seen used in my equipment. This was specifically to support the DZ dimmers and switches. It does add a 2 to 3 second delay to openHAB hearing about updates, so I have those switches where immediate notification are not super critical (like outside lights).
Could central placement of the controller alleviate that? Fewer hops to get from the reporting device to the controller would mean that fewer devices would have to carry the traffic.
I'm curious Mark, what wired technology did you switch to?
--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/432de5b2-c801-4763-876d-e7d4520531d1%40googlegroups.com.