- Code: Select all
ackValue : 0
address : 22.F7.44
cmdBytes : [17, 0]
cmdFunc : on
cmdScene : 3
cmdSuccess : True
cmdValue : 0
replyBytes : []
cmdScene is the button #.
This is a legacy forum which is locked for new topics. New topics should be started in one of the other forums under Extending Indigo
ackValue : 0
address : 22.F7.44
cmdBytes : [17, 0]
cmdFunc : on
cmdScene : 3
cmdSuccess : True
cmdValue : 0
replyBytes : []
You can, of course, subscribe to incoming INSTEON commands and watch for button presses that way.
hamw wrote:Would a general solution include "One" of the Holy Grails of home automation: multiple events/single trigger?
Perry The Cynic wrote:Do I need to worry about cmdSuccess in incoming INSTEON commands being False, and if so, what am I supposed to do about it - ignore it? Yell at the user?
Perry The Cynic wrote:Is there something problematic about calling indigo.server.turnOn from inside an insteonCommandReceived handler? When I do, I get frequent "send failed (no acknowledgment)" errors. Adding a one-second delay solves the problem, but of course isn't nice for responsiveness. (And it really needs to be almost a full second; delaying by 0.3 seconds doesn't seem good enough.)
Perry The Cynic wrote:Is there any way my plugin can find out that a turnOn/turnOff command has failed, so it can retry it? (Short of issuing a state query, at least, or filtering the event log for errors.)
So, yeah, it's sometimes going to be a problem because it's likely that the INSTEON cleanup messages from the command are still floating around - the delay gives them a chance to complete. A delay is your only option or you'll get collisions.
Users browsing this forum: No registered users and 1 guest