- I only have Apple Airports at home, which aren't supported; A Mitsubishi support rep I emailed suggested this $15 (!!) router from PB Tech, which *is* on the supported devices list:
- I bought one of the above and have set it up as a straight access point on a different SSID, just for the heat pump. Works fine.
Everything now works as advertised, though as already mentioned it is quite slow as _everything_ goes through a remote server. I have done a packet capture and can see whats happening:
- Exactly every minute, the heat pump does an HTTP POST to this URL: http://reg.melview.net/SOME_ID/
- The POST data is sent on port 80 in the clear (GARGH!)
- The request body is XML, which contains a single key which is a base64 encoded payload:
- The request payload itself, when decoded, is lots more XML; see here: https://gist.github.com/jonathanhoskin/9f7784cc031e7d7caf05
- The response body is XML which is a single key with a base64 encoded payload:
- If there are no new commands for the unit, the response payload decodes to this:
- However, if there is some pending command for the unit (e.g. increase fan speed):
It's a bit of a concern is that the WiFi adaptor is communicating in the clear, but the data it sends is quite boring.
As for the mobile and web apps, they appear to send sensitive data over HTTPS. The web app is hosted on a non-SSL site, but uses AJAX over HTTPS for the actual sensitive data. I'm still pulling those bits apart.
By the looks it is all pretty straight forward, so it would totally be possible to hijack everything that is being done over the wire to build all the automation locally.