[weewx-user] Odd MQTT & Belchertown skin interaction.

2020-09-23 Thread Tim Tuck 

Hi all,

I have "Cloud Base" on my front page and it shows like below when first 
accessing my server


Once MQTT kicks in it does this ...

I've checked my config a couple of times but I cant see what might be 
causing this!


You can see this for yourselves here... 
http://metoffice.skybase.net/weewx/belchertown/


Any ideas of what to look at appreciated. I didn't do this on my other 
server.:-[


thanks

Tim

Extension Name    Version   Description
Belchertown   1.2   A clean modern skin with real time streaming 
updates and interactive charts. Modeled after BelchertownWeather.com

GW1000    0.1.0b12  WeeWX driver for GW1000 WiFi gateway.
mqtt  0.23  Upload weather data to MQTT server.
aqi   1.3   Calculates air quality indexes.

--
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/da5f1868-fb5d-2459-9bf8-9f0cbd0f7837%40skybase.net.

Re: [weewx-user] How to display pm2.5 & lightning graphs?

2020-09-23 Thread Tim Tuck 

Hi Andy,

I have PM2.5 from my WH41 graphing in my Belchertown skin, you can see 
that on the bottom left of this page...


http://metoffice.skybase.net/weewx/belchertown

I put

    [[chart7]]
    title = PM 2.5
  [[[pm2_5]]]
 name = PM 2.5
 zIndex = 1
 color = "#ffc83f"
  y_label = "ug/m3"

in/etc/weewx/skins/Belchertown/graphs.conf

I have a lightning graph too but since there hasn't been any lightning 
there has been nothing to test the graphing. I've been tempted to build 
a spark gap and create my own "lightning" to work things out.


I've yet to create the graphs for batteries etc. I'll work on that soon 
since I 4 soil moisture sensors too.


regards

Tim


On 22/9/20 7:26 pm, Big OB wrote:
I have been using weewx 4.1.1 on a RPi since April using 
ecowitt-client from a HP2551 with no problems at all, but have 
recently added a lightning detector (wh57), pm2.5 detector (wh41) and 
a DP1500 (GW1000) gateway to my set up.


I changed over to using the GW1000 API (installed 
by/wee_extension/ utility on a weewx package install) which appears to 
be working fine - data received with no problem, and after searching 
here managed to get the 'Radiation' graph working, but still have not 
found any answer on how to get the pm2.5 and lightning graphs showing.


Battery status for wh57 and wh41 show up on weather station screen 
under sensor status so I assume it must be a simple task to get the 
graphs showing.


GW1000 'test-driver' shows the following:

2020-09-22 10:22:27 BST (1600766547): UV: 1, dateTime: 1600766547, 
dayRain: 0.0, daymaxwind: 4.6, inHumidity: 58, inTemp: 21.9, 
lightning_distance: 1, lightning_last_det_time: 1600584975, 
lightning_strike_count: None, luminosity: 22630.0, monthRain: 0.7, 
outHumidity: 87, outTemp: 17.6, pm2_5: 15.0, pm2_51_24hav: 9.7, 
pressure: 1007.8, rain: None, rainRate: 0.0, relbarometer: 1011.8, 
stormRain: 0.0, usUnits: 17, uvradiation: 27.9, weekRain: 0.0, 
wh41_ch1_batt: 6, wh57_batt: 5, wh65_batt: 0, windDir: 258, windGust: 
2.0, windSpeed: 1.3, yearRain: 258.9


Any assistance much appreciated - VMT.

Andy




--
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/5635dfd3-4537-9015-e5f8-f6cd0a93406c%40skybase.net.

[weewx-user] Re: Bresser 6in1

2020-09-23 Thread sc.lep...@gmail.com 
Hello all, 
I want to buy a bresser station but I dont know which model to choose. ( I 
want to user it with weewx software on rpi2) 

It seems with some bresser station I will connect to weewx on rpi2 .
( the first url from this post doesnt work well ;-( ) 
Can someone help ? 

Actually I user WMR200 from oregon  but rain is out of service and I want 
to change all my station but continue to use weewx .
https://meteo-pontscorff.fr/

Thanks a lot / best regards

Stéphane 

Le samedi 16 mai 2020 à 15:00:55 UTC+2, Remy Lavabre a écrit :

> Hello Bob,
>
> Indeed you have done a very good job !!!
> I have a Bresser 6-1 station and everything works perfectly with my 
> Raspberry Pi Zero W !!!
> That's great ! I can only thank you!
>
> Without wanting to abuse, I would however have three small things to ask 
> you:
>
> A/ My weather station is equipped with 3 additional sensors (thermometers 
> and hygrometers).
> The three temperature information (with history) appears on the html page 
> xxx.xxx.xxx.xxx/weewx/
> in the form of three curves in a single table 
> (Temperature1Temperature2Tempreature3)
> The humidity 1,2 and 3 of the three additional probes does not appear 
> anywhere, however...
> Is this information retrieved by your pilot and if so, how to display it 
> as for the temperature?
>
> B/ I use the SteelSeries-Weather-Gauges which correspond exactly to what I 
> want (https://github.com/mcrossley/SteelSeries-Weather-Gauges).
> Everything is displayed correctly and perfectly except ... the 
> temperatures 1,2,3 and the humidity 1,2 and 3 of my three additional probes!
> Could you tell me what to add (and where) to bring up an additional 
> temperature gauge (with 3 pushbuttons 1,2 and 3) as well as an additional
> humidity gauge (with if possible again 3 push buttons) to display this 
> additional data on the html page?
>
> C/ My Bresser weather station records the data every 30 minutes. Is it 
> possible with Weewx and
> your driver to recover this data in a file in "CSV" format as does Windows 
> software which
> connects via the USB port? And if yes, how ?
>
> Here bob, know that you have done a lot for me with your pilot and that 
> the solution to the
> three questions that remain would fulfill all my hopes !
>
> And thank you again for this great pilot 
> Signed a great admirer of your work!  ;-)
>

-- 
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/57a35220-734c-4eef-b0f4-0ed077e419c8n%40googlegroups.com.

[weewx-user] Re: Extension to read purpleAir data via json?

2020-09-23 Thread vince 
On Wednesday, September 23, 2020 at 12:03:21 PM UTC-7, loonsailor wrote:
>
> I'd like to add air quality to my weewx data.  There is a purple air 
> sensor very near to me, but it's not mine and I don't have lan access to 
> it.  It does report to purpleair.com, and I can read the data from there 
> in json format.  I thought I remembered seeing that somebody had done an 
> extension to read from purple air.com, instead of accessing the sensor 
> directly, but I can't find it now.  Does it exist, or was I imagining it?


I have an extension at https://github.com/vinceskahan/weewx-purpleair that 
you can probably tweak a little to do this.


-- 
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/627d95d4-b9f0-4fdb-b1b7-b785ef8300e7o%40googlegroups.com.

[weewx-user] Extension to read purpleAir data via json?

2020-09-23 Thread 'loonsailor' via weewx-user 
I'd like to add air quality to my weewx data.  There is a purple air sensor 
very near to me, but it's not mine and I don't have lan access to it.  It 
does report to purpleair.com, and I can read the data from there in json 
format.  I thought I remembered seeing that somebody had done an extension 
to read from purple air.com, instead of accessing the sensor directly, but 
I can't find it now.  Does it exist, or was I imagining it?

-- 
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/32275c47-dceb-4ad9-be8b-55a5416b7fa3n%40googlegroups.com.

Re: [weewx-user] Re: GW1000 0.1.0b12 bugs ??

2020-09-23 Thread Larry 
Yes Gary - as soon as I cycled power to the GW1000 - then Weewx connected 
up to it again on it's next retry  and works fine again.  I have had it 
crash 3 times in past month though I did not pay close attention to find 
the cause . I will from now on. Thanks for your efforts developing the 
driver. 
Larry 

On Wednesday, September 23, 2020 at 5:27:03 AM UTC-5 gjr80 wrote:

> Larry,
>
> So I guess the GW1000 driver picked up the GW1000 again? If the WSView app 
> doesn't pick p the GW1000 then the driver probably doe snot have much 
> chance either. I believe there have been a few issues after firmware 
> updates, I have been getting into the habit of verifying everything is 
> working after a firmware update.
>
> From the log extract you posted the driver appears to have been doing what 
> it should have on loss of contact with/being unable to contact the GW1000.
>
> Gary
>
>
> On Wednesday, 23 September 2020 12:42:33 UTC+10, Larry wrote:
>>
>> okay I just checked with WSview and notice it isn't seeing the weather 
>> station . I guess that is the problem. Seems like these issues happened 
>> after the last Ecowitt updates. 
>> I repowered the GW1000 and it came back to life and WSView now sees it 
>> again. 
>> The lights were all on the GW1000 - not sure what made it crash . 
>>
>> Larry 
>>
>> On Tuesday, September 22, 2020 at 9:33:06 PM UTC-5 Larry wrote:
>>
>>> I have had three crashes of Weewx on my Raspberry Pi Zero W in past few 
>>> weeks .
>>> Here is the log I have now - not sure if it is the right one you would 
>>> need to gather any clues. 
>>> Any help on what I should do is appreciated 
>>> Thanks  
>>> Larry 
>>>  sudo tail -f /var/log/syslog
>>>
>>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__:   Waiting 
>>> 60 seconds then retrying...
>>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: retrying...
>>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Debug is 0
>>> Sep 22 21:24:34 pizerowx weewx[701] INFO weewx.engine: Loading station 
>>> type GW1000 (user.gw1000)
>>> Sep 22 21:25:01 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to 
>>> detect GW1000 ip address and/or port after 3 attempts
>>> Sep 22 21:25:01 pizerowx weewx[701] ERROR weewx.engine: Import of driver 
>>> failed: Failed to detect GW1000 ip address and/or port after 3 attempts 
>>> ()
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> Traceback (most recent call last):
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> self.console = loader_function(config_dict, self)
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 1136, in loader
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> return Gw1000Driver(**config_dict[DRIVER_NAME])
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 1415, in __init__
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> super(Gw1000Driver, self).__init__(**stn_dict)
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 762, in __init__
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> debug_wind=self.debug_wind)
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 1630, in __init__
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> lost_contact_log_period=lost_contact_log_period)
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> raise GW1000IOError(_msg)
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 
>>> attempts
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__: Unable to load 
>>> driver: Failed to detect GW1000 ip address and/or port after 3 attempts
>>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__:   Waiting 
>>> 60 seconds then retrying...
>>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> lost_contact_log_period=lost_contact_log_period)
>>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine: 
>>> File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
>>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:   
>>> raise GW1000IOError(_msg)
>>> Sep 22 21:23:34 pizerowx

Re: [weewx-user] Feature Request

2020-09-23 Thread Tom Keffer 
1. Not sure what you mean by "native support." There is an uploader
extension.

2. What are you thinking that would be different from running weewx
directly from the command line? This prints out the raw data coming off the
driver, albeit after running through the engine's pipeline.

3. While this would be nice, it also complicates the porting problem, and
can use a huge amount of personpower. I'd rather focus on improving
reliability, and, especially, adaptability of WeeWX. It's goal has always
been to support the hobbyist / enthusiast who wants to try new stuff. It
was never intended as a consumer-grade piece of software, although it has
become that.

4. Usually this is done using an MQTT broker. There are many examples of
this in the Wiki and user forums.

-tk

On Wed, Sep 23, 2020 at 7:20 AM 'karlch...@googlemail.com' via weewx-user <
weewx-user@googlegroups.com> wrote:

> 1. Native support of meteotemplate.
>
> I guess many Users are using meteotemplate because its donationware and a
> really nice piece of software. Is there any plan or possibility to implent
> native support in weewx?
>
>
> 2. Debug Screen with data from the weather station
>
> Maybe i am dumb - but can’t find any possibility to view the „raw“ data
> from my weather station in the console - especially during the first setup
> or recovery after some major changes it could help to find my own mistakes
> ;)
>
> 3. Graphical installer (Terminal and GUI based)
>
> For the most users its really a little bit to hard to change things here
> and there in some python scripts - but the most users don’t need that much
> to change. So i guess a simple and a pro config with a setup wizard could
> improve the user experience and also the installations around the globe.
>
> 4. Easy support of different other sources
>
> We want to add some additional sensors to weewx - but not directly
> connected to the raspberry pi - we want to use some wifi connected
> arduinos. But we don’t know how to setup these in weewx so that this data
> will be stored in the database and forwarded to some cloud services...
>
>
>
> --
> 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/e913164a-231b-4f90-ac07-294f3b135a48n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zECJS-p_8N%3DkUF1iMagn%3D%3DfiSRge7N6H%3D667D%3D5semNBcQ%40mail.gmail.com.

[weewx-user] Re: Feature Request

2020-09-23 Thread vince 
On Wednesday, September 23, 2020 at 7:20:46 AM UTC-7, 
karlch...@googlemail.com wrote:
>
> 3. Graphical installer (Terminal and GUI based)
>
> For the most users its really a little bit to hard to change things here 
> and there in some python scripts - but the most users don’t need that much 
> to change. So i guess a simple and a pro config with a setup wizard could 
> improve the user experience and also the installations around the globe. 
>  
>
 
If you install the packaged version of weewx it asks all the right 
questions already.  Why require a GUI ?   That opens up a lot of complexity 
and potential security risk to get the GUI the permissions to write the 
output file(s) out.

Each extension or driver could potentially require different customization 
(example - Belchertown skin and WeatherFlow UDP driver tend to require a 
lot of editing in weewx.conf).   There is probably no reasonable way to 
handle this generically that I can think of.  Ultimately the user needs to 
be able to edit a simple text file.  That's not much to ask.


4. Easy support of different other sources
>
> We want to add some additional sensors to weewx - but not directly 
> connected to the raspberry pi - we want to use some wifi connected 
> arduinos. But we don’t know how to setup these in weewx so that this data 
> will be stored in the database and forwarded to some cloud services...
>
>  
>

There have been many posts for how to get data into and out of weewx from a 
variety of sensors.  Look around in the wiki and group archive a bit.  
Typically people import a flat file (csv perhaps) or use MQTT for this.

 

-- 
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/0a8ca782-b997-4032-8608-f16ae3b499deo%40googlegroups.com.

[weewx-user] Feature Request

2020-09-23 Thread 'karlch...@googlemail.com' via weewx-user 
1. Native support of meteotemplate.

I guess many Users are using meteotemplate because its donationware and a 
really nice piece of software. Is there any plan or possibility to implent 
native support in weewx?


2. Debug Screen with data from the weather station

Maybe i am dumb - but can’t find any possibility to view the „raw“ data 
from my weather station in the console - especially during the first setup 
or recovery after some major changes it could help to find my own mistakes 
;)

3. Graphical installer (Terminal and GUI based)

For the most users its really a little bit to hard to change things here 
and there in some python scripts - but the most users don’t need that much 
to change. So i guess a simple and a pro config with a setup wizard could 
improve the user experience and also the installations around the globe. 
 
4. Easy support of different other sources

We want to add some additional sensors to weewx - but not directly 
connected to the raspberry pi - we want to use some wifi connected 
arduinos. But we don’t know how to setup these in weewx so that this data 
will be stored in the database and forwarded to some cloud services...

 

-- 
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/e913164a-231b-4f90-ac07-294f3b135a48n%40googlegroups.com.

Re: [weewx-user] Historical Data from KlimaLogg missing in report and database

2020-09-23 Thread David 
Hi.
Attached you find the requested log after "normal" restart: 
20200923_1_DebugLogAfterRestart.txt
As well as another excerpt of the syslog after manual invocing "wee_reports 
weewx.conf 1600671954": 20200923_2_DebugLogAfterManualReport.txt

tke...@gmail.com schrieb am Dienstag, 22. September 2020 um 16:35:09 UTC+2:

> Hard to say without seeing the log. Stop weewx, set debug=1, restart, then 
> post from the restart through the first reporting cycle.
>
> On Tue, Sep 22, 2020 at 12:55 AM David  wrote:
>
>>
>> Hi there,
>> I just installed weewx and really like it!
>> I do have no problems with the reports or data.
>> When I open the index.html I get the layou I expect.
>>
>> Problem is: I only see data starting today when I installed weewx.
>> But I see in syslog that "all" historical data from my KlimaLogg-Device 
>> got read by weewx.
>>
>> So I assume this data should be in the database and should also be 
>> contained in the reports.
>> But it is definitly not contained in reports and seems to be missing in 
>> the database as well. As when I ask the rport to be generated with 
>> timestamp yesterday "he" says not to have the data.
>> Command->  wee_reports weewx.conf 1600671954
>> Output in Syslog: *INFO weewx.cheetahgenerator: Skipping template 
>> index.html.tmpl: generate time 2020-09-21 09:05:54 CEST (1600671954) not in 
>> database*
>>
>> What should I do?
>>
>> Sorry if this might be a dumb question to someone, but if it is: Please 
>> help ;-)
>>
>> Best regards
>> David
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/873a2959-59bc-4445-b87a-2b511e0b2a8cn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/5d6fb322-0711-4759-9731-8568edf6bfd3n%40googlegroups.com.
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.engine: StdConvert target 
unit is 0x1
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.manager: Daily summary 
version is 2.0
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.wxservices: The following 
values will be calculated: pressure=prefer_hardware, altimeter=prefer_hardware, 
appTemp=prefer_hardware, barometer=prefer_hardware, beaufort=prefer_hardware, 
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
heatindex=prefer_hardware, humidex=prefer_hardware, inDewpoint=prefer_hardware, 
maxSolarRad=prefer_hardware, rainRate=prefer_hardware, 
windchill=prefer_hardware, windrun=prefer_hardware
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.wxservices: The following 
algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.engine: Archive will use 
data binding kl_binding
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Sep 23 15:48:36 erdmen wee_reports[4089] INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Sep 23 15:48:36 erdmen wee_reports[4089] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Sep 23

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-23 Thread Andy 

I used these instruction  and 
now I have a sensor here 
. Used the 
SDS011 sensor for this one. Couple of the Plantower sensors on the way. This 
 and this 
.

Andy



On Tuesday, September 22, 2020 at 12:25:32 PM UTC-7 vince wrote:

> On Tuesday, September 22, 2020 at 11:05:10 AM UTC-7, John Kline wrote:
>
>> In my logs, I see that it is a redirect that fails.  It seems 
>> purpleair-38fe.lan cannot be resolved without an internet connection:
>>
>>
>>
> I have a local pihole box with a hosts file in it that is my LAN primary 
> resolver, so I added the alias there to make it resolve without needing 
> Internet access.
>
> Can't stop a determined network engineer with too many computers on the 
> LAN :-)
>
>

-- 
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/aff90d60-488d-4fac-8f01-e0e9ed262414n%40googlegroups.com.

Re: [weewx-user] Re: GW1000 0.1.0b12 bugs ??

2020-09-23 Thread gjr80 
Larry,

So I guess the GW1000 driver picked up the GW1000 again? If the WSView app 
doesn't pick p the GW1000 then the driver probably doe snot have much 
chance either. I believe there have been a few issues after firmware 
updates, I have been getting into the habit of verifying everything is 
working after a firmware update.

>From the log extract you posted the driver appears to have been doing what 
it should have on loss of contact with/being unable to contact the GW1000.

Gary

On Wednesday, 23 September 2020 12:42:33 UTC+10, Larry wrote:
>
> okay I just checked with WSview and notice it isn't seeing the weather 
> station . I guess that is the problem. Seems like these issues happened 
> after the last Ecowitt updates. 
> I repowered the GW1000 and it came back to life and WSView now sees it 
> again. 
> The lights were all on the GW1000 - not sure what made it crash . 
>
> Larry 
>
> On Tuesday, September 22, 2020 at 9:33:06 PM UTC-5 Larry wrote:
>
>> I have had three crashes of Weewx on my Raspberry Pi Zero W in past few 
>> weeks .
>> Here is the log I have now - not sure if it is the right one you would 
>> need to gather any clues. 
>> Any help on what I should do is appreciated 
>> Thanks  
>> Larry 
>>  sudo tail -f /var/log/syslog
>>
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__:   Waiting 
>> 60 seconds then retrying...
>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: retrying...
>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Debug is 0
>> Sep 22 21:24:34 pizerowx weewx[701] INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000)
>> Sep 22 21:25:01 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to 
>> detect GW1000 ip address and/or port after 3 attempts
>> Sep 22 21:25:01 pizerowx weewx[701] ERROR weewx.engine: Import of driver 
>> failed: Failed to detect GW1000 ip address and/or port after 3 attempts 
>> ()
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> Traceback (most recent call last):
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> self.console = loader_function(config_dict, self)
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 1136, in loader
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> return Gw1000Driver(**config_dict[DRIVER_NAME])
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 1415, in __init__
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> super(Gw1000Driver, self).__init__(**stn_dict)
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 762, in __init__
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> debug_wind=self.debug_wind)
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 1630, in __init__
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> lost_contact_log_period=lost_contact_log_period)
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> raise GW1000IOError(_msg)
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:   
>> GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 
>> attempts
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__: Unable to load 
>> driver: Failed to detect GW1000 ip address and/or port after 3 attempts
>> Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__:   Waiting 
>> 60 seconds then retrying...
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:   
>> lost_contact_log_period=lost_contact_log_period)
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:   
>> raise GW1000IOError(_msg)
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:   
>> GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 
>> attempts
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__: Unable to load 
>> driver: Failed to detect GW1000 ip address and/or port after 3 attempts
>> Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__:   Waiting 
>> 60 seconds then retrying...
>> Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: retrying...
>> Sep 22 21:24:34 pizerowx

Re: [weewx-user] Re: alarm module - multiple alarms

2020-09-23 Thread pligg...@gmail.com 
Ok thanks Gary for clarifying that! Not a big issue but we'll see what you 
can do about it. 

//Mikael

onsdag 23 september 2020 kl. 04:20:58 UTC+2 skrev gjr80:

> Mikael,
>
> I believe the old version of alarm.py that had hard coded alarm 
> expressions did print just the offending field but the current version of 
> alarm.py and alarm_multi.py only print the entire record and cannot print 
> just the offending fields. To print just the field would require parsing of 
> the alarm expression to identify the fields involved and then just pass 
> those fields to the mail routine rather than the whole record. Doable but 
> will require a little more code. I will see what I can incorporate in the 
> revised version.
>
> Gary
> On Tuesday, 22 September 2020 at 05:45:19 UTC+10 pligg...@gmail.com wrote:
>
>> Great!
>>
>> One more question. When I used alarm.py I somehow managed to get only the 
>> "faulty" record to show in the email, not every other reading. Don't 
>> remember how I did this. Could you tell me what to change in the code?
>>
>> Alarm expression "extraTemp1 > 52 " evaluated True at 2020-09-21 14:40:00 
>> CEST (1600692000)
>> Record:
>> {'outTempBatteryStatus': 0.0, 'outHumidity': 71.0, 'extraHumid1': 99.9, 
>> 'maxSolarRad': 428.4915916113489, 'extraTemp2': 68.0, 'interval': 10, 'ET': 
>> None, 'ptr': 25408.0, 'rainRate': 0.0, 'heatindex': 60.16181818181818, 
>> 'radiation': None, 'delay': 23.818181818181817, 'inTemp': 
>> 52.980001, 'inDewpoint': 43.832655655290985, 'status': 0.0, 
>> 'barometer': 29.95817287439312, 'windchill': 60.16181818181818, 'dewpoint': 
>> 50.72247794136099, 'windrun': 1.511630402977166, 'rain': 0.0, 'humidex': 
>> 62.800666120830144, 'pressure': 29.050527884772734, 'rxCheckPercent': 
>> 100.0, 'rainTotal': 8.158, 'altimeter': 29.965138110733474, 
>> 'extraTemp3': 64.2866, 'usUnits': 1, 'extraTemp1': 52.025, 'appTemp': 
>> 55.33343408771088, 'UV': None, 'dateTime': 1600692000, 'windDir': 
>> 221.75921118258643, 'outTemp': 60.16181818181818, 'windSpeed': 
>> 9.069782417862998, 'inHumidity': 71.0, 'windGust': 19.68508829706588, 
>> 'windGustDir': 180.0, 'cloudbase': 2998.325092976762
>> So I just want to see the value that trigger the alarm.
>>
>> //Mikael
>>
>> Den mån 21 sep. 2020 15:44gjr80  skrev:
>>
>>> Good that it is working. I think alarm.py and alarm_multi.py diverged 
>>> quite some time ago and some of the common code should be brought back in 
>>> sync. I will have a look through in the coming days and post an updated 
>>> alarm-multi.py to hopefully prevent similar situations developing in the 
>>> future (well at least until WeeWX 5.0 is released :) ).
>>>
>>> Gary
>>>
>>> On Monday, 21 September 2020 at 18:47:23 UTC+10 pligg...@gmail.com 
>>> wrote:
>>>
 Thanks Gary!



 I first tried your new file, but got an error at line 223 --> "s = 
 smtplib.SMTP(self.smtp_host)". I looked at my old alarm.py file and saw 
 that it had _SSL after SMTP
 "s = smtplib.SMTP_SSL(self.smtp_host)" So I put that in the new code 
 and then it sent my mail!


 Here's the log when the error occurred:

 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: 
 Unexpected exception of type 
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  Traceback (most recent call last):
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
    File "/usr/share/weewx/user/alarm_multi.py", line 223, in 
 soundTheAlarm
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  s = smtplib.SMTP(self.smtp_host)
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
    File "/usr/lib/python2.7/smtplib.py", line 256, in __init__
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  (code, msg) = self.connect(host, port)
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
    File "/usr/lib/python2.7/smtplib.py", line 316, in connect
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  self.sock = self._get_socket(host, port, self.timeout)
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
    File "/usr/lib/python2.7/smtplib.py", line 291, in _get_socket
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  return socket.create_connection((host, port), timeout)
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
    File "/usr/lib/python2.7/socket.py", line 575, in create_connection
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  raise err
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR user.alarm_multi: rtgd: 
  error: [Errno 101] Nätverket kan inte nås
 Sep 21 09:31:20 raspberrypi weewx[14582] ERROR