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 them:
- If you use the --no-prompt switch to wee_config you get only a partial
stanza installed (I didn't check the code to see if this matters or not).
You might want to consider having it write out all the items if this
matters.
- init_on_loop gets added right under the version string in weewx.conf
with no comment or whitespace. That might be easy to overlook later on.
- uninstalling the driver leaves the init_on_loop item in weewx.conf.
Admittedly, it is unusual to uninstall a driver as folks would just use
wee_config to point to a different one (if they follow the instructions
that is :-)
But the driver has been rock solid for me here, so it's of course much
appreciated.
On Sunday, December 27, 2020 at 4:30:55 PM UTC-8 gjr80 wrote:
> 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’
> brigade will start complaining).
>
> Of course anyone is free to fork the driver...
>
> 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/76fec035-b204-43a6-a9a3-bfb8c456f974n%40googlegroups.com.
