I like more reliable posting to WU and choice of other weather sites from Kevin's program, mix of sensors and offsets, etc.
This might be simpler to set up hardware wise, but is more complicated from network configuration perspective.
Setup of Kevin's is the same except no step 1 of bridging adapters.
What we want to do is get the SmartHub to get a local IP address when it looks up myacurite instead of the "real" internet address.
The SmartHub needs to receive its DHCP configuration that sets the DNS server to your local router. A lot of routers have options for host overrides, DNS forwarding etc. search for your model to see if it is possible and how to do it.
Redirect the host
hubapi.myacurite.com to the local computer running Kevin's software so the SmartHub connects to it.
Ideally, the Windows machine running Kevin's program will not use the local DNS and be able to look up the real internet IP of
hubapi.myacurite.comIf that isn't possible, you could use an ip address instead of
hubapi.myuacurite.com in the command below, but the IP may change and you'd have to update your command.
Using ncat from
https://nmap.org/ncat/ we can listen on port 80, and then relay it to myacurate.
In a command prompt, run:
ncat -e "ncat hubapi.myacurite.com 80" -l 80 -k-l 80 listens on port 80 (http/web)
-k keep listening
-e executes another ncat command to connect to myacurite to send the data from SmartHub, and receive the response back.
WU should be disabled in MyAcurite and you want to check that the settings have been cleared from your SmartHub by viewing its webpage before starting to send from Kevin's.
It's also possible to use Kevin's without posting to myacurite at all
. It is again more complicated, but you can avoid forced firmware updates and have more choice about how you use your equipment and data. The average consumer is fine to be locked into Acurite's world, but I think most people coming to this forum want more.