Anytime we lose power, my EISY controller loses the ability to control my ELK M1 Alarm through the EISY node. What I've learned is I have to restart the node and then go into the UD user interface and actually set the state of the alarm in any mode and that seems to restore the communication between the two. While this isn't a common issue, it's still not ideal.

Has anyone seen this similar issue and how reliable has the ELK node been for you guys?

I don't have a Elk M1 but here is a general suggestion: program (in IoX) a variable as a flag that gets set upon startup, and create a program that looks for the flag set to that value, then have the program reset the flag, set your alarm status to a temporary value (armed might be the best one) and then query the M1 for it's status to update the eisy.

Thank you

9 hours ago, midrar said:

Anytime we lose power, my EISY controller loses the ability to control my ELK M1 Alarm through the EISY node. What I've learned is I have to restart the node and then go into the UD user interface and actually set the state of the alarm in any mode and that seems to restore the communication between the two. While this isn't a common issue, it's still not ideal.

Has anyone seen this similar issue and how reliable has the ELK node been for you guys?

I would suggest setting the logging in pg3x for the Elk plugin to debug and checking for any errors.

If none are visible while monitoring, you can download a log file and look through the text files.

If you still can't identify the issue, send the log file to plugin developer for review.