[weewx-user] c84612 GAS utility setup?

[Charlie Huang]

Hi,

I don't know what's going on but when I run "sudo weewxd weewx.conf" it 
does not show anything.
Here is my GAS screenshot. 192.168.0.64 is my raspberry pi local ip 
address. I did not change anything else.

[image: 20180815134228.png] 

And my log:

Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: sensor 
map: None
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: using 
station serial 7FFF (sensitive)
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: using 
ping interval 120s
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: using 
sensor interval 1m
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: using 
history interval 3 (15m)
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: mode is 
listen
Aug 14 22:40:39 raspberrypi weewx[3792]: interceptor: MainThread: listen on 
:80
Aug 14 22:40:39 raspberrypi weewx[3792]: import of driver failed: [Errno 
98] Address already in use ()
Aug 14 22:40:39 raspberrypi weewx[3792]: engine: Unable to load driver: 
[Errno 98] Address already in use
Aug 14 22:40:39 raspberrypi weewx[3792]:   Exiting...

-- 
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 more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: C84612 with GW1000U gateway

[Charlie Huang]

what's the GAS utility? i'm pretty on this step. need some help.

On Tuesday, January 10, 2017 at 10:13:16 AM UTC+8, Tony McConnell wrote:
>
> I am having trouble configuring weewx to grab data from my GW1000U gateway 
> and C84612 weather station. I have installed weewx to an Ubuntu Server 
> (fresh install of ubuntu I might add), installed the driver from this 
> , configured weewx 
> using the same settings as mentioned in "Example: GW1000U" and set the 
> proxy on the GAS to the same address as my server. Not really sure where to 
> go from there because when I run 
>
> sudo weewxd weewx.conf
>
> nothing is displayed on the console. Even tried with -r argument with no 
> luck.
>
> Not sure what I'm missing, any advice?
>
> Thanks
>

-- 
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 more options, visit https://groups.google.com/d/optout.

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

[gjr80]

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 more options, visit https://groups.google.com/d/optout.

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

[Pat]

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, Douglas Krug wrote:
>
> 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 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 comfortable I may need your Ambient Weather API and APP keys 
>> (sent as a private message so its not public) to be able to read the data 
>> as a way to validate the driver. You should be able to change these when 
>> done to re-secure your keys. 
>>
>> On Tuesday, August 14, 2018 at 10:06:09 AM UTC-4, Douglas Krug wrote:
>>>
>>> *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 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 buy a $150 license from them. But if you own their 
 equipment, there's no charge to upload. Since there's a way to subscribe 
 to 
 Ambientweather.net via their API, there's for sure a possibility to bring 
 it into Weewx. In fact, there doesn't even need to be node servers and 
 routers passing the data, but I don't know how to code, so I wouldn't be 
 able to execute the concept. The ambient2pwsweather server is needed if 
 you're not running Weewx, but if you are, it's redundant since you can 
 just 
 post to PWSweather from Weewx. It's the ambientweather.net piece that 
 is tricky due to their restrictions. However, everyone with any internet 
 connected Ambient Weather device and up-to-date firmware can upload to 
 ambientweather.net for free. So if there was just a way to subscribe 
 to data from ambientweather.net and bring it into Weewx, there would 
 be no need for Ambient Weather IP sniffing or listening, just an internet 
 connection, Weewx and a plugin.

 But I'm a home automation geek. I already have an always on Node.js 
 server running. I was reluctant to add another router, but I have several 
 of them and it was the easiest way to get data into Weewx. So adding 
 another piece to the puzzle doesn't phase me that much. It *can* all 
 be so simple, but it takes talented developers to do the work.

 On Tue, Aug 14, 2018 at 9:14 AM Pat  wrote:

>>> Taking a look at the ambient2pwsweather project, it looks like he's 
> really using the ambient-weather-api 
>  project as his heavy 
> lifting for ambient. And looking at the project it looks like what we 
> talked about where AmbientWeather's API documentation 
>  talks about how to 
> subscribe to data, but not how to submit data. 
>
> 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? 
>
> I've also upgraded to a Davis Vantage Pro 2, so I no longer am using 
> my Ambient ObserverIP, so I don't have test data to use. 
>
>
> On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:
>>
>> The API into weewx would be a driver. Typically the weather equipment 
>> is directly connected and the driver would control the weather station. 
>> That's why I wrote the socket driver a few years ago because my 
>> equipment 
>> isn't directly connected. 
>>
>> The good news is the interceptor driver has multiple ways to input 
>> data into weewx, so it's probably as much of an API as you're going to 
>> find. By sending HTTP data to the driver's web server, it can then pass 
>> it 
>> to weewx like a standard driver would.
>>
>> That being said, I can't help but to think about others who may want 
>> to publish data to Ambient as well. As mentioned on wxforum, the Ambient 
>> documentation is kind of lacking for a developer and what the value 
>> names 
>> are to submit (and how... GET vs. POST). But if there's a project 

Re: [weewx-user] Re: Skins

[Pat]

Thanks everyone. Appreciate it! Made some good progress last couple of days 
with the skin file. At this point I'm letting it "cook" to see if I've 
missed anything. 

While we're on the topic of the skin I'm working on, if @gjr80 is lurking 
about take a look at my question on your weewx highcharts extension 
 on GitHub. 


On Tuesday, August 14, 2018 at 9:04:47 PM UTC-4, Thomas Keffer wrote:
>
> I agree. That's a nicely done website, Pat. I like how you've integrated 
> real-time and forecasting elements into a good looking interface.
>
> -tk
>
> On Tue, Aug 14, 2018 at 4:57 PM Colin Larsen  > wrote:
>
>> Pat your website is fantastic, I'd love to be able to use a ported skin 
>> once you have it done. Happy to donate for your time and effort :)
>>
>> On Saturday, 11 August 2018 12:42:55 UTC+12, Pat wrote:
>>>
>>> What kind of skin are you looking for? 
>>>
>>> For what it's worth, I'm working on porting my site 
>>>  to a skin. It has a couple years of 
>>> custom code I've created that I need to port over to weewx skins. Hope to 
>>> have it in a beta form soon. 
>>>
 -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Skins

[Thomas Keffer]

I agree. That's a nicely done website, Pat. I like how you've integrated
real-time and forecasting elements into a good looking interface.

-tk

On Tue, Aug 14, 2018 at 4:57 PM Colin Larsen  wrote:

> Pat your website is fantastic, I'd love to be able to use a ported skin
> once you have it done. Happy to donate for your time and effort :)
>
> On Saturday, 11 August 2018 12:42:55 UTC+12, Pat wrote:
>>
>> What kind of skin are you looking for?
>>
>> For what it's worth, I'm working on porting my site
>>  to a skin. It has a couple years of
>> custom code I've created that I need to port over to weewx skins. Hope to
>> have it in a beta form soon.
>>
>>> --
> 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 more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Skins

[Colin Larsen]

Pat your website is fantastic, I'd love to be able to use a ported skin 
once you have it done. Happy to donate for your time and effort :)

On Saturday, 11 August 2018 12:42:55 UTC+12, Pat wrote:
>
> What kind of skin are you looking for? 
>
> For what it's worth, I'm working on porting my site 
>  to a skin. It has a couple years of 
> custom code I've created that I need to port over to weewx skins. Hope to 
> have it in a beta form soon. 
>
>>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Skins

[Colin Larsen]

Pat your website is fantastic, I'd love to be able to use a ported skin 
once you have it done. Happy to donate for your time and effort :)

On Saturday, 11 August 2018 12:42:55 UTC+12, Pat wrote:
>
> What kind of skin are you looking for? 
>
> For what it's worth, I'm working on porting my site 
>  to a skin. It has a couple years of 
> custom code I've created that I need to port over to weewx skins. Hope to 
> have it in a beta form soon. 
>
> On Wednesday, August 8, 2018 at 3:04:27 AM UTC-4, Bengt Carlsson wrote:
>>
>> Yes, but cant find any similar.
>>
>> Bengt C
>>
>>  
>>
>> *Från:* weewx...@googlegroups.com  *För *Andrew 
>> Milner
>> *Skickat:* den 8 augusti 2018 08:44
>> *Till:* weewx-user 
>> *Ämne:* [weewx-user] Re: Skins
>>
>>  
>>
>> Have you looked in the wiki??
>>
>>  
>>
>>  
>>
>>
>> On Wednesday, 8 August 2018 09:05:19 UTC+3, John Clark wrote:
>>
>> Is there a "repository" of various "Standard" skins that may be 
>> downloaded? Or a "how-to" manual? So far, understanding "skin theory" has 
>> been problematic. I have seen a few I love, but have no idea on how to 
>> reproduce them. Need to "get my foot in the door" so to speak.
>>
>> -- 
>> *John Clark*
>>
>> -- 
>> 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+...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout 
>> 
>> .
>>
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] First installation - station web page not found

[vince]

On Tuesday, August 14, 2018 at 2:34:50 PM UTC-7, Charlie Huang wrote:
>
> i think the problem is i don't even know where the config file is...
>
>
http://www.weewx.com/docs/usersguide.htm#Where_to_find_things

The config file is in different places depending on whether you used 
'setup.py' to install, or if you used a .deb package. 

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] First installation - station web page not found

[Charlie Huang]

i think the problem is i don't even know where the config file is...

On Wednesday, August 15, 2018 at 5:08:21 AM UTC+8, Thomas Keffer wrote:
>
> When you ran the main program, weewxd, you gave it an invalid path to your 
> configuration file.
>
> -tk
>
> On Tue, Aug 14, 2018 at 1:59 PM Charlie Huang  > wrote:
>
>> Hi,
>>
>> I just reinstalled the weewx and chose "Simulator" option instead of 
>> "ws28xx".
>> Now I have the web page displayed but the data it shows are not correct.
>>
>> Here is the log:
>>
>> Aug 14 13:55:16 raspberrypi weewx[467]: manager: Added record 2018-08-14 
>> 13:55:00 PDT (1534280100) to database 'weewx.sdb'
>> Aug 14 13:55:17 raspberrypi weewx[467]: manager: Added record 2018-08-14 
>> 13:55:00 PDT (1534280100) to daily summary in 'weewx.sdb'
>> Aug 14 13:55:19 raspberrypi weewx[467]: cheetahgenerator: Generated 14 
>> files for report StandardReport in 1.22 seconds
>> Aug 14 13:55:20 raspberrypi weewx[467]: imagegenerator: Generated 12 
>> images for StandardReport in 0.72 seconds
>> Aug 14 13:55:20 raspberrypi weewx[467]: copygenerator: copied 0 files to 
>> /var/www/html/weewx
>> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Initializing weewx 
>> version 3.8.0
>> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Using Python 2.7.13 
>> (default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516]
>> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Platform 
>> Linux-4.14.52-v7+-armv7l-with-debian-9.4
>> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Locale is 'en_US.UTF-8'
>> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Unable to open 
>> configuration file /home/pi/weewx.conf
>>
>> On Wednesday, August 15, 2018 at 4:04:23 AM UTC+8, Thomas Keffer wrote:
>>>
>>> Charlie,
>>>
>>> You haven't given us much information to go on. At a minimum, include 
>>> the logs. See the Wiki post *Help! Posting to weewx-user 
>>> *.
>>>
>>> -tk
>>>
>>> On Tue, Aug 14, 2018 at 11:16 AM Charlie Huang  
>>> wrote:
>>>
 Hey,

 I have a WS2816/C84612 wx station and I now installing weewx on my 
 Raspberry pi. But i can't see the station web page it has been about 20 
 minutes.
 Anyone knows what's happening?

 -- 
 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+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] First installation - station web page not found

[Thomas Keffer]

When you ran the main program, weewxd, you gave it an invalid path to your
configuration file.

-tk

On Tue, Aug 14, 2018 at 1:59 PM Charlie Huang  wrote:

> Hi,
>
> I just reinstalled the weewx and chose "Simulator" option instead of
> "ws28xx".
> Now I have the web page displayed but the data it shows are not correct.
>
> Here is the log:
>
> Aug 14 13:55:16 raspberrypi weewx[467]: manager: Added record 2018-08-14
> 13:55:00 PDT (1534280100) to database 'weewx.sdb'
> Aug 14 13:55:17 raspberrypi weewx[467]: manager: Added record 2018-08-14
> 13:55:00 PDT (1534280100) to daily summary in 'weewx.sdb'
> Aug 14 13:55:19 raspberrypi weewx[467]: cheetahgenerator: Generated 14
> files for report StandardReport in 1.22 seconds
> Aug 14 13:55:20 raspberrypi weewx[467]: imagegenerator: Generated 12
> images for StandardReport in 0.72 seconds
> Aug 14 13:55:20 raspberrypi weewx[467]: copygenerator: copied 0 files to
> /var/www/html/weewx
> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Initializing weewx
> version 3.8.0
> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Using Python 2.7.13
> (default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516]
> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Platform
> Linux-4.14.52-v7+-armv7l-with-debian-9.4
> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Locale is 'en_US.UTF-8'
> Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Unable to open
> configuration file /home/pi/weewx.conf
>
> On Wednesday, August 15, 2018 at 4:04:23 AM UTC+8, Thomas Keffer wrote:
>>
>> Charlie,
>>
>> You haven't given us much information to go on. At a minimum, include the
>> logs. See the Wiki post *Help! Posting to weewx-user
>> *.
>>
>> -tk
>>
>> On Tue, Aug 14, 2018 at 11:16 AM Charlie Huang 
>> wrote:
>>
>>> Hey,
>>>
>>> I have a WS2816/C84612 wx station and I now installing weewx on my
>>> Raspberry pi. But i can't see the station web page it has been about 20
>>> minutes.
>>> Anyone knows what's happening?
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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 more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] First installation - station web page not found

[Charlie Huang]

Hi,

I just reinstalled the weewx and chose "Simulator" option instead of 
"ws28xx".
Now I have the web page displayed but the data it shows are not correct.

Here is the log:

Aug 14 13:55:16 raspberrypi weewx[467]: manager: Added record 2018-08-14 
13:55:00 PDT (1534280100) to database 'weewx.sdb'
Aug 14 13:55:17 raspberrypi weewx[467]: manager: Added record 2018-08-14 
13:55:00 PDT (1534280100) to daily summary in 'weewx.sdb'
Aug 14 13:55:19 raspberrypi weewx[467]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.22 seconds
Aug 14 13:55:20 raspberrypi weewx[467]: imagegenerator: Generated 12 images 
for StandardReport in 0.72 seconds
Aug 14 13:55:20 raspberrypi weewx[467]: copygenerator: copied 0 files to 
/var/www/html/weewx
Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Initializing weewx version 
3.8.0
Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Using Python 2.7.13 
(default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516]
Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Platform 
Linux-4.14.52-v7+-armv7l-with-debian-9.4
Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Locale is 'en_US.UTF-8'
Aug 14 13:55:44 raspberrypi weewx[3386]: engine: Unable to open 
configuration file /home/pi/weewx.conf

On Wednesday, August 15, 2018 at 4:04:23 AM UTC+8, Thomas Keffer wrote:
>
> Charlie,
>
> You haven't given us much information to go on. At a minimum, include the 
> logs. See the Wiki post *Help! Posting to weewx-user 
> *.
>
> -tk
>
> On Tue, Aug 14, 2018 at 11:16 AM Charlie Huang  > wrote:
>
>> Hey,
>>
>> I have a WS2816/C84612 wx station and I now installing weewx on my 
>> Raspberry pi. But i can't see the station web page it has been about 20 
>> minutes.
>> Anyone knows what's happening?
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] First installation - station web page not found

[Thomas Keffer]

Charlie,

You haven't given us much information to go on. At a minimum, include the
logs. See the Wiki post *Help! Posting to weewx-user
*.

-tk

On Tue, Aug 14, 2018 at 11:16 AM Charlie Huang  wrote:

> Hey,
>
> I have a WS2816/C84612 wx station and I now installing weewx on my
> Raspberry pi. But i can't see the station web page it has been about 20
> minutes.
> Anyone knows what's happening?
>
> --
> 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 more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

[weewx-user] How to send AS3935 Thunder Board (SwitchDocs) data to weewx.sdb

[bgrattan]

Hello,

I am using an Arduino with the SwitchDoc Labs Thunder Board - AS3935 for 
lightning detection and would like to incorporate the data in my weewx 
station (weewx.tgz, ubuntu 16.04, VP2+).
Not being much of a programmer, I wonder if anyone has tried this setup?
Since I'm running ubuntu on a linux machine (Intel NUC), I wonder if I need 
to setup a separate Rpi to send the data to the weewx machine (I have an 
extra if this is easier). The Thunder Board is presently configured to send 
data via MQTT to pubsub.com which I don't want to do but am not sure how to 
modify the Arduino code.
Any help on this would be greatly appreciated. Thanks.

Bob
http://grattans.org/wx

-- 
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 more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: First installation - station web page not found

[vince]

On Tuesday, August 14, 2018 at 11:16:53 AM UTC-7, Charlie Huang wrote:
>
> I have a WS2816/C84612 wx station and I now installing weewx on my 
> Raspberry pi. But i can't see the station web page it has been about 20 
> minutes.
> Anyone knows what's happening?
>

Not without your syslogs 

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Degrees measurement in exact figures

[Thomas Keffer]

Fixed in commit 2b5764
.
Let me know if this still causes problems.

Antonis: While only the file weewx/accum.py was affected, Version 3.4.0 is
2-1/2 years old. Many other things have probably changed since then. You
should upgrade if you want this fix.

-tk

-tk

On Mon, Aug 13, 2018 at 6:19 AM Antonis Katsonis <
nafpaktia.weat...@gmail.com> wrote:

> The same happens with windGustDir.
>
> --
> 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 more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

[weewx-user] First installation - station web page not found

[Charlie Huang]

Hey,

I have a WS2816/C84612 wx station and I now installing weewx on my 
Raspberry pi. But i can't see the station web page it has been about 20 
minutes.
Anyone knows what's happening?

-- 
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 more options, visit https://groups.google.com/d/optout.

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

[Douglas Krug]

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 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 comfortable I may need your Ambient Weather API and APP keys
> (sent as a private message so its not public) to be able to read the data
> as a way to validate the driver. You should be able to change these when
> done to re-secure your keys.
>
> On Tuesday, August 14, 2018 at 10:06:09 AM UTC-4, Douglas Krug wrote:
>>
>> *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 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 buy a $150 license from them. But if you own their
>>> equipment, there's no charge to upload. Since there's a way to subscribe to
>>> Ambientweather.net via their API, there's for sure a possibility to bring
>>> it into Weewx. In fact, there doesn't even need to be node servers and
>>> routers passing the data, but I don't know how to code, so I wouldn't be
>>> able to execute the concept. The ambient2pwsweather server is needed if
>>> you're not running Weewx, but if you are, it's redundant since you can just
>>> post to PWSweather from Weewx. It's the ambientweather.net piece that
>>> is tricky due to their restrictions. However, everyone with any internet
>>> connected Ambient Weather device and up-to-date firmware can upload to
>>> ambientweather.net for free. So if there was just a way to subscribe to
>>> data from ambientweather.net and bring it into Weewx, there would be no
>>> need for Ambient Weather IP sniffing or listening, just an internet
>>> connection, Weewx and a plugin.
>>>
>>> But I'm a home automation geek. I already have an always on Node.js
>>> server running. I was reluctant to add another router, but I have several
>>> of them and it was the easiest way to get data into Weewx. So adding
>>> another piece to the puzzle doesn't phase me that much. It *can* all be
>>> so simple, but it takes talented developers to do the work.
>>>
>>> On Tue, Aug 14, 2018 at 9:14 AM Pat  wrote:
>>>
>> Taking a look at the ambient2pwsweather project, it looks like he's
 really using the ambient-weather-api
  project as his heavy
 lifting for ambient. And looking at the project it looks like what we
 talked about where AmbientWeather's API documentation
  talks about how to subscribe
 to data, but not how to submit data.

 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?

 I've also upgraded to a Davis Vantage Pro 2, so I no longer am using my
 Ambient ObserverIP, so I don't have test data to use.


 On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:
>
> The API into weewx would be a driver. Typically the weather equipment
> is directly connected and the driver would control the weather station.
> That's why I wrote the socket driver a few years ago because my equipment
> isn't directly connected.
>
> The good news is the interceptor driver has multiple ways to input
> data into weewx, so it's probably as much of an API as you're going to
> find. By sending HTTP data to the driver's web server, it can then pass it
> to weewx like a standard driver would.
>
> That being said, I can't help but to think about others who may want
> to publish data to Ambient as well. As mentioned on wxforum, the Ambient
> documentation is kind of lacking for a developer and what the value names
> are to submit (and how... GET vs. POST). But if there's a project that's
> successfully posting data to Ambient, then maybe a weewx extension could 
> be
> created to post to Ambient. An extension like the one for wunderground or
> PWSWeather might be easy enough to fork for Ambient. This would save the
> need of setting up and maintaining a node server (and help those here who
> don't know what node is). The more complicated things get, the more
> potential for something to break and you not catching it (like your node
> server crashing and 

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

[Pat]

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 comfortable I may need your Ambient Weather API and APP keys 
(sent as a private message so its not public) to be able to read the data 
as a way to validate the driver. You should be able to change these when 
done to re-secure your keys. 

On Tuesday, August 14, 2018 at 10:06:09 AM UTC-4, Douglas Krug wrote:
>
> *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 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 buy a $150 license from them. But if you own their 
>> equipment, there's no charge to upload. Since there's a way to subscribe to 
>> Ambientweather.net via their API, there's for sure a possibility to bring 
>> it into Weewx. In fact, there doesn't even need to be node servers and 
>> routers passing the data, but I don't know how to code, so I wouldn't be 
>> able to execute the concept. The ambient2pwsweather server is needed if 
>> you're not running Weewx, but if you are, it's redundant since you can just 
>> post to PWSweather from Weewx. It's the ambientweather.net piece that is 
>> tricky due to their restrictions. However, everyone with any internet 
>> connected Ambient Weather device and up-to-date firmware can upload to 
>> ambientweather.net for free. So if there was just a way to subscribe to 
>> data from ambientweather.net and bring it into Weewx, there would be no 
>> need for Ambient Weather IP sniffing or listening, just an internet 
>> connection, Weewx and a plugin.
>>
>> But I'm a home automation geek. I already have an always on Node.js 
>> server running. I was reluctant to add another router, but I have several 
>> of them and it was the easiest way to get data into Weewx. So adding 
>> another piece to the puzzle doesn't phase me that much. It *can* all be 
>> so simple, but it takes talented developers to do the work.
>>
>> On Tue, Aug 14, 2018 at 9:14 AM Pat > 
>> wrote:
>>
>>> Taking a look at the ambient2pwsweather project, it looks like he's 
>>> really using the ambient-weather-api 
>>>  project as his heavy 
>>> lifting for ambient. And looking at the project it looks like what we 
>>> talked about where AmbientWeather's API documentation 
>>>  talks about how to subscribe 
>>> to data, but not how to submit data. 
>>>
>>> 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? 
>>>
>>> I've also upgraded to a Davis Vantage Pro 2, so I no longer am using my 
>>> Ambient ObserverIP, so I don't have test data to use. 
>>>
>>>
>>> On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:

 The API into weewx would be a driver. Typically the weather equipment 
 is directly connected and the driver would control the weather station. 
 That's why I wrote the socket driver a few years ago because my equipment 
 isn't directly connected. 

 The good news is the interceptor driver has multiple ways to input data 
 into weewx, so it's probably as much of an API as you're going to find. By 
 sending HTTP data to the driver's web server, it can then pass it to weewx 
 like a standard driver would.

 That being said, I can't help but to think about others who may want to 
 publish data to Ambient as well. As mentioned on wxforum, the Ambient 
 documentation is kind of lacking for a developer and what the value names 
 are to submit (and how... GET vs. POST). But if there's a project that's 
 successfully posting data to Ambient, then maybe a weewx extension could 
 be 
 created to post to Ambient. An extension like the one for wunderground or 
 PWSWeather might be easy enough to fork for Ambient. This would save the 
 need of setting up and maintaining a node server (and help those here who 
 don't know what node is). The more complicated things get, the more 
 potential for something to break and you not catching it (like your node 
 server crashing and you don't know it for a few days). 

 I'm working on a skin for weewx now, but this could be a fun project to 
 think about - forking a PWSWeather 

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

[Douglas Krug]

*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 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 buy a $150 license from them. But if you own their 
> equipment, there's no charge to upload. Since there's a way to subscribe to 
> Ambientweather.net via their API, there's for sure a possibility to bring 
> it into Weewx. In fact, there doesn't even need to be node servers and 
> routers passing the data, but I don't know how to code, so I wouldn't be 
> able to execute the concept. The ambient2pwsweather server is needed if 
> you're not running Weewx, but if you are, it's redundant since you can just 
> post to PWSweather from Weewx. It's the ambientweather.net piece that is 
> tricky due to their restrictions. However, everyone with any internet 
> connected Ambient Weather device and up-to-date firmware can upload to 
> ambientweather.net for free. So if there was just a way to subscribe to 
> data from ambientweather.net and bring it into Weewx, there would be no 
> need for Ambient Weather IP sniffing or listening, just an internet 
> connection, Weewx and a plugin.
>
> But I'm a home automation geek. I already have an always on Node.js server 
> running. I was reluctant to add another router, but I have several of them 
> and it was the easiest way to get data into Weewx. So adding another piece 
> to the puzzle doesn't phase me that much. It *can* all be so simple, but 
> it takes talented developers to do the work.
>
> On Tue, Aug 14, 2018 at 9:14 AM Pat  wrote:
>
>> Taking a look at the ambient2pwsweather project, it looks like he's 
>> really using the ambient-weather-api 
>>  project as his heavy 
>> lifting for ambient. And looking at the project it looks like what we 
>> talked about where AmbientWeather's API documentation 
>>  talks about how to subscribe 
>> to data, but not how to submit data. 
>>
>> 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? 
>>
>> I've also upgraded to a Davis Vantage Pro 2, so I no longer am using my 
>> Ambient ObserverIP, so I don't have test data to use. 
>>
>>
>> On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:
>>>
>>> The API into weewx would be a driver. Typically the weather equipment is 
>>> directly connected and the driver would control the weather station. That's 
>>> why I wrote the socket driver a few years ago because my equipment isn't 
>>> directly connected. 
>>>
>>> The good news is the interceptor driver has multiple ways to input data 
>>> into weewx, so it's probably as much of an API as you're going to find. By 
>>> sending HTTP data to the driver's web server, it can then pass it to weewx 
>>> like a standard driver would.
>>>
>>> That being said, I can't help but to think about others who may want to 
>>> publish data to Ambient as well. As mentioned on wxforum, the Ambient 
>>> documentation is kind of lacking for a developer and what the value names 
>>> are to submit (and how... GET vs. POST). But if there's a project that's 
>>> successfully posting data to Ambient, then maybe a weewx extension could be 
>>> created to post to Ambient. An extension like the one for wunderground or 
>>> PWSWeather might be easy enough to fork for Ambient. This would save the 
>>> need of setting up and maintaining a node server (and help those here who 
>>> don't know what node is). The more complicated things get, the more 
>>> potential for something to break and you not catching it (like your node 
>>> server crashing and you don't know it for a few days). 
>>>
>>> I'm working on a skin for weewx now, but this could be a fun project to 
>>> think about - forking a PWSWeather extension to the AmbientWeather service 
>>> - (unless someone else reading this wants to give it a try).
>>>
>>>
>>> On Monday, August 13, 2018 at 10:34:09 PM UTC-4, Douglas Krug wrote:

 Hello again Pat,

 Thanks for commenting. This is basically a continuation of the 
 conversation we had on wxforum. I've got experience setting up node.js, 
 that shouldn't be a problem. I stumble across the ambient2pwsweather node 
 project and reached out to see if he would consider modifying it. He 
 wasn't 
 really interested if there was no API for Weewx, which to the best of my 
 understanding, there is not. I suggested Matthew Wall's interceptor 
 plugin, 
 to 

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

[Douglas Krug]

*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 buy a $150 license from them. But if you own their
equipment, there's no charge to upload. Since there's a way to subscribe to
Ambientweather.net via their API, there's for sure a possibility to bring
it into Weewx. In fact, there doesn't even need to be node servers and
routers passing the data, but I don't know how to code, so I wouldn't be
able to execute the concept. The ambient2pwsweather server is needed if
you're not running Weewx, but if you are, it's redundant since you can just
post to PWSweather from Weewx. It's the ambientweather.net piece that is
tricky due to their restrictions. However, everyone with any internet
connected Ambient Weather device and up-to-date firmware can upload to
ambientweather.net for free. So if there was just a way to subscribe to
data from ambientweather.net and bring it into Weewx, there would be no
need for Ambient Weather IP sniffing or listening, just an internet
connection, Weewx and a plugin.

But I'm a home automation geek. I already have an always on Node.js server
running. I was reluctant to add another router, but I have several of them
and it was the easiest way to get data into Weewx. So adding another piece
to the puzzle doesn't phase me that much. It *can* all be so simple, but it
takes talented developers to do the work.

On Tue, Aug 14, 2018 at 9:14 AM Pat  wrote:

> Taking a look at the ambient2pwsweather project, it looks like he's really
> using the ambient-weather-api
>  project as his heavy
> lifting for ambient. And looking at the project it looks like what we
> talked about where AmbientWeather's API documentation
>  talks about how to subscribe to
> data, but not how to submit data.
>
> 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?
>
> I've also upgraded to a Davis Vantage Pro 2, so I no longer am using my
> Ambient ObserverIP, so I don't have test data to use.
>
>
> On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:
>>
>> The API into weewx would be a driver. Typically the weather equipment is
>> directly connected and the driver would control the weather station. That's
>> why I wrote the socket driver a few years ago because my equipment isn't
>> directly connected.
>>
>> The good news is the interceptor driver has multiple ways to input data
>> into weewx, so it's probably as much of an API as you're going to find. By
>> sending HTTP data to the driver's web server, it can then pass it to weewx
>> like a standard driver would.
>>
>> That being said, I can't help but to think about others who may want to
>> publish data to Ambient as well. As mentioned on wxforum, the Ambient
>> documentation is kind of lacking for a developer and what the value names
>> are to submit (and how... GET vs. POST). But if there's a project that's
>> successfully posting data to Ambient, then maybe a weewx extension could be
>> created to post to Ambient. An extension like the one for wunderground or
>> PWSWeather might be easy enough to fork for Ambient. This would save the
>> need of setting up and maintaining a node server (and help those here who
>> don't know what node is). The more complicated things get, the more
>> potential for something to break and you not catching it (like your node
>> server crashing and you don't know it for a few days).
>>
>> I'm working on a skin for weewx now, but this could be a fun project to
>> think about - forking a PWSWeather extension to the AmbientWeather service
>> - (unless someone else reading this wants to give it a try).
>>
>>
>> On Monday, August 13, 2018 at 10:34:09 PM UTC-4, Douglas Krug wrote:
>>>
>>> Hello again Pat,
>>>
>>> Thanks for commenting. This is basically a continuation of the
>>> conversation we had on wxforum. I've got experience setting up node.js,
>>> that shouldn't be a problem. I stumble across the ambient2pwsweather node
>>> project and reached out to see if he would consider modifying it. He wasn't
>>> really interested if there was no API for Weewx, which to the best of my
>>> understanding, there is not. I suggested Matthew Wall's interceptor plugin,
>>> to just capture html traffic from the node server. He said it should not be
>>> too difficult, but wants info on how it should be formatted. You say it
>>> shouldn't be difficult, and that's cool. @mwall hasn't commented yet and
>>> I'm not a developer, so my understanding of it all is pretty rudimentary.
>>>
>>> I've got a lot of brilliant minds here, but the data is passing through
>>> me and 

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

[Pat]

Taking a look at the ambient2pwsweather project, it looks like he's really 
using the ambient-weather-api 
 project as his heavy 
lifting for ambient. And looking at the project it looks like what we 
talked about where AmbientWeather's API documentation 
 talks about how to subscribe to 
data, but not how to submit data. 

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? 

I've also upgraded to a Davis Vantage Pro 2, so I no longer am using my 
Ambient ObserverIP, so I don't have test data to use. 


On Tuesday, August 14, 2018 at 8:57:42 AM UTC-4, Pat wrote:
>
> The API into weewx would be a driver. Typically the weather equipment is 
> directly connected and the driver would control the weather station. That's 
> why I wrote the socket driver a few years ago because my equipment isn't 
> directly connected. 
>
> The good news is the interceptor driver has multiple ways to input data 
> into weewx, so it's probably as much of an API as you're going to find. By 
> sending HTTP data to the driver's web server, it can then pass it to weewx 
> like a standard driver would.
>
> That being said, I can't help but to think about others who may want to 
> publish data to Ambient as well. As mentioned on wxforum, the Ambient 
> documentation is kind of lacking for a developer and what the value names 
> are to submit (and how... GET vs. POST). But if there's a project that's 
> successfully posting data to Ambient, then maybe a weewx extension could be 
> created to post to Ambient. An extension like the one for wunderground or 
> PWSWeather might be easy enough to fork for Ambient. This would save the 
> need of setting up and maintaining a node server (and help those here who 
> don't know what node is). The more complicated things get, the more 
> potential for something to break and you not catching it (like your node 
> server crashing and you don't know it for a few days). 
>
> I'm working on a skin for weewx now, but this could be a fun project to 
> think about - forking a PWSWeather extension to the AmbientWeather service 
> - (unless someone else reading this wants to give it a try).
>
>
> On Monday, August 13, 2018 at 10:34:09 PM UTC-4, Douglas Krug wrote:
>>
>> Hello again Pat,
>>
>> Thanks for commenting. This is basically a continuation of the 
>> conversation we had on wxforum. I've got experience setting up node.js, 
>> that shouldn't be a problem. I stumble across the ambient2pwsweather node 
>> project and reached out to see if he would consider modifying it. He wasn't 
>> really interested if there was no API for Weewx, which to the best of my 
>> understanding, there is not. I suggested Matthew Wall's interceptor plugin, 
>> to just capture html traffic from the node server. He said it should not be 
>> too difficult, but wants info on how it should be formatted. You say it 
>> shouldn't be difficult, and that's cool. @mwall hasn't commented yet and 
>> I'm not a developer, so my understanding of it all is pretty rudimentary.
>>
>> I've got a lot of brilliant minds here, but the data is passing through 
>> me and packets are being dropped ;-)
>> Appreciate the link to Matt's python code. I'll forward this info and see 
>> if he can modify from that.
>>
>> On Monday, August 13, 2018 at 10:00:29 PM UTC-4, Pat wrote:
>>>
>>> @G Hammer - It's not too bad if you have the extra hardware to do the 
>>> iptables redirect. The $6 dongle is surely cheaper than a new router 
>>> though. Also I notice you're local to me in Western MA (based off the weewx 
>>> map). Glad I'm not the only one using weewx around here anymore :)
>>>
>>> I don't have any experience with the interceptor driver, but since 
>>> mwall's given me credit for the observer portion 
>>> ,
>>>  
>>> I thought that maybe I can help a little?
>>>
>>> I read the code for the interceptor driver and it looks like if you use 
>>> the device_type = observer in your weewx.conf file, then the data 
>>> received to the driver's built in web server needs to be in the Observer 
>>> format in this example within the code 
>>> ,
>>>  
>>> and similar to the format on my site (which you already linked). 
>>>
>>> Since each variable in the URL has a corresponding value (like 
>>> tempf=43.3 means temperature in Fahrenheit is 43.3), this should be 
>>> pretty simple for the ambient2pwsweather dev to figure out how to format 
>>> the observations being sent to the weewx driver. 
>>>
>>> Hope this helps a little...
>>>
>>>
>>> On Monday, August 13, 

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

[Pat]

The API into weewx would be a driver. Typically the weather equipment is 
directly connected and the driver would control the weather station. That's 
why I wrote the socket driver a few years ago because my equipment isn't 
directly connected. 

The good news is the interceptor driver has multiple ways to input data 
into weewx, so it's probably as much of an API as you're going to find. By 
sending HTTP data to the driver's web server, it can then pass it to weewx 
like a standard driver would.

That being said, I can't help but to think about others who may want to 
publish data to Ambient as well. As mentioned on wxforum, the Ambient 
documentation is kind of lacking for a developer and what the value names 
are to submit (and how... GET vs. POST). But if there's a project that's 
successfully posting data to Ambient, then maybe a weewx extension could be 
created to post to Ambient. An extension like the one for wunderground or 
PWSWeather might be easy enough to fork for Ambient. This would save the 
need of setting up and maintaining a node server (and help those here who 
don't know what node is). The more complicated things get, the more 
potential for something to break and you not catching it (like your node 
server crashing and you don't know it for a few days). 

I'm working on a skin for weewx now, but this could be a fun project to 
think about - forking a PWSWeather extension to the AmbientWeather service 
- (unless someone else reading this wants to give it a try).


On Monday, August 13, 2018 at 10:34:09 PM UTC-4, Douglas Krug wrote:
>
> Hello again Pat,
>
> Thanks for commenting. This is basically a continuation of the 
> conversation we had on wxforum. I've got experience setting up node.js, 
> that shouldn't be a problem. I stumble across the ambient2pwsweather node 
> project and reached out to see if he would consider modifying it. He wasn't 
> really interested if there was no API for Weewx, which to the best of my 
> understanding, there is not. I suggested Matthew Wall's interceptor plugin, 
> to just capture html traffic from the node server. He said it should not be 
> too difficult, but wants info on how it should be formatted. You say it 
> shouldn't be difficult, and that's cool. @mwall hasn't commented yet and 
> I'm not a developer, so my understanding of it all is pretty rudimentary.
>
> I've got a lot of brilliant minds here, but the data is passing through me 
> and packets are being dropped ;-)
> Appreciate the link to Matt's python code. I'll forward this info and see 
> if he can modify from that.
>
> On Monday, August 13, 2018 at 10:00:29 PM UTC-4, Pat wrote:
>>
>> @G Hammer - It's not too bad if you have the extra hardware to do the 
>> iptables redirect. The $6 dongle is surely cheaper than a new router 
>> though. Also I notice you're local to me in Western MA (based off the weewx 
>> map). Glad I'm not the only one using weewx around here anymore :)
>>
>> I don't have any experience with the interceptor driver, but since 
>> mwall's given me credit for the observer portion 
>> ,
>>  
>> I thought that maybe I can help a little?
>>
>> I read the code for the interceptor driver and it looks like if you use 
>> the device_type = observer in your weewx.conf file, then the data 
>> received to the driver's built in web server needs to be in the Observer 
>> format in this example within the code 
>> ,
>>  
>> and similar to the format on my site (which you already linked). 
>>
>> Since each variable in the URL has a corresponding value (like tempf=43.3 
>> means temperature in Fahrenheit is 43.3), this should be pretty simple for 
>> the ambient2pwsweather dev to figure out how to format the observations 
>> being sent to the weewx driver. 
>>
>> Hope this helps a little...
>>
>>
>> On Monday, August 13, 2018 at 9:19:34 AM UTC-4, Douglas Krug wrote:
>>>
>>> I've been discussing the possibility to have the author of "a
>>> mbient2pwsweather " 
>>> modify his node.js service to allow input to Matthew Wall's Interceptor 
>>> plugin. The idea is to allow the continued use of Ambientweather.net, while 
>>> still capturing weather data for Weewx, so that it can be published to the 
>>> supported weather services and used with Hubitat or other home automation 
>>> systems. I'm already able to listen to my WS-0900-IP bridge and get the 
>>> data into Weewx, but currently that comes at the cost of no longer being 
>>> able to use Ambientweather.net or any of their services such as IFTTT, Alex 
>>> Voice Services and Google Assistant.
>>>
>>>
>>> Is there a guide for how the data must be formatted for input to the 
>>> interceptor.py plugin? Hoping anyone with