date:20190724

[weewx-user] Clearing Archive Memory on Davis Westher Envoy

2019-07-24 Thread Allan Tyson

I have a Davis USB Westher Envoy connected to an RPi running weewx. It was
running fine but I stopped weewx on the RPi and disconnected the Weather Envoy
USB cable from the RPi to connect it to another RPi I was using to install
Raspbian Buster with weewx on a smaller micro SD card so I could save it’s
image to a smaller backup image file having originally installed it on an
internal 120GB SSD drive.
The new installation worked just great but when I reconnected the Weather
Envoy to the original RPi I discovered that the USB loggers’s memory was
somehow corrupted so that weewx would no longer update Nginx. I cleared the
memory by connecting the Logger to my Mac laptop & used WeatherLink to clear
the archive memory.
There was a Post by Tom in 2012 saying you could change the configuration of a
weather envoy using the config utility in weewx as well as using the
WeatherLink software. I did see the instructions for using wee_device to change
the parameters of the Davis driver but when running it I get an unrecognized
hardware error and the Weather Envoy isn’t listed as being supported hardware
in the list of supported hardware. Only the Vantsge Vue and Vantsge Pro2
Consoles are listed though in the pictorial list of supported hardware the
Weather Envoy is shown.
Is there a way of clearing the Weather Envoy archive memory from the command
line of the RPi so I can clear it without having to stop the RPI, disconnect
the Envoy USB cable and connect it to my laptop to use the WeatherLink software
to perform the clearing and then have to reconnect it to my RPi ?.

Allan

--
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/e122fd87-079c-4c63-83ff-44ca9bb88cc4%40googlegroups.com.

[weewx-user] Acurite Access + RaspberryPi --> WU DNS hijacking (DD-WRT) - howto

2019-07-24 Thread Xant



The following is a note response by Matthew in GitHub blog regarding 
Acurite Access:


*weewx does work with the access, but the access must send data in wu 
format. configure the access to send wu data. ideally you would configure 
it to send to the computer running weewx (use dns hijacking for this). then 
configure interceptor to listen (not sniff), and it will simply receive the 
wu data.*

*if you prefer to send to wu, then you must configure the interceptor to 
sniff the traffic (not listen).*

*please post on the weewx user group for further help on this.*

*i am sorry there is not yet a guide specifically for intercepter and 
access*




*1) WU DNS forwarding by DD-WRT router*


Setup>Forced DNS Redirection [On]

Services>ServicesTab>DNSmasq>Additional DNSmasq Options
address=/rtupdate.wunderground.com/Y.Y.Y.Y (where Y.Y.Y.Y is RaspberryPi IP)



*2) Directly test Interceptor* (should receive packages)


# PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=wu-client --mode=listen --port=80



*3) WeeWX Config*


[Interceptor]
# This section is for the network traffic interceptor driver.
driver = user.interceptor
device_type = wu-client
mode = listen
port = 80


If all works, html file generated at /var/www/html/weewx/index.html


PS: repost, with minor tweek

-- 
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/b57d0980-afd2-4ab1-a0e8-5ff284ec11dc%40googlegroups.com.

[weewx-user] Acurite Access + RaspberryPi --> WU DNS hijacking (DD-WRT) - howto

2019-07-24 Thread Xant



The following is a note response by Matthew in GitHub blog regarding 
Acurite Access:


*weewx does work with the access, but the access must send data in wu 
format. configure the access to send wu data. ideally you would configure 
it to send to the computer running weewx (use dns hijacking for this). then 
configure interceptor to listen (not sniff), and it will simply receive the 
wu data.*

*if you prefer to send to wu, then you must configure the interceptor to 
sniff the traffic (not listen).*

*please post on the weewx user group for further help on this.*

*i am sorry there is not yet a guide specifically for intercepter and 
access*




*1) WU DNS forwarding by DD-WRT router*


Setup>Forced DNS Redirection [On]

Services>ServicesTab>DNSmasq>Additional DNSmasq Options
address=/wunderground.com/Y.Y.Y.Y (where Y.Y.Y.Y is RaspberryPi IP)



*2) Directly test Interceptor* (should receive packages)


# PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=wu-client --mode=listen --port=80



*3) WeeWX Config*


[Interceptor]
# This section is for the network traffic interceptor driver.
driver = user.interceptor
device_type = wu-client
mode = listen
port = 80


If all works, html file generated at /var/www/html/weewx/index.html

-- 
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/ea50cd2c-4a94-41ac-a1bd-bb6a59e46851%40googlegroups.com.

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

2019-07-24 Thread 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 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/58fac131-2a28-4ef9

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

2019-07-24 Thread 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*
>
> 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..': 1

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

2019-07-24 Thread Xant

As always, too many hours already trying to make WeeWX on RasperryPi to
connect to Acurite Access, at no result (1st try normal installation; 2nd
try driver standalone; etc).

Acurite Access has a Static DHCP through DD-WRT router. The following
command, returns no result:

PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py
--device=acurite-bridge --mode=sniff --iface=eth0 --filter="src
192.168.1.135 and dst port 80"

Understand there might be other 'strong' approaches (DNS hijack, direct
eth0 connection, etc). Please, advice whats "next" and usually works for
WeeWX Interceptor and Acurite Access.

After much plus hours, I was able to DNS hijack "atlasapi.myacurite.com"
(this is the "new" API/myacurite.com address) to RaspberryPi/WeeWX IP
address through DD-WRT DNSmasq/DNS Forwarding... still, no luck and stuck.

The above, was a posted of mine in the GitHub Interceptor blog, which
Matthew was kind to reply and respond as the following (so ALL Acurite
Access users to be aware):

*weewx does work with the access, but the access must send data in wu
format. configure the access to send wu data. ideally you would configure
it to send to the computer running weewx (use dns hijacking for this). then
configure interceptor to listen (not sniff), and it will simply receive the
wu data.*

*if you prefer to send to wu, then you must configure the interceptor to
sniff the traffic (not listen).*

*please post on the weewx user group for further help on this.*

*i am sorry there is not yet a guide specifically for intercepter and
access*

Thanks Matthew for continue support and response.

Some progress! (more to come)

DD-WRT can do DNS forwarding as the following:

Upload data to WU consider
"https://weatherstation.wunderground.com/weatherstation"; (ref:
https://projects.raspberrypi.org/en/projects/uploading-weather-data-to-weather-underground/4)

In DD-WRT:

Setup>Forced DNS Redirection [On]

Services>ServicesTab>DNSmasq>Additional DNSmasq Options
address=/website/forwardIP , or in this case
address=wunderground/Y.Y.Y.Y

In RaspberryPi:

PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py
--device=wu-client --mode=listen --port=80

Finally some data packages. Now, trying with WeeWX and identifiers.

Best, ZX

--
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/5993451e-d755-4db3-ae6c-b5d6e0837512%40googlegroups.com.

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

2019-07-24 Thread Xant



On Wednesday, July 24, 2019 at 9:14:40 PM UTC-4, 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 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/4cb8264a-5d4a-4a21-a0f6-29c1f3bf1faa%40googlegroups.com.

Re: [weewx-user] Re: OWFS install instructions

2019-07-24 Thread Glenn McKechnie

The additional information you provided helps, but I'm curious. You
say an original Dallas weather station - is this the AAG station with
wind vane, anenometer?
What other sensors do you have - temperature?

My first reaction seeing the i2c would have been that weewx-OWFS.py is
not the path, however following up on your later hints leads to a
schematic and a set of instructions  which suggest it may well work
with mwalls script.

https://www.abelectronics.co.uk/kb/article/3/owfs-with-i2c-support-on-raspberry-pi

The schematic also hints that a 'strict' i2c method may not be required.

Have you run through that AB Electronics HowTo above? If you can get a
result from that then OWFS.py should work as well as it uses the
ow-server.

>From a wee_extension install of owfs on a weewx installed via the
setup.py method
owfs.py - that script will be found in  /home/weewx/bin/user Nothing
should need to be touched / edited within that script but if you're
familiar with 1-wire terminology it will offer clues.
The actual 1-wire configuration section will have been added to your
existing weewx.conf file in /home/weewx under a heading labelled
[OWFS]

What version of Debian runs on the pi? ie: can you get owserver
installed and running as per that HowTo? (A recent post suggests the
Buster version may have issues)

On 25/07/2019, Bret Craytor  wrote:
>
>
> On Wednesday, July 24, 2019 at 10:10:31 PM UTC-5, Bret Craytor wrote:
>>
>> I can't seem to find instructions on how to install a i2c to 1-wire
>> adaptor to an original Dallas Semicondutor 1-wire weather station.  I have
>>
>> OWFS installed, and ran setup.py using the Texas Weather as the extension,
>>
>> then used wee_extension to add the owfs (0.21) files.  I saw some
>> instructions, but with the re-boots, I can't find where they went.
>>
>> Can somebody point me in the right direction? do I need OWFS.py?
>>
>> Bret
>>
>
> by the way using a Raspberry Pi 3B
> AB electronics UK  i2c-onewire adapter
>
> --
> 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/06369fc5-ab58-4235-bb29-48642d1fc837%40googlegroups.com.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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/CAAraAzhOLL_-aRgXn1fy5EQ7LRnRMhnRZUDTrfBnSA_L8ePh5g%40mail.gmail.com.