meteohub.de

I just replaced a failed TP-Link with a new D-Link DIR 505. Flashing the firmware to Meteobridge went without a hitch, but I spent more than 4 hours trying to get the unit to accept the network configuration.

I followed the Wiki and setup the wireless LAN, while the 505 was connected by cable, but when Save, Apply & Reboot is pressed, I get the red software warning about 30 seconds unavailability, but the Router starts the reboot sequence and then goes into fast flash mode and the red warning remains. At this point it is not accessible by IP and my IPScan24 software shows it as being "Dead".

Following the advice, pressing the side button until the light flashes once will get me back in. The network configuration has not changed, so multiple times I tried the Save, Apply & Reboot, but the result is the same.

I eventually used the cloud device, saving the config.tgz file to a memory stick and rebooted from that, inserted in the USB port. The result is the same, a fast green flash after rebooting, I am unable to access the Router on WiFi by typing the IP into the browser and IPScan says it's dead, but I can access it if I connect by cable and reboot..

Leaving it on overnight, this morning I find that it is uploading data to Wunderground (and has been all night), on WiFi, but my Aicam web cam picture is not being uploaded. Now for the really strange bit, I still cannot access the router by typing the IP address, IPScan sees it but still says it is dead, but I can access the Aircam (it has a fixed IP address) and data is being uploaded every 5 minutes, as it should to wunderground. IPScan sees the camera IP and shows it as live.

If data is being collected from my IROX station by USB2 link and the data and access to the camera can be done over WiFi, why can I not log into the Router? Can anyone offer any suggestions? LAN Bridge is enabled, which would account for the camera access, but not the weather data being sent.

Thanks for reading

As WiFi is used by other users of this device fine the remaining explanation
is that you simply don't give the right WiFi credentials.

Did you select one of the found SSIDs from the dropdown? Any special characters in there?
Did you select the correct encryption type?
Did you enter the right passphrase? Any special characters or spaces in there.

As WiFi is used by other users of this device fine the remaining explanation
is that you simply don't give the right WiFi credentials.

I Don't think this is credible. The device had linked and was transmitting data to Wundergrund, and then stopped. HOWEVER, the device was not visible when I used IPScan24, only the webcam (which has a fixed IP above all others, 192.168.0.120) I do not understand how there can be an attached device which cannot be found yet can send data.

Did you select one of the found SSIDs from the dropdown? Yes

Any special characters in there? No

Did you select the correct encryption type? Yes

Did you enter the right passphrase? Yes

Any special characters or spaces in there. No

I suspect a firmware issue, perhaps due to a change in the model

NormanW wrote:I Don't think this is credible. The device had linked and was transmitting data to Wundergrund, and then stopped. HOWEVER, the device was not visible when I used IPScan24, only the webcam (which has a fixed IP above all others, 192.168.0.120) I do not understand how there can be an attached device which cannot be found yet can send data.

It has an IP for sure, otherwise it cannot communicate to the outside. This all looks
very much like some basic problems in your LAN. May be there is a second device that also
provides network addresses/IPs via DHCP etc. There are tons of errors one can do setting up
a LAN. I would recommend to find out the IP as follows:
1) Your router should be able to tell in his logs which IP it gave to it.
2) MB can blink its IP
3) browse to "magicip.meteobridge.com"

You find tons of information how to find out IPs here:
http://meteobridge.com/wiki/index.php/G ... eteobridge