[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

Und hier haben wir dann Anfänge einer Anleitung 
.

-- 
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/3f16c0b3-b76a-493d-aeab-adf3878be945n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

Darstellung der Farblegende:

#from user.weatherservicesradar import DwdRadar

...

 #for $idx,$val in $DwdRadar.TEXT['de'].items()

 

 

 $val

 

 #end for

Und in einer CSS-Datei:

*.statusIcon* {

  *width*:14px;

  *height*:14px;

  *display*:inline-block;

  *border*:1px solid #808080;

}

[image: Farblegende.png]

-- 
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/a6c72b4b-e268-4a7a-b3a0-fc14038d321cn%40googlegroups.com.

Re: [weewx-user] Re: Availability of v5.0.0rc3

[matthew wall]

On Friday, January 12, 2024 at 7:53:24 PM UTC-5 sab...@gmail.com wrote:

After some troubleshooting, I found the acurite idVendor code has a typo.  
Once I changed this the string to "24c0" instead of 24C0",  I was able to 
get the permissions working and all was good.


nice catch!  fixed at commit a92c9c7a
 

-- 
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/fa332dbc-572c-464e-9366-0efc2da71497n%40googlegroups.com.

Re: [weewx-user] Importing data from awair sensor

[Glenn McKechnie]

Hi,
As the author of the previously mentioned uradmon, I probably should pitch
in.

At first glance your json data and fields look very similar to uradmons,
and that's without looking at the uradmon code (it's been a while!)
Reviewing the code confirms that.
It should be a fairly straight forward to adapt it, with the bonus that the
extra uradmon specific code (retries and timeouts) can hopefully be ignored
in your case.
One difference is your data supplies a timestamp. uradmon.py generates its
own timestamp as the unit doesn't supply one. The choices begin!

The uradmon.py was written pretty much as a standalone service, under weewx
control of course.
It defines the units / groups  / formats /  labels and conversions etc that
it uses because at the time these weren't included in weewx itself, plus it
uses some oddball ones - Pa, cpm. I believe some of them are now included
in weewx.

It writes to its own database primarily because I didn't want to go adding
or co-opting weewx fields for uradmon purposes, and then live with the
consequences at upgrade time. It also seemed the simplest method to prevent
stomping on other users choices.  It was also written before the new schema
although looking at your fields there are some rather awair specific names?

The uradmon code is fairly well commented with example data (there are at
least 4 different types of urad units) and if you go down that path and
have any queries then you can contact me directly - if you read this via an
email client my address should be visible.


Cheers
 Glenn

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


On Sat, 13 Jan 2024 at 08:21, sting ray  wrote:

> the uradman example looks promising  Am also using seasons 4.10.2.
> another possibility https://github.com/jonathankoren/weewx-aqi
> On Friday, January 12, 2024 at 7:29:48 AM UTC-5 michael.k...@gmx.at wrote:
>
>> Write an extension that queries the device every archive_interval
>>
>> or
>>
>> Get the device to publish it's value per MQTT (if it supports anything
>> such this) and use mqttsubscribe
>>
>> or
>>
>> find a third party that queries the device and publishes the value per
>> MQTT (node red should work) and use mqttsubscribe
>>
>> I'd go for the first option, if the second option isn't available, since
>> I've done something like this already: (Get JSON, parse it and put the
>> values into a desired column of the weewx database):
>> https://github.com/mKainzbauer/weewx_extensions/blob/master/fronius.py
>> John Smith schrieb am Freitag, 12. Januar 2024 um 12:57:29 UTC+1:
>>
>>> On Fri, 12 Jan 2024 at 22:41, sting ray  wrote:
>>>
 Any advice how to import and display data from awair element
 sensors?These are intended for indoor aqi monitoring but appear to
 function in covered outdoor locations like a back porch.

>>>
>>> If no one else replies with a better answer you could look at
>>> https://github.com/glennmckechnie/weewx-uradmon which takes json values
>>> on a uradmon and injects it into a DB and then has a skin to display
>>> graphs.
>>>
>> --
> 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/181df546-7bb9-427c-94ba-23b4c8b41cdan%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/CAAraAzh%2BxQ289k4mMYXd7qCkeFKhqrORGSR_SQ_iS20%3DgA8yLg%40mail.gmail.com.

Re: [weewx-user] Re: Availability of v5.0.0rc3

[sab...@gmail.com]

I just tried a new install of 5.0RC3 on a RPi4 using the latest released 
Rasbian lite and used the PIP install for weewx.  The install process was 
pretty smooth, but I did hit a small snag with the udev file assigning the 
permissions for my acurite console.  Despite multiple attempts to 
unplug.replug the station I kept getting permissions errors.

After some troubleshooting, I found the acurite idVendor code has a typo.  
Once I changed this the string to "24c0" instead of 24C0",  I was able to 
get the permissions working and all was good.

Change
# acurite
SUBSYSTEM=="usb",ATTRS{idVendor}=="24C0",ATTRS{idProduct}=="0003",MODE="0666"

to
# acurite
SUBSYSTEM=="usb",ATTRS{idVendor}=="24c0",ATTRS{idProduct}=="0003",MODE="0666"

I should be good now for the final release but anyone else who has an 
acurite weather station is likely to hit the same problem.

Thanks
Scott



On Wednesday, January 10, 2024 at 12:34:45 PM UTC-6 michael.k...@gmx.at 
wrote:

> Thanks! Patched the file, it's working again.
>
> Tom Keffer schrieb am Mittwoch, 10. Januar 2024 um 15:23:11 UTC+1:
>
>> Michael,
>>
>> I've reverted the StdCalibrate behavior back to the way it was in V4.10. 
>> To appear in the next V5 release.
>>
>> On Tue, Jan 9, 2024 at 8:43 PM 'michael.k...@gmx.at' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> It looks very much like it's the loop in my case. For instance, 
>>> extraHumid1 is coming from a different device using the mqttSubscribe 
>>> Service. So it is not in the loop packet from ws28xx. The same with 
>>> supplyVoltage, BTW I messed up the ws28xx stanza, this one is correct, 
>>> failing on both, outHumidity and supplyVoltage:
>>>
>>> [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
>>> #outHumidity = extraHumid1
>>> barometer = pressure
>>> altimeter = pressure
>>> outHumidity = extraHumid1 if extraHumid1 is not None else 
>>> outHumidity
>>> supplyVoltage = (supplyVoltage + 35) / 1000
>>>
>>> In 5.0.0-b13 it didn't crash, so it wasn't only a difference to 4.10.
>>> Tom Keffer schrieb am Dienstag, 9. Januar 2024 um 21:25:59 UTC+1:
>>>
 Michael, I think the issue is that extraHumid1 and/or 
 lightning_strike_count do not appear *at all* in at least some of the 
 loop packers and/or archive records.

 Version 4.10 swallowed NameErrors, this one does not. Perhaps that's a 
 mistake. Let me think if there's a better solution.

 -tk

 On Tue, Jan 9, 2024 at 3:13 AM 'michael.k...@gmx.at' via weewx-user <
 weewx...@googlegroups.com> wrote:

> I did a pip upgrade from b13 (no new install, no new venv). I run 3 
> drivers: ws28xx, interceptor and ecowitt gateway driver from the same 
> installations, using 3 different weewx.conf files and three databases
>
> After upgrading, two installations are crashing, when having certain 
> corrections configured. Interestingly, one station (ecowitt gateway) 
> keeps 
> running, although it has the same correction configured, as the other 
> crashing (interceptor). Log following, tell me, what else you need. 
> (debug 
> = 1, etc...)
>
> Correction stanza for ecowitt gateway (no crashing):
> [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
> #outHumidity = extraHumid1
> radiation = luminosity/126.7 if luminosity is not None else 
> None#gw1000 fix
> lightning_distance = lightning_distance if 
> lightning_strike_count > 0 else None
>
> Corrections Stanza for interceptor:
> [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
> #outHumidity = extraHumid1
> barometer = pressure
> altimeter = pressure
> #outHumidity = extraHumid1 if extraHumid1 is not None else 
> outHumidity
> #supplyVoltage = (supplyVoltage + 35) / 1000
> #radiation = luminosity/126.7 if luminosity is not None else 
> None*#<= this one also caused a crash just before and is already 
> edited*
> lightning_distance = lightning_distance if 
> lightning_strike_count > 0 else None *#<= removing this will prevent 
> the crash*
> Interceptor log:
> 2024-01-09 11:24:06 weewxd-interceptor[196235] INFO __main__: 
> Initializing weewxd versi

Re: [weewx-user] Importing data from awair sensor

[sting ray]

the uradman example looks promising  Am also using seasons 4.10.2.  
another possibility https://github.com/jonathankoren/weewx-aqi
On Friday, January 12, 2024 at 7:29:48 AM UTC-5 michael.k...@gmx.at wrote:

> Write an extension that queries the device every archive_interval
>
> or
>
> Get the device to publish it's value per MQTT (if it supports anything 
> such this) and use mqttsubscribe
>
> or
>
> find a third party that queries the device and publishes the value per 
> MQTT (node red should work) and use mqttsubscribe
>
> I'd go for the first option, if the second option isn't available, since 
> I've done something like this already: (Get JSON, parse it and put the 
> values into a desired column of the weewx database):
> https://github.com/mKainzbauer/weewx_extensions/blob/master/fronius.py
> John Smith schrieb am Freitag, 12. Januar 2024 um 12:57:29 UTC+1:
>
>> On Fri, 12 Jan 2024 at 22:41, sting ray  wrote:
>>
>>> Any advice how to import and display data from awair element sensors?
>>> These are intended for indoor aqi monitoring but appear to function in 
>>> covered outdoor locations like a back porch.
>>>
>>
>> If no one else replies with a better answer you could look at 
>> https://github.com/glennmckechnie/weewx-uradmon which takes json values 
>> on a uradmon and injects it into a DB and then has a skin to display 
>> graphs. 
>>
>

-- 
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/181df546-7bb9-427c-94ba-23b4c8b41cdan%40googlegroups.com.

Re: [weewx-user] Re: WDC Skin

[tarob...@gmail.com]

Just upgraded to the new 3.4.0 skin (from 3.1.1). I am getting the 
following error when the reports run.

Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
Evaluation of template /etc/weewx/skins/weewx-wdc/index.html.tmpl failed 
with exception ''
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
 Ignoring template /etc/weewx/skins/weewx-wdc/index.html.tmpl
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
 Reason: could not convert string to float: 'geocode=34.743313'
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  Traceback (most recent call last):
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in 
generate
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_index_html_tmpl.py", line 267, in 
respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_body_alternative_inc.py", 
line 286, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_inc.py", line 
256, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1708, in _handleCheetahInclude
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
line 1749, in respond
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_weewx_wdc_includes_forecast_table_inc.py", 
line 520, in __errorCatcher65
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
File "", line 1, in 
Jan 12 15:30:34 raspberrypiNAS weewx[19495] ERROR weewx.cheetahgenerator: 
  ValueError: could not convert string to float: 'geocode=34.743313'
Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.cheetahgenerator: 
Generated 11 files for report WdcReport in 19.02 seconds
Jan 12 15:30:50 raspberrypiNAS weewx[19495] INFO weewx.reportengine: Copied 
0 files to /var/www/html/weewx

I also changed the base path in skin.conf to /weewx/wdc/ and still trying 
to send the generated files to /weewx/

Thanks,
Troy

On Sunday, August 27, 2023 at 10:14:41 AM UTC-4 David Bätge wrote:

> Hi Mau,
>
> yes, the wiki realy includes a lot of information. I guess you are missing 
> the base_path setting, see 
> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>  
> and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras
>
>
>
> Mau Hernandez schrieb am Mittwoch, 23. August 2023 um 01:00:26 UTC+2:
>
>> I just found your Wiki!  Will 
>> give that a shot! 
>>
>> On Tuesday, August 22, 2023 at 3:45:36 PM UTC-7 Mau Hernandez wrote:
>>
>>> Hi David,
>>>
>>> New user of WeeWx and found this thread with your Skin which Im trying 
>>> to install. I saw above that data might be needed so hopefully that 
>>> explains why Im getting a blank page but the Menu's are showing.
>>>
>>> I used the DEB package to do fresh install in a Debian machine. 
>>> Everything was setup and accesible at http://IP/weewx/. When I select 
>>> any submenu on the skin I see it goes back to root http://IP/about.html so 
>>> I probably missed a sym-link during setup? (http://IP/weewx/about.html 
>>> should 
>>> be the correct? ) 
>>>
>>> Thanks for your help
>>>
>>> [image: Screenshot 2023-08-22 at 3.37.53 PM.png]
>>> On Friday, August 18, 2023 at 7:17:21 AM UTC-7 David Bätge wrote:
>>>
 Great, I will include the change in the next release! 

 gert.a...@gmail.com schrieb am Freitag, 18. August 2023 um 13:44:22 
 UTC+2:

> Hi David
>
> I was to fast, it seems to work with the new main.ja.
>
> Thanks f

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

[Karen K]

michael.k...@gmx.at schrieb am Freitag, 12. Januar 2024 um 20:04:50 UTC+1:

Hört sich nach einem Geniestreich an. Da sich mein Standort in Österreich 
noch in dem Ausschnitt der Karte befindet, melde ich mein Interesse an. 
Würde das auch gerne als Option für den Bootstrap Skin übernehmen.


Das ist skin-unabhängig. Man muß nur weewx-DWD 
 installiert haben. Die Beispiele in 
der Dokumentation beziehen sich teilweise auf die Belchertown-Skin, aber 
man kann "Belchertown" auch durch einen anderen Namen ersetzen.

Als Warnung muß ich noch den Thread "Report thread freezes after weewx.conf 
change " 
voranstellen. Wenn es solche Probleme gibt, muß man die Option "include" 
nutzen. Wenn nicht, kann man die Konfiguration direkt in weewx.conf 
eintragen.

Sämtliche Konfigurationsinformationen für weewx-DWD finden sich im 
Abschnitt "[WeatherServices]". Das gilt auch für die Radardaten. Die 
Konfiguration sieht ungefähr so aus:

[WeatherServices]

path = /etc/weewx/skins/SKINNAME/dwd

...

[[radar]]

[[[Station]]]

provider = DWD

model = HG

easting = replace_me

northing = replace_me

prefix = ""

latitude = replace_me

longitude = replace_me

[[[Karte]]]

provider = DWD

model = HG

prefix = ""

map = 100, 100, 900, 1000

borders = countrycoords.txt

"path" ist der Ort, wohin die Graphikdatei geschrieben werden soll. Das 
kann auch /var/lib/weewx oder irgendwo anders sein. latitude und longitude 
sind, denke ich, klar. Spannend wird es mit easting und northing. Dazu muß 
ich ausholen. Das folgt weiter unten. map gibt die Koordinaten des 
Ausschnitts in Pixeln an, für den die Karte erzeugt werden soll. Die ersten 
beiden Zahlen sind die linke *untere* Ecke, die anderen beiden Breite und 
Höhe. Die Breite kann maximal 1100 sein, die Höhe 1200. prefix ist ein 
Namenspräfix, falls man mehrere Stationen oder mehrere Karten hat.

Deutschland ist hier in ein 1km-Raster eingeteilt. easting (deutsch: 
Rechtswert) und northing (deutsch: Hochwert) sind die Koordinaten innerhalb 
dieses Rasters in Metern. Allerdings ist hier der Koordinatenursprung weit 
außerhalb. Nun ist die Frage, wie man diese Werte bekommt. Da die Erde rund 
ist, kann man ein ebenes Raster nicht einfach so über das Land legen. Man 
braucht eine kartographische Projektion. Dazu gibt der Deutsche 
Wetterdienst an, man soll das Programm "proj" benutzen. Zum Glück gibt es 
das auch für Linux, und man kann es ganz normal mit "apt-get" installieren. 
Der Aufruf ist wie folgt:

echo longitude latitude | proj +proj=stere +lat_0=90 +lat_ts=60 +lon_0=10 
+a=6378137 +b=6356752.3142451802 +no_defs +x_0=543196.83521776402 
+y_0=3622588.8619310018

Bitte aufpassen, die Reihenfolge ist umgekehrt wie üblich.

Als Ergebnis spuckt das Programm die beiden Werte aus, die man als easting 
und northing eintragen muß.

Die Datei countrycoords.txt kann Linien enthalten, die als Grenzen o.ä. in 
die Graphik eingezeichnet werden sollen. Pro Zeile muß ein Koordinatenpaar 
stehen, wieder mit dem Programm "proj" erzeugt, dem man dazu direkt eine 
Liste von geographischen Koordinaten übergeben kann. Anfang und Ende einer 
Linie wird durch eine Zeile mit zwei Sternchen und einem Leerzeichen 
dazwischen gekennzeichnet.

Soweit erst einmal die grobe Übersicht.

-- 
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/97a04787-ae4c-4d1d-a28d-6ca111aa4d58n%40googlegroups.com.

[weewx-user] Re: Using radar data provided by the German Weather Service DWD

['michael.k...@gmx.at' via weewx-user]

Hört sich nach einem Geniestreich an. Da sich mein Standort in Österreich 
noch in dem Ausschnitt der Karte befindet, melde ich mein Interesse an. 
Würde das auch gerne als Option für den Bootstrap Skin übernehmen.

Karen K schrieb am Freitag, 12. Januar 2024 um 19:30:17 UTC+1:

> As this covers Germany only, I write it in german.
>
> Am Anfang hat mich einfach gestört, daß das Wettersymbol auf der 
> Startseite der Belchertown-Skin oft falsch war, weil es aus der Vorhersage 
> stammt und die halt nicht immer zutrifft. Die Lösung bestand dann für mich 
> in einem sehr tiefen Griff in den Geldbeutel und der Anschaffung eines 
> Distrometers. Nun habe ich mich mit den Radardaten beschäftigt, die er 
> Deutsche Wetterdienst anbietet, und gesehen, daß man da zumindest einen 
> Teil der Information auch ganz aktuell bekommt.
>
> In einem binären Format wird unter der Bezeichnung HG für ein 1km-Raster 
> über Deutschland der Niederschlagsstatus bereitgestellt. Diese Daten werden 
> beeindruckend häufig, nämlich aller 5 Minuten, aktualisiert. Wenn man weiß, 
> in welchem Rasterpunkt der eigene Standort liegt, kann man den 
> Niederschlagsstatus dafür aus der Datei ablesen.
>
> Ich habe mich daran versucht und die WeeWX-Erweiterung weewx-DWD 
>  um ein Modul für Radardaten 
> erweitert. Es liefert:
>
>- Variablen (observation types), die den Niederschlagsstatus für 
>definierte Orte in Deutschland enthalten und in Skins verwendet werden 
>können, z.B. mittels $current.radarHGValue. (Also, das heißt, man kann 
>die gewünschten Orte in der Konfiguration festlegen. Die sind nicht von 
> mir 
>vorgegeben.)
>- den wawa-Wert des Niederschlagsstatus, den man mittels 
>$presentweather in ein Niederschlagssymbol zur Anzeige auf der 
>Web-Seite verwandeln kann
>- Karten von Deutschland oder einem Ausschnitt davon mit dem 
>Niederschlagsstatus als PNG-Datei zum Einbinden in Web-Seiten
>
> Beispiel für eine Karte:
> [image: radar-HG.png]
>
> Aktuelles Beispiel 
> 
>
> Es ist natürlich alles noch ganz neu und enthält ganz sicher noch Fehler. 
>
> Wenn jemand Interesse an der Nutzung hat, beschreibe ich die Konfiguration.
>

-- 
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/31411fd9-98ab-4ca6-8c89-57e9c839b702n%40googlegroups.com.

[weewx-user] Re: Trying to upgrade to 5...

[Mike Ekim]

Perfect!  Thank you.

On Friday, January 12, 2024 at 12:08:44 PM UTC-5 vince wrote:

> The docs point to the production steps they will require once v5 drops.
>
> For the beta edit /etc/apt/sources.list.d/weewx.list to point to 
> https://weewx.com/apt-test/python3 so your apt update picks up the 
> contents of the test repo rather than the prod repo that still points to v4 
> weewx.   Remember to edit it back when v5 drops and that becomes the new 
> production version.
>
>
>

-- 
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/08859b08-efb2-4c58-aeb5-544d243b84a1n%40googlegroups.com.

[weewx-user] Re: Trying to upgrade to 5...

[vince]

The docs point to the production steps they will require once v5 drops.

For the beta edit /etc/apt/sources.list.d/weewx.list to point to 
https://weewx.com/apt-test/python3 so your apt update picks up the contents 
of the test repo rather than the prod repo that still points to v4 weewx.   
Remember to edit it back when v5 drops and that becomes the new production 
version.


-- 
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/ce04f693-8c0c-4a26-b11e-6797f2529101n%40googlegroups.com.

[weewx-user] Trying to upgrade to 5...

[Mike Ekim]

I must be missing something.  On the page telling you how to upgrade to 5 
it says, 

Upgrade to the latest version like this:
sudo apt update
sudo apt install weewx

When I do that I get (I did do a sudo apt update before this)

me@raspberrypi:~ $ sudo apt install weewx
Reading package lists... Done
Building dependency tree
Reading state information... Done
weewx is already the newest version (4.10.2-1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

This is running on a raspi 4 running Raspbian Buster with Davis Vantage Pro 
2

-- 
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/c0c26507-f410-4ba6-ba89-d3c1d7db78ban%40googlegroups.com.

[weewx-user] Re: can't install weewx / public key is not available: NO_PUBKEY A0CB255B75BF977C

[David Schulz]

it works, thx.

matthew wall schrieb am Freitag, 12. Januar 2024 um 16:37:34 UTC+1:

> On Friday, January 12, 2024 at 9:20:03 AM UTC-5 schulz@gmail.com 
> wrote:
>
> hi,
>
> i can't install weewx today.
>
> wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
> /etc/apt/sources.list.d/weewx.list
> wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor --output 
> /etc/apt/trusted.gpg.d/weewx.gpg
> apt update
>
>
> please do this:
>
> wget -qO - https://weewx.com/keys-old.html | sudo gpg --dearmor --output 
> /etc/apt/trusted.gpg.d/weewx.gpg
>
> then do the apt update, etc.
>
> we have an old SHA1 key that signed many of the releases, and i am in the 
> middle of re-signing packages to make it all future-proof
>
> 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/5d8c1828-8cbe-40c8-98f2-1e6d9c93a9a9n%40googlegroups.com.

[weewx-user] Re: can't install weewx / public key is not available: NO_PUBKEY A0CB255B75BF977C

[matthew wall]

On Friday, January 12, 2024 at 9:20:03 AM UTC-5 schulz@gmail.com wrote:

hi,

i can't install weewx today.

wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list
wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor --output 
/etc/apt/trusted.gpg.d/weewx.gpg
apt update


please do this:

wget -qO - https://weewx.com/keys-old.html | sudo gpg --dearmor --output 
/etc/apt/trusted.gpg.d/weewx.gpg

then do the apt update, etc.

we have an old SHA1 key that signed many of the releases, and i am in the 
middle of re-signing packages to make it all future-proof

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/5e556d49-8dfd-415c-85e3-a63fefec6e7bn%40googlegroups.com.

[weewx-user] can't install weewx / public key is not available: NO_PUBKEY A0CB255B75BF977C

[David Schulz]

hi,

i can't install weewx today.

wget -qO - https://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list
wget -qO - https://weewx.com/keys.html | sudo gpg --dearmor --output 
/etc/apt/trusted.gpg.d/weewx.gpg
apt update

Hit:1 http://security.ubuntu.com/ubuntu mantic-security InRelease
Hit:2 http://de.archive.ubuntu.com/ubuntu mantic InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu mantic-updates InRelease
Get:4 http://weewx.com/apt/python3 buster InRelease [3907 B]
Hit:5 http://de.archive.ubuntu.com/ubuntu mantic-backports InRelease
Get:6 https://download.docker.com/linux/ubuntu mantic InRelease [48.8 kB]
Err:4 http://weewx.com/apt/python3 buster InRelease
  The following signatures couldn't be verified because the public key is 
not available: NO_PUBKEY A0CB255B75BF977C
Reading package lists... Done
W: GPG error: http://weewx.com/apt/python3 buster InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY A0CB255B75BF977C
E: The repository 'http://weewx.com/apt/python3 buster InRelease' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

Description:Ubuntu 23.10
Release:23.10
Codename:   mantic

-- 
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/d01c6ebd-44d6-480b-88fd-1b036e0fe636n%40googlegroups.com.

Re: [weewx-user] Importing data from awair sensor

['michael.k...@gmx.at' via weewx-user]

Write an extension that queries the device every archive_interval

or

Get the device to publish it's value per MQTT (if it supports anything such 
this) and use mqttsubscribe

or

find a third party that queries the device and publishes the value per MQTT 
(node red should work) and use mqttsubscribe

I'd go for the first option, if the second option isn't available, since 
I've done something like this already: (Get JSON, parse it and put the 
values into a desired column of the weewx database):
https://github.com/mKainzbauer/weewx_extensions/blob/master/fronius.py
John Smith schrieb am Freitag, 12. Januar 2024 um 12:57:29 UTC+1:

> On Fri, 12 Jan 2024 at 22:41, sting ray  wrote:
>
>> Any advice how to import and display data from awair element sensors?
>> These are intended for indoor aqi monitoring but appear to function in 
>> covered outdoor locations like a back porch.
>>
>
> If no one else replies with a better answer you could look at 
> https://github.com/glennmckechnie/weewx-uradmon which takes json values 
> on a uradmon and injects it into a DB and then has a skin to display 
> graphs. 
>

-- 
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/83788295-5f58-4a47-9349-e05e2f3c2a42n%40googlegroups.com.

[weewx-user] Report thread freezes after weewx.conf change

[Karen K]

Please note: This is not reproducable. The only question is, if someones 
knows about threading issues in Python, that may produce such behavior. So 
don't ask about the log etc. I explain it below why.

It happened while I wrote an extension.

I added some entries at the end of weewx.conf. They are for the new 
extension, but the extension itself is not loaded (not added to 
data_services so far). After the restart of WeeWX all was working as 
expected, except that no report was created any more. 

The log was identical, except the missing messages about reports. The same 
applies if debug is set to 1.

There was no error message. There was no exception.

If I removed some unused lines from weewx.conf (NOT in section StdReport), 
the reports were created again.

I found out, that the StdReportEngine thread freezes at the beginning of 
the report loop
(statement: enabled = to_bool(self.config_dict['StdReport'][report].get(
'enable', True))).

I did a lot of debugging, and finally I added a logging statement 
(log.info) between every line of code in reportengine.py.

After that all reports were created again. (But lots of messages in syslog 
of course)

So why do I not provide a log excerpt? Unfortunately all this happens in my 
production environment only. The test environment does not show this 
behavior. And I don't want to perform more tests on the production 
environment.

There are a lot of findings at Google about freezing threads in Python, but 
I did not find something appropriate.

So does this description remember someone on something?

(And meanwhile I have to invent some solution to have a smaller weewx.conf. 
It is about 64 KB in size now because of a lot of extensions.)

-- 
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/d09f5799-05fd-45e7-aa4b-29051dfebe97n%40googlegroups.com.

Re: [weewx-user] Importing data from awair sensor

[John Smith]

On Fri, 12 Jan 2024 at 22:41, sting ray  wrote:

> Any advice how to import and display data from awair element sensors?
> These are intended for indoor aqi monitoring but appear to function in
> covered outdoor locations like a back porch.
>

If no one else replies with a better answer you could look at
https://github.com/glennmckechnie/weewx-uradmon which takes json values on
a uradmon and injects it into a DB and then has a skin to display graphs.

-- 
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/CAGTinV6LHoL6fqkVLk%3D9nz4Jsu%2Bf8yu8FeR-cuYfrfJeoreCog%40mail.gmail.com.

[weewx-user] Importing data from awair sensor

[sting ray]

Any advice how to import and display data from awair element sensors?
These are intended for indoor aqi monitoring but appear to function in 
covered outdoor locations like a back porch.

Thanks,
Steve Lim

Can access current sensor data on LAN with url 
http://192.168.86.43/air-data/latest
raw data:   
{"timestamp":"2024-01-12T11:26:12.379Z","score":95,"dew_point":13.51,"temp":23.85,"humid":52.37,"abs_humid":11.27,"co2":630,"co2_est":400,"co2_est_baseline":36710,"voc":164,"voc_baseline":37478,"voc_h2_raw":27,"voc_ethanol_raw":36,"pm25":0,"pm10_est":1}
 

[image: Screenshot 2024-01-12 063551.png]

-- 
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/6a92b9c3-ae8a-4ee3-887c-362e36f1d4d6n%40googlegroups.com.