Ok both, I hope the NodeMCU has arrived by now (or will have in the next day or so).
It has taken a LONG time to package everything up and merge the changes between multiple different codebases which I have for other projects (they all seem to be needed in some reason or other for this such as forwarding requests or connecting to external devices such as the Elk).
I think the current status is that we should start to have some control options working and that is all for now, though as Ive said without any option of testing it might do absolutely NOTHING in the first few versions! Lol, once Ive got the connection up and running to the alarm (for control), then it should be fairly logical and easy (if time consuming) to start to get alarm/zone status back from it.
Start by giving the device WiFi credentials by connecting to its access point which you should see as an open router you can connect to on your phone. Then you can type in credentials and disconnect, you should then find it on your own WiFi network by looking in the router for its IP address (or it should show up in Windows Network places).
Then you need to update the firmware to this:
Then you need to configure the device which is all done through web commands as below (you can do this from a browser or something like that):
Note that the password is effectively the pin, and if you have a 4 digit pin then prefix two zeros so that it is 6 char, i.e. if pin is 1234 then your PIN_CODE_FOR_ALARM should be 001234
A completed request string might be as follows:
Then install the device handler if you want to have the basics of ST control, though if you cant arm/disarm from the webpage of the NodeMCU then adding it to ST will not help you…:
Let me know whether the arm/disarm buttons do anything!!