The data is available via the Elk RS-232 protocol -- doc available on their web site.jlegault said:Is there an established way to collect Elk sensor data (thermostat temp, probe temp, keypad temp)? I would like to start collecting so I can overlay with energy usage. Ideally I'd like to poll, time stamp, and stuff into a DB.
That is very cool. I suspect if you post a copy here many will find it very useful (especially those who do not have homeseer so have not been able to take advantage of Electron's my.Elk.johndoe74 said:I've written a .NET application that connects to the ELK Ethernet module, parse the events and output them to a log file. Currently, I do not have time to update it so I am not sure if it's useful to you. But I can send it to you if you want. Here's a screenshot:
I don't think it is reading the actual Elk "logs". The "logs" are where the M1 records all the arms, disarms & troubles. This tool appears to pick up all the data that the M1 spits out when things change. This is the same as the way that my.elk gets its data. This program appears to be logging only, so it would not control things or send data to the M1, but the Elk protocol supports it.3DogKnight said:That is really cool. So you are just reading the logs, not actually directly interacting with the Elk variables, correct? So using the program to change something (like turn on a light) is not possible?
Unless I'm mistaken I suspect he just implemented the serial protocol that is on the elk site:3DogKnight said:I would like to get a copy of the .net code. Are there specific calls or dll libraries that were acquired from Elk Products to make this work? Any documentaion on the supported protocol? I assume somewhere in the code you need to supply an IP address of the Elk, and password and port, etc., correct?