Thanks for the comments. I checked weewx.conf for all "loop" entries, no loop_on_init exists. So, by default, is it set to false? Shouldn't it be generally enabled for gw1000 driver? I wonder, why weewx could not be started after exiting. To me, this indicates, that it was in fact still running in this status for more than 30 minutes. I could stop it, which took some seconds, and then start it again. At that stage the network was up and running, so everything worked well. As I reboot the Raspberry very rarely, next time I might have forgotten about this problem with the gw1000 and the Raspberry Pi after reboot. As the gw1000 itself is continuously running and sending the data without interruption to ecowitt, thus showing valid data on the WsView dashboard, I might not check, that weewx does not receive data then. I'm getting old....
If loop_on_init would also solve this issue, and additionally the problem of a temporarily missing network connection to gw1000, this would indeed overcome my solution with weewx.service, which only works at startup. As the Raspberry Pi has to serve some other services (cups, home assistant, Unifi), I am not very happy with the idea to inspect weewx/gw1000 after repeated reboots. Especially, if I do not exactly know, which protocols have to be logged and evaluated. I could even assume, that at next time, the network might have started slightly faster, so this issue will not always be observable by chance. So, there should be a well defined environment for testing, which I currently don't have. Meanwhile, before I forget about it, I will enable weewx.service modified with the Stanza mentioned above. -Peter gjr80 schrieb am Samstag, 6. Februar 2021 um 22:32:10 UTC+1: > Different but I guess related issue. WeeWX/GW1000 driver will happily > connect to the GW1000 wether the GW1000 has internet connectivity or not. > Any data will be at best sporadic or, in some cases, next to useless but > the lack of internet does not prevent WeeWX/GW1000 driver operation per se. > > Gary > > On Sunday, 7 February 2021 at 07:05:53 UTC+10 vince wrote: > >> Peter - the gw1000 has at least two watchdog timers in it, and will >> reboot without being able to contact both the NTP and Web servers at >> Ecowitt for too long a period. There is some discussion on wxforum.net >> regarding how to set up your own LAN services to fake it out. Multiple >> people including me have asked Ecowitt to give us a way to disable their >> watchdogs, but they have declined to agree to do that. They just respond >> with the same information saying how the user can impersonate their servers >> with some DNS and webserver sleight of hand. >> >> -- 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/7713054c-74e5-47e6-a918-a9b7bfff6ff3n%40googlegroups.com.
