davidmc36 wrote: ↑Sun Aug 31, 2025 1:52 pm
All I can say is that my Airlink stays connected on my MB running 6.2. I have never actually set the IP to static. But it reconnects at same address whenever it or WiFi power cycles.
I had a lot of trouble before running two WiFi systems.
Now I only have one network with the mesh nodes in bridge mode and router WiFi turned off.
ALL my devices connect better now that network is "cleaner".
Tee Hee Hee
As I say it, the bugger disconnected last night/this morning.
Just as OP says. All other things are reading it fine.
I will cycle the WiFi plug it is powered by and all will be fine.
jasonmfarrow wrote: ↑Mon Sep 01, 2025 10:57 am
A reboot of the Airlink results in an instant reconnection to Meteobridge. Last night the log showed a drop and, 7-hrs later, a reconnect without the need to reboot the Airlink.
Thanks for giving that detail. I checked the Airlink read out code on the NANOs:
#!/bin/sh
#
while :
do
wget -q -t 1 -T 20 -O- "http://$2/v1/current_conditions"
sync
sleep 10
done
I had some issues with ambient weather IP devices in the past that also had their data readout via a HTTP GET request. The issue there was related to HTTP requests being answered slower and slower over time. I guess this was because of a memory leak in the firmware of the device. As a result the device gets more and more unresponsive on their web interface until it finally stalls. New FW helped to solve this for the ambient device.
If someone knows of a reboot command that can be issued to the Davis Airlink over HTTP, I could trigger this when wget runs into timeouts while waiting for Airlink to reply. The 20 seconds timeout in the wget code should be fine. I doubt that waiting longer will solve it.
I don't know of any way to upgrade Airlink firmware. Davis does not publish any nor any tool to do so. The App for Airlink (Weatherlink Cloud) does not have a Firmware update option nor a remote reboot option.