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/051a8565-40b7-4b79-9297-e8e905efce20n%40googlegroups.com.
