meteohub.de

Hello,
I’ve had the Nano for about 2 years now and have started getting a problem. Symptom is when I try to access the Nano via the internet it says “Oops, remote access to your Nano is currently not available”. My internet router hasn’t had a firmware update required in a year, and I’m up to date on the Nano software versions.

When I check my internet router logs I get the series of messages pasted below. The Mac address matches the Nano. It is connecting using 2.4Ghz channel on the router.

I tried rebooting the Nano a few days ago using the remote access and it seemed OK for a while, but then starts acting abnormal again.

Any idea what is causing this and how to fix it? Thank you in advance.
———————-
Mar 22 06:40:53 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:40:57 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:40:57 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:40:57 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:02 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:02 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:05 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:05 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:05 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:05 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:09 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:09 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:11 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:11 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:16 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:16 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:18 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:18 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:18 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:22 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:22 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:24 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:24 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:24 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:29 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:29 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:32 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:38 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:38 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:40 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:40 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:44 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:44 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:46 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:46 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:46 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:46 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:46 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:51 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:51 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:53 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:53 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:57 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 22 06:41:57 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:41:59 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:59 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:59 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:41:59 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:42:06 syslog: wlceventd_proc_event(508): eth1: Disassoc BA:D8:12:00:58:6E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 22 06:42:06 syslog: wlceventd_proc_event(527): eth1: Auth BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:42:06 syslog: wlceventd_proc_event(556): eth1: Assoc BA:D8:12:00:58:6E, status: Successful (0), rssi:0
Mar 22 06:42:11 syslog: wlceventd_proc_event(491): eth1: Deauth_ind BA:D8:12:00:58:6E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rss
———————————-

Looks like a weak WLAN connection to me.

admin wrote: ↑Wed Mar 22, 2023 7:42 pm Looks like a weak WLAN connection to me.

Thanks for the reply. The Nano is about 15 feet from the router. The router shows the signal strength going from 3 bars to 4 bars (out of 4 possible bars) to 3 bars, repeatedly.

I tried changing the 2.4Ghz config of the router to use only 1 channel vs. auto thinking that might help, but it hasn’t.

I took a screenshot of the Nano network tab - do you see anything here I should change? Thanks

What does Meteobridge Log-File tell?

admin wrote: ↑Thu Mar 23, 2023 11:30 pm What does Meteobridge Log-File tell?

Thanks for the reply. Here is the log after I rebooted it yesterday. I’m not sure what the last 5 lines mean, or if that is normal. Can you please let me know what is happening there? Thank you.
—————-
setup (22.03.2023 17:58:50): use UTC stamp 2023-03-22 21:58:50 (1 tries)
database (22.03.2023 17:59:05): process started.
database (22.03.2023 17:59:07): Content of RAM database restored.
wnetd (22.03.2023 17:59:09): process started.
system (22.03.2023 17:59:09): start of logging process initiated.
wnetd (22.03.2023 17:59:09): send data thread started (pid:2084 tid:2085)
logger (22.03.2023 17:59:10): databases connected. Update interval 3600 seconds.
logger (22.03.2023 17:59:10): data logger (version 5.4, build 4424) started.
logger (22.03.2023 17:59:11): connect station 0 (Vantage via serial).
logger (22.03.2023 17:59:11): connect station 9 (System Data via Plug-in).
logger (22.03.2023 17:59:12): station 0 (Vantage), wakeup sent.
logger (22.03.2023 17:59:15): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (22.03.2023 17:59:15): services paused.
logger (22.03.2023 17:59:15): station 0 (Vantage), no need to update console date/time.
logger (22.03.2023 17:59:15): station 0 (Vantage), setup script executed.
logger (22.03.2023 17:59:16): station 0 (Vantage), internal logger activated.
logger (22.03.2023 17:59:16): station 0 (Vantage), syncing.
database (22.03.2023 17:59:17): database sync done (29 tables, 107/928 writes).
logger (22.03.2023 17:59:26): station 0 (Vantage), gettime request sent.
logger (22.03.2023 17:59:26): station 0 (Vantage), no Vantage time offset.
logger (22.03.2023 17:59:26): station 0 (Vantage), eeprom request sent.
logger (22.03.2023 17:59:26): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (22.03.2023 17:59:26): station 0 (Vantage), transmitter 2 active as station type #0 "ISS".
logger (22.03.2023 17:59:26): station 0 (Vantage), firmware version request sent.
logger (22.03.2023 17:59:26): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (22.03.2023 17:59:26): station 0 (Vantage), no reading of Vantage's internal logger.
logger (22.03.2023 17:59:30): sensors are now providing data.
logger (22.03.2023 17:59:30): services started.
system (22.03.2023 18:15:04): Access point operation disabled 1058 secs after boot.
system (22.03.2023 18:45:15): Access point operation disabled 2869 secs after boot.
system (23.03.2023 03:01:05): Disconnected from WLAN or Internet, reconnect issued.
system (23.03.2023 03:01:12): Access point operation temporarily enabled.
system (23.03.2023 03:06:40): Access point operation disabled 32954 secs after boot.

I may have found the problem, but I’m still interested in what the last 5 lines are from the log above.

I turned off something called “beam forming” on the 2.4ghz wifi settings and the messages appear to have stopped.

Thx for the help

On boot a NANO provides an its own AP which allows you to connect and configure the unit and connect as a WiFi client to your WLAN etc. For security purposes once the unit is connected to your WLAN then the temporary AP is disabled after a short period of time after boot and the WiFi Access Point is no longer accessible.

Hello,
I've had the Nano for 3 years, and although I've always struggled with problems like the one described in this post, mainly the Nano disconnecting from the Wifi network, I always could connect it back by reseting the device, removing power from the console or unplugging/plugging it back to Davis Vue console.

But this time, none of the mentioned solutions are working, Nano is stuck flashing endlessly and eventually the flashing disappears. Even the meteobridge network that should be available after a reboot or after plugging the device to the console, is no longer showing up.

I really don't know what to do, so any help would be highly appreciated.

Thank you.
Albert.