Hi, Vince! To complete the questions: The pi is LAN connected. I did sudo shutdown -r now or sudo shutdown -h now, then unplug the power cable and start again by power connection. In both cases weewx fails because of a network error. Because of a missing log file I think, that the IP-Adresses won't help
Thanks Peter Vetti52 schrieb am Freitag, 2. Februar 2024 um 22:24:17 UTC+1: > Oops, the log entry is missing: It should read > sudo journalctl -xeu weewx.service > ... > raspbee weewxd.py[1316]: historygenerator.py: Generated 5 tables in 0.15 > seconds > > every five minutes. Nothing else. > > Thanks > Peter > Vetti52 schrieb am Freitag, 2. Februar 2024 um 22:19:25 UTC+1: > >> Well, there are some drawbacks. Sorry, that blames me. Of course I should >> have attached the log files, but I still struggle with the new journalctl >> log file system. The only entry I see there is >> >> every five minutes. >> So, I tested the reboot with the simulator driver. Then weewx starts as >> expected, assuming, it is correllated to the gw1000 driver >> At least, I can show the gw1000 related entry in weewx.conf: >> >> ############################################################################## >> >> # Options for extension 'GW1000' >> [GW1000] >> driver = user.gw1000 >> # This section is for the GW1000 API driver. >> >> # How often to poll the GW1000 API, default is every 20 seconds: >> poll_interval = 20 >> [[field_map_extensions]] >> # WeeWX field name = GW1000 field name >> rainEvent = t_rainevent >> txBatteryStatus = wh65_batt >> >> ############################################################################## >> >> # Options for extension 'GW1000' >> [Accumulator] >> [[rainEvent]] >> extractor = last >> [[txBatteryStatus]] >> extractor = last >> >> There as a lot more of these Accumulator entries. Don't know, if they are >> still necessary or up to date. My latest update of the gw000.driver was by >> replacing /usr/share/weewx/user/gw1000.py >> Version: 0.6.0b3 Date: 9 January 2024 >> vince schrieb am Donnerstag, 1. Februar 2024 um 22:44:11 UTC+1: >> >>> Without seeing your logs and the gw1000 section of weewx.conf, we can't >>> help too much. >>> >>> As always start with setting debug=1, restart weewx, let it run through >>> at least 'two' archive periods, and post the log. >>> >>> WeeWX isn't going to start nor run reliably if the driver can't find >>> your ecowitt gateway, which happens if your network is unstable and >>> especially if the pi is on wifi. We'd need to see the gw1000 section of >>> weewx.conf to suggest much there. And what ip is your pi and what ip is >>> the ecowitt gateway ? >>> >>> Also does this happen on 'reboot' or on 'power down and up' ? The pi >>> has no battery backed realtime clock so weewx might be waiting for your pi >>> to get accurate network time. >>> >>> On Thursday, February 1, 2024 at 1:27:26 PM UTC-8 Vetti52 wrote: >>> >>>> After upgrading to version 5.0.0, I can regularily observe, that >>>> starting Weewx sudo sdystemctl status weewx.service fails because of >>>> network error. >>>> >>>> My setup is a Rasperry Pi4 under a freshly installed bookworm. I >>>> installed the apt package as described in the guide, immediately stopped >>>> Weewx and edited weewx.conf to adopt my previous settings. That is to >>>> change to GW1000. I also changed from US to metric. >>>> As the Raspi has no display nor keyboard, I log in via ssd. Usually it >>>> runs without interaction for many months. However, up to date rebooting >>>> was >>>> not a problem. No, I have to log in and do a sudo systemctl start weewx, >>>> which I would like to avoid, as I tend to forget this, when doing it once >>>> per year or so. >>>> Why does this happen since version 5.0.0? And, if there are new >>>> conditions for starting, is there a way to tell weewx, to wait for an >>>> established network? >>>> >>>> BTW, I found a more of cosmetic curiosity: The date in the seasons skin >>>> is now displayed in form of dd/mm/yy. Ok, I can read it , but it is very >>>> unusual. As I did not touch this part in the seasons files, I have now >>>> idea, where this format comes from. >>>> >>>> Thanks for any suggestions >>>> Peter >>>> >>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/038012eb-d5c4-4b00-a87b-410de34f7483n%40googlegroups.com.
