sdf777 Posted June 1, 2014 Posted June 1, 2014 I have a keypad light which lights if the garage door is open. it was not working consistently for each of 2 doors. After much tribulation I finally figured out that the motor was sucking the status send command. After the door action, my ISY had the improper status until I did a query. What I need to figure out is how do I query the garage door status say 15 seconds after the garage door open/close button is pressed and the motor has stopped. I can't just do a wait 15 seconds after the command is done as it requires another 2 if statements, based on on or off conditions to light up the button or turn it off. Please help.
sdf777 Posted June 1, 2014 Author Posted June 1, 2014 Does the status command do a query first? If not it will give the wrong status above. Can you query within a program to change the status?
LeeG Posted June 1, 2014 Posted June 1, 2014 "Does the status command do a query first? If not it will give the wrong status above. Can you query within a program to change the status?" The If Status does not Query before reacting to a Status change. If the I/O Linc Sensor state change message is not making it to the PLM the If would not trigger because the Sensor state change did not reach the ISY. A Program can issue a Query. If the Query changes the Sensor state a Program checking the Status will trigger. If it is the Program that issues the Query the Program will not trigger again until the current processing is complete or a Wait/Repeat is encountered.
sdf777 Posted June 1, 2014 Author Posted June 1, 2014 I only have under then, action, insteon set ISY, query. Is that what you mean?
sdf777 Posted June 1, 2014 Author Posted June 1, 2014 I realize now you mean to query the device name.
LeeG Posted June 1, 2014 Posted June 1, 2014 That is correct, Query the device that is not providing the needed state information (Status). I think the better approach is to fix the noise/absorption problem with the openers rather than do a Query.
mwester Posted June 1, 2014 Posted June 1, 2014 That is correct, Query the device that is not providing the needed state information (Status). I think the better approach is to fix the noise/absorption problem with the openers rather than do a Query. I agree - fix the problem, not the symptom! Try a filterlinc on the door opener(s).
Recommended Posts