Thanks for all of the feedback - brilliant!
Mike - I was a bit wary of claiming too much 'copyright' as I must admit
I've "borrowed" quite a bit from your "pmon" extension.
I noticed that using the "wee_extension" install method only put into the
config file the lines in 'config' section of the 'install.py' file. However
the driver itself has the 'confeditor_loader' function that I must have got
be run sometime in the past (just putting the code in the directory and
using the 'wee_config' reconfigure to switch to the new driver perhaps???)
and that has commented lines which I think is much better.
I'll also change the name. the XC0422 was the only clone that I had access
to and I didn't want to make claims that I could not back up by calling it
anything else. However it would seem that it does work on other 'clones'
and so using the original name woudl be netter.
Dr Bob (name taken from the old Muppet sketch per chance???), I can put in
a delay (with the delay length driven by an optional parameter with a
default of 5 seconds). I must admit that the network traffic didn't bother
me on my home local network (especially when you look at the garbage my
Apple TV puts onto the network) but this is a good idea.
Also I'll add in the suggestion for the systemctl file. In the 'readme' I
mention that you should put in references to make sure the network is up
and running so the Weewx daemon will not cause problems on startup.
Gary - Thanks for the suggestions. I'll read to read up on 'markdown' and
give that a go.
Back with another go shortly. Also thinking about using the 'HISTORY' data
to see if there are gaps in the Weewx databse that can be filled in by the
console, but that will be V2.
Any thoughts about sampling the SDETUP packet more often to detect console
unit changes or is just telling people to restart Weewx OK?
Susan
