If you're using systemd and once the network recovers things work again
just do the following

systemctl edit weewx.service

[Unit]
...
StartLimitIntervalSec=0

[Service]
...
WatchdogSec=2s
Restart=always
RestartSec=2s

Then systemd will just keep trying to load the program until manually
stopped

On Wed, 5 Aug 2026 at 21:30, 'Michael Waldor' via weewx-user <
[email protected]> wrote:

> Yes. And that's necessary because typically the driver gets a connection
> only after its second try.
>
> W.r.t. the error message/crash: This only happens IF IP network is not
> available (I now avoid that situation by an improved systemd setup of my
> raspberry pi4). Otherwise there is no such crash. Thus a fix is not really
> mandatory, it's only recommended to improve on sane error recovery.
>
> John Smith <[email protected]> schrieb am Mi., 5. Aug. 2026,
> 13:21:
>
>> Do you have loop_on_init = True at the top of your weewx.conf file?
>>
>> On Wed, 5 Aug 2026 at 16:18, 'Michael Waldor' via weewx-user <
>> [email protected]> wrote:
>>
>>> Of course the driver EcowittHttp relies on a working network connection.
>>> But during boot weewx might be started too early before network is up. In
>>> that exceptional  case weewx will crash:
>>>
>>> CRITICAL __main__: **** File "/etc/weewx/bin/user/ecowitt_http.py", line
>>> 6775> CRITICAL __main__: **** if self.collector.device.model is not None:
>>> CRITICAL __main__: **** File "/etc/weewx/bin/user/ecowitt_http.py", line
>>> 13722> CRITICAL __main__: **** version_data = self.api.get_version()
>>> CRITICAL __main__: **** File "/etc/weewx/bin/user/ecowitt_http.py", line
>>> 7224> CRITICAL __main__: **** raise DeviceIOError(f"Failed to obtain
>>> 'get_version' data: {e}")> CRITICAL __main__: ****
>>> user.ecowitt_http.DeviceIOError: Failed to obtain 'get> CRITICAL __main__:
>>> **** Exiting.
>>>
>>> I myself have resolved that issue on my raspberry pi4 by enabling "wait
>>> on network" before starting other services.
>>>
>>> --
>>> 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 visit
>>> https://groups.google.com/d/msgid/weewx-user/8abdb32e-9590-40c9-9649-664daaafd85cn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/8abdb32e-9590-40c9-9649-664daaafd85cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/yhzIxvDzpy8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion visit
>> https://groups.google.com/d/msgid/weewx-user/CAGTinV7sD6FCXFZkz0ThEnmZ8V89omRg-v-A7SLRGr%2Bx99uvoQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CAGTinV7sD6FCXFZkz0ThEnmZ8V89omRg-v-A7SLRGr%2Bx99uvoQ%40mail.gmail.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 visit
> https://groups.google.com/d/msgid/weewx-user/CAAwHSbYAeOSA1ethnH1viebxYosdb-mKZg0sJ%2B0rmTQkM7Ohbw%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAAwHSbYAeOSA1ethnH1viebxYosdb-mKZg0sJ%2B0rmTQkM7Ohbw%40mail.gmail.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 visit 
https://groups.google.com/d/msgid/weewx-user/CAGTinV553kaQ9FuAn0aiRRUJq2d6UQc%2BbExfOL%3DAPpdVgBWZPQ%40mail.gmail.com.

Reply via email to