No, those are using sockets like how you and I think sockets are. I'm familiar with traditional sockets (my SocketLogger driver, and I forked the meteostick driver to use sockets).... and I'm familiar with websockets, but this is using socket.io which is a websocket, but not a normal websocket apparently. It's designed to support old browsers so they use a bit of a custom algo to make it happen.
Since AW is using https and not wss, only the socketIO-client Python lib will work, but when trying to connect to the endpoint it gives a 404. But using the same endpoint on an online JavaScript socket.io test tool, its a success. Could be a limitation with the lib. The AW socket.io endpoint is for the real-time streaming data from AmbientWeather. Perhaps plan B is to implement a time.sleep() in the driver and just request data every 10 seconds (or something) and submit to the loop. Downside could be duplicate timestamps, unless the weewx loop already allocates for that? Which could be a non-issue. On Tuesday, August 14, 2018 at 11:39:10 PM UTC-4, gjr80 wrote: > > So nothing in the vantage or ws1 drivers or restx.py to help? > > 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]. For more options, visit https://groups.google.com/d/optout.
