Comments below.
Gary
On Monday, 28 December 2020 at 11:22:30 UTC+10 vince wrote:
> Agree.
>
> Also thanks for the reminder re: wee_config --reconfigure. I had not seen
> magic buried in a driver that asked questions when you reconfigure. That
> kinda blows up scripted installs to some extent
Agree.
Also thanks for the reminder re: wee_config --reconfigure. I had not seen
magic buried in a driver that asked questions when you reconfigure. That
kinda blows up scripted installs to some extent for folks like me who use
--no-prompt a lot.
These might be nits but I thought I'd mention
I think the install instructions are clear and concise. At the end of the
day if you choose not to follow them a degree of caveat emptor applies. I
believe the current loop_on_init setting is appropriate and see no need to
change it (experience shows if I did then the ‘stop polluting my logs’
b
by the install script...
>> I assume it's to set in the [GW1000] stanza - that's where I added it now.
>>
>>
>> Forwarded Message
>> Subject: [weewx-user] Re: gw1000 driver fail on wifi loss
>> Date: Sun, 27 Dec 2020 13:12:19 -0800 (PST)
>&
et by the install script...
> I assume it's to set in the [GW1000] stanza - that's where I added it now.
>
>
> ---- Forwarded Message --------
> Subject: [weewx-user] Re: gw1000 driver fail on wifi loss
> Date: Sun, 27 Dec 2020 13:12:19 -0800 (PST)
> From: g
I had the same issue like Vince the other day - and loop_on_init
hadn't been set by the install script...
I assume it's to set in the [GW1000] stanza - that's where I added it now.
Forwarded Message
Subject: [weewx-user] Re: gw1000 driver fail on
suggestion: gw1000 install set loop_on_init to true by default. we will always
have this kind of problem when the wifi (re)starts and weewx races ahead of it
> On 28 Dec 2020, at 8:12 am, gjr80 wrote:
>
> That would explain the behaviour then, if loop_on_init is not set the loss of
> connectiv
That would explain the behaviour then, if loop_on_init is not set the loss
of connectivity with the station (for whatever reason) will cause WeeWX to
exit as it does with any other driver. I will make a point of pulling the
network on my GW1000 and confirming the driver and loop_on_init work as
(unsure if this blasted google groups new interface ate my draft reply -
grr...)
loop_on_init was not set at all, so it's sure acting like the default is
False.
I'll define it as True for the next time, which hopefully won't need
testing for a long time
Thanks.
On Sunday, December 27,
Vince,
Thank you. From memory the driver should retry continuously when the
network returns if loop_on_init = True in weewx.conf (though I am not sure
I tested this by turning of my network). Can you confirm the loop_on_init
setting at the time?
Gary
On Monday, 28 December 2020 at 03:54:33 UT
10 matches
Mail list logo
