Problem with weewx after power failure

[Monica Mulholland]

My Rpi with weewx has been running very successfully for many years.....until we had a power failure recently. I can still get into my Rpi from my desktop and see that it is running....but nothing is been updating on my website. It is still stuck at the time the power came back on. I suppose it could be the battery on the external weather station but that was changed recently and it the signal strength on the last webpage is not showing any problem. When I look at the log, I get a stream of these.

Apr 13 12:25:28 WeatherPi dhcpcd[349]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1

Apr 13 12:25:28 WeatherPi dhcpcd[349]: wlan0: soliciting a DHCPv6 lease

Can somebody who knows more about these things than me, please tell me what is going on and how I can sort this out,

Thanks in anticipation.

[dunbrokin]

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e75c2ddf-368e-4e45-b0c9-e238058eeb4cn%40googlegroups.com.

[Jeffrey Pritts]

It could be a variety of issues, but I would simply start with the CLI.

Run rtl_433 with the appropriate switches for your sdr dongle and the frequency, etc.  If it comes up with a USB claim error, then you know the rtl_433 for weewx is running and that's not the issue.  I would then stop the weewx service and be sure that the rtl_433 is still running using htop.  Then rerun rtl_433 and watch for your wx sensors,  They should report at least every minute; all my Ambient wx, Nexus and Fine Offset sensors do.  If you're not sure of the frequency, then you can run both to alternate.  Here's is my example I keep running 24/7 to monitor all my sensors...

rtl_433 -d rtl_tcp://192.168.0.35:1200 -C customary -M level -M time:tz -H 60 -f 433.92M -f 915M -v

I am using the tcp for a remote RPI3B+ with two dongles running rtl_tcp.  You can omit the -C if you like.  This should start with 433MHz and monitor for a minutes then switch to 915MHz for a minute and then loop back to 433...As far as the log entries, I am guessing that your RPI is trying to lease an IPv6 address to something and nothing is taking it.  My guess is you are using IPv4, so you should be able to ignore those.

N3EDS

Jeff P.

[Tom Keffer]

You're not giving us much information. At the very least, what kind of weather station? Better yet, include the log. See the wiki article Help! Posting to weewx-user for how to get a good log.

The wlan0 entries are probably red herrings.

-tk

--

[p q]

Did you try rebooting the Pi? 😜

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEAobmP7beSg4Nw4i%2BqM%2B9pui1SV9_25Zu8xChwjs-XwKg%40mail.gmail.com.

[dunbrokin]

Yes tried that thank you!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAA1SM23dvAKSawpfjTSjkoPHnJOwwB0W8S7pL8n6n8H2zeEDzA%40mail.gmail.com.

[dunbrokin]

Yes apologies, it has been so long since my system misbehaved (probably 10 years), I had forgotten what was required.

I looked back over the history of commands in the terminal of the Rpi and found these commands: (probably given to me by you last time around)

1297 sudo /etc/init.d/weewx stop

1298 wee_device --dump

1299 wee_device --clear-memory

1300 sudo /etc/init.d/weewx start

I tried them and lo! and behold! We are back online!

Thank you to all who tried to help...always much appreciated.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEAobmP7beSg4Nw4i%2BqM%2B9pui1SV9_25Zu8xChwjs-XwKg%40mail.gmail.com.