Moving Over from Elk

[apostolakisl]

I have spent the last day moving programs over from Elk rules, to ISY programs. I have to say, it is a pleasure to be able to write programs in ISY accessing virtually all of the features of Elk. The flexibility, ease of programming, ease of organizing in ISY, and abundant memory is making this a pleasure.

 

Thanks for getting this going!

 

I would like to have an outline of all the commands, their trigger conditions and their true/false determinants. A nice table would be great.

 

Example:

 

Command- - - - - - - - - - - - -- - Trigger - - - - - -- - -- -- - --- -- True state - - - - - False state

Elk zone x status is normal- - - -zone changes status -- -- - - - Zone Secure - - - - - zone violated/trouble/bypassed

 

I think this would be great for the wiki. If we decided on a format, I would be happy to take a section of the commands and outline it.

[sanders2222]

This sounds great apostolakisl, even though I have no idea what you are talking about. I hope to get my ELK connected into my system within a couple of weeks and I based on what I know, it appears the wiring is the easy part!

[Michel Kohanim]

Hello apostolakisl,

 

Great idea ... we are still in backlog mode trying to get everything done. Once we have some reprieve, we'll start working on the documentation. Volunteers are quite welcome!

 

With kind regards,

Michel