Re: [weewx-user] NOAA weather radar replacement

[Ralph Underwood]

Thanks


On Wednesday, November 1, 2023 at 1:49:00 PM UTC-7 Ben Cotton wrote:

> On Wed, Nov 1, 2023 at 4:17 PM Ralph Underwood  wrote:
> >
> > I was using the NOAA Aviation Radar image (
> https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif)
> > in my Seasons skin. They improved/fixed it so it no longer works.
> >
> > Anyone find a replacement that works from NOAA?
> > I find some images but they are all national US, I live on the left 
> coast and really only want to see a NW regional view.
>
> There are loops available for specific sites as well as regional and
> CONUS images at https://radar.weather.gov/ridge/standard/
>
> -- 
> Ben Cotton (he/him)
> TZ=America/Indiana/Indianapolis
>

-- 
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/4dc79cc2-5bb3-4aa4-bdf2-615b57eb5f81n%40googlegroups.com.

[weewx-user] NOAA weather radar replacement

[Ralph Underwood]

I was using the NOAA Aviation Radar image 
(https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif)
in my Seasons skin. They improved/fixed it so it no longer works.

Anyone find a replacement that works from NOAA?  
I find some images but they are all national US, I live on the left coast 
and really only want to see a NW regional view.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6d734334-f790-406e-ba33-506491630776n%40googlegroups.com.

Re: [weewx-user] plots and how to display a constant value ie a limit

[Ralph Underwood]

Probably not too elegant, I have been setting soilTemp4 to 32 and setting 
the label to "Freezing" and adding it to any charts that I want to show 
freezing.

-- 
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/6d49fa86-a98e-4db0-95b8-5aea75a2eca8n%40googlegroups.com.

[weewx-user] Unknown Type using PurpleAir sensor

[Ralph Underwood]

I recently installed a PurpleAir outdoor sensor. It’s connected on wifi and 
appears to be sending data. I can display all of the data points listed in 
the purple air driver docs on a WeeWx Seasons page. 


When I attempt to a create a graph - I get the errors in the log below 
(this is with logging set to 0 - if more is needed I can set it to 1 and 
get a very big log as the MQTT reports a lot)


*Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
weewx.UnknownType: purple_temperature*

If I comment out the offending line, nearly the same error will occur for 
the next purple value.


Did I miss something in the wee_extension install? Where do I create or 
link the various purple data points to a type(s)?



Thanks.






I’m running WeeWx 4.5.1


pi@JV-Wx:/home/weewx/bin $ ./wee_extension --list

Extension NameVersion   Description

MQTTSubscribe 1.6.1 Augment WeeWX records or packets with data MQTT

purpleair 0.4   Collect Purple Air air quality data.

mem   1.1   Collect and display process memory usage.



Raspberry Pi 4



ep 24 17:45:24 JV-Wx weewx[15299] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 13 files in 7.62 seconds

Sep 24 17:50:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:47:00 PDT (1632530820) to database 'purpleair.sdb'

Sep 24 17:50:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:47:00 PDT (1632530820) to daily summary in 'purpleair.sdb'

Sep 24 17:50:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:50:15 PDT (1632531015) to database 'mem.sdb'

Sep 24 17:50:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:50:15 PDT (1632531015) to daily summary in 'mem.sdb'

Sep 24 17:50:16 JV-Wx weewx[15299] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 1.23 seconds

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
purple_temperature

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
Traceback (most recent call last):

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
  File "/home/weewx/bin/weewx/reportengine.py", line 196, in run

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
obj.start()

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
  File "/home/weewx/bin/weewx/reportengine.py", line 281, in start

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
self.run()

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
  File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
self.genImages(self.gen_ts)

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
  File "/home/weewx/bin/weewx/imagegenerator.py", line 181, in genImages

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
aggregate_interval=aggregate_interval)

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
  File "/home/weewx/bin/weewx/xtypes.py", line 94, in get_series

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
raise weewx.UnknownType(obs_type)

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
weewx.UnknownType: purple_temperature

Sep 24 17:50:16 JV-Wx weewx[15299] ERROR weewx.reportengine:   
Generator terminated

Sep 24 17:50:16 JV-Wx weewx[15299] INFO weewx.reportengine: Copied 0 files 
to /home/weewx/public_html

Sep 24 17:50:16 JV-Wx weewx[15299] INFO weewx.cheetahgenerator: Generated 1 
files for report mem in 0.02 seconds

Sep 24 17:50:16 JV-Wx weewx[15299] INFO weewx.imagegenerator: Generated 1 
images for report mem in 0.05 seconds

Sep 24 17:50:16 JV-Wx weewx[15299] INFO weewx.reportengine: Copied 0 files 
to /home/weewx/public_html/mem

Sep 24 17:50:24 JV-Wx weewx[15299] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 13 files in 7.50 seconds

Sep 24 17:55:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:52:00 PDT (1632531120) to database 'purpleair.sdb'

Sep 24 17:55:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:52:00 PDT (1632531120) to daily summary in 'purpleair.sdb'

Sep 24 17:55:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:55:15 PDT (1632531315) to database 'mem.sdb'

Sep 24 17:55:15 JV-Wx weewx[15299] INFO weewx.manager: Added record 
2021-09-24 17:55:15 PDT (1632531315) to daily summary in 'mem.sdb'

Sep 24 17:55:16 JV-Wx weewx[15299] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 1.25 seconds

Sep 24 17:55:16 JV-Wx weewx[15299] ERROR weewx.reportengine: Caught 

Re: [weewx-user] NWS Radar Changes

[Ralph Underwood]

Thanks. I now have the aviation weather radar displaying.



On Tuesday, January 12, 2021 at 5:30:23 AM UTC-8 mjenk...@gmail.com wrote:

> If you go up a level, the ones not in the folders are the current ones.
>
> https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif
>
>
> On Monday, January 11, 2021 at 10:07:55 PM UTC-6 ral...@gmail.com wrote:
>
>> Anybody able to make the new and improved NWS radar work?  Has anyone 
>> written code to build a dynamic link for the aviation weather radar? It 
>> appears to me that we need to enter date and time into the url for the 
>> radar. I copied the aviation radar link into my skin.conf and it appeared 
>> to work, then after a week I noticed that its showing Dec 31 data.   
>> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>>
>> On Friday, January 1, 2021 at 5:28:07 AM UTC-8 messyp...@gmail.com wrote:
>>
>>> I just found out why my "
>>> http://radar.weather.gov/ridge/lite/N0R/HTX_loop.gif; is broke, and, 
>>> why I can't find the replacement. They redesigned the entire system (from 
>>> something that was working fine) to what could be described as "the new 
>>> Coke" of NWS radar services. This article explains it succinctly:
>>>
>>> https://www.washingtonpost.com/weather/2020/12/21/nws-new-radar-website-slow/
>>> Really disappointing. 
>>> --MP
>>>
>>> On Thursday, December 31, 2020 at 9:44:39 PM UTC+1 tke...@gmail.com 
>>> wrote:
>>>
 Here's another option: NOAA's aviation radar. 
 https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif

 The images load fast and cover the entire USA.

 [image: image.png]

 On Wed, Dec 30, 2020 at 9:52 AM John Mora  wrote:

> I have been using these links:
> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=ILN
> =wui=18=15=N0R=0=1.000=0&
> showstorms=1=1=1=1=1=1 
>
> https://www.wunderground.com/radar/us/oh/cincinnati/iln
>
> Just replace the station with the one you desire.
>
> To me they are an adequate replacement until a better one is found
>
> Cheers!
>
> On Wednesday, December 30, 2020 at 12:40:17 PM UTC-5 
> jo...@johnkline.com wrote:
>
>> >  I haven't see this link listed anywhere yet.
>> It’s listed in this thread.
>>
>> On Dec 30, 2020, at 8:35 AM, Mark Jenks  wrote:
>>
>> Finally got an answer back from NOAA.  I haven't see this link 
>> listed anywhere yet.   Images aren't the best, but it's something better 
>> than the .gz's and straight .gif files
>>
>>
>>
>> https://radar.weather.gov/ridge/lite/
>>
>>
>> On Wednesday, December 23, 2020 at 7:12:15 AM UTC-6 Mark Jenks wrote:
>>
>>> Email contact information here:
>>> https://www.weather.gov/radarfaq
>>>
>>> On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:
>>>
 I just sent an email to NWS.  I'll let you know the response if I 
 get one..

 

 Good Morning!

 For years, there have been many many people who have linked your 
 radar images and loops to their PWS (Personal weather station) 
 websites.  I 
 currently use weewx @ http://weather.mjenks.net
 With the new radar, this is no longer possible, and the .gz 
 versions just aren't good enough quality.  So I have to use someone 
 else's 
 radar now.

 It sure would be nice if you could provide an iframe code snipped 
 that we could embed into our webpages.Or at least recreate the 
 images 
 and loops.

 This is what I have been using that no longer works.

 radar_img = 
 http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
 radar_url = 
 http://radar.weather.gov/ridge/radar.php?product=NCR=GRB=yes

 Thank you!

 Mark Jenks
 Station ID - DW7584

 On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com 
 wrote:

> Thank you for looking into this folks. It sounds as though they 
> have gone the same route as Environment Canada did a long time ago 
> now.  No 
> more animated gifs available, instead they build the animations on 
> the fly 
> with overlays and a repository of images. The best I could do for 
> Environment Canada radars was to create a shell script that runs on 
> the web 
> server cron that guesses at the current time stamp for the latest 
> image and 
> saves it to my webserver.
>
> Less than great.
>
> It sure would be nice if they could just provide an iframe code 
> snipped that we could embed into our webpages.
> Alas.
> Cheers

Re: [weewx-user] NWS Radar Changes

[Ralph Underwood]

Anybody able to make the new and improved NWS radar work?  Has anyone 
written code to build a dynamic link for the aviation weather radar? It 
appears to me that we need to enter date and time into the url for the 
radar. I copied the aviation radar link into my skin.conf and it appeared 
to work, then after a week I noticed that its showing Dec 31 data.   
https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif

On Friday, January 1, 2021 at 5:28:07 AM UTC-8 messyp...@gmail.com wrote:

> I just found out why my "
> http://radar.weather.gov/ridge/lite/N0R/HTX_loop.gif; is broke, and, why 
> I can't find the replacement. They redesigned the entire system (from 
> something that was working fine) to what could be described as "the new 
> Coke" of NWS radar services. This article explains it succinctly:
>
> https://www.washingtonpost.com/weather/2020/12/21/nws-new-radar-website-slow/
> Really disappointing. 
> --MP
>
> On Thursday, December 31, 2020 at 9:44:39 PM UTC+1 tke...@gmail.com wrote:
>
>> Here's another option: NOAA's aviation radar. 
>> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>>
>> The images load fast and cover the entire USA.
>>
>> [image: image.png]
>>
>> On Wed, Dec 30, 2020 at 9:52 AM John Mora  wrote:
>>
>>> I have been using these links:
>>> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=ILN;
>>> brand=wui=18=15=N0R=0=1.000=0
>>> wstorms=1=1=1=1=1=1 
>>>
>>> https://www.wunderground.com/radar/us/oh/cincinnati/iln
>>>
>>> Just replace the station with the one you desire.
>>>
>>> To me they are an adequate replacement until a better one is found
>>>
>>> Cheers!
>>>
>>> On Wednesday, December 30, 2020 at 12:40:17 PM UTC-5 jo...@johnkline.com 
>>> wrote:
>>>
 >  I haven't see this link listed anywhere yet.
 It’s listed in this thread.

 On Dec 30, 2020, at 8:35 AM, Mark Jenks  wrote:

 Finally got an answer back from NOAA.  I haven't see this link listed 
 anywhere yet.   Images aren't the best, but it's something better than the 
 .gz's and straight .gif files



 https://radar.weather.gov/ridge/lite/


 On Wednesday, December 23, 2020 at 7:12:15 AM UTC-6 Mark Jenks wrote:

> Email contact information here:
> https://www.weather.gov/radarfaq
>
> On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:
>
>> I just sent an email to NWS.  I'll let you know the response if I get 
>> one..
>>
>> 
>>
>> Good Morning!
>>
>> For years, there have been many many people who have linked your 
>> radar images and loops to their PWS (Personal weather station) websites. 
>>  I 
>> currently use weewx @ http://weather.mjenks.net
>> With the new radar, this is no longer possible, and the .gz versions 
>> just aren't good enough quality.  So I have to use someone else's radar 
>> now.
>>
>> It sure would be nice if you could provide an iframe code snipped 
>> that we could embed into our webpages.Or at least recreate the 
>> images 
>> and loops.
>>
>> This is what I have been using that no longer works.
>>
>> radar_img = http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
>> radar_url = 
>> http://radar.weather.gov/ridge/radar.php?product=NCR=GRB=yes
>>
>> Thank you!
>>
>> Mark Jenks
>> Station ID - DW7584
>>
>> On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com 
>> wrote:
>>
>>> Thank you for looking into this folks. It sounds as though they have 
>>> gone the same route as Environment Canada did a long time ago now.  No 
>>> more 
>>> animated gifs available, instead they build the animations on the fly 
>>> with 
>>> overlays and a repository of images. The best I could do for 
>>> Environment 
>>> Canada radars was to create a shell script that runs on the web server 
>>> cron 
>>> that guesses at the current time stamp for the latest image and saves 
>>> it to 
>>> my webserver.
>>>
>>> Less than great.
>>>
>>> It sure would be nice if they could just provide an iframe code 
>>> snipped that we could embed into our webpages.
>>> Alas.
>>> Cheers
>>> Chris
>>> On Saturday, December 19, 2020 at 9:59:31 AM UTC-8 
>>> peterq...@gmail.com wrote:
>>>
 I hooked up the NWS gif and it's worse than useless. It's hours old 
 and shows nothing, flashes clutter, and repeats. Now, it should show 
 nothing but the flashing of clutter is super annoying. 

 As much as I'm pissed at WU, I'm going to use their gif while it's 
 available.

 On Sat, Dec 19, 2020 at 7:17 AM wfs...@gmail.com  
 wrote:

> Yes John kind of crummy images and I just tried mine for KILX and 
> 

[weewx-user] Re: Installation at remote site using RPi and VNC?

[Ralph Underwood]

What's wrong with using VNC? I use it to get to two remote Weewx running 
RPi. With the RPi, VNC has a deal to access up to five computers for free.

On Wednesday, December 9, 2020 at 6:33:55 PM UTC-8 wa4...@gmail.com wrote:

> Many good ideas here.
>
> My suggestion:
> Set up an identical package at home. Same model pi, same ip address, same 
> weather station setup.
> That way you can update, reconfigure and test your setup and just carry 
> the sim chip on a visit to your remote site.
>
> On Wednesday, December 9, 2020 at 6:55:44 PM UTC-6 mwall wrote:
>
>> On Wednesday, December 9, 2020 at 11:11:23 AM UTC-5 Sunray wrote:
>>
>>>
>>> Anybody done this or can help otherwise? Many thanks in advance! 
>>>
>>
>> excellent suggestions in this thread, especially using only ssh for 
>> access.  you can always tunnel over the ssh connection for vnc or to 
>> probe/diagnose other parts of the remote network.
>>
>> tor is great, but you can also map port 22 on the pi to some other high 
>> port on the public-facing router.  that will stop a lot of the brute force 
>> ssh attacks.  definitely use certificate-only authentication - no passwords.
>>
>> test the catch-up capabilities while you are on site.  weewx was designed 
>> to get data from any logger, so you should not have any gaps in data, even 
>> if the computer running weewx is down for awhile.  but test it to be sure, 
>> and be sure that your logger interval is short enough to get the data you 
>> want, but long enough to get through the longest outage you anticipate.
>>
>> if you have solar+battery in place, then the weak link will typically be 
>> your internet provider at the remote site.  while you are on site, do some 
>> testing of the cable modem or cell uplink or satellite uplink.  be sure 
>> that it will come back online after power failure, and be sure that your 
>> router will properly re-negotiate with your ISP hardware when everything 
>> comes back.
>>
>> avoid auto-configuration software such as NetworkManager or fakehwclock.  
>> you'll want your systems to remain exactly as you configured them.
>>
>> rpi should boot automatically when it gets power, but for anyone using 
>> intel-based hardware, be sure to set the power-on policy in the bios.  in 
>> some bios this setting is rather obscure, but you want it to be always on.
>>
>> definitely do the periodic probe to a web server whose logs you can query 
>> - dyndns can be pretty reliable, but then someone forgets to pay the bill, 
>> or a dns table gets messed up somewhere, or ...
>>
>> of course, there are also all of the mother nature things to watch out 
>> for - lightning strikes, critters chewing through network or power cables, 
>> salt water penetrating your supposedly waterproof poe connections, 
>> temperatures exceeding 50C in your enclosure after spiders build webs 
>> across all of the ventilation ports, UV degradation of your sensor shields 
>> ...
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ac54f8de-d542-47f1-98f2-5718796f5123n%40googlegroups.com.

[weewx-user] Re: Peet Bros Ultimeter 2100 - Humidity Pad

[Ralph Underwood]

Also the humidity sensor did not come included with the Ultimeter 2100 
package, it is an option.

On Monday, April 20, 2020 at 6:49:26 AM UTC-7, Ralph Underwood wrote:
>
> Did you enter a local barometer reading to the 2100? I don't have my 
> manual handy, but seem to remember that in order for the 2100 to output the 
> barometer reading you first have to calibrate it by entering a local value 
> once. I don't upload to weather sites with my systems but both of my 
> Ultimeter 2100s output  a barometer reading for WeeWx. 
>
>
>
> On Sunday, April 19, 2020 at 5:51:36 AM UTC-7, Burt Wizeman wrote:
>>
>> Thanks for all the info in this group!  It has helped me with my weekend 
>> spent trying to debug some of the issues I ran into.   One of those issues 
>> was that no barometer was showing up at CWOP.  I have now learned that is 
>> due to the calc needing the humidity which I lack. I notice that Weather 
>> Display software in Windows provides CWOP with barometer so I assume that 
>> is pulling humidity from some source.  Is there a way to add a pad to the 
>> Ultimeter driver so it could be configured to grab humidity from another 
>> source so that the altimeter calc could be accomplished?  Any ideas?  
>> Trying to save the 110.00 for the meter.
>>
>> Burt
>> K4SRQ
>>
>

-- 
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/1f7bd9a2-e2be-4aa7-876c-62330f05f6fb%40googlegroups.com.

[weewx-user] Re: Peet Bros Ultimeter 2100 - Humidity Pad

[Ralph Underwood]

Did you enter a local barometer reading to the 2100? I don't have my manual 
handy, but seem to remember that in order for the 2100 to output the 
barometer reading you first have to calibrate it by entering a local value 
once. I don't upload to weather sites with my systems but both of my 
Ultimeter 2100s output  a barometer reading for WeeWx. 



On Sunday, April 19, 2020 at 5:51:36 AM UTC-7, Burt Wizeman wrote:
>
> Thanks for all the info in this group!  It has helped me with my weekend 
> spent trying to debug some of the issues I ran into.   One of those issues 
> was that no barometer was showing up at CWOP.  I have now learned that is 
> due to the calc needing the humidity which I lack. I notice that Weather 
> Display software in Windows provides CWOP with barometer so I assume that 
> is pulling humidity from some source.  Is there a way to add a pad to the 
> Ultimeter driver so it could be configured to grab humidity from another 
> source so that the altimeter calc could be accomplished?  Any ideas?  
> Trying to save the 110.00 for the meter.
>
> Burt
> K4SRQ
>

-- 
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/5407c57e-e98f-4945-bf26-0aca44057135%40googlegroups.com.

[weewx-user] Re: draw user-defined lines in graphics

[Ralph Underwood]

I like to see the freezing level on many of my charts so I set soilTemp4 to 
32 degrees in the StdCalibrate section of weewx.conf

[StdCalibrate]

[[Corrections]]
# For each type, an arbitrary calibration expression can be given.
# It should be in the units defined in the StdConvert section.
# Example:
foo = foo + 0.2
soilTemp4 = 32

This allows me to add soilTemp4 to any chart.

[image: Outside Temperature]
Not sure about about setting a wind limit, but maybe this will get you 
started.

>
>

-- 
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/77814759-2f3d-4e2e-a8ae-32c01eded846%40googlegroups.com.

[weewx-user] Re: MQTT client service - proof of concept/alpha code

[Ralph Underwood]

Bravo! Look forward to testing next month when I should have some free 
time. 



On Tuesday, April 9, 2019 at 1:45:51 PM UTC-7, bell...@gmail.com wrote:
>
> To further my WeeWX/MQTT/Python knowledge,  I have written a WeeWX 
> multi-threaded service. One thread receives the MQTT messages and puts them 
> on a queue. In the other thread, when a NEW_ARCHIVE_RECORD event is 
> received, it process the queue and updates the archive record with the data.
> Currently, processing of the queue means - take the last element and use 
> its data to update the archive record. My next big education will be to 
> develop some type of accumulation of these (essentially software 
> generation). 
> Also, the MQTT payload is expected to be json. I am hoping that other 
> formats can easily be supported by creating a subclass and overriding the 
> function that maps the MQTT payload to a WeeWX like dictionary.
> Being a proof of concept, documentation is lacking, error handling is 
> minimal, limited functionality, no install support, etc.  But, I thought 
> even in this form it might be useful/educational. 
> If interested, it can be found here, 
> https://github.com/bellrichm/weewx-addons/blob/master/user/MQTTSubscribeService.py
> - Rich
>
>

-- 
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] Import MQTT value into weewx database, display via seasons skin

[Ralph Underwood]

Hi George,

Try just writing the file with python - 

m1 = "test"
file = open('/var/tmp/file-test.txt' , 'w')
file.write(str(m1)+'\n')
file.close()

My first time with my python script I had a typo that I could not see for a 
couple of hours - I did learn a lot as I scoured the reference books for 
why it did not work.

Good luck.

Ralph


On Monday, April 8, 2019 at 3:28:51 AM UTC-7, George Alexander wrote:
>
> Hi Ralph,
>
> Unfortunately no, I had been running the script as root.
>
> Thanks anyway, I'll try find another way.
>
>

-- 
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] Import MQTT value into weewx database, display via seasons skin

[Ralph Underwood]

Probably a permissions issue. I run my python script as sudo.  Hope that 
helps.


Ralph



-- 
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] Import MQTT value into weewx database, display via seasons skin

[Ralph Underwood]

I have a small python program that subscribes to mqtt and writes a text 
file. I then use the filepile as a service to get the data into WeeWx. The 
"main" data comes from a Ultimeter station via the driver.

I came up with this approach while I was modifing/testing using the 
WeeWxMQTT driver a service.  It works and I put the conversion to a service 
on the back burner.

#!/usr/bin/python
import syslog
import time
import ftplib
import time
import logging
import paho.mqtt.client as mqtt
 
MQTT_SERVER = "10.0.1.47"
MQTT_TOPIC = "weather"

 # The callback for when the client receives a CONNACK response from the 
server.
def on_connect(client, userdata, flags, rc):
print("Connected with result code "+str(rc))
 
# Subscribing in on_connect() means that if we lose the connection and
# reconnect then subscriptions will be renewed.
client.subscribe(MQTT_TOPIC)
 
# The callback for when a PUBLISH message is received from the server.
def on_message(client, userdata, msg):

#print(msg.topic+" "+str(msg.payload))
#print(str(msg.payload))
   
m1 = (msg.payload).replace(':',' = ')
m2 = m1.split(",")
m3 = m2[1]
m4 = "soilTemp4 = 32"
file = open('/var/tmp/filepile.txt' , 'w')
file.write(str(m3)+'\n')
file.write(str(m4)+'\n')
#print(m3)  
#print (m4)   
#print("file stent")
file.close()
 

   
client = mqtt.Client()
client.on_connect = on_connect
client.on_message = on_message
 
client.connect(MQTT_SERVER, 1883, 60)
 
client.loop_forever()


There are some print lines which are commented out for debugging. I also 
use this to set soilTemp4 to 32 degrees - that's so I can easily add a 
freezing level line on charts.


from weewx.conf:

# Options for extension 'filepile'
[FilePile]
# Where to find the incoming new data:
filename = /var/tmp/filepile.txt
# What unit system they will be in.
# Choices are 'US', 'METRIC', or 'METRICWX'
unit_system = US
# Map from incoming names, to WeeWX names.
[[label_map]]
# Example: incoming observation 'filelabel1' will be mapped to 
'extraTemp4'
INTE = extraTemp2








-- 
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: Help with minor edit to Seasons main page

[Ralph Underwood]

You may find that you need to look to the seasons.css file to see how 
things are formatted in titlebar.inc.


On Saturday, March 30, 2019 at 6:27:40 PM UTC-7, tomn...@frontier.com wrote:
>
> Thanks, that's sort-of what I was thinking, but couldn't find any clues 
> about about where they'd be placed. The existing elements are far left
> and right, but I couldn't see why.
>
> Thx, 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Ralph Underwood]

I haven't been using TOP to monitor memory usage - I have cmon running and 
note the total memory use is creeping up.  I restarted this station a 
couple of times yesterday. I had a request to show the freezing level on 
some charts - ended up setting soilTemp4 to 32 degrees and including it on 
some charts. 


[image: Screen Shot 2019-02-25 at 5.56.31 AM.png]



Ralph



On Sunday, February 24, 2019 at 6:34:05 PM UTC-8, Steve2Q wrote:
>
> My experience so far:
>
> With driver v 0.22, I first did a run of 44 hours with the DISABLE_ 
> removed from the set time and get time portions of the driver. TOP showed 
> 3.3% memory usage at startup, which climbed to 10.4% at 44 hours.
>
> I then replaced the DISABLE_ in both lines which put the driver back to 
> its original state. Again there was 3.3% usage at startup, and while I am 
> writing this, I have 9.1% after 36 hours. I am going to let in run in the 
> current state to see if it levels off.
>
> Ralph, do you see the same thing happening?
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Ralph Underwood]

I will test v0.22.  Thanks!!

On Thursday, February 21, 2019 at 9:04:04 AM UTC-8, Ralph Underwood wrote:
>
> The URL for the development station is http://www.mapleleaf.ruresearch.com. 
>  This station is in my basement lab area - the wind and rain stuff is 
> sitting on a counter so that's why there are no readings for them. The 
> "Temperature 1" reading is from a DS18B20 sensor connected to an Adafruit 
> Huzzah ESP8266 which uses wifi / mqtt. I have a python program running 
> which collects the mqtt data and writes it to a file, which filepile.py 
> reads and puts into WeeWx.  It's working, however the goal is to modify the 
> existing wxMesh and wxMQTT to operate as WeeWx service.
>
>
> The cmon memory chart shows the increasing memory use, there is a big drop 
> when I restarted WeeWx this AM and then started a browser to download the 
> ultimeter.py files.
>
> The driver I tried was the last one Tom posted.
>
>
> On Thursday, February 21, 2019 at 8:32:13 AM UTC-8, Steve2Q wrote:
>>
>> Ralph. Thanks for joining this discussion. A few questions:
>>
>> 1. What is your station URL? There are not too many of us Ultimeter 
>> users, but I think it is great that Tom, Matt, Andrew, Vince and so many 
>> other help out our small population as best they can. Having another 2100 
>> user may make debugging easier (?).
>>
>> 2. Which version of the driver did you try? The newest one, I assume. I 
>> am going to try it with the debug "switches" turned on. And which version 
>> did you roll back to?
>>
>> Steve
>>
>>>
>>>

-- 
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: Second crash after 11 days

[Ralph Underwood]

The URL for the development station is http://www.mapleleaf.ruresearch.com. 
 This station is in my basement lab area - the wind and rain stuff is 
sitting on a counter so that's why there are no readings for them. The 
"Temperature 1" reading is from a DS18B20 sensor connected to an Adafruit 
Huzzah ESP8266 which uses wifi / mqtt. I have a python program running 
which collects the mqtt data and writes it to a file, which filepile.py 
reads and puts into WeeWx.  It's working, however the goal is to modify the 
existing wxMesh and wxMQTT to operate as WeeWx service.


The cmon memory chart shows the increasing memory use, there is a big drop 
when I restarted WeeWx this AM and then started a browser to download the 
ultimeter.py files.

The driver I tried was the last one Tom posted.


On Thursday, February 21, 2019 at 8:32:13 AM UTC-8, Steve2Q wrote:
>
> Ralph. Thanks for joining this discussion. A few questions:
>
> 1. What is your station URL? There are not too many of us Ultimeter users, 
> but I think it is great that Tom, Matt, Andrew, Vince and so many other 
> help out our small population as best they can. Having another 2100 user 
> may make debugging easier (?).
>
> 2. Which version of the driver did you try? The newest one, I assume. I am 
> going to try it with the debug "switches" turned on. And which version did 
> you roll back to?
>
> Steve
>
>>
>>

-- 
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: Second crash after 11 days

[Ralph Underwood]

I have a couple of stations with Ultimeter 2100 and usb-serial connections 
to RPi 3 B+.  Both appear to have increasing memory usage.  

I just copied the "new" ultimeter.py driver to the driver directory and 
restarted - this was my result. I went back to "old" version of driver and 
restarted OK.

Feb 21 07:26:54 RanchWx weewx[7135]: engine: Starting up weewx version 3.9.1
Feb 21 07:26:54 RanchWx weewx[7135]: engine: Station does not support 
reading the time
Feb 21 07:26:54 RanchWx weewx[7135]: engine: Starting main packet loop.
Feb 21 07:26:54 RanchWx weewx[7135]: ultimeter: Failed attempt 1 of 5 to 
get readings: Unexpected buffer length 49
Feb 21 07:26:57 RanchWx weewx[7135]: ultimeter: Failed attempt 2 of 5 to 
get readings: Unexpected buffer length 446
Feb 21 07:27:00 RanchWx weewx[7135]: ultimeter: Failed attempt 3 of 5 to 
get readings: Unexpected buffer length 446
Feb 21 07:27:03 RanchWx weewx[7135]: ultimeter: Failed attempt 4 of 5 to 
get readings: Unexpected buffer length 463
Feb 21 07:27:06 RanchWx weewx[7135]: ultimeter: Failed attempt 5 of 5 to 
get readings: Unexpected buffer length 461
Feb 21 07:27:09 RanchWx weewx[7135]: ultimeter: Max retries (5) exceeded 
for readings
Feb 21 07:27:09 RanchWx weewx[7135]: engine: Main loop exiting. Shutting 
engine down.
Feb 21 07:27:09 RanchWx weewx[7135]: ultimeter: close serial port 
/dev/ttyUSB0
Feb 21 07:27:10 RanchWx weewx[7135]: engine: Caught WeeWxIOError: Max 
retries (5) exceeded for readings
Feb 21 07:27:10 RanchWx weewx[7135]:   Waiting 60 seconds then 
retrying...


On Thursday, February 21, 2019 at 5:51:41 AM UTC-8, Thomas Keffer wrote:
>
> Oops. The set of valid buffer lengths was wrong. Try this one.
>
>
>
> On Thu, Feb 21, 2019 at 5:49 AM Thomas Keffer  > wrote:
>
>> Possibly, but I don't think so. The way I read the documents, a given 
>> instrument has a given buffer length. Yours seems to be 52 bytes, which is 
>> what the driver is expecting.
>>
>> The trouble is there is a communications glitch. Then the number of  
>> bytes may be unknown.
>>
>> It would help if you could include the log for one of these glitches. Be 
>> sure to not only set debug=1 at the top of weewx.conf, but also set 
>> debug_serial in the [Ultimeter] section:
>>
>> debug = 1
>> ...
>>
>> [Ultimeter]
>>   port = XXX
>>   debug_serial = 1
>>
>>
>> At the risk of confusing things, here's another version of the driver. 
>> This one looks for the number of bytes in the serial port buffer, then 
>> reads exactly that many. So, it should work for 48, 50, or 52 byte buffers. 
>> But, it could still have a sync problem.
>>
>> -tk
>>
>> On Thu, Feb 21, 2019 at 5:39 AM Steve2Q > 
>> wrote:
>>
>>> A follow up: According to Peet Bros web site the Ultimeter 2100 (and 
>>> several other models) emit data in 48 byte chunks in Data Logger Mode, 
>>> while ultimeter.py (version .20) apparently expects 52 bytes. Could this be 
>>> the problem?. Here is a snip from their web site:
>>>
>>>
>>>- *Data Logger Mode**:  to manually select, press CLEAR + WIND SPEED 
>>>for 3 seconds. ** While in this mode, records are sent out 
>>>continuously at up to about 120 per minute.  The total record size is 48 
>>>hex digits + header, carriage return and line feed.  (All models)* 
>>>- *Packet Mode**:  to manually select, press CLEAR + WIND CHILL for 
>>>3 seconds.  While in this mode, one record is output every five minutes 
>>> (at 
>>>5 min past the hour, 10 min past, 15 min past, etc.). The total record 
>>>length is 52 hex digits + header, carriage return and line feed.  (All 
>>>models)*
>>>
>>> and this:
>>>
>>> *DATA LOGGER MODE - RECORD STRUCTURE* 
>>>
>>>- *Header = !!  (or || if in Multiple Output Mode) * 
>>>- *Data Fields * 
>>>   - *1. Wind Speed (0.1 kph) * 
>>>   - *2. Wind Direction (0-255) * 
>>>   - *3. Outdoor Temp (0.1 deg F) * 
>>>   - *4. Rain* Long Term Total (0.01 inches) * 
>>>   - *5. Barometer (0.1 mbar) * 
>>>   - *6. Indoor Temp (0.1 deg F) * 
>>>   - *7. Outdoor Humidity (0.1%) * 
>>>   - *8. Indoor Humidity (0.1%) * 
>>>   - *9. Date (day of year) * 
>>>   - *10. Time (minute of day) * 
>>>   - *11. Today's Rain Total (0.01 inches)* * 
>>>   - *12. 1 Minute Wind Speed Average (0.1kph)* *
>>>- *Carriage Return & Line Feed *
>>>
>>>
>>> **Some instruments may not include field 12, some may not include 11 or 
>>> 12. Please contact Peet Bros. if this presents any problem. Total size: 40, 
>>> 44 or 48 characters (hex digits) + header, carriage return and line feed. *
>>>
>>> *PACKET MODE - RECORD STRUCTURE* 
>>>
>>>- *Header = $ULTW * 
>>>- *Data Fields * 
>>>   - *1. Wind Speed Peak over last 5 min. (0.1 kph) * 
>>>   - *2. Wind Direction of Wind Speed Peak (0-255) * 
>>>   - *3. Current Outdoor Temp (0.1 deg F) * 
>>>   - *4. Rain Long Term Total (0.01 in.) * 
>>>   - *5. Current Barometer (0.1 mbar) * 
>>>   - *6. Barometer 

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

What's involved in changing the driver to a service?  My coding skills are 
just above minimal, however I would be happy to be involved in testing. I 
frequently fall asleep reading my 1,540 page "Learning Python" - using it 
as a pillow has only raised by knowledge level slightly.

I have one station in the wild that uses owfs and file parse. I would like 
to add mqtt capability to that one. I was going to experiment with using 
mqtt as driver and both fileparse and owfs as services. One option I have 
been thinking about would be to convert the sensors I use file parse for to 
mqtt - then only having one driver and one service for sensors. That option 
would have two (or more) mqtt clients publishing and WxMesh magically 
sorting it out.

The station at my vacation home has a Ultimeter 2100 and to add mqtt based 
sensors I think I would need to run wxMesh as a service.

Again thanks so much for the help getting this working.

-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

*IT WORKS!*

I added: TIME = dateTime to wxMesh stanza of weewx.conf the stopped and 
restarted WeeWx - waited a few minutes and I now have values showing up in 
/var/www/html/weewx/index.html

Thanks a lot for all of the help!

Now that I have something working I can start experimenting with other 
sensors.

-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?

I thought that the TIME sent from mosquitto would be ignored.

I attempted Vince's suggestion and still same.

I'll look it all over again later.

Thanks 

On Wednesday, April 11, 2018 at 11:24:38 AM UTC-7, vince wrote:
>
> On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>>
>> Line 308 in wxservices.py is failing:
>> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
>> 307 self.latitude, self.longitude, self.altitude_m,
>> 308 data['dateTime'], self.atc)
>>
>>
>>
> I'm wondering if perhaps you have no 'dateTime' in the data[] that you 
> are generating
>
> If you're ok with hacking+slashing in there with a test copy of that file, 
> I'd suggest trying to print 'data' out and see what's in there
>
> Something like (untested):
>
>else:
>try:
>   # the existing stuff on lines 306-308
>except:
>  print data
>
>  
>
>  
>

-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

I didn't start a discussion on that but I will look for it.  I have been 
searching for a post where (I thought it was mwall) mentions setting the 
dateTime to something to force weewx to use the correct one. Or maybe it 
was a dream :)

Thanks for your help.

-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

pi@mapleleaf:~ $ date +%s
1523465424
pi@mapleleaf:~ $ date
Wed Apr 11 09:50:28 PDT 2018

appears to match my iMac time.  The Rpi does not have a realtime clock; 
however I have a couple in my parts drawer. I will find a battery and try 
one of them.

I programmed the Huzzah with another Rpi - when I do a date +%s on both of 
them as fast as I can click the  results are 1523465622 and 1523465625  - I 
think that they are pretty close considering I have to change windows and 
click.




-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

Hi Bill

I rebuilt my development system, installed Jessie, configured rpi, 
installed Mosquitto and weewx with the simulator. Attempted to do the 
extension install of wxMesh, that failed so I manually installed the wxMesh 
file in /usr/share/weewx/user. Changed the driver to wxMesh and made 
changes to weewx.conf as described in wxMesh.py.  

Now I am getting this: (my comments are in* blue*)




Apr 11 08:03:17 mapleleaf systemd[1]: Starting LSB: weewx weather system...
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Initializing weewx version 
3.8.0
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Using Python 2.7.9 (default, 
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Locale is 'en_US.UTF-8'
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: pid file is 
/var/run/weewx.pid
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: debug is 1
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Initializing engine
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading station type wxMesh 
(user.wxMesh)
Apr 11 08:03:17 mapleleaf weewx[4065]: Starting weewx weather system: weewx.
Apr 11 08:03:17 mapleleaf systemd[1]: Started LSB: weewx weather system.
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT host is 10.0.0.161
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT topic is weather
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT client is wxclient
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: polling interval is 5.0
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: label map is {'INTE': 
'inTemp', 'INHU': 'outHumidity'}
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: Connected to MQTT   
 *(I edited this message in wxMesh 
while troubleshooting - used to say "Connected)*
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdTimeSynch
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdConvert
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: StdConvert target unit is 0x1
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdConvert
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdCalibrate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdCalibrate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdQC
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdQC
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr 11 08:03:17 mapleleaf weewx[4079]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 11 08:03:17 mapleleaf weewx[4079]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdArchive
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Archive will use data 
binding wx_binding
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Record generation will be 
attempted in 'hardware'
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Use LOOP data in hi/low 
calculations: 1
Apr 11 08:03:17 mapleleaf weewx[4079]: manager: Daily summary version is 2.0
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Apr 11 08:03:17 mapleleaf weewx[4079]: manager: Starting backfill of daily 
summaries
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdArchive
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.restx.StdStationRegistry
Apr 11 08:03:17 mapleleaf weewx[4079]: restx: StationRegistry: Registration 
not requested.
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.restx.StdWunderground
Apr 11 08:03:17 mapleleaf weewx[4079]: restx: Wunderground: Posting not 
enabled.
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.restx.StdWunderground

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

Thanks Bill.

I have to go to my tax guy. 

When I get back I will reconfigure my development set up with a clean 
install and use my Huzzah and HTU21 and your sketch.

Thanks again!



On Tuesday, April 10, 2018 at 10:14:40 AM UTC-7, Bill Morrow wrote:
>
> On Tuesday, 10 April 2018 12:44:32 UTC-3, Ralph Underwood wrote:
>>>
>>> I understand that you are using the HTU21 and think that it might be 
>>> best if I concentrate on that setup.  Can you post the actual sketch you 
>>> are using?
>>>
>>  
> Attached. I use an Adafruit Feather Huzzah,
>

-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

I restarted mosquitto and when I use mosquitto_sub -d -t weather I get:

Client mosqsub|16684-ru-pi sending CONNECT
Client mosqsub|16684-ru-pi received CONNACK
Client mosqsub|16684-ru-pi sending SUBSCRIBE (Mid: 1, Topic: weather, QoS: 
0)
Client mosqsub|16684-ru-pi received SUBACK
Subscribed (mid: 1): 0
Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r1, m0, 'weather', ... 
(11 bytes))
*temperature*
Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', ... 
(10 bytes))
INTE:72.50
Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', ... 
(10 bytes))
INTE:72.39

So I need to figure out how to clear the buffer.

Don't worry about insulting me. Many have said I know just enough to be 
dangerous.  I fairly sure that I made the sketch changes. Will verify that.

With each run of the sketch loop I get something like:
20.50
68.79
Published: INTE:68.79

The first two lines are serial printing the temp in C and then my converted 
to F value.


-- 
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: Using WeeWxMQTT - problems

[Ralph Underwood]

Thanks Bill for the reply.

I am now sending 

INTE:68.11 

via mqtt

I do note that I do not have TIME in my mqtt message.


WeeWx still not happy with this as the log after starting:

Apr 10 08:24:14 ru-pi systemd[1]: Starting LSB: weewx weather system...
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Initializing weewx version 3.8.0
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Using Python 2.7.9 (default, Sep 
17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Locale is 'en_US.UTF-8'
Apr 10 08:24:14 ru-pi weewx[6379]: engine: pid file is /var/run/weewx.pid
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr 10 08:24:14 ru-pi weewx[6385]: engine: debug is 1
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Initializing engine
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading station type wxMesh 
(user.wxMesh)
Apr 10 08:24:14 ru-pi weewx[6369]: Starting weewx weather system: weewx.
Apr 10 08:24:14 ru-pi systemd[1]: Started LSB: weewx weather system.
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT host is 10.0.0.161
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT topic is weather
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT client is wxclient
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: polling interval is 5.0
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: label map is {'TIME': 
'dateTime', 'INTE': 'outTemp', 'INHU': 'inHumidity'}
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Connected
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.engine.StdTimeSynch
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
user.owfs.OWFSService
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: service version is 0.21
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: binding is archive
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: interface is u
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor map is {'extraTemp': 
'/uncached/28.7A06/temperature', 'inTemp': 
'/uncached/28.03CF0806/temperature'}
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor type map is {}
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor unit system is metric
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
user.owfs.OWFSService
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.engine.StdConvert
Apr 10 08:24:14 ru-pi weewx[6385]: engine: StdConvert target unit is 0x1
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.engine.StdConvert
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.engine.StdCalibrate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.engine.StdCalibrate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.engine.StdQC
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.engine.StdQC
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.engine.StdArchive
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Archive will use data binding 
wx_binding
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Record generation will be 
attempted in 'hardware'
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Use LOOP data in hi/low 
calculations: 1
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Added to queue of 1 message 
temperature
Apr 10 08:24:14 ru-pi weewx[6385]: manager: Daily summary version is 2.0
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Apr 10 08:24:14 ru-pi weewx[6385]: manager: Starting backfill of daily 
summaries
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.engine.StdArchive
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service 
weewx.restx.StdStationRegistry
Apr 10 08:24:14 ru-pi weewx[6385]: restx: StationRegistry: Registration not 
requested.
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading 

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

I found some goof info on the development group and got closer to a working 
setup.  I purchased an Adafruit HTU21 sensor board and using Bill Morrows 
code example I now get MQTT output like this:

TIME:0,INTE:19.36,INHU:59.75
TIME:0,INTE:19.35,INHU:59.74
TIME:0,INTE:19.35,INHU:59.88
TIME:0,INTE:19.32,INHU:59.83

*WeeWx still is not happy as I get this after starting WeeWX:*

Apr  7 18:59:33 ru-pi systemd[1]: Starting LSB: weewx weather system...
Apr  7 18:59:33 ru-pi weewx[19707]: engine: Initializing weewx version 3.8.0
Apr  7 18:59:33 ru-pi weewx[19707]: engine: Using Python 2.7.9 (default, 
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Apr  7 18:59:33 ru-pi weewx[19707]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Apr  7 18:59:33 ru-pi weewx[19707]: engine: Locale is 'en_US.UTF-8'
Apr  7 18:59:33 ru-pi weewx[19707]: engine: pid file is /var/run/weewx.pid
Apr  7 18:59:33 ru-pi weewx[19697]: Starting weewx weather system: weewx.
Apr  7 18:59:33 ru-pi systemd[1]: Started LSB: weewx weather system.
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr  7 18:59:33 ru-pi weewx[19737]: engine: debug is 1
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Initializing engine
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading station type wxMesh 
(user.wxMesh)
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: MQTT host is localhost
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: MQTT topic is weather
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: MQTT client is wxclient
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: polling interval is 5.0
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: label map is {'INTE': 
'outTemp', 'INHU': 'inHumidity'}
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: Connected
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.engine.StdTimeSynch
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
user.owfs.OWFSService
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: service version is 0.21
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: binding is archive
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: interface is u
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: sensor map is {'extraTemp': 
'/uncached/28.7A06/temperature', 'inTemp': 
'/uncached/28.03CF0806/temperature'}
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: sensor type map is {}
Apr  7 18:59:33 ru-pi weewx[19737]: owfs: sensor unit system is metric
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
user.owfs.OWFSService
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.engine.StdConvert
Apr  7 18:59:33 ru-pi weewx[19737]: engine: StdConvert target unit is 0x1
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.engine.StdConvert
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.engine.StdCalibrate
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.engine.StdCalibrate
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.engine.StdQC
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.engine.StdQC
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr  7 18:59:33 ru-pi weewx[19737]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr  7 18:59:33 ru-pi weewx[19737]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Apr  7 18:59:33 ru-pi weewx[19737]: wxMesh: Added to queue of 1 message 
temperature
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.engine.StdArchive
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Archive will use data binding 
wx_binding
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Record generation will be 
attempted in 'hardware'
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Use LOOP data in hi/low 
calculations: 1
Apr  7 18:59:33 ru-pi weewx[19737]: manager: Daily summary version is 2.0
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Apr  7 18:59:33 ru-pi weewx[19737]: manager: Starting backfill of daily 
summaries
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Finished loading service 
weewx.engine.StdArchive
Apr  7 18:59:33 ru-pi weewx[19737]: engine: Loading service 
weewx.restx.StdStationRegistry
Apr  7 18:59:33 ru-pi 

[weewx-user] Using WeeWxMQTT - problems

[Ralph Underwood]

My goals is to add some sensors via MQTT to my stations which are all RPi 3 
and use WeeWx 3.8.0.  I am running the Mosquitto broker on the same RPi as 
WeeWx

One station uses a Ultimeter 2100 driver -* can I use WeeWxMQTT as a 
service*?

Other stations are a combination of OWFS and FileParse (using a python 
program to read from i2c bus on RPi).  

The station I am testing/developing (driving myself crazy) on now has 
WeeWxMQTT set as driver and OWFS as a service. It gives me errors like:
  Apr  6 09:22:44 ru-pi weewx[17871]: wxMesh: Working on queue of 0
  Apr  6 09:22:44 ru-pi weewx[17871]: wxMesh: Sleeping for 5
This tells me that WeeWxMqTT is not finding the MQTT messages in the 
correct format.

I am struggling with getting the esp8266 to output anything resembling the 
expected: 

TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 
4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20,WIND: 0.0,WDIR: 0.0 (from the 
WeeWxMQTT 
wiki)

The output is have managed to send is like this:
* {"temperature":69.12} *



*My Arduino sketch for the esp8266 is:*


// use OWFS temperature sensor

#include 
#include 
#include 
#include 

// Data wire is plugged into pin 2 on the Arduino
#define ONE_WIRE_BUS 5

// Setup a oneWire instance to communicate with any OneWire devices 
// (not just Maxim/Dallas temperature ICs)
OneWire oneWire(ONE_WIRE_BUS);


DallasTemperature sensors();

// Update these with values suitable for your network.
const char* ssid = "My Network";
const char* password = "MyPW";
const char* mqtt_server = "10.0.0.161";

char* topic ="weather";

WiFiClient espClient;
PubSubClient client(espClient);
long lastMsg = 0;
float temp = 0;
int inPin = 5;

String dataString;
char charBuf[150];


void setup_wifi() {
  delay(10);
  // We start by connecting to a WiFi network
  Serial.println();
  Serial.print("Connecting to ");
  Serial.println(ssid);
  WiFi.begin(ssid, password);

  while (WiFi.status() != WL_CONNECTED) 
  {
delay(500);
Serial.print(".");
  }
  Serial.println("");
  Serial.println("WiFi connected");
  Serial.println("IP address: ");
  Serial.println(WiFi.localIP());
}

void reconnect() {
  // Loop until we're reconnected
  while (!client.connected()) {
Serial.print("Attempting MQTT connection...");
// Attempt to connect
if (client.connect("arduinoClient_temperature_sensor")) {
  Serial.println("connected");
} else {
  Serial.print("failed, rc=");
  Serial.print(client.state());
  Serial.println(" try again in 5 seconds");
  // Wait 5 seconds before retrying
  delay(5000);
}
  }
}
 
void setup()
{
  Serial.begin(115200);
  setup_wifi(); 
  client.setServer(mqtt_server, 1883);
  pinMode(inPin, INPUT);
  sensors.begin();
}

void loop()
{
  if (!client.connected()) {
reconnect();
  }
  client.loop();

  long now = millis();
  if (now - lastMsg > 5000) {
lastMsg = now;
sensors.setResolution(12);
sensors.requestTemperatures(); // Send the command to get temperatures
temp = sensors.getTempCByIndex(0);
Serial.println(temp);
temp = (temp *1.8) + 32; // convert to F
Serial.println(temp);
if((temp > -20) && (temp <110))
  dataString = String("{\"temperature\":") + temp + String("}");
  dataString.toCharArray(charBuf, 150);
  {
  client.publish(topic,charBuf );
  }
  }
}

*Any advice would be greatly 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.

[weewx-user] Re: ds18b20 multiple sensors from esp8266 nodemcu to file

[Ralph Underwood]

I am interested in your progress. I have a esp8266 on my work bench - 
haven't got started with it yet. I was looking for options use wifi with my 
OWFS based system. I use the file parse driver to add data connected to 
RPi. 



On Sunday, January 21, 2018 at 10:42:47 AM UTC-8, Andreas Otten wrote:
>
> hmm not working how i want it.
>
> can someone tell me how to read values from a ip adress?
>
> I have on 192.168.0.70 my data comma separated and i want to read the 
> values with:
>
> import syslog
> import requests
> import weewx
> from weewx.wxengine import StdService
>
> class ds18b20(StdService):
> def __init__(self, engine, config_dict):
> super(ds18b20, self).__init__(engine, config_dict)
> d = config_dict.get('PondService', {})
> #self.filename = d.get('filename', 
> '/home/weewx/public_html/data/ds18b20.txt')
> #self.filename = d.get('filename', 'urllib2.urlopen("
> http://192.168.0.70;).read()')
> # link = "http://192.168.0.70;
> syslog.syslog(syslog.LOG_INFO, "ds18b20: using %s" % self.filename)
> self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_file)
>
> def read_file(self, event):
> try:
> with open(self.filename) as f:
> #value = f.read()
> line = f.readline()
> value = line.split(',')
> syslog.syslog(syslog.LOG_DEBUG, "ds18b20: found value of %s" % 
> value)
> event.record['soilTemp1'] = float(value[0])
> event.record['soilTemp2'] = float(value[1])
> event.record['soilTemp3'] = float(value[2])
> event.record['soilTemp4'] = float(value[3])
> except Exception, e:
> syslog.syslog(syslog.LOG_ERR, "ds18b20: cannot read value: %s" 
> % e)
>
> i fail here. What is the line to read from URL? my both attempts are 
> faulty :(
>
>
>
> Am Samstag, 20. Januar 2018 20:31:25 UTC+1 schrieb Andreas Otten:
>>
>> Before i invent the wheel new  :)
>>
>> anybody have a *ino file with a http post to write the values in a file 
>> from multiple ds18b20 sensors ?
>>
>> I have the weewx functions ready, but not the ino file for the esp8266
>>
>> if yes, i am happy when you share it :)
>>
>> if not i made one :)
>>
>

-- 
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: Peet Brothers [Error no 2] ttyUSB0 issue

[Ralph Underwood]

My Ultimeter 2100 has been very reliable. One time after a lightning storm 
it did find its way into the wrong mode. After finding the manual, I hit 
the right key combination and it has been rock solid.

I am also currently using FSWEBCAM in test mode - haven't noticed any 
problems.



On Wednesday, January 17, 2018 at 1:43:35 AM UTC-8, Chris Thompstone wrote:
>
> Hi Terry,
> Don't have a lot of info to offer, other than, I've been running a Peet 
> Bros Ultimeter 2100 for a few years now with Weewx
> For me it runs perfect 24/7 365 days of the year, never need to touch it.
>
> I use an Odroid U3 with an eMMC card in it.  It's completely headless.
> I use:
> ebay link 
> 
> as the USB to serial device.
>
> Nothing else is connected to it other than power and ethernet
>
> My website is:
> http://rollestonpark.myzen.co.uk/
> in case your interested.
>

-- 
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: owfs wireless ?

[Ralph Underwood]

Good suggestion. I can't wait for the ice and snow to be gone for a day or 
two and get the sensor down where I can really troubleshoot what is wrong. 
 Everything is working great with that sensor disconnected.  It could also 
be a problem with AD converter on the Hobby Board's anemometer board.  

While looking for online manual for the vane, I found that Hobby Boards has 
a new owner and the products may be back in production.

And I like transit - I drive a twin turbo Ford Transit!

-- 
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: owfs wireless ?

[Ralph Underwood]

Those ESP8266 look interesting. I ordered a couple so I can do some 
experimenting.

-- 
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: Barometer to use with OWFS station

[Ralph Underwood]

I missed that little detail, the wiki shows separate lines, I just was so 
happy I managed to get the sensor data into a file 

I now have a two line txt file and both readings are picked up by the 
fileparse driver.

Thanks.
 

On Friday, January 6, 2017 at 9:51:13 PM UTC-8, Andrew Milner wrote:
>
> shouldn't each reading be on a separate line - so it should be
> soilTemp1=60.64
> pressure=29.54
>
> rather than
>
> soilTemp1=60.64 pressure=29.54
>
>
> On Saturday, 7 January 2017 07:23:27 UTC+2, Ralph Underwood wrote:
>
>> I made a change so that only the pressure value shows up in my txt file 
>> and it works!  Maybe tomorrow I can figure out what is wrong with the 
>> temperature.
>>
>>
>>

-- 
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: Barometer to use with OWFS station

[Ralph Underwood]

I made a change so that only the pressure value shows up in my txt file and 
it works!  Maybe tomorrow I can figure out what is wrong with the 
temperature.


-- 
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: Barometer to use with OWFS station

[Ralph Underwood]

I used wee_extension to install fileparse.py and now I am stumped with this 
error: fileparse: cannot read value for '61.34,29.534': invalid literal for 
float(): 61.34,29.534

Appears that I might have to do some more studying about floats and such.

-- 
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: Barometer to use with OWFS station

[Ralph Underwood]

I decided to try the barometer sensor on the RPi i2c bus. 

I have managed to get data from the sensor and write out a text file in 
/var/tmp/wxdata.  I have a cron job overwrite the file every minute (for 
now) with fresh readings. 

Attempting to follow the directions in FileParse.py gets me this:
Jan  6 13:26:56 ruWX systemd[1]: Starting LSB: weewx weather system...
Jan  6 13:26:57 ruWX weewx[3511]: engine: Initializing weewx version 3.6.2
Jan  6 13:26:57 ruWX weewx[3511]: engine: Using Python 2.7.9 (default, Sep 
17 2016, 20:26:04) #012[GCC 4.9.2]
Jan  6 13:26:57 ruWX weewx[3511]: engine: Platform 
Linux-4.4.34-v7+-armv7l-with-debian-8.0
Jan  6 13:26:57 ruWX weewx[3511]: engine: pid file is /var/run/weewx.pid
Jan  6 13:26:57 ruWX weewx[3515]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan  6 13:26:57 ruWX weewx[3515]: engine: Initializing engine
Jan  6 13:26:57 ruWX weewx[3515]: engine: Loading station type FileParse 
(user.FileParse)
Jan  6 13:26:57 ruWX weewx[3515]: engine: Caught unrecoverable exception in 
engine:
Jan  6 13:26:57 ruWX weewx[3515]:   No module named FileParse
Jan  6 13:26:57 ruWX weewx[3515]:   Traceback (most recent call 
last):
Jan  6 13:26:57 ruWX weewx[3515]: File 
"/usr/share/weewx/weewx/engine.py", line 841, in main
Jan  6 13:26:57 ruWX weewx[3515]:   engine = 
engine_class(config_dict)
Jan  6 13:26:57 ruWX weewx[3515]: File 
"/usr/share/weewx/weewx/engine.py", line 70, in __init__
Jan  6 13:26:57 ruWX weewx[3515]:  
 self.setupStation(config_dict)
Jan  6 13:26:57 ruWX weewx[3515]: File 
"/usr/share/weewx/weewx/engine.py", line 94, in setupStation
Jan  6 13:26:57 ruWX weewx[3515]:   __import__(driver)
Jan  6 13:26:57 ruWX weewx[3515]:   ImportError: No module named 
FileParse
Jan  6 13:26:57 ruWX weewx[3515]:   Exiting.


I have the FileParse.py in /user/share/weewx.

This all running on a RPi3 with an apt-get installation of WeeWx. I started 
with Simulator and them tried to put FileParse as the station type.

Should I be running the FileParse as a service?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Barometer to use with OWFS station

[Ralph Underwood]

I have a OWFS station on  Rpi going with temps, rain gauge, wind and 
direction. I started work on this station several years ago and and the got 
too busy with my day job. 

In the mean time I implemented at Pete Bros. Ultimeter  2100 station which 
was working fine until a recent power outage, it's 500 miles away so it 
will remain off line for awhile, then I will put it on a UPS. I bought it 
because it is NOT wireless. The wireless stations have proved to be 
unreliable in my local (One of the stations is near several radio 
transmitters, which I think may be part of the problem).

Back to the OWFS station - when I started this station I had a Hobby Boards 
barometer, I was never able to get it to work and Hobby Boards is no more. 
Now I am looking for a way to get a barometer connected to the OWFS 
station. 

Options I am considering are connecting something like a WMR100 via USB and 
using the OWFS as a service to get the wind & rain data instead of using 
the wireless stuff that comes with a WMR100 or using a sensor connected to 
the pins on the RPi. Problem with this approach is the RTC on the RPi  may 
conflict.

Anyone have thoughts or suggestions.

thanks and 
Happy New Year.

-- 
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: Attempting to use a Pete Bros. Ultimeter2100 on a RPi3 with a serial to usb converter

[Ralph Underwood]

I installed the station last week and it appears to be working. I managed 
to break the anemometer while I was installing the mast so I have no wind 
info until my next visit to the site in a week or two. Pete Bros. had the 
parts available and I already have them in hand.  I ended up commenting out 
all of the one-wire stuff for my extra temps as I was getting some weird 
readings from two of the sensors and I figured it would be easier to 
troubleshoot in my "lab" than on-site. 

-- 
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: wee_extension problem

[Ralph Underwood]

That worked when used sudo and put the complete path in for the tgz file.

Thanks. 

I am going to have to study the paths stuff fin linux.


On Saturday, November 5, 2016 at 6:57:08 PM UTC-7, gjr80 wrote:
>
> Hi,
>
> What directory are you in? If you are in the same directory as 
> wee_extension try 
>
> ./wee_extension --install weewx-owfs-0.18.tgz
>
> Note the ./
>
> Gary
>
> On Sunday, 6 November 2016 11:54:16 UTC+10, Ralph Underwood wrote:
>>
>> I am running weewx 3.6.1 on a Rpi  using an Utilmeter 2100. I am trying 
>> to install owfs-0.18 and I can't seem to get past the step "*wee_extension 
>> --install weewx-owfs-0.18.tgz*".
>>
>> I get "command not found".  I can see the wee_extension file in 
>> /home/weewx/bin 
>>
>> I have never used wee_extension before - I suspect I am missing something 
>> that should be obvious.
>>
>> Thanks.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] wee_extension problem

[Ralph Underwood]

I am running weewx 3.6.1 on a Rpi  using an Utilmeter 2100. I am trying to 
install owfs-0.18 and I can't seem to get past the step "*wee_extension 
--install weewx-owfs-0.18.tgz*".

I get "command not found".  I can see the wee_extension file in 
/home/weewx/bin 

I have never used wee_extension before - I suspect I am missing something 
that should be obvious.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Attempting to use a Pete Bros. Ultimeter2100 on a RPi3 with a serial to usb converter

[Ralph Underwood]

I'll second that, great support from users and developers!  

This is the third weewx station I have cobbled together - one with a 
wireless Oregon Scientific, one with one-wire, and now this one with Pete 
Bros. - Plus two more carefully monitoring my basement as I test and 
experiment. The Rpi price makes all of this possible, just skip a couple of 
Starbucks visits and you can buy a computer.  I now know just enough Linux 
to get things going and it is fun learning.

The wireless station looses connectivity too often. That station is located 
near I-90 and I suspect that there is some powerful interference from the 
truckers radios as well as some nearby state radios. Just a suspicion, 
everything worked fine when it was twenty feet away in my workshop, but in 
the field not so much. So I wanted a wired system for my new system to be 
installed at my vacation home. With the demise of Hobby Boards; I was 
looking for an alternative to one-wire. I still plan on adding some 
one-wire sensors to this installation as I have a bundle of temperature 
probes.

Thanks again to all of the supportive users.

On Saturday, October 29, 2016 at 2:13:06 PM UTC-7, Steve2Q wrote:
>
> Ralph..good to see another Peet Bros user (not many of us here). I am not 
> a programmer, but have learned some very basic Linux to tweak my install. 
> One of the things I like about Weewx is all of the support. Tom, mwall, and 
> many others always help out,and have developed drivers for stations that 
> are not very common like ours. Mine is also a 2100.
> Welcome to Weewx. 
> Steve   N2QLQ 
>

-- 
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: Attempting to use a Pete Bros. Ultimeter2100 on a RPi3 with a serial to usb converter

[Ralph Underwood]

Thanks, that got me to a point where WeeWx is running and the log says it 
is ftp'ing. Nothing on the web page. 

Have to go to work for a while and then I will attack it again.

Thanks.


On Thursday, October 27, 2016 at 8:06:50 PM UTC-7, mwall wrote:
>
> On Thursday, October 27, 2016 at 9:15:45 PM UTC-4, Ralph Underwood wrote:
>>
>> Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Unable to load driver: 
>> could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
>> '/dev/ttyUSB0'
>>
>
> hi ralph,
>
> it looks like your rpi does not have the kernel module installed for the 
> usb-serial converter that you are using.
>
> you could try updating your pi to the latest kernel with 'sudo rpi-update'
>
> otherwise you might have to build the kernel module yourself
>
> when the pi is working properly you should see /dev/ttyUSB0 when you plug 
> in the usb-serial converter
>
> 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] Attempting to use a Pete Bros. Ultimeter2100 on a RPi3 with a serial to usb converter

[Ralph Underwood]

I could use some hints on what I need to modify to get the Ultimter to talk 
to WeeWx. 

I have a serial to usb converter as the Rpi does not have a serial port and 
I somehow missed that the Ultimeter was not USB when I ordered it. 

I tried to use this in my weewx.conf :


##

[Ultimeter]
# This section is for the PeetBros Ultimeter series of weather stations.

# Serial port such as /dev/ttyS0, /dev/ttyUSB0, or /dev/cuaU0
port = /dev/ttyUSB0

# The station model, e.g., Ultimeter 2000, Ultimeter 100
model = Ultimeter

# The driver to use:
driver = weewx.drivers.ultimeter

##

part of the tail :

Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Platform 
Linux-4.4.21-v7+-armv7l-with-debian-8.0
Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Using configuration file 
/home/weewx/weewx.conf
Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Initializing engine
Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Loading station type 
Ultimeter (weewx.drivers.ultimeter)
Oct 27 17:24:15 raspberrypi weewx[6672]: ultimeter: driver version is 0.16
Oct 27 17:24:15 raspberrypi weewx[6672]: ultimeter: using serial port 
/dev/ttyUSB0
Oct 27 17:24:15 raspberrypi weewx[6672]: ultimeter: open serial port 
/dev/ttyUSB0
Oct 27 17:24:15 raspberrypi weewx[6672]: import of driver failed: could not 
open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' 
()
Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Unable to load driver: 
could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
'/dev/ttyUSB0'
Oct 27 17:24:15 raspberrypi weewx[6672]:   Exiting...


Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.