I think somebody else was working a while back on a combination driver that could get WS and/or UDP data. You might want to ask around over at the WF Forums to see how far they got.
On Tuesday, May 3, 2022 at 9:49:38 PM UTC-7 [email protected] wrote: > Hi, > > I'm trying to write a driver for my Tempest WS. I currently have the UDP > driver from captain-coredump up and running (thank you!) on a pi but I'd > like to pump data straight from the websockets API into weewx also. I may > expand it to capture archive packets from the rest API also. > > The prototype is here... https://github.com/livysdad27/tempestAPI > > I borrowed a LOT from captain-coredump's driver. Where I'm struggling is > with the getLoopPackets generator. I've attempted to use the on_message > handler for this but have read in another thread that it doesn't work well > due to running in a separate thread. My websockets code is a bit simple > and I'm not completely sure how drivers get called for sure. > > Is it even realistic to try and run a websocket-client app implementation > with "run_forever" and expect it to work correctly with weewx? My > suspicion is weewx is starting, entering the websocket app and sitting > there forever because I don't get report or other messages after it kicks > off. > > Super grateful for any help/pointers! > > Billy > -- 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/90537d08-ce55-4a70-9340-eed727c42578n%40googlegroups.com.
