Originally Posted by
eXOBeX
Interesting to see this work in progress. You shouldn't have to be doing it (there's no reason for Honeywell not to offer API or web access) but there y'go.
Have you considered decoding the link between gateway and server instead of gateway and app? Communicating with the gateway (via a Pi running a web server on the same network, for example) would cut Honeywell's servers out of the loop completely, useful if Honeywell decide they're end-of-life and try to push a replacement product.
For what it's worth I've installed Wireshark today to see what the gateway is up to. I'm unfamiliar with Wireshark so forgive any noobishness :)
First thing it does is looks for the local router, then makes a HTTPS request (from port 30000 to dest port 443) to auiredir1.alarmnet.com (204.141.57.100).
After a brief chat it then turns its attention to auiredir2.alarmnet.com (204.141.57.101), again HTTPS but this time with a source port of 30001.
Next is more HTTPS to 12.149.218.73 (registered to ADI), incrementing the source port once more.
The cycle then repeats over and over, with the gateway sending snippets of data to auiredir1.alarmnet.com, auiredir2.alarmnet.com and 12.149.218.73 and incrementing the source port counter each time. Most data packets I saw were 170 bytes or less, the third ever auiredir2 packet being the only exception at 634 bytes.
None of these three appear to make the first move, the Evohome gateway calls them first.