I'm happy to see that, after adding loop_on_init, both my Pi Zero W and Pi 4B are now booting up and waiting for the WiFi to stabilize. It's working well
On Thursday, August 6, 2020 at 4:10:44 AM UTC-5 [email protected] wrote: > ah, i see the problem now. the wifi is useable only after it connects to > an access point, which is above the level that systemctl manages. $network > is not enough (i tried it), nor $sockets, not even $default. there is some > arbitrary delay after the network is ‘up’ before the wifi is accessible… so > ‘weewxd —loop-on-init’ (just keep trying ‘till it connects) is a good > solution. i think we will need this as default setting for wifi-based > interfaces (recommend it be part of driver installation) > > On 5 Aug 2020, at 5:58 pm, gjr80 <[email protected]> wrote: > > I seem to recall this issue coming up a few times in the past, with mixed > results. However, it is worth trying. > > Gary > > On Wednesday, 5 August 2020 16:12:25 UTC+10, Graham Eddy wrote: >> >> at the moment /etc/init.d/weewx says weewx depends on ‘localfs', >> ‘remotefs', ‘syslog' and ‘time' for startup. >> i notice in your syslog that ‘network' is reached *after* weewx starts → >> maybe we need to add ‘network’ to weewx’s dependencies: >> * edit /etc/init.d/weewx to add ‘$network’ to end of Required-Start line >> * run ‘systemctl reload-daemon’ to compile the changed weewx LSB entry >> (probably superfluous with the next step…) >> * reboot and examine syslog to see if weewx start delayed until after >> ‘Reached target Network' >> >> On 5 Aug 2020, at 3:07 pm, Bill Arthur wrote: >> >> Google Groups does NOT like a file names syslog. Perhaps syslog.txt will >> get through. >> >> On Tuesday, August 4, 2020 at 2:24:23 PM UTC-5 Bill Arthur wrote: >> >>> Gary, >>> I'll grab and post the info this evening. >>> It looks like this happens only when booting, as if weewx starts before >>> the WiFi has stabilized. >>> >>> On Tuesday, August 4, 2020 at 3:30:09 AM UTC-5 gjr80 wrote: >>> >>>> Bill, >>>> >>>> For some reason the driver was unable to communicate with (one of) your >>>> GW1000(s). Before you get the log could you set debug = 3 in weewx.conf, >>>> restart WeeWX then post the log from startup through until the error. >>>> Would >>>> also help if you could post your [GW1000] stanza from WeeWX.conf. >>>> >>>> Gary >>>> >>>> >> -- >> 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/5e7aaf86-ebc7-47b1-9bf1-95c92aeeb088n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/5e7aaf86-ebc7-47b1-9bf1-95c92aeeb088n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> <syslog.txt> >> >> >> > -- > 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/648e4930-42a0-4b61-8f58-41cc75276cebo%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/648e4930-42a0-4b61-8f58-41cc75276cebo%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- 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/bb6aad07-8e3c-4857-928b-4f2929263166n%40googlegroups.com.
