Hi all,
I've been running a Vantage/Meteohub/Meteoplug setup successfully for almost a year now.
However, some major construction was done around the house and along with it came several power outages and a new phone and internet provider. I am now behind a Speedport W724V of Deutsche Telekom in which all necessary settings have been adjusted (encryption, ports etc.).
Since the power outages my iConnect won't come back up on my WLAN, no matter how often I reboot. It seems to be happily writing data to the flash drive, though.
Two questions:
- Are there any known issues with the iConnect and Speedport routers (especially their DHCP IP range 192.168.2.xxx)?
- I have quite a bit of historical data on my current flash drive. Can I use another drive to update the image on the iConnect and then plug in my old flash drive to access that data again?
Thanks a lot for your efforts, the Meteohub/plug system has been a lot of fun to play with so far.
Cheers
Chris
New router / no reboot on Iconnect
Moderator: Mattk
Re: New router / no reboot on Iconnect
I would recommend to setup a new USB stick and get it running.
Then insert the old stick and copy over the monthly raw data from the past,
which is located at "/data/weather/yyyymm/raw"
When done, issue a manual recompute on the new system.
Then insert the old stick and copy over the monthly raw data from the past,
which is located at "/data/weather/yyyymm/raw"
When done, issue a manual recompute on the new system.
Re: New router / no reboot on Iconnect
Thanks for your swift reply. I will proceed as you suggest and replace the old flash drive that way.
Usind an IP scanner, I figured out why the reconnect won't work. The Speedport router has a preset IP range to draw from, starting at 192.168.2.1 (which is the router itself).
Even with WLAN DHCP mode activated I noticed the Hub coming up on the network with its last assigned IP still from the old router and the old range (classic 192.168.0.xxx and up). The Speedport, set to 192.168.2.xxx, won't have that and kicks it. Same for the fallback IP.
Changing the IP range available for DHCP from the Speedport finally solved the issue. This first requires the router gateway IP to be changed to 192.168.1.1. After that, the IP range 192.168.1.xxx becomes available in the Home Network tab.
Usind an IP scanner, I figured out why the reconnect won't work. The Speedport router has a preset IP range to draw from, starting at 192.168.2.1 (which is the router itself).
Even with WLAN DHCP mode activated I noticed the Hub coming up on the network with its last assigned IP still from the old router and the old range (classic 192.168.0.xxx and up). The Speedport, set to 192.168.2.xxx, won't have that and kicks it. Same for the fallback IP.
Changing the IP range available for DHCP from the Speedport finally solved the issue. This first requires the router gateway IP to be changed to 192.168.1.1. After that, the IP range 192.168.1.xxx becomes available in the Home Network tab.