[weewx-user] Re: Driver permission error when starting Weewx

[Chris McLeod]

Tomasz, 

Thank you very much for the steps on how to manually install the driver!
Chris 

On Thursday, February 1, 2024 at 1:15:20 AM UTC-7 Tomasz Lewicki wrote:

> That's strange message. When you manualy decompress ZIP (I suppose 
> downloaded from GitHub) and look into install.py, last line says:
>
> *files=[('bin/user', ['bin/user/interceptor.py'])]*
>
> I don't know why in your case there is / (slash) in error message:
>
> *FileNotFoundError: [Errno 2] No such file or directory: 
> '/bin/user/interceptor.py'*
>
> But I think you can manually copy just one file - *interceptor.py*  - to 
> */etc/weewx/bin/user* directory and make changes in *weewx.conf,* then 
> restart weewx, it should work. There are additiional files in *util* 
> directory but install.py omits them so they are not necessary. 
> czwartek, 1 lutego 2024 o 08:35:01 UTC+1 Chris McLeod napisał(a):
>
>> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
>> drivers by weectl. " Can you provide some insight into how you did this? I 
>> have a fresh install of 5.0.1 and when I run 'weectl extension install 
>> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
>> posting here just in case I am missing something obvious, if not I will 
>> start a new thread. 
>>
>> Thanks, 
>> Chris 
>>
>> :~$ weectl extension install weewx-interceptor.zip
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'weewx-interceptor.zip' (y/n)? y
>> Extracting from zip archive weewx-interceptor.zip
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
>> install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
>> _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
>> install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/bin/user/interceptor.py'
>>
>> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>>
>>> Mystery solved. 
>>>
>>> But answering to vince question, my system is rather typical - Raspbian 
>>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>>> server. But still I couldn't see any traffic on my router. Total silence. 
>>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>>> I just needed credentials for conversation between console and Weewx. I 
>>> entered ID and password - and then console started send data to real WU. So 
>>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>>> data from WiFi console via interceptor driver :)
>>>
>>> Thank you to everyone who patiently read my writings and tried to help.
>>>
>>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>>
>>&

[weewx-user] Re: Driver permission error when starting Weewx

[Chris McLeod]

Gary, 

Thank you very much for the quick reply. I will stand by for the new 
release. 

Thanks,
Chris

On Thursday, February 1, 2024 at 1:52:59 AM UTC-7 gjr80 wrote:

> You have almost certainly encountered the bug mentioned in this post 
> . 
> The bug does not bite (ie potentially delete system files) unless you 
> uninstall the extension using weectl extension - so my strong advice to 
> you is do not attempt to uninstall the extension. A manual uninstall (or 
> install) will be fine. But I would further suggest waiting a few days for 
> v5.0.1 which fixes this bug, its release should not be too far off.
>
> Gary
>
> On Thursday 1 February 2024 at 17:35:01 UTC+10 csm...@gmail.com wrote:
>
>> @Tomasz, you stated above that ' I installed both interceptor and HP1000 
>> drivers by weectl. " Can you provide some insight into how you did this? I 
>> have a fresh install of 5.0.1 and when I run 'weectl extension install 
>> weewx-interceptor.zip (fresh download) I get an error stack below. I am 
>> posting here just in case I am missing something obvious, if not I will 
>> start a new thread. 
>>
>> Thanks, 
>> Chris 
>>
>> :~$ weectl extension install weewx-interceptor.zip
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'weewx-interceptor.zip' (y/n)? y
>> Extracting from zip archive weewx-interceptor.zip
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 138, in 
>> install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>   File "/usr/share/weewx/weecfg/extension.py", line 168, in 
>> _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 185, in 
>> install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/bin/user/interceptor.py'
>>
>> On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:
>>
>>> Mystery solved. 
>>>
>>> But answering to vince question, my system is rather typical - Raspbian 
>>> on Raspberry Pi, only WLAN interface is active. Weewx was unwillingly 
>>> updated from 4.10.2 to 5.0.0. I checked all point of failure: Python 
>>> version, permissions (thank you Gary!), network traffic. As I wrote before, 
>>> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
>>> Weewx. So I deleted this bypass, allowing console to send data to real WU 
>>> server. But still I couldn't see any traffic on my router. Total silence. 
>>> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
>>> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
>>> empty, password was obfuscated by asterisks. I don't use WU website at all, 
>>> I just needed credentials for conversation between console and Weewx. I 
>>> entered ID and password - and then console started send data to real WU. So 
>>> I redirected  network traffic on my DNS again, and Weewx started to receive 
>>> data from WiFi console via interceptor driver :)
>>>
>>> Thank you to everyone who patiently read my writings and tried to help.
>>>
>>> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>>>
 Difficult to answer with no info from you on exactly 'what' command you 
 ran for wireshark and whether your listening computer is wifi, ethernet, 
 or 
 both.  What kind of computer are you running on ?  What os ?  What version 
 ?  Which interfaces ?  What was your 'exact' wireshark command ?

 But I see nothing basically in that 6-second pcap.  If running a 
 sniffer on your computer sees no traffic being redirected from the 
 station, 
 then there is nothing for interceptor to intercept on the weewx computer.

 Again, when you say "*But I hijacked DNS on my router*" that (to me) 
 does not cause any traffic from your station to wunderground to be 
 redirected to your weewx system unless I'm not understanding what you're 
 saying.  Perhaps you should tell everybody what yo

[weewx-user] Re: Driver permission error when starting Weewx

[Chris McLeod]

@Tomasz, you stated above that ' I installed both interceptor and HP1000 
drivers by weectl. " Can you provide some insight into how you did this? I 
have a fresh install of 5.0.1 and when I run 'weectl extension install 
weewx-interceptor.zip (fresh download) I get an error stack below. I am 
posting here just in case I am missing something obvious, if not I will 
start a new thread. 

Thanks, 
Chris 

:~$ weectl extension install weewx-interceptor.zip
Using configuration file /etc/weewx/weewx.conf
Install extension 'weewx-interceptor.zip' (y/n)? y
Extracting from zip archive weewx-interceptor.zip
Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 66, in main
namespace.func(namespace)
  File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in 
install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File "/usr/share/weewx/weecfg/extension.py", line 138, in 
install_extension
extension_name = self._install_from_file(extension_path, filetype)
  File "/usr/share/weewx/weecfg/extension.py", line 168, in 
_install_from_file
extension_name = self.install_from_dir(extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 
'/bin/user/interceptor.py'

On Thursday, January 25, 2024 at 1:27:34 AM UTC-7 Tomasz Lewicki wrote:

> Mystery solved. 
>
> But answering to vince question, my system is rather typical - Raspbian on 
> Raspberry Pi, only WLAN interface is active. Weewx was unwillingly updated 
> from 4.10.2 to 5.0.0. I checked all point of failure: Python version, 
> permissions (thank you Gary!), network traffic. As I wrote before, 
> rtupdate.wunderground.com was hijacked - local DNS redirected it to 
> Weewx. So I deleted this bypass, allowing console to send data to real WU 
> server. But still I couldn't see any traffic on my router. Total silence. 
> It was abnormal (and it explains why PCAP file captured by Tshark was empty 
> on port 80). But I didn't check WU settings in WiFi console. Station ID was 
> empty, password was obfuscated by asterisks. I don't use WU website at all, 
> I just needed credentials for conversation between console and Weewx. I 
> entered ID and password - and then console started send data to real WU. So 
> I redirected  network traffic on my DNS again, and Weewx started to receive 
> data from WiFi console via interceptor driver :)
>
> Thank you to everyone who patiently read my writings and tried to help.
>
> środa, 24 stycznia 2024 o 22:54:46 UTC+1 vince napisał(a):
>
>> Difficult to answer with no info from you on exactly 'what' command you 
>> ran for wireshark and whether your listening computer is wifi, ethernet, or 
>> both.  What kind of computer are you running on ?  What os ?  What version 
>> ?  Which interfaces ?  What was your 'exact' wireshark command ?
>>
>> But I see nothing basically in that 6-second pcap.  If running a sniffer 
>> on your computer sees no traffic being redirected from the station, then 
>> there is nothing for interceptor to intercept on the weewx computer.
>>
>> Again, when you say "*But I hijacked DNS on my router*" that (to me) 
>> does not cause any traffic from your station to wunderground to be 
>> redirected to your weewx system unless I'm not understanding what you're 
>> saying.  Perhaps you should tell everybody what your system config is so 
>> those who do interceptor can try to help more. 
>>
>> On Wednesday, January 24, 2024 at 1:38:25 PM UTC-8 Tomasz Lewicki wrote:
>>
>>> I attach PCAP file with packets captured for 120 seconds. TCP/80 only. 
>>> Weewx was shut down. No traffic on this port until I manually have done the 
>>> operation described in one of me previous posts (browser query): 
>>> https://groups.google.com/g/weewx-user/c/O8DTjzeeQcg/m/psrDaMHoAAAJ 
>>>
>>> środa, 24 stycznia 2024 o 22:22:37 UTC+1 vince napisał(a):
>>>
 Stop weewx.  Just run the packet capture and post the .pcap file so 
 others can take a look please.  Be sure to capture only tcp/80.   Compress 
 the pcap file if it's large or post it someplace online where others can 
 download it.

 The gui version of wireshark is much easier to understand.

 On Wednesday, January 24, 2024 at 1:16:50 PM UTC-8 Tomasz Lewicki wrote:

> My mistake. These packets were captured 

[weewx-user] Interceptor.py - unrecognized parameter

[Chris McLeod]

Hello, 

I have interceptor up and runnign with a DNS redirect from my Acurite 
Access and getting the data using the wu-client option in interceptor. The 
only issue I am having is that my logs are getting spammed with the 
following:

interceptor: MainThread: unrecognized parameter rainin=0.00

I turned logging to debug and can see the following with the unrecognized 
parmeter line highlighted:

Jul 26 13:34:11 wxstation weewx[]: interceptor: ServerThread: GET: 
ID=KCOTHORN74&PASSWORD=&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.24&UV=6&humidity=19&tempf=94.7&windspeedmph=1&winddir=100&windgustmph=3&windgustdir=100&dewptf=46.0&dailyrainin=0.00&rainin=0.00
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: raw data: 
ID=KCOTHORN74&PASSWORD=YdrxbW2U&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.24&UV=6&humidity=19&tempf=94.7&windspeedmph=1&winddir=100&windgustmph=3&windgustdir=100&dewptf=46.0&dailyrainin=0.00&
*rainin=0.00*
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: using 
rain_total 0.0 from dailyrainin
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: firmware 
myAcuRite: baromin is barometer
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: *unrecognized 
parameter rainin=0.00*
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter softwaretype=myAcuRite
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter realtime=1
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter rtfreq=35
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter action=updateraw
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: ignored 
parameter ID=KCOTHORN74
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: raw packet: 
{'wind_speed': 1.0, 'barometer': 30.24, 'wind_gust': 3.0, 'dewpoint': 46.0, 
'humidity_out': 19.0, 'uv': 6.0, 'rain': 0.0, 'dateTime': 1564169651, 
'temperature_out': 94.7, 'wind_dir': 100.0, 'rain_total': 0.0, 
'wind_gust_dir': 100.0, 'usUnits': 1}
Jul 26 13:34:11 wxstation weewx[]: interceptor: MainThread: mapped 
packet: {'barometer': 30.24, 'dewpoint': 46.0, 'outHumidity': 19.0, 'UV': 
6.0, 'rain': 0.0, 'dateTime': 1564169651, 'windDir': 100.0, 'outTemp': 
94.7, 'windSpeed': 1.0, 'windGust': 3.0, 'usUnits': 1, 'windGustDir': 100.0}

I can see that there are several other parmeters that are ignored and many 
that are recognized and mapped. 

I am running version 0.46 of the interceptor driver on version 3.9.2 of 
weewx and I can see at line 1206 that 'rainin' is one of several assigned 
to a variable called IGNORED_LABELS and that set also includes all the 
items shown as ignored in the debug output above. 

IGNORED_LABELS = ['relbaro', 'rainin',
  'weeklyrain', 'monthlyrain',
  'weeklyrainin', 'monthlyrainin',
  'realtime', 'rtfreq',
  'action', 'ID', 'PASSWORD', 'PASSKEY', 'dateutc',
  'softwaretype']

Can anyone see why rainin isn't being ignored while the others are? I am 
assuming there is good reason for it to be ignored or it wouldn't be in the 
IGNORED_LABELS grouping. 

Thanks, 

Chris 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/136d6394-ebd1-46c1-bb3d-6f377012ae33%40googlegroups.com.

[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground

[Chris McLeod]

One more thing, I looked back at my syslog once more after posting the 
below and see three lines and thought I would post them for completeness in 
case they help sort the rain issue out.  

Jul 24 22:19:20 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized 
parameter rainin=0.00
Jul 24 22:19:20 Weewx2 weewx[20428]: interceptor: MainThread: skipping rain 
measurement of 0.0: no last rain
Jul 24 22:19:23 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized 
parameter rainin=0.00


On Wednesday, July 24, 2019 at 7:14:40 PM UTC-6, Chris McLeod wrote:
>
> Hello, 
>
> I just got my new Atlas set up and having not done my research found that 
> getting it to work with SDR isn't a solved solution as yet (if I am missing 
> something please tell me) so I decided to go the interceptor route. I have 
> the Access setup up and sending, have the pfSense resolver routing it to my 
> ubuntu box and I can see the data both with tcpdump and with interceptor.py 
> running in debug mode. I have made two attempts at a [[sensor_map]] (one 
> off of tcpdump and one off of interceptor.py in debug mode) but I am still 
> not getting anything but an eroneous rain measurement into the database. I 
> am guessing its the sensor_map that is borked but since I don't know for 
> sure I will be putting much more data here in case someone can assist. 
>
> Thanks in advance,
>
> Chris
>
> weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS
>
> *tcpdump on Ubuntu box:*
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
> 17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 > 
> rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192, 
> length 439: HTTP: GET 
> /weatherstation/updateweatherstation.php?ID=@@@&PASSWORD=*&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.13&UV=1&humidity=19&tempf=92.6&windspeedmph=2&winddir=53&windgustmph=3&windgustdir=90&dewptf=44.3&dailyrainin=0.00&rainin=0.00
>  
> HTTP/1.1
>
> From this I built the following sensor_map
>
> [[sensor_map]]
> barometer = baromin
> UV = UV
> outHumidity = humidity
> outTemp = tempf
> windSpeed = windspeedmph
> windDir = winddir
> windGust = windgustmph
> windGustDir= windgustdir
> dewpoint = dewptf
> rain = rainin
>
> but got nothing but the humidity on to the index.html
>
> *interceptory.py in manually with device type acurite-bridge*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen 
> --port=80
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
>
> *interceptor.py in manual mode with device type observer (found old post 
> where someone mentioned they got it going with observer)*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
> --port=80
> identifiers: {}
>
> *Interceptor.py debug output w/accurite-bridge setting*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen 
> --port=80 --bug
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
> raw data: 
> ID=KCOTHORN74&PASSWORD=YdrxbW2U&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.20&UV=1&humidity=53&tempf=74.7&windspeedmph=8&winddir=34&windgustmph=16&windgustdir=37&dewptf=56.4&dailyrainin=0.08&rainin=0.00
> raw packet: {'winddir..': 34.0, 'dateTime': 1564016918, 'usUnits..': 1, 
> 'pressure..': 30.2, 'temperature..': 74.7, 'dateTime..': 1564016918, 
> 'windspeed..': 8.0, 'rainfall..': None, 'usUnits': 1, 'humidity..': 53.0}
> mapped packet: {'pressure': 30.2, 'usUnits': 1, 'dateTime': 1564016918}
>
> As you can see the items here are named quite a bit differently than in 
> just the raw HTTP GET so I generated a new sensor_map
>
>   [[sensor_map]]
> barometer = pressure
> outHumidity = humidity
> outTemp = temperature
> windSpeed = windspeed
> windDir = winddir
> dewpoint = dewptf
> rain = rainfall
> UV = UV
>
> And now I have lost the barometric pressure.  
>
> So as you can see the data is getting sent from my access to wun

[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground

[Chris McLeod]

Hello, 

Sorry for the wasted post, I have this sorted (for the most part). 
Apparently I was a bit overdone getting the networking sorted and didn't 
read the fine manual provided for interceptor so I missed there was a 
wu-client device. Once that was set things work much, much better. The only 
error I am getting in syslog is:

Jul 24 22:21:08 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized 
parameter *rainin=0.00*

I removed the sensor_map so I guess this is part of interceptor.py? Below 
is representative of what I get when running interceptor.py in debug mode:

:~$ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=listen 
--port=80 --debug
identifiers: {}
raw data: 
ID=@@@&PASSWORD=&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.26&UV=0&humidity=42&empf=76.6&windspeedmph=4&winddir=195&windgustmph=7&windgustdir=0&dewptf=51.8&
*dailyrainin=0.00*&*rainin=0.00*
raw packet: {'wind_speed': 4.0, 'barometer': 30.26, 'wind_gust': 7.0, 
'dewpoint': 51.8, 'humidity_out': 42.0, 'uv': 0.0, 'rain': None, 
'dateTime':1564028339, 'temperature_out': 76.6, 'wind_dir': 195.0, 
'rain_total': 0.0, 'wind_gust_dir': 0.0, 'usUnits': 1}
mapped packet: {'barometer': 30.26, 'dewpoint': 51.8, 'outHumidity': 42.0, 
'UV': 0.0, *'rain': None*, 'dateTime': 1564028339, 'windDir': 195.0, 
'outemp': 76.6, 'windSpeed': 4.0, 'windGust': 7.0, 'usUnits': 1, 
'windGustDir': 0.0}

I see that I am getting dailyrain from the wu data and it is likely getting 
mapped to rain, would it be better to map rainin to rain and let weewx 
calculate my daily rain? Any assistance on this appreciated as rain 
measurement is one of my primary wants from this setup. 

Thanks, 

Chris 




On Wednesday, July 24, 2019 at 7:14:40 PM UTC-6, Chris McLeod wrote:
>
> Hello, 
>
> I just got my new Atlas set up and having not done my research found that 
> getting it to work with SDR isn't a solved solution as yet (if I am missing 
> something please tell me) so I decided to go the interceptor route. I have 
> the Access setup up and sending, have the pfSense resolver routing it to my 
> ubuntu box and I can see the data both with tcpdump and with interceptor.py 
> running in debug mode. I have made two attempts at a [[sensor_map]] (one 
> off of tcpdump and one off of interceptor.py in debug mode) but I am still 
> not getting anything but an eroneous rain measurement into the database. I 
> am guessing its the sensor_map that is borked but since I don't know for 
> sure I will be putting much more data here in case someone can assist. 
>
> Thanks in advance,
>
> Chris
>
> weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS
>
> *tcpdump on Ubuntu box:*
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
> 17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 > 
> rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192, 
> length 439: HTTP: GET 
> /weatherstation/updateweatherstation.php?ID=@@@&PASSWORD=*&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.13&UV=1&humidity=19&tempf=92.6&windspeedmph=2&winddir=53&windgustmph=3&windgustdir=90&dewptf=44.3&dailyrainin=0.00&rainin=0.00
>  
> HTTP/1.1
>
> From this I built the following sensor_map
>
> [[sensor_map]]
> barometer = baromin
> UV = UV
> outHumidity = humidity
> outTemp = tempf
> windSpeed = windspeedmph
> windDir = winddir
> windGust = windgustmph
> windGustDir= windgustdir
> dewpoint = dewptf
> rain = rainin
>
> but got nothing but the humidity on to the index.html
>
> *interceptory.py in manually with device type acurite-bridge*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen 
> --port=80
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
>
> *interceptor.py in manual mode with device type observer (found old post 
> where someone mentioned they got it going with observer)*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
> --port=80
> identifiers: {}
>
> *Interceptor.py debug output w/accurite-bridge setting*

[weewx-user] Acurite Atlas/Access with interceptor and wunderground

[Chris McLeod]

Hello, 

I just got my new Atlas set up and having not done my research found that 
getting it to work with SDR isn't a solved solution as yet (if I am missing 
something please tell me) so I decided to go the interceptor route. I have 
the Access setup up and sending, have the pfSense resolver routing it to my 
ubuntu box and I can see the data both with tcpdump and with interceptor.py 
running in debug mode. I have made two attempts at a [[sensor_map]] (one 
off of tcpdump and one off of interceptor.py in debug mode) but I am still 
not getting anything but an eroneous rain measurement into the database. I 
am guessing its the sensor_map that is borked but since I don't know for 
sure I will be putting much more data here in case someone can assist. 

Thanks in advance,

Chris

weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS

*tcpdump on Ubuntu box:*

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 > 
rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192, 
length 439: HTTP: GET 
/weatherstation/updateweatherstation.php?ID=@@@&PASSWORD=*&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.13&UV=1&humidity=19&tempf=92.6&windspeedmph=2&winddir=53&windgustmph=3&windgustdir=90&dewptf=44.3&dailyrainin=0.00&rainin=0.00
 
HTTP/1.1

>From this I built the following sensor_map

[[sensor_map]]
barometer = baromin
UV = UV
outHumidity = humidity
outTemp = tempf
windSpeed = windspeedmph
windDir = winddir
windGust = windgustmph
windGustDir= windgustdir
dewpoint = dewptf
rain = rainin

but got nothing but the humidity on to the index.html

*interceptory.py in manually with device type acurite-bridge*

cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen 
--port=80
identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}

*interceptor.py in manual mode with device type observer (found old post 
where someone mentioned they got it going with observer)*

cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
--port=80
identifiers: {}

*Interceptor.py debug output w/accurite-bridge setting*

cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen 
--port=80 --bug
identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
raw data: 
ID=KCOTHORN74&PASSWORD=YdrxbW2U&softwaretype=myAcuRite&dateutc=now&action=updateraw&realtime=1&rtfreq=35&baromin=30.20&UV=1&humidity=53&tempf=74.7&windspeedmph=8&winddir=34&windgustmph=16&windgustdir=37&dewptf=56.4&dailyrainin=0.08&rainin=0.00
raw packet: {'winddir..': 34.0, 'dateTime': 1564016918, 'usUnits..': 1, 
'pressure..': 30.2, 'temperature..': 74.7, 'dateTime..': 1564016918, 
'windspeed..': 8.0, 'rainfall..': None, 'usUnits': 1, 'humidity..': 53.0}
mapped packet: {'pressure': 30.2, 'usUnits': 1, 'dateTime': 1564016918}

As you can see the items here are named quite a bit differently than in 
just the raw HTTP GET so I generated a new sensor_map

  [[sensor_map]]
barometer = pressure
outHumidity = humidity
outTemp = temperature
windSpeed = windspeed
windDir = winddir
dewpoint = dewptf
rain = rainfall
UV = UV

And now I have lost the barometric pressure.  

So as you can see the data is getting sent from my access to wunderground, 
redirected by pfSense to my Ubuntu box. I had hoped that would be the hard 
part and getting it into the db would be easier but I am obviously doing 
something wrong. Any assistance appreciated. I will respond quicky for asks 
for any missing infomration. 




-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b4afadb-1126-48c9-9899-fe314a253048%40googlegroups.com.