Last but not least, here's a driver tips wiki page that covers the basics of driver packaging etc... https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips . I'd welcome any feedback here as there's still a few things I don't fully understand like why the file structure of bin/user seems to drop the file in /usr/share/weewx/user on my Ubuntu VMs. I also still suspect there's an opportunity to place the driver stanza in the "right" location under the Station stanza but after reading the wee_config source I think it likely belongs there kind of like the report cleanup stuff does. That or else it could go into wee_extension after checking to see that this is indeed a driver.
Feedback welcome of course. Billy On Saturday, July 2, 2022 at 4:12:48 PM UTC-7 Billy Jackson wrote: > I think I got it sorted most of the way. There's still an opportunity to > figure out where to place the stanza on first install, and I can see it > being done by wee_config when it changes drivers but am not quite sure how > to pull that off in the install.py. It could also likely go into > wee_extension source to detect if it's a driver but I'm not quite good > enough with python to pull that off. > > If anyone would like to peer review/look at the installation instructions > or source feel free. https://github.com/livysdad27/tempestWS is where > it's at. > > Billy > > On Saturday, July 2, 2022 at 12:01:04 PM UTC-7 Billy Jackson wrote: > >> Thanks Vince, I'll go look up ecowitt . Also, I was banging my head >> against the wall about why the Belchertown install file puts a stanza >> replacing all of stdReport in the right place and found the code where it >> "reshuffles" skin stanzas to make sure they come before ftp/rsync. >> >> I'm wondering if I can access the entire configobject from the install.py >> but likely I don't actually want to :^). Seems a bit intense. >> >> In other news the Websocket driver is working nicely and comparing it to >> the restAPI driver does a good job of capturing a LOT more wind data. >> Biggest thing I lose from not using the UDP data is rssi strength for the >> hub/tempeest but I finally have that nailed down pretty good in my >> installation so I'm not too worried there. >> >> Thanks for all the help. Once I work through this, get a readme into the >> module I'll post it for folks to try out/test. I'll also consider trying >> to figure out how to do a pull request for the wiki and at least covering >> the basics of a driver install. >> >> Billy >> >> On Saturday, July 2, 2022 at 8:56:50 AM UTC-7 [email protected] wrote: >> >>> You might want to require the user run wee_config themselves to pick >>> which station type they want to activate. Sometimes folks install the >>> driver and then configure a lot of things manually 'before' activating it. >>> My hazy recollection is some drivers (Gary's ecowitt one perhaps) might >>> even ask questions as well when you activate them with wee_config. >>> >>> -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/3235f0da-29ac-4639-8ec0-551989a06252n%40googlegroups.com.
