Re: [weewx-user] Re: PWS data format for Interceptor

Hello, everyone I realize this is a rather old entry, but I'd like to share my findings. I've had some success on connecting to the realtime API using the socketIO-client-nexus library Apparently it's regarding an issue with the socketio protocol used by the AW server, since the original

Re: [weewx-user] Re: PWS data format for Interceptor

I have not. I was hoping someone from AW would reply as well. You may be better off with the node developer for the time being. AW is using socket.io which seems very node friendly, and not so much Python. On Monday, August 20, 2018 at 4:05:08 PM UTC-4, Douglas Krug wrote: > > @pat Have you

Re: [weewx-user] Re: PWS data format for Interceptor

@pat Have you gotten any further with this? Really disappointed to see that no one from Ambient Weather has chimed in or even sent me an email to say that they won't for [insert reasons here]. On Thursday, August 16, 2018 at 12:54:50 PM UTC-4, Pat wrote: > > That's my thought is trying to find

Re: [weewx-user] Re: PWS data format for Interceptor

That's my thought is trying to find the right combination. The documentation isn't exactly complete, but looking at the "supported" node library they reference, it shows the URL they are using. But they explicitly define websockets there too

Re: [weewx-user] Re: PWS data format for Interceptor

I've sent this conversation to supp...@ambientweather.com to see if they could offer some guidance or get involved with the discussion here. They have a Facebook API group for questions and discussion, but I think they didn't expect it to be so unloved! Nobody had posted a single comment there

Re: [weewx-user] Re: PWS data format for Interceptor

I guess I was wrong! I find it hard to believe that the Python socket.io library is incapable of handling such a simple case. The problem must be some combination of getting the base host, api endpoint, and parameters right. -tk On Thu, Aug 16, 2018 at 8:34 AM Pat wrote: > I tried that too

Re: [weewx-user] Re: PWS data format for Interceptor

I tried that too and couldn't get it to work. Forgot to mention that. Trying it a couple of different ways again, I get the apiKey is missing: with SocketIO('https://api.ambientweather.net/v1/devices?applicationKey=YOUR_APP_KEY=YOUR_API_KEY', 443, LoggingNamespace, verify=False ) as

Re: [weewx-user] Re: PWS data format for Interceptor

I'm betting this is a ssl certificate problem. Try setting verify=False. -tk On Thu, Aug 16, 2018 at 8:15 AM Pat wrote: > I'm still thinking about this, and since I can't get the socket.io real > time stream > > to work in

Re: [weewx-user] Re: PWS data format for Interceptor

I'm still thinking about this, and since I can't get the socket.io real time stream to work in Python, I thought about using a timer to poll the endpoint. However it looks like they only update the endpoint every 5

Re: [weewx-user] Re: PWS data format for Interceptor

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

Re: [weewx-user] Re: PWS data format for Interceptor

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 weewx-user+unsubscr...@googlegroups.com. For

Re: [weewx-user] Re: PWS data format for Interceptor

Proving to be a bit of a challenge. Does anyone have any socket.io Python experience? I'm following the dev guides but the endpoint keeps coming up as 404. If I try it with an online socket.io test tool, it works fine (using javascript). Hmm... On Tuesday, August 14, 2018 at 11:55:50 AM UTC-4,

Re: [weewx-user] Re: PWS data format for Interceptor

That sounds amazing. I haven’t requested the key yet, but will now and send to you. On Tue, Aug 14, 2018 at 11:49 AM Pat wrote: > It should be doable. Just need to get Python connected to their websocket > realtime endpoint and the rest of it (weewx driver wise) should be similar > to the

Re: [weewx-user] Re: PWS data format for Interceptor

It should be doable. Just need to get Python connected to their websocket realtime endpoint and the rest of it (weewx driver wise) should be similar to the drivers I've written in the past. I haven't played with Python websockets yet, but sounds fun to tinker with and figure out! If you're

Re: [weewx-user] Re: PWS data format for Interceptor

*I no longer am using my Ambient ObserverIP, so I don't have test data to use.* I do of course, so let me know if I could help in this regard. On Tuesday, August 14, 2018 at 9:44:33 AM UTC-4, Douglas Krug wrote: > > *So maybe the thought here is to have your station submit to > AmbientWeather

Re: [weewx-user] Re: PWS data format for Interceptor

*So maybe the thought here is to have your station submit to AmbientWeather natively, and create a driver which gets the data from Ambient's real-time subscribe system and submits it to weewx for archival?* Yes, that's the idea exactly! Ambient doesn't let you upload to their server unless you