I adapted an existing weewx driver to process data 'sniffed' from the AcuLink Bridge when it forwards sensor data to their web service and I'm sharing my work.
Why would someone else use this:
The driver should work with anything that listens on a TCP port and emits the aculink POST request data, one request per line, when a remote peer (like the driver) connects. My instructions cover how to do that with a router running OpenWRT that sits between the AcuLink and the Internet connection. At some point, I'll probably switch to some sort of transparent proxy or DNS hijacking so I can collect data even if the internet connection or the Aculink servers are down.
Thanks to the people here, and elsewhere on the internet who've shared what they've learned about sniffing and interpreting data from the AcuLink.
For more info & a download link visit: http://geekfun.com/hackulink
Why would someone else use this:
- To post more frequent updates to Weather Underground and other services, and the other stuff weewx can do.
- Because its there.
The driver should work with anything that listens on a TCP port and emits the aculink POST request data, one request per line, when a remote peer (like the driver) connects. My instructions cover how to do that with a router running OpenWRT that sits between the AcuLink and the Internet connection. At some point, I'll probably switch to some sort of transparent proxy or DNS hijacking so I can collect data even if the internet connection or the Aculink servers are down.
Thanks to the people here, and elsewhere on the internet who've shared what they've learned about sniffing and interpreting data from the AcuLink.
For more info & a download link visit: http://geekfun.com/hackulink