[weewx-user] Re: Can MISOL station work with weewx, suggest me one

[Douglas Krug]

If you have the Observer IP module, this is very simple. I did this with my 
Ambient Weather Observer IP (same as MISOL as both are made by Fine Offset, 
just different firmware), just follow "Method 2" here on Pat O'Brien's blog 
7 . 
All you need is an inexpensive router compatible with DD-WRT and the 
patience to flash its firmware. You can stop at the end of Pat's 
instructions before getting to "Accepting the data on your server". That 
bit is unnecessary. Once I did this. it was simple to redirect WU data that 
I was uploading from my Observer IP module to Weewx. Since this method uses 
the WU upload data, it doesn't matter which firmware version the Observer 
IP bridge is using.

On Monday, April 8, 2019 at 7:22:04 AM UTC-4, Ramesh Rasappan wrote:
>
> noob here, I spent several hrs to find a weather station that can work 
> with weewx (can be hooked up with my existing Rasberry Pi 3), my budget is 
> limited (~$120). I prefer to buy a station from China since it is too 
> expensive to import from US. I found MISOL products (very similar to Fine 
> Offset products) in AliExpress and they have a whole range of products but 
> I am not sure if they can be used with weewx!! They do have a 
> console with USB connection for connecting a PC to upload the data to 
> weather stations like wunderground but I don't know if weewx can pull the 
> data from this console!! Also, the MISOL products can be bought without the 
> console (cheaper) but again I am not sure if I can directly hook the 
> station to Rasberry Pi 3, I may need few adapters and the overall cost may 
> increase a lot.
>
> I found a discussion that talks about weewx and MISOL WH2310 station but 
> it is not clear from that discussion that the following models can work or 
> not (https://groups.google.com/forum/#!topic/weewx-user/4NeVsThRxJk 
>  andhttps://github.com/weewx/weewx)
>
>
> can you suggest me if I can buy one of them? (also should I go with 
> console or without?)
>
> with console (WS-2310-1)
>
> https://www.aliexpress.com/store/product/MISOL-professional-weather-station-wind-speed-wind-direction-rain-meter-pressure-temperature-humidity-UV/112828_32673332115.html?spm=2114.12010612.8148357.32.44fe336bpL60C8
>
> without the console (same as above)
>
> https://www.aliexpress.com/store/product/1-set-of-Spare-part-outdoor-unit-for-Professional-Wireless-Weather-Station-with-small-solar-panel/112828_32846646856.html?spm=2114.12010612.8148357.47.44fe336bpL60C8
>
> same with different console and cheaper
>
> https://www.aliexpress.com/store/product/misol-Professional-Wireless-Weather-Station-Touch-Panel-w-Solar-sensor-w-PC-interface/112828_32765225865.html?spm=2114.12010612.8148357.38.44fe336bpL60C8
>
> directly uploads to wunderground
>
> https://www.aliexpress.com/store/product/MISOL-IP-OBSERVER-Solar-Powered-Wireless-Internet-Remote-Monitoring-Weather-Station/112828_32624080442.html?spm=2114.12010612.8148357.20.44fe336bpL60C8
>
>

-- 
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] Any true step by step for Interceptor

[Douglas Krug]

I'm back struggling with this again. Still cannot get any results from it.
Tried a year ago to get data from my old Acurite smartHUB. Back then I had 
more options than I do today, now that the server is shut down, 
and still couldn't get it to work. I finally gave up and bought an Ambient 
Weather 900-IP station. Had very little trouble getting that to work with 
Pat O'Brien's socket logger
and my Observer IP bridge.

Today, I'd like to send my Acurite smartHUB to my Dad and setup the RPi 
image for him. I'm OK with using a separate router, I'll configure it and 
send that to him as well.
That's how I did it with Socket Logger and the Observer IP bridge, but with 
Acurite, I cannot get anything out of Interceptor. I'm not understanding 
how so many people are getting
it to work, but I can't get anything from it. Worked at it for two weeks 
the first time round, and I've been plugging away for two days this time 
around.

Here's what works:

I have a DD-WRT flashed router with the WLAN  in client mode to join my 
main WiFi router where the RPi Zero W is connected, and I have the IP 
reserved for the Acurite smartHUB in the second router I've tried using Pat 
O'Brien's firewall so the data from the Acurite smartHUB is sent to the 
RPi. Works with the Observer IP bridge, so I can't
understand why it wouldn't work here.


iptables -t nat -A PREROUTING -s [Acurite smartHUB] -p tcp --dport 80 -j 
DNAT --to-destination [Raspberry Pi]: iptables -t nat -A POSTROUTING -j 
MASQUERADE

I see no results from this. I've tried port 80, 800, 8080, 2999, and  
for the destination.

I have installed the Interceptor plugin on weewx and configured it.

station_type = Interceptor

[Interceptor]
driver = user.interceptor
device_type = acurite-bridge
port = 



I have, to the best of my knowledge, configured the DD-WRT to 
forward hubapi.myacurite.com and www.acu-link.com to the RPi IP address.
I'm exhausted from this and would really like a detailed step by step to 
help me if someone can do that. Seems people really want to help, but 
there's
always a part where I get the "just do that" type of instruction and I'm 
lost.

Here's what I see from the Acurite smartHUB, so I know it's working.

[image: Acurite Hub.png]


Here's a video I followed for DNS resolution setup on the DD-WRT and what I 
entered.

[image: DD-WRT dns forwarding.png]


I'm obviously doing something wrong over and over again, but in all the 
parts and possible combinations, I'm really lost as to where the issue is.

Can really use some step by step help and a simple method to confirm that 
each of the component parts is configured correctly. I've been using tail 
-f /var/log/syslog
to view the logs, and while that has been helpful, it's shown me that 
either there's a port conflict or that I'm not getting any result from 
weewx, which is where I'm at now. 





   

-- 
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: Belchertown skin for weewx now available!

[Douglas Krug]

This looks awesome Pat. Well I may have distracted you with the Ambient 
Weather to Weewx thing, but you sure did a great service to a lot of people 
with this. Thank you!

On Tuesday, August 21, 2018 at 2:45:13 PM UTC-4, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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]

@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 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 
> 
> . 
>
> There's a way to get socket.io to fallback onto websockets 
>  where you can use wss, but 
> I haven't figured that bit out yet with AW.
>
>
>
> On Thursday, August 16, 2018 at 11:47:49 AM UTC-4, Thomas Keffer wrote:
>>
>> 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 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 socketIO:
>>> socketIO.on('connect', on_connect)
>>>
>>> /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: 
>>> InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
>>> certificate verification is strongly advised. See: https://
>>> urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings 
>>> InsecureRequestWarning)
>>>
>>> WARNING:socketIO-client:api.ambientweather.net:443/v1/devices/socket.io 
>>> [engine.io waiting for connection] unexpected status code (401 {"error":
>>> "apiKey-missing"})
>>>
>>> Or the 404 again
>>>
>>> SocketIO(
>>> 'https://api.ambientweather.net/v1/devices/YOUR_MAC_ADDR', 443, 
>>> LoggingNamespace,
>>> verify=False,
>>> params={'apiKey': 'YOUR_API_KEY', 'applicationKey': 'YOUR_APP_KEY' 
>>> })
>>>
>>>
>>> /usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:857: 
>>> InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
>>> certificate verification is strongly advised. See: https://
>>> urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings 
>>> InsecureRequestWarning)
>>>
>>> WARNING:socketIO-client:api.ambientweather.net:443/v1/devices/
>>> YOUR_MAC_ADDR/socket.io [engine.io waiting for connection] unexpected 
>>> status code (404 {"name":"NotFound","message":"Page not found","code":
>>> 404,"className":"not-found","errors":{}})
>>>
>>> Pat
>>>
>>>
>>>
>>>
>>> On Thursday, August 16, 2018 at 11:24:00 AM UTC-4, Thomas Keffer wrote:

 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 Python, I thought about using a timer to poll the endpoint. 
> However it looks like they only update the endpoint every 5 minutes. I'm 
> thinking that's not really a good option since you probably want real 
> time 
> loop data, and not a 5 minute archive. 
>
> Since it seems to be working with node, and you're familiar with node, 
> maybe that's your best bet right now to get the real time updates out of 
> AW? 
>
>
>
> Since you're a customer of AW, you could also email them asking for 
> Python help with the real time endpoint 
>  
> and see what they say. Their API docs 
>  
> say "The easiest way to use the API is to use a Socket.io helper library. 
> They are available in most languages.", but when I use their endpoint 
> with 
> a Python helper library all I get is a 404. 
>
> Here's the code from sockerIO_client's sample code 
> . Nothing fancy here yet, 
> just trying to connect, and it doesn't. 
>
> After doing sudo pip install socketIO_client
>
> I ran this code
>
> import logging
> logging.getLogger('socketIO-client').setLevel(logging.DEBUG)
> logging.basicConfig()
>
>
> from socketIO_client import SocketIO, LoggingNamespace
>
>
> def on_connect():
> print('connect')
>
>
> with SocketIO('
> https://api.ambientweather.net/?api=1=YOUR_APPLICATION_KEY
> ', 443, 

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

[Douglas Krug]

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 
in the last 30 days.

On Thursday, August 16, 2018 at 11:15:26 AM UTC-4, Pat wrote:
>
> 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 minutes. I'm 
> thinking that's not really a good option since you probably want real time 
> loop data, and not a 5 minute archive. 
>
> Since it seems to be working with node, and you're familiar with node, 
> maybe that's your best bet right now to get the real time updates out of 
> AW? 
>
>
>
> Since you're a customer of AW, you could also email them asking for Python 
> help with the real time endpoint 
>  
> and see what they say. Their API docs 
>  
> say "The easiest way to use the API is to use a Socket.io helper library. 
> They are available in most languages.", but when I use their endpoint with 
> a Python helper library all I get is a 404. 
>
> Here's the code from sockerIO_client's sample code 
> . Nothing fancy here yet, just 
> trying to connect, and it doesn't. 
>
> After doing sudo pip install socketIO_client
>
> I ran this code
>
> import logging
> logging.getLogger('socketIO-client').setLevel(logging.DEBUG)
> logging.basicConfig()
>
>
> from socketIO_client import SocketIO, LoggingNamespace
>
>
> def on_connect():
> print('connect')
>
>
> with SocketIO('
> https://api.ambientweather.net/?api=1=YOUR_APPLICATION_KEY'
> , 443, LoggingNamespace ) as socketIO:
> socketIO.on('connect', on_connect)
>
>
> which outputs:
>
> WARNING:socketIO-client:api.ambientweather.net:443//socket.io [engine.io 
> waiting for connection] unexpected status code (404 
> {"name":"NotFound","message":"Page not 
> found","code":404,"className":"not-found","errors":{}})
>
> Adding your API Key to that HTTPS endpoint:
>
> with SocketIO('
> https://api.ambientweather.net/v1/devices?applicationKey=YOUR_APPLICATION_KEY=YOUR_API_KEY
> ', 443, LoggingNamespace ) as socketIO:
> socketIO.on('connect', on_connect)
>
> gave me:
>
> WARNING:socketIO-client:api.ambientweather.net:443/v1/devices/socket.io [
> engine.io waiting for connection] unexpected status code (401 {"error":
> "apiKey-missing"})
>
> But the API key isn't missing, it's in the string :)
>
>
>
> Or if I did something even different (again from the examples 
> )
>
> SocketIO(
> 'https://api.ambientweather.net/v1/devices/YOUR_MAC_ADDRESS', 443, 
> LoggingNamespace,
> params={'apiKey': 'YOUR_API_KEY', 'applicationKey': 
> 'YOUR_APPLICATION_KEY' })
>
> I get
>
> WARNING:socketIO-client:api.ambientweather.net:443/v1/devices/
> YOUR_MAC_ADDRESS/socket.io [engine.io waiting for connection] unexpected 
> status code (404 {"name":"NotFound","message":"Page not found","code":404,
> "className":"not-found","errors":{}})
>
>
>
>
>
> However, if I go to an online socket.io test tool 
> , and enter in your real 
> time endpoint, it connects just fine. This is farther than Python is 
> letting me get. 
>
> [image: socketio.png]
> Again, not sure where to go from here. Maybe Node is your best bet. But 
> also maybe the information above is enough info to get help from them if 
> you do end up reaching out to them?
>
>
>
>
> On Wednesday, August 15, 2018 at 9:04:34 AM UTC-4, Pat wrote:
>>
>> 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? 

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
>>>> <https://github.com/owise1/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
>>>> <https://ambientweather.docs.apiary.io/#> 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
>>

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 
>> <https://github.com/owise1/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 
>> <https://ambientweather.docs.apiary.io/#> 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

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
> <https://github.com/owise1/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
> <https://ambientweather.docs.apiary.io/#> 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 shou

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

[Douglas Krug]

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 
> <https://github.com/matthewwall/weewx-interceptor/blob/master/bin/user/interceptor.py#L16>,
>  
> 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 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fmatthewwall%2Fweewx-interceptor%2Fblob%2Fmaster%2Fbin%2Fuser%2Finterceptor.py%23L881=D=1=AFQjCNHlyqeOp8RM5pr4RRaU3tcxMsv11w>,
>  
> 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 <https://github.com/killroyboy/ambient2pwsweather>" 
>> 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 knowledge of interceptor or 
>> @mwall could comment please.
>>
>>
>> Here's what the ambient2pwsweather 
>> <https://github.com/killroyboy/ambient2pwsweather> developer wrote:
>>
>>
>>
>> *"If I'm understanding it correctly, it wouldn't be that difficult to 
>> enhance this utility to send the data to a different url/port. You would 
>> then need to run a new interceptor instance running in "listen mode" that 
>> would handle the insertion into weewx.*
>>
>> *The minor difficulty would be in ensuring the data is in a format that 
>> the interceptor would understand. If you can work that out and get me some 
>> documentation (or point me to a URL), I can enhance ambient2pwsweather."*
>>
>

-- 
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: PWS data format for Interceptor

[Douglas Krug]

No, not the entire post from Pat O'Brien, just the firewall script. If you 
can setup DD-WRT (which I've done so many times I don't even need to be 
awake now), you just enter two lines in the firewall commands. That will 
pass the data to the interceptor plugin running on Weewx.

iptables -t nat -A PREROUTING -s 192.168.1.55 -p tcp --dport 80 -j DNAT 
--to-destination x.x.x.x:80
iptables -t nat -A POSTROUTING -j MASQUERADE

Probably there's a way to mirror and not redirect, but I don't know what it 
is, not do I claim to even fully understand the above script. I just 
entered it and finally after months of beating my head against the wall, I 
was able to make something work. From your description, I still really 
don't understand how exactly you achieved that. I probably don't need an 
adapter and could sniff with the router I have, but I wouldn't know how. 
Some have said sniffing isn't as good as listening, but I'm not sure why 
unless it results in inaccurate data. I have read that many who were 
originally using the sniff method have switched to the listen method, 
noting it didn't work as well, but that explanation is a bit short on 
details.

I just know that if I can find out how the data should be formatted for 
Interceptor, I can maybe get the ambient2pwsweather developer to modify his 
code, allowing the preferred listen mode for the Interceptor plug-in and 
full Ambientweather.net functionality.


On Monday, August 13, 2018 at 8:18:27 PM UTC-4, G Hammer wrote:
>
> Wow! Looks pretty involved.
> I bought a $6 WiFi USB adapter and run an AP on my weewx box.
> The WiFi USB is in monitor mode and then you can sniff the data.
> There is a way with the routes to mirror the data, letting the data 
> continue to it's original destination while mirroring it to another.
> iptables is still the way to do it that method, just mirror instead of 
> redirect.
>
> On Monday, August 13, 2018 at 5:06:34 PM UTC-4, Douglas Krug wrote:
>>
>> LOL. How are you sniffing the data from the console! I could not get that 
>> to work with either an Acurite bridge or my Observer IP bridge.
>>
>> I'm using listen as was recommended for the FineOffset (e.g. Ambient 
>> Weather and others) Observer IP bridge. I used Pat O'Brien's instructions 
>> <https://obrienlabs.net/redirecting-weather-station-data-from-observerip/> 
>> for the DD-WRT firewall script together with Matthew Wall's Interceptor 
>> plugin <https://github.com/matthewwall/weewx-interceptor> (configured 
>> for Observer) and it worked.
>>
>> On Monday, August 13, 2018 at 4:37:41 PM UTC-4, G Hammer wrote:
>>>
>>> How are you capturing the data from the console?
>>> I have this configured so that weewx gets the data, but only by sniffing 
>>> it. The data is never interrupted/diverted so everyone gets the feed from 
>>> the console along with weewx.
>>>
>>>
>>> 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 <https://github.com/killroyboy/ambient2pwsweather>" 
>>>> 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 knowledge of interceptor or 
>>>> @mwall could comment please.
>>>>
>>>>
>>>> Here's what the ambient2pwsweather 
>>>> <https://github.com/killroyboy/ambient2pwsweather> developer wrote:
>>>>
>>>>
>>>>
>>>> *"If I'm understanding it correctly, it wouldn't be that difficult to 
>>>> enhance this utility to send the data to a different url/port. You would 
>>>> then need to run a new interceptor instance running in "listen mode" that 
>>>> would handle the insertion into weewx.*
>>>>
>>>> *The minor difficulty would be in ensuring the data is in a format that 
>>>> the interceptor would understand. If you can work that out and get me some 
>>>> documentation (or point me to a URL), I can enhance ambient2pwsweather."*
>>>>
>>>

-- 
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: PWS data format for Interceptor

[Douglas Krug]

LOL. How are you sniffing the data from the console! I could not get that 
to work with either an Acurite bridge or my Observer IP bridge.

I'm using listen as was recommended for the FineOffset (e.g. Ambient 
Weather and others) Observer IP bridge. I used Pat O'Brien's instructions 
<https://obrienlabs.net/redirecting-weather-station-data-from-observerip/> 
for the DD-WRT firewall script together with Matthew Wall's Interceptor 
plugin <https://github.com/matthewwall/weewx-interceptor> (configured for 
Observer) and it worked.

On Monday, August 13, 2018 at 4:37:41 PM UTC-4, G Hammer wrote:
>
> How are you capturing the data from the console?
> I have this configured so that weewx gets the data, but only by sniffing 
> it. The data is never interrupted/diverted so everyone gets the feed from 
> the console along with weewx.
>
>
> 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 <https://github.com/killroyboy/ambient2pwsweather>" 
>> 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 knowledge of interceptor or 
>> @mwall could comment please.
>>
>>
>> Here's what the ambient2pwsweather 
>> <https://github.com/killroyboy/ambient2pwsweather> developer wrote:
>>
>>
>>
>> *"If I'm understanding it correctly, it wouldn't be that difficult to 
>> enhance this utility to send the data to a different url/port. You would 
>> then need to run a new interceptor instance running in "listen mode" that 
>> would handle the insertion into weewx.*
>>
>> *The minor difficulty would be in ensuring the data is in a format that 
>> the interceptor would understand. If you can work that out and get me some 
>> documentation (or point me to a URL), I can enhance ambient2pwsweather."*
>>
>

-- 
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] PWS data format for Interceptor

[Douglas Krug]

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 knowledge of interceptor or 
@mwall could comment please.


Here's what the ambient2pwsweather 
 developer wrote:



*"If I'm understanding it correctly, it wouldn't be that difficult to 
enhance this utility to send the data to a different url/port. You would 
then need to run a new interceptor instance running in "listen mode" that 
would handle the insertion into weewx.*

*The minor difficulty would be in ensuring the data is in a format that the 
interceptor would understand. If you can work that out and get me some 
documentation (or point me to a URL), I can enhance ambient2pwsweather."*

-- 
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: Sending WS 2902 directly to RPi (Internet independency)

[Douglas Krug]

Thanks for quick reply Daniel. If you're just trying to get data into Weewx 
and don't care about being connected to Ambientweather.net, then this 
information helped me immensely.

https://obrienlabs.net/redirecting-weather-station-data-from-observerip/

I tried using Patrick's socket logger, but couldn't get anywhere with that. 
Where the help came in was the firewall script for DD-WRT. I ended up using 
Matthew Wall's interceptor driver for weewx, together with Patrick 
O'brien's instructions for the router, and after beating my head against 
the wall for many previous weeks (months actually) I was finally able to 
get it working.

On Wednesday, August 8, 2018 at 3:26:25 PM UTC-4, Daniel West wrote:
>
> Hey Douglas,
>
> I never did have luck with that. Honestly, I gave up. I tried using my 
> DD-WRT but never had luck. My understanding is that the weather station 
> needs an internet connection to even begin pushing weather information out. 
> Could never get beyond that.
>
> I decided to just stick with the internet dependency. I am currently using 
> the Ambient Weather API, which pulls my uploaded weather station data from 
> their site and then stores it in a txt document. I'm currently on summer 
> break and working an internship so I havent had time. Class is starting up 
> again soon so all I need to do now is slice the txt document for the info 
> im looking for.
>
> Hadnt heard of Hubitat, I will definitely look into that!
>
> On Wed, Aug 8, 2018 at 2:15 PM Douglas Krug  > wrote:
>
>> Did you figure out how to get weather data from ambientweather.net to 
>> weewx? I'm not a developer, so totally useless in that area.
>>
>> I run a home automation system called Hubitat which runs local groovy 
>> code and can connect to cloud sources when required by the device. One of 
>> the users has created an app he calls Weather Switch that can turn on 
>> switches (virtual or real) based on weather data pulled from Weewx. I have 
>> it working but the issue is I lose connection with Ambientweather.net when 
>> I do that, and I really like their dashboard and features. If it were 
>> possible to get weather data from ambient to weewx, then it could be 
>> uploaded to any number of places, as well as be used by Weather Switch on 
>> Hubitat and other home automation systems via Weewx.
>>
>> There is a node.js project out there that pulls from ambientweather.net 
>> and uploads to PWSWeather, but that's not useful to me. Perhaps someone 
>> that understood the code could figure out what's needed from that example 
>> though.
>>
>> On Monday, April 30, 2018 at 6:25:47 PM UTC-4, Daniel West wrote:
>>>
>>>
>>> Creating a script on the router goes way over my head, wasnt aware that 
>>> was really a thing. I cant capture the TCP traffic oddly enough. I thought 
>>> I had everything set in my weewx.conf file set correctly but I suppose not. 
>>>
>>> Ive attached my super simple script to capture the info through AW's 
>>> API. Follow the Ambient Weather API link 
>>> <https://ambientweather.docs.apiary.io/#reference/ambient-realtime-api>, 
>>> under Authentication it tells you how to get the two keys I used in my 
>>> script, you must have an account and your WS uploading to 
>>> ambientweather.net. They asked me for the MAC address of my WS 2902. 
>>>
>>> I would agree with your assumption. In stead of pulling information from 
>>> the station itself I am actually pulling it from the website. Im wondering 
>>> if I have to spoof that, again, way over my head. 
>>>
>>> Thanks a bunch :D
>>>
>>> p.s. Ive only known one other Tremblay so I have to ask. Are you related 
>>> to a Joe Tremblay that served in the US Navy?
>>>
>>>
>>> On Monday, April 30, 2018 at 5:09:25 PM UTC-5, Lorin Tremblay wrote:
>>>>
>>>> I've been at this for a couple of days even maybe weeks with partial 
>>>> success.
>>>> So far i'm using the weewx extension interceptor to capture the TCP 
>>>> traffic and feed the interceptor.
>>>>
>>>> My biggest problem is to create a script on the router to intercept the 
>>>> data. I have tried some many ways with only partial success and have been 
>>>> posting all over to try and get some assistance since I'm like you sort of 
>>>> a NOOB...
>>>>
>>>> If you don't mind sharing how you use your api key to capture to file 
>>>> the info, would be great, that I'll try more stuff to finally get this 
>>>> working...
>>>>
>>>

[weewx-user] Re: Sending WS 2902 directly to RPi (Internet independency)

[Douglas Krug]

Did you figure out how to get weather data from ambientweather.net to 
weewx? I'm not a developer, so totally useless in that area.

I run a home automation system called Hubitat which runs local groovy code 
and can connect to cloud sources when required by the device. One of the 
users has created an app he calls Weather Switch that can turn on switches 
(virtual or real) based on weather data pulled from Weewx. I have it 
working but the issue is I lose connection with Ambientweather.net when I 
do that, and I really like their dashboard and features. If it were 
possible to get weather data from ambient to weewx, then it could be 
uploaded to any number of places, as well as be used by Weather Switch on 
Hubitat and other home automation systems via Weewx.

There is a node.js project out there that pulls from ambientweather.net and 
uploads to PWSWeather, but that's not useful to me. Perhaps someone that 
understood the code could figure out what's needed from that example though.

On Monday, April 30, 2018 at 6:25:47 PM UTC-4, Daniel West wrote:
>
>
> Creating a script on the router goes way over my head, wasnt aware that 
> was really a thing. I cant capture the TCP traffic oddly enough. I thought 
> I had everything set in my weewx.conf file set correctly but I suppose not. 
>
> Ive attached my super simple script to capture the info through AW's API. 
> Follow the Ambient Weather API link 
> , 
> under Authentication it tells you how to get the two keys I used in my 
> script, you must have an account and your WS uploading to 
> ambientweather.net. They asked me for the MAC address of my WS 2902. 
>
> I would agree with your assumption. In stead of pulling information from 
> the station itself I am actually pulling it from the website. Im wondering 
> if I have to spoof that, again, way over my head. 
>
> Thanks a bunch :D
>
> p.s. Ive only known one other Tremblay so I have to ask. Are you related 
> to a Joe Tremblay that served in the US Navy?
>
>
> On Monday, April 30, 2018 at 5:09:25 PM UTC-5, Lorin Tremblay wrote:
>>
>> I've been at this for a couple of days even maybe weeks with partial 
>> success.
>> So far i'm using the weewx extension interceptor to capture the TCP 
>> traffic and feed the interceptor.
>>
>> My biggest problem is to create a script on the router to intercept the 
>> data. I have tried some many ways with only partial success and have been 
>> posting all over to try and get some assistance since I'm like you sort of 
>> a NOOB...
>>
>> If you don't mind sharing how you use your api key to capture to file the 
>> info, would be great, that I'll try more stuff to finally get this 
>> working...
>>
>> Also from what I understand you will need to continuously upload your 
>> data to the ambient website and the pull it back from there again, but not 
>> sure about that, will be able to establish that once I see how you use the 
>> api key.
>>
>> If we can share our ressource to get this working i'll be a happy man ;)
>>
>>
>> On Monday, April 30, 2018 at 11:03:45 AM UTC-4, Daniel West wrote:
>>>
>>> Greetings all, I have to give the obligatory noob alert, so thank you in 
>>> advance for patience and help.
>>>
>>> Ill start with my end goal:
>>> I would like my RPi to receive my WS 2902 sensor values as CSV, TXT, 
>>> anything really. These values will be used to determine if/when GPIO's can 
>>> be triggered. It is highly preferable to be able to bypass any actual 
>>> uploading to the internet. I see that it may possible from the intake 
>>> strategies 
>>> 
>>>  section 
>>> of the weeWX GitHub. 
>>>
>>> On to my problem:
>>> I installed weeWX following this installation guide 
>>> . I get 
>>> all the way down to "Checking connectivity to your weather station" but 
>>> then it fails with "Timed out too many times" continuously. I have attached 
>>> a snippet of my user.log and my weewx.conf files. 
>>>
>>> Guidance for end goal:
>>> Once I see weeWX working I can focus on my desired intake strategy 
>>> (unless its just as easy to do at the same time). What do I need to achieve 
>>> my goal? Aside from what I have installed from the installation guide, I 
>>> essentially have whatever comes with Debian stretch. Ive seen mentions of 
>>> iptables but I'm not really sure what that involves. I am using an Arris 
>>> TG1682G (aka XB3, from Comcast). But I also have a spare Linksys WRT54G 
>>> with DD-WRT on it. The WRT would ultimately be the desired router to use.
>>>
>>> I should mention, I have gotten the Ambient Weather API 
>>>  to 
>>> work, I can receive my sensor values and save them into a txt file. If it 

[weewx-user] Re: Exceptions attribute error - Interceptor driver for Acurite bridge

[Douglas Krug]

Hi Matthew, is there an older version of the weewx-interceptor code before 
the pylibpcap binding change I might be able to try?

On Thursday, May 24, 2018 at 11:55:21 AM UTC-4, mwall wrote:
>
> douglas,
>
> this looks like a pcap library issue.  i think there are two python 
> bindings for pcap:  pypcap and pylibpcap.  apparently pylibpcap has the 
> pcapObject, but pypcap does not.
>
>
> https://stackoverflow.com/questions/2501138/module-object-has-no-attribute-pcapobject
>
> when i did the development of weewx-interceptor, the 'pip install pypcap' 
> gave me the pylibpcap bindings.  but more recently i have been using the 
> debian-based python-libpcap package, which seems to have pylibpcap bindings 
> as well.  if you did the 'pip install pypcap' you might have gotten the 
> pypcap bindings.
>
> so what do we do?
>
> option 1: figure out how to install the pylibpcap bindings on your system. 
>  you might be able to do this with 'pip install pylibpcap'
>
> option 2: adjust the weewx-interceptor code so that it works with either 
> pypcap or pylibpcap bindings.  i'm happy to support whichever pcap bindings 
> are more prevalent/modern/available.  the APIs are not compatible, but they 
> are used in only less than 10 lines of code. 
>
> m
>

-- 
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: Exceptions attribute error - Interceptor driver for Acurite bridge

[Douglas Krug]

Thanks so much for that helpful reply Matthew. I found the pylibpcap 
bindings here , 
but unfortunately I still get the same result. Tried rebooting for good 
measure, but no change. Tried uninstalling pypcap as well, but still no 
change in result.

On Thursday, May 24, 2018 at 11:55:21 AM UTC-4, mwall wrote:
>
> douglas,
>
> this looks like a pcap library issue.  i think there are two python 
> bindings for pcap:  pypcap and pylibpcap.  apparently pylibpcap has the 
> pcapObject, but pypcap does not.
>
>
> https://stackoverflow.com/questions/2501138/module-object-has-no-attribute-pcapobject
>  
> 
>
> when i did the development of weewx-interceptor, the 'pip install pypcap' 
> gave me the pylibpcap bindings.  but more recently i have been using the 
> debian-based python-libpcap package, which seems to have pylibpcap bindings 
> as well.  if you did the 'pip install pypcap' you might have gotten the 
> pypcap bindings.
>
> so what do we do?
>
> option 1: figure out how to install the pylibpcap bindings on your system. 
>  you might be able to do this with 'pip install pylibpcap'
>
> option 2: adjust the weewx-interceptor code so that it works with either 
> pypcap or pylibpcap bindings.  i'm happy to support whichever pcap bindings 
> are more prevalent/modern/available.  the APIs are not compatible, but they 
> are used in only less than 10 lines of code. 
>
> m
>

-- 
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] Exceptions attribute error - Interceptor driver for Acurite bridge

[Douglas Krug]

 

Have installed weeWX on MacOS 10.11.6 and I think my install is correct. 
I'm able to launch with Simulator configured, but I get the following error 
when I try to run configured with Interceptor for an Acurite bridge.

I also installed libcap as instructed.


*From wee_debug*


Using configuration file /Users/Shared/weewx/weewx.conf

Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'


System info

  Platform:   Darwin-15.6.0-x86_64-i386-64bit

  Python Version: 2.7.10


Load Information

  1 minute load average:  1.12

  5 minute load average:  1.22

  15 minute load average: 1.17


General Weewx info

  Weewx version 3.8.0 detected.


Station info

  Station type: Interceptor

  Driver:   user.interceptor


Driver info

[Interceptor]

# This section is for the network traffic interceptor driver.



# The driver to use:

driver = user.interceptor



# Specify the hardware device to capture.  Options include:

#   acurite-bridge - acurite internet bridge

#   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'

#   lw30x - oregon scientific LW301/LW302

#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge

device_type = acurite-bridge

mode = sniff

iface = en0

pcap_filter = src 192.168.0.125 and dst port 80


Currently installed extensions

Extension NameVersion   Description

Traceback (most recent call last):

  File "/Users/Shared/weewx/bin/wee_debug", line 427, in 

main()

  File "/Users/Shared/weewx/bin/wee_debug", line 160, in main

options.verbosity)

  File "/Users/Shared/weewx/bin/wee_debug", line 227, in generateDebugInfo

ext.enumerate_extensions()

  File "/Users/Shared/weewx/bin/weecfg/extension.py", line 81, in 
enumerate_extensions

info = self.get_extension_info(f)

  File "/Users/Shared/weewx/bin/weecfg/extension.py", line 93, in 
get_extension_info

_, installer = weecfg.get_extension_installer(ext_cache_dir)

  File "/Users/Shared/weewx/bin/weecfg/__init__.py", line 1296, in 
get_extension_installer

raise ExtensionError("Cannot find 'install' module in %s" % 
extension_installer_dir)

weecfg.ExtensionError: Cannot find 'install' module in 
/Users/Shared/weewx/bin/user/installer/.DS_Store


Not sure if this last error is typical on Mac OS when using wee_debug, but 
I don't get an error when I install the Interceptor driver.

*Output from Mac OS console*

5/24/18 1:12:59.654 AM weewx[677]: import of driver failed: 'module' object 
has no attribute 'pcapObject' ()
5/24/18 1:12:59.655 AM weewx[677]: engine: Unable to load driver: 'module' 
object has no attribute 'pcapObject'
5/24/18 1:12:59.655 AM weewx[677]:  Exiting...

*From my conf file*

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use: driver = user.interceptor # Specify the hardware device to 
capture. Options include: # acurite-bridge - acurite internet bridge # observer 
- fine offset WH2600/HP1000/HP1003, aka 'observer' # lw30x - oregon scientific 
LW301/LW302 # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge 
device_type = acurite-bridge mode = sniff iface = eth1 pcap_filter = src 
192.168.0.125 and dst port 80

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture. Options include:
# acurite-bridge - acurite internet bridge
# observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
# lw30x - oregon scientific LW301/LW302
# lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
device_type = acurite-bridge
mode = sniff
iface = eth1
pcap_filter = src 192.168.0.125 and dst port 80

Not sure where to go from here. I know nothing about python. Any guidance 
would be helpful and much appreciated.

-- 
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.