[weewx-user] Re: SDR and BME280 Data using Acurite Sensors

[gjr80]

Hi,

It's worth noting the bme280wx service is not marked as WeeWX 4/python 3 
compatible but that should not matter since it is a very simple service and 
you are running python2 .

Can you try running WeeWX directly 
. This will cause 
WeeWX to display the contents of the loop packets (lines starting with 
Loop:) and archive records (lines starting with REC:) to the console. Could 
you post the output back here making sure you capture at least one archive 
record (REC:). Would also help to see a copy of your [Engine] stanza from 
weewx.conf.

Gary

On Thursday, 25 June 2020 01:31:53 UTC+10, Troy Roberts wrote:
>
> So I am currently running weewx version 4.1.1 and collecting data via SDR 
> from an Acurite 5n1, three Acurite Temp/Humidity sensors, and a BME280 
> sensor for pressure. All data is populating the fields as I would expect 
> them to. I am currently using one of the acurite temp/humidity sensors to 
> populate the "inTemp" and "inHumidity" data fields however, I would like to 
> change those "inTemp" and "inHumidity" data fields to be populated by the 
> BME280 sensor and change the acurite temp/humidity sensor over to 
> "extraTemp3". However, when I edited the weewx.conf file, no data from the 
> BME280 sensor was being uploaded but I was now populating extraTemp3 data. 
> I'm not seeing any errors in the syslog. Below is my weewx.config sensor 
> mapping [SDR] and [BME280] that works and what I edited to switch sensors.
>
> This config sensor map works as I expect it to:
>
> [SDR]
> # This section is for the software-defined radio driver.
> # The driver to use
> driver = user.sdr
> # cmd = rtl_433 -M utc -F json -R 17 -R 44 -R 50
> # cmd = rtl_433 -M utc -F json -G  # you can uncomment this if you have
> # issues - check your logs! 
> path = /usr/local/bin
> ld_library_path = /usr/local/lib
> [[sensor_map]]
> windDir = wind_dir.098A.Acurite5n1PacketV2
> windSpeed = wind_speed.098A.Acurite5n1PacketV2
> outTemp = temperature.098A.Acurite5n1PacketV2
> outHumidity = humidity.098A.Acurite5n1PacketV2
> rain_total = rain_total.098A.Acurite5n1PacketV2 
> inTemp = temperature.258E.AcuriteTowerPacketV2   #Nursery
> inHumidity = humidity.258E.AcuriteTowerPacketV2  #Nursery
> # I have more sensors, so I added them below, you may not.
> #extraTemp1 = temperature_probe.0BF1.Acurite00275MPacket
> #extraTemp2 = temperature.0BF1.Acurite00275MPacket
> extraTemp1 = temperature.169B.AcuriteTowerPacketV2#Beer Fridge
> extraHumidity1 = humidity.169B.AcuriteTowerPacketV2   #Beer Fridge
> extraTemp2 = temperature.2CE5.AcuriteTowerPacketV2#Garage
> extraHumidity2 = humidity.2CE5.AcuriteTowerPacketV2   #Garage
> #extraTemp3 = temperature.258E.AcuriteTowerPacketV2#Nursery
> #extraHumidity3 = humidity.258E.AcuriteTowerPacketV2   #Nursery
> [[deltas]]
> rain = rain_total
>
>
> ##
>
> # Options for extension 'bme280wx'
> [Bme280wx]
> temperature_must_have = ""
> humidityKeys = ""
> pressureKeys = pressure
> pressure_must_have = inTemp
> i2c_port = 1
> humidity_must_have = ""
> i2c_address = 0x76
> usUnits = US
> temperatureKeys = ""
>
>
>
> This is config sensor map does not work (no BME280 data is populated):
>
> [SDR]
> # This section is for the software-defined radio driver.
> # The driver to use
> driver = user.sdr
> # cmd = rtl_433 -M utc -F json -R 17 -R 44 -R 50
> # cmd = rtl_433 -M utc -F json -G  # you can uncomment this if you have
> # issues - check your logs! 
> path = /usr/local/bin
> ld_library_path = /usr/local/lib
> [[sensor_map]]
> windDir = wind_dir.098A.Acurite5n1PacketV2
> windSpeed = wind_speed.098A.Acurite5n1PacketV2
> outTemp = temperature.098A.Acurite5n1PacketV2
> outHumidity = humidity.098A.Acurite5n1PacketV2
> rain_total = rain_total.098A.Acurite5n1PacketV2 
> # inTemp = temperature.258E.AcuriteTowerPacketV2   #Nursery
> # inHumidity = humidity.258E.AcuriteTowerPacketV2  #Nursery
> # I have more sensors, so I added them below, you may not.
> #extraTemp1 = temperature_probe.0BF1.Acurite00275MPacket
> #extraTemp2 = temperature.0BF1.Acurite00275MPacket
> extraTemp1 = temperature.169B.AcuriteTowerPacketV2#Beer Fridge
> extraHumidity1 = humidity.169B.AcuriteTowerPacketV2   #Beer Fridge
> extraTemp2 = temperature.2CE5.AcuriteTowerPacketV2#Garage
> extraHumidity2 = humidity.2CE5.AcuriteTowerPacketV2   #Garage
> extraTemp3 = temperature.258E.AcuriteTowerPacketV2#Nursery
> extraHumidity3 = humidity.258E.AcuriteTowerPacketV2   #Nursery
> [[deltas]]
> rain = rain_total
>

Re: [weewx-user] Re: Full day highcharts question

[Pat O'Brien]

Wow! I'm not sure why you're getting that error either. Something is
missing somewhere

On Wed, Jun 24, 2020, 5:14 PM Manfred Maier 
wrote:

> I'll have to try that tomorrow.
> My skin installation includes a number of individual adaptions (e.g. pi
> page, individual website widget, horizontal lines in some graphs, etc) and
> it always takes me 1-2 hours to update the skin.
>
> Pat schrieb am Mittwoch, 24. Juni 2020 um 23:07:57 UTC+2:
>
>> Can you try to reinstall the whole development skin and restart weewx?
>>
>> On Wed, Jun 24, 2020, 5:03 PM Manfred Maier 
>> wrote:
>>
>>> Didn't work :(
>>>
>>> I don't understand this error. The 'forecast_provider' is in my
>>> skin.conf and the weewx.conf:
>>>
>>> # Forecast defaults
>>>
>>> forecast_enabled = 1
>>>
>>> forecast_provider = "darksky"
>>>
>>> forecast_api_id = "b6b2add3..."
>>>
>>> forecast_api_secret = "b6b2add3..."
>>>
>>> forecast_units = "ca"
>>>
>>> forecast_lang = "de"
>>>
>>> forecast_stale = 3540
>>>
>>> forecast_alert_enabled = 1
>>>
>>> forecast_alert_limit = 1
>>>
>>> forecast_show_daily_forecast_link = 0
>>>
>>> forecast_daily_forecast_link = ""
>>>
>>>
>>> Pat schrieb am Mittwoch, 24. Juni 2020 um 22:32:50 UTC+2:
>>>
 Update your skins.conf to latest version too

 On Wed, Jun 24, 2020, 4:28 PM Manfred Maier 
 wrote:

>
> Hi Pat,
> apologies, it's me again.
>
> Yesterday (and today) I've just copied the new belchertown.py in my
> user folder.
> Now I've seen that i get a two error messages in my syslog.
>
> The first one I've been able to resolve. It was caused by the "check
> for update" functionality that you have removed recently. After setting 
> the
> update setting to zero the error was gone.
>
> The second one I'm not able to locate. This is the error I get:
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> Generate failed with exception ''
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>  Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>  Reason: cannot find 'forecast_provider'
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   Traceback (most recent call last):
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in
> generate
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   unicode_string = compiled_template.respond()
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", 
> line
> 1154, in respond
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   NameMapper.NotFound: cannot find 'forecast_provider'
>
> didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50
> UTC+2:
>
>> Perfect !
>> Thanks
>>
>> Le mer. 24 juin 2020 à 16:04, Manfred Maier <
>> in...@wetter-zorneding.de> a écrit :
>>
>>> Solved!
>>> Thanks so much!
>>>
>>> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>>>
 Can you try the latest belchertown.py file from the devleopment
 branch? I think I got it working. See screenshot.



 On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier
 wrote:
>
> Sent by email. The file has been too big for an upload here (or
> the database content isn't allowed?).
> Thanks for looking into 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>
 You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: [weewx-user] Re: Full day highcharts question

[Manfred Maier]

I'll have to try that tomorrow. 
My skin installation includes a number of individual adaptions (e.g. pi 
page, individual website widget, horizontal lines in some graphs, etc) and 
it always takes me 1-2 hours to update the skin. 

Pat schrieb am Mittwoch, 24. Juni 2020 um 23:07:57 UTC+2:

> Can you try to reinstall the whole development skin and restart weewx?
>
> On Wed, Jun 24, 2020, 5:03 PM Manfred Maier  
> wrote:
>
>> Didn't work :(
>>
>> I don't understand this error. The 'forecast_provider' is in my skin.conf 
>> and the weewx.conf:
>>
>> # Forecast defaults
>>
>> forecast_enabled = 1
>>
>> forecast_provider = "darksky"
>>
>> forecast_api_id = "b6b2add3..."
>>
>> forecast_api_secret = "b6b2add3..."
>>
>> forecast_units = "ca"
>>
>> forecast_lang = "de"
>>
>> forecast_stale = 3540
>>
>> forecast_alert_enabled = 1
>>
>> forecast_alert_limit = 1
>>
>> forecast_show_daily_forecast_link = 0
>>
>> forecast_daily_forecast_link = ""
>>
>>
>> Pat schrieb am Mittwoch, 24. Juni 2020 um 22:32:50 UTC+2:
>>
>>> Update your skins.conf to latest version too
>>>
>>> On Wed, Jun 24, 2020, 4:28 PM Manfred Maier  
>>> wrote:
>>>

 Hi Pat,
 apologies, it's me again.

 Yesterday (and today) I've just copied the new belchertown.py in my 
 user folder.
 Now I've seen that i get a two error messages in my syslog.

 The first one I've been able to resolve. It was caused by the "check 
 for update" functionality that you have removed recently. After setting 
 the 
 update setting to zero the error was gone.

 The second one I'm not able to locate. This is the error I get:

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
 Generate failed with exception ''

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
  Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
  Reason: cannot find 'forecast_provider'

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
   Traceback (most recent call last):

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in 
 generate

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
   unicode_string = compiled_template.respond()

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
 File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", 
 line 
 1154, in respond

 Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
   NameMapper.NotFound: cannot find 'forecast_provider'

 didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50 
 UTC+2:

> Perfect !
> Thanks
>
> Le mer. 24 juin 2020 à 16:04, Manfred Maier  
> a écrit :
>
>> Solved!
>> Thanks so much! 
>>
>> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>>
>>> Can you try the latest belchertown.py file from the devleopment 
>>> branch? I think I got it working. See screenshot.
>>>
>>>
>>>
>>> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:

 Sent by email. The file has been too big for an upload here (or the 
 database content isn't allowed?).
 Thanks for looking into 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 

>>> You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/4e605379-67f9-4db4-b1a9-07b752dcbcebn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message 

Re: [weewx-user] Re: Full day highcharts question

[Pat O'Brien]

Can you try to reinstall the whole development skin and restart weewx?

On Wed, Jun 24, 2020, 5:03 PM Manfred Maier 
wrote:

> Didn't work :(
>
> I don't understand this error. The 'forecast_provider' is in my skin.conf
> and the weewx.conf:
>
> # Forecast defaults
>
> forecast_enabled = 1
>
> forecast_provider = "darksky"
>
> forecast_api_id = "b6b2add3..."
>
> forecast_api_secret = "b6b2add3..."
>
> forecast_units = "ca"
>
> forecast_lang = "de"
>
> forecast_stale = 3540
>
> forecast_alert_enabled = 1
>
> forecast_alert_limit = 1
>
> forecast_show_daily_forecast_link = 0
>
> forecast_daily_forecast_link = ""
>
>
> Pat schrieb am Mittwoch, 24. Juni 2020 um 22:32:50 UTC+2:
>
>> Update your skins.conf to latest version too
>>
>> On Wed, Jun 24, 2020, 4:28 PM Manfred Maier 
>> wrote:
>>
>>>
>>> Hi Pat,
>>> apologies, it's me again.
>>>
>>> Yesterday (and today) I've just copied the new belchertown.py in my user
>>> folder.
>>> Now I've seen that i get a two error messages in my syslog.
>>>
>>> The first one I've been able to resolve. It was caused by the "check for
>>> update" functionality that you have removed recently. After setting the
>>> update setting to zero the error was gone.
>>>
>>> The second one I'm not able to locate. This is the error I get:
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>> Generate failed with exception ''
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>>  Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>>  Reason: cannot find 'forecast_provider'
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>>   Traceback (most recent call last):
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in
>>> generate
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>>   unicode_string = compiled_template.respond()
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>> File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", line
>>> 1154, in respond
>>>
>>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>>>   NameMapper.NotFound: cannot find 'forecast_provider'
>>>
>>> didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50
>>> UTC+2:
>>>
 Perfect !
 Thanks

 Le mer. 24 juin 2020 à 16:04, Manfred Maier 
 a écrit :

> Solved!
> Thanks so much!
>
> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>
>> Can you try the latest belchertown.py file from the devleopment
>> branch? I think I got it working. See screenshot.
>>
>>
>>
>> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>>>
>>> Sent by email. The file has been too big for an upload here (or the
>>> database content isn't allowed?).
>>> Thanks for looking into 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+...@googlegroups.com.
>
 To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com
> 
> .
>
 --
>>>
>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/4e605379-67f9-4db4-b1a9-07b752dcbcebn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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/aa56d448-ba0a-4d31-a737-ba2eb27c191fn%40googlegroups.com
> 

Re: [weewx-user] Re: Full day highcharts question

[Manfred Maier]

Didn't work :(

I don't understand this error. The 'forecast_provider' is in my skin.conf 
and the weewx.conf:

# Forecast defaults

forecast_enabled = 1

forecast_provider = "darksky"

forecast_api_id = "b6b2add3..."

forecast_api_secret = "b6b2add3..."

forecast_units = "ca"

forecast_lang = "de"

forecast_stale = 3540

forecast_alert_enabled = 1

forecast_alert_limit = 1

forecast_show_daily_forecast_link = 0

forecast_daily_forecast_link = ""


Pat schrieb am Mittwoch, 24. Juni 2020 um 22:32:50 UTC+2:

> Update your skins.conf to latest version too
>
> On Wed, Jun 24, 2020, 4:28 PM Manfred Maier  
> wrote:
>
>>
>> Hi Pat,
>> apologies, it's me again.
>>
>> Yesterday (and today) I've just copied the new belchertown.py in my user 
>> folder.
>> Now I've seen that i get a two error messages in my syslog.
>>
>> The first one I've been able to resolve. It was caused by the "check for 
>> update" functionality that you have removed recently. After setting the 
>> update setting to zero the error was gone.
>>
>> The second one I'm not able to locate. This is the error I get:
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>> Generate failed with exception ''
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>>  Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>>  Reason: cannot find 'forecast_provider'
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>>   Traceback (most recent call last):
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in 
>> generate
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>>   unicode_string = compiled_template.respond()
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>> File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", line 
>> 1154, in respond
>>
>> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
>>   NameMapper.NotFound: cannot find 'forecast_provider'
>>
>> didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50 
>> UTC+2:
>>
>>> Perfect !
>>> Thanks
>>>
>>> Le mer. 24 juin 2020 à 16:04, Manfred Maier  
>>> a écrit :
>>>
 Solved!
 Thanks so much! 

 Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:

> Can you try the latest belchertown.py file from the devleopment 
> branch? I think I got it working. See screenshot.
>
>
>
> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>>
>> Sent by email. The file has been too big for an upload here (or the 
>> database content isn't allowed?).
>> Thanks for looking into 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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com
  
 
 .

>>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4e605379-67f9-4db4-b1a9-07b752dcbcebn%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/aa56d448-ba0a-4d31-a737-ba2eb27c191fn%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Rich Bell]

Great to hear. Just give a shout if you run into any other difficulties.
rich

On Wednesday, 24 June 2020 16:50:26 UTC-4, Christian Peters wrote:
>
> Hi Rich,
>
> thank you very much. 
> It works like a charm! :-) 
>
> I set up a temporary mapping to values already available in the databae. 
> For the temp and humid values it works out of the box, for CPM, CPS and 
> radiation I have to setup unit groups later. 
>
> This is my working setup - just to have that written down for others:
>
> my data form the MQTT broker:
>
>
> radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00
>
> weewx.conf:
>
> [MQTTSubscribeService]
> host = xxx.xxx.xxx.xxx # IP of the broker
> payload_type = keyword
> console = True
> [[topics]]
>  [[[weather]]]   # The topic you are subscribing to
>unit_system = METRICWX # Not sure weather you want METRICWX or 
> METRIC. See http://weewx.com/docs/customizing.htm#units
>temp_2m # Name in the MQTT message
>name = extraTemp1 # WeeWX name
>temp_5cm
>name = extraTemp2
>temp_dht22
>name = extraTemp3
>hum_dht22
>name = extraHumid3
>rain
>name = hail
>radiation
>name = signal1
>cpm
>name = signal2
>cps
>name = signal3
>
> [[message_callback]]
>  type = keyword
>  keyword_delimiter = "," # The delimiter between the name/value pairs
>  keyword_separator = ":" # The separator between the name and the value
>
> [[Services]]
> data_services = user.MQTTSubscribe.MQTTSubscribeService
>
> That's quite nice and more elegant as to set up a second weewx instance 
> with a MQTT driver! 
> Thank you very much.
>
> My MQTT broker runs on a BananaPi which is located in the garden near the 
> sensors (Temp2m, Temp5cm, raingauge, temp and hum sensor inside the 
> controlbox and a MightyOhm Geiger Counter Kit).
> I can't figure out why...but somtimes I lost the WLAN connection (after 
> 7-30 days). Then I restart the BananPi, start the mosquitto deamon...but 
> the weewx instance running the wxMesh driver didn't reconnect. 
> I have to start and stop this instance, then it works again. But I saw a 
> post in weewx-development that someone pointed out the connection was setup 
> once at initialisation...maybe there is no check of the connection and a 
> reconnect condition?
>
> If the setup goes online (at the moment I run the simulator whil mograting 
> all sensors and tweak the new webpage) and the VanatgeVP2 is connected, I 
> will check the behavior of your drriver in my setup. 
>
> Thanks again for the excellent support. If I run into some problems I will 
> contact you again. :-)
>
> Regards,
>
> Christian 
>
> P.S. Ken, thanks for you fix...it works..! :-) But the 
> MQTTSubscribeService works great and I will prefer to run only one weewx 
> instance to deal with all sensors. 
>
>
> Am Mittwoch, 24. Juni 2020 19:25:05 UTC+2 schrieb Rich Bell:
>>
>>
>> Well, I haven't heard of having to restart WeeWX when the connection is 
>> lost, and if that happens I would certainly want to look into fixing that. 
>> I'll do some experiments to see if I can recreate. 
>>
>> Sounds like picking the service might be the best long term choice, with 
>> the caveat about the reconnect logic needing to be verified. But if you 
>> want to get your feet wet, I would suggest that we get it up and running as 
>> a driver - perhaps even running from the command line for a bit. The actual 
>> configuration work is really the same. So you could migrate to the service 
>> as you get more comfortable or after we prove that lost connections are not 
>> a problem. 
>>
>> The following assumes that you install 1.5.4-rc01. This changed the way 
>> to configure MQTTSubscribe. Once installed, there will be three key 
>> sections the [MQTTSubscribeDriver]/[MQTTSubscribeService] section. This is 
>> the MQTT connection information, and I believe this is pretty straight 
>> forward. But after looking at it, if you have questions let me know.
>>
>> Next up is the [[topics]] section. Based on the information you posted, I 
>> think this is what you would want
>>
>> [[topics]]
>>  [[[weather]]]   # The topic you are subscribing to
>>unit_system = METRICWX # Not sure weather you want METRICWX or METRIC. 
>> See http://weewx.com/docs/customizing.htm#units
>>temp_2m # Name in the MQTT message
>>name = extraTemp1 # WeeWX name
>>temp_5cm 
>> name = extraTemp2
>>temp_dht22 
>> name = inTemp
>>hum_dht22 
>>   name = inHumidity
>>rain 
>> name = rain
>>geiger 
>>   name = radiation
>>
>> Not sure about your TIME field and the value of 0. I left it out and 
>> since it is missing MQTTSubscribe will use the date/time from the 

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Rich Bell]

I should say that in the first test, I saw the disconnect and reconnect and 
processing pick back up.
I did a couple more tests. First, just stop publishing. No disconnect, 
MQTTSubscribe waited until the next message. No surprise there. Next I shut 
the broker down. Again, I saw MQTTSubscribe disconnect and reconnect and 
continue processing.
So, I think the reconnect logic is working, but there still might be some 
other real world case that could cause a problem.

On Wednesday, 24 June 2020 13:50:22 UTC-4, Rich Bell wrote:
>
> Christian,
> What are the symptoms that cause you to have to restart WeeWX when MQTT 
> connection is lost with wxmesh? The reason I ask, I tried just 
> disconnection the MQTTSubscribe client from the network and then 
> reconnecting. It seemed to behave correctly. I am hesitant to stop the 
> broker, but I will work on setting up a second broker to do some more 
> testing.  
> Thanks for any information/help. - 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4b3f3030-b1c1-4600-94a9-4333596a8a5co%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

['Christian Peters' via weewx-user]

Hi Rich,

thank you very much. 
It works like a charm! :-) 

I set up a temporary mapping to values already available in the databae. 
For the temp and humid values it works out of the box, for CPM, CPS and 
radiation I have to setup unit groups later. 

This is my working setup - just to have that written down for others:

my data form the MQTT broker:

radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00

weewx.conf:

[MQTTSubscribeService]
host = xxx.xxx.xxx.xxx # IP of the broker
payload_type = keyword
console = True
[[topics]]
 [[[weather]]]   # The topic you are subscribing to
   unit_system = METRICWX # Not sure weather you want METRICWX or 
METRIC. See http://weewx.com/docs/customizing.htm#units
   temp_2m # Name in the MQTT message
   name = extraTemp1 # WeeWX name
   temp_5cm
   name = extraTemp2
   temp_dht22
   name = extraTemp3
   hum_dht22
   name = extraHumid3
   rain
   name = hail
   radiation
   name = signal1
   cpm
   name = signal2
   cps
   name = signal3

[[message_callback]]
 type = keyword
 keyword_delimiter = "," # The delimiter between the name/value pairs
 keyword_separator = ":" # The separator between the name and the value

[[Services]]
data_services = user.MQTTSubscribe.MQTTSubscribeService

That's quite nice and more elegant as to set up a second weewx instance 
with a MQTT driver! 
Thank you very much.

My MQTT broker runs on a BananaPi which is located in the garden near the 
sensors (Temp2m, Temp5cm, raingauge, temp and hum sensor inside the 
controlbox and a MightyOhm Geiger Counter Kit).
I can't figure out why...but somtimes I lost the WLAN connection (after 
7-30 days). Then I restart the BananPi, start the mosquitto deamon...but 
the weewx instance running the wxMesh driver didn't reconnect. 
I have to start and stop this instance, then it works again. But I saw a 
post in weewx-development that someone pointed out the connection was setup 
once at initialisation...maybe there is no check of the connection and a 
reconnect condition?

If the setup goes online (at the moment I run the simulator whil mograting 
all sensors and tweak the new webpage) and the VanatgeVP2 is connected, I 
will check the behavior of your drriver in my setup. 

Thanks again for the excellent support. If I run into some problems I will 
contact you again. :-)

Regards,

Christian 

P.S. Ken, thanks for you fix...it works..! :-) But the MQTTSubscribeService 
works great and I will prefer to run only one weewx instance to deal with 
all sensors. 


Am Mittwoch, 24. Juni 2020 19:25:05 UTC+2 schrieb Rich Bell:
>
>
> Well, I haven't heard of having to restart WeeWX when the connection is 
> lost, and if that happens I would certainly want to look into fixing that. 
> I'll do some experiments to see if I can recreate. 
>
> Sounds like picking the service might be the best long term choice, with 
> the caveat about the reconnect logic needing to be verified. But if you 
> want to get your feet wet, I would suggest that we get it up and running as 
> a driver - perhaps even running from the command line for a bit. The actual 
> configuration work is really the same. So you could migrate to the service 
> as you get more comfortable or after we prove that lost connections are not 
> a problem. 
>
> The following assumes that you install 1.5.4-rc01. This changed the way to 
> configure MQTTSubscribe. Once installed, there will be three key sections 
> the [MQTTSubscribeDriver]/[MQTTSubscribeService] section. This is the MQTT 
> connection information, and I believe this is pretty straight forward. But 
> after looking at it, if you have questions let me know.
>
> Next up is the [[topics]] section. Based on the information you posted, I 
> think this is what you would want
>
> [[topics]]
>  [[[weather]]]   # The topic you are subscribing to
>unit_system = METRICWX # Not sure weather you want METRICWX or METRIC. 
> See http://weewx.com/docs/customizing.htm#units
>temp_2m # Name in the MQTT message
>name = extraTemp1 # WeeWX name
>temp_5cm 
> name = extraTemp2
>temp_dht22 
> name = inTemp
>hum_dht22 
>   name = inHumidity
>rain 
> name = rain
>geiger 
>   name = radiation
>
> Not sure about your TIME field and the value of 0. I left it out and since 
> it is missing MQTTSubscribe will use the date/time from the server it is 
> running on. There are other options for converting the incoming data, but 
> yours looks pretty straight forward.
>
> Last is the [[message_callback]] section. I would call your data 
> 'keyword'. If it was json, I would expect quotes around the fieldnames. So, 
> something like this
>
> [[message_callback]]
>  type = 

Re: [weewx-user] Re: Full day highcharts question

[Pat O'Brien]

Update your skins.conf to latest version too

On Wed, Jun 24, 2020, 4:28 PM Manfred Maier 
wrote:

>
> Hi Pat,
> apologies, it's me again.
>
> Yesterday (and today) I've just copied the new belchertown.py in my user
> folder.
> Now I've seen that i get a two error messages in my syslog.
>
> The first one I've been able to resolve. It was caused by the "check for
> update" functionality that you have removed recently. After setting the
> update setting to zero the error was gone.
>
> The second one I'm not able to locate. This is the error I get:
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> Generate failed with exception ''
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
> Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
> Reason: cannot find 'forecast_provider'
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   Traceback (most recent call last):
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in
> generate
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   unicode_string = compiled_template.respond()
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
> File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", line
> 1154, in respond
>
> Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:
>   NameMapper.NotFound: cannot find 'forecast_provider'
>
> didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50 UTC+2:
>
>> Perfect !
>> Thanks
>>
>> Le mer. 24 juin 2020 à 16:04, Manfred Maier 
>> a écrit :
>>
>>> Solved!
>>> Thanks so much!
>>>
>>> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>>>
 Can you try the latest belchertown.py file from the devleopment branch?
 I think I got it working. See screenshot.



 On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>
> Sent by email. The file has been too big for an upload here (or the
> database content isn't allowed?).
> Thanks for looking into 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/UWSnqt7tY3Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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/4e605379-67f9-4db4-b1a9-07b752dcbcebn%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/CAJv44%2BktTfwD0v54A5d%3D6zYT_Ot_kJDyX3jxf%3D-ZV1yDtH2gaA%40mail.gmail.com.

Re: [weewx-user] Re: Full day highcharts question

[Manfred Maier]

Hi Pat,
apologies, it's me again.

Yesterday (and today) I've just copied the new belchertown.py in my user 
folder.
Now I've seen that i get a two error messages in my syslog.

The first one I've been able to resolve. It was caused by the "check for 
update" functionality that you have removed recently. After setting the 
update setting to zero the error was gone.

The second one I'm not able to locate. This is the error I get:

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator: 
Generate failed with exception ''

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'forecast_provider'

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:   
  File "_etc_weewx_skins_Belchertown_js_belchertown_js_tmpl.py", line 1154, 
in respond

Jun 24 22:20:20 raspberrypi weewx[6177] ERROR weewx.cheetahgenerator:   
NameMapper.NotFound: cannot find 'forecast_provider'

didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 21:12:50 UTC+2:

> Perfect !
> Thanks
>
> Le mer. 24 juin 2020 à 16:04, Manfred Maier  a 
> écrit :
>
>> Solved!
>> Thanks so much! 
>>
>> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>>
>>> Can you try the latest belchertown.py file from the devleopment branch? 
>>> I think I got it working. See screenshot.
>>>
>>>
>>>
>>> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:

 Sent by email. The file has been too big for an upload here (or the 
 database content isn't allowed?).
 Thanks for looking into 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/295f9456-430d-44fb-9c4e-9b61640794e0n%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/4e605379-67f9-4db4-b1a9-07b752dcbcebn%40googlegroups.com.

[weewx-user] Re: Cannot decode reading of 'None' for gauge 'windDir'

[Pat]

I'm not the maintainer of this extension, and I don't use it so I'm purely 
guessing here.  

But based on the information you've given, try replacing the section you've 
pasted with this. Maintain a backup copy in case you need to revert back. 

try:
history = int(plot_options.get('history'))
except:
pass
else:
history_list = []
windspeed_history_list = []


batch_records = self.db_manager.genBatchRecords(self.lastGoodStamp 
- history * 60 * 60, self.lastGoodStamp)


for rec in batch_records:
db_value_tuple = weewx.units.as_value_tuple(rec, columnname)
history_value = weewx.units.convert(db_value_tuple, 
target_unit)[0]


try:
if history_value is not None:
history_list.append(float(history_value))
else:
continue
except:
syslog.syslog(syslog.LOG_DEBUG, "GaugeGenerator: Cannot 
decode reading of '%s' for gauge '%s'"
  % (history_value, gaugename))



On Wednesday, June 24, 2020 at 12:15:36 PM UTC-4, Andrej B. wrote:
>
> Good afternoon,
>
> I use Bootstrap theme with Nick gauges (dajda.net). Weewx ver. 4.1 under 
> python 2.7 (Debian Buster)
> In my syslog every archive interval I see hundreds messages like: 
> GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'
> This is only happens when wind speed is not None. Below is logfile part:
>
>
>
>
>
>
>
>
>
>
>
> *Jun 24 19:00:15 weewxpi weewxd: GaugeGenerator: outTemp reading = 25.5 
> degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: inTemp reading = 
> 24.11 degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: 
> barometer reading = 1022.58763232 mbarJun 24 19:00:15 weewxpi weewxd: 
> GaugeGenerator: outHumidity reading = 49.0 percentJun 24 19:00:15 weewxpi 
> weewxd: GaugeGenerator: inHumidity reading = 56.0 percentJun 24 19:00:16 
> weewxpi weewxd: GaugeGenerator: windSpeed reading = 2.68224 
> meter_per_secondJun 24 19:00:16 weewxpi weewxd: GaugeGenerator: windGust 
> reading = 6.25856 meter_per_secondJun 24 19:00:16 weewxpi weewxd: 
> GaugeGenerator: windDir reading = 0.0 degree_compassJun 24 19:00:16 weewxpi 
> weewxd: GaugeGenerator: Cannot decode reading of 'None' for gauge 
> 'windDir'Jun 24 19:00:16 weewxpi weewxd: GaugeGenerator: Cannot decode 
> reading of 'None' for gauge 'windDir'Jun 24 19:00:16 weewxpi weewxd: 
> GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'*
>
> This is part of code responsible for this:
>
> try:
> history = int(plot_options.get('history'))
> except:
> pass
> else:
> history_list = []
> windspeed_history_list = []
>
> batch_records = 
> self.db_manager.genBatchRecords(self.lastGoodStamp - history * 60 * 60, 
> self.lastGoodStamp)
>
> for rec in batch_records:
> db_value_tuple = weewx.units.as_value_tuple(rec, 
> columnname)
> history_value = weewx.units.convert(db_value_tuple, 
> target_unit)[0]
>
> try:
> history_list.append(float(history_value))
> except:
> syslog.syslog(syslog.LOG_DEBUG, "GaugeGenerator: 
> Cannot decode reading of '%s' for gauge '%s'"
>   % (history_value, gaugename))
>
>
> Why this happens when wind speed has reading?
>
> 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/5328740c-4e91-4b66-bc9c-b1423327971fo%40googlegroups.com.

[weewx-user] Re: Cannot decode reading of 'None' for gauge 'windDir'

[Andrej B.]

If wind speed is 0, then "cannot decode" message is not seen:

Jun 24 22:20:16 weewxpi weewxd: GaugeGenerator: windSpeed reading = 0.0 
meter_per_second
Jun 24 22:20:16 weewxpi weewxd: GaugeGenerator: windGust reading = 0.0 
meter_per_second
Jun 24 22:20:16 weewxpi weewxd: GaugeGenerator: windDir has no reading 
(None)
Jun 24 22:20:16 weewxpi weewxd: GaugeGenerator: radiation reading = 0.0 
watt_per_meter_squared
Jun 24 22:20:16 weewxpi weewxd: GaugeGenerator: UV reading = 0.0 uv_index


2020 m. birželis 24 d., trečiadienis 19:15:36 UTC+3, Andrej B. rašė:
>
> Good afternoon,
>
> I use Bootstrap theme with Nick gauges (dajda.net). Weewx ver. 4.1 under 
> python 2.7 (Debian Buster)
> In my syslog every archive interval I see hundreds messages like: 
> GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'
> This is only happens when wind speed is not None. Below is logfile part:
>
>
>
>
>
>
>
>
>
>
>
> *Jun 24 19:00:15 weewxpi weewxd: GaugeGenerator: outTemp reading = 25.5 
> degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: inTemp reading = 
> 24.11 degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: 
> barometer reading = 1022.58763232 mbarJun 24 19:00:15 weewxpi weewxd: 
> GaugeGenerator: outHumidity reading = 49.0 percentJun 24 19:00:15 weewxpi 
> weewxd: GaugeGenerator: inHumidity reading = 56.0 percentJun 24 19:00:16 
> weewxpi weewxd: GaugeGenerator: windSpeed reading = 2.68224 
> meter_per_secondJun 24 19:00:16 weewxpi weewxd: GaugeGenerator: windGust 
> reading = 6.25856 meter_per_secondJun 24 19:00:16 weewxpi weewxd: 
> GaugeGenerator: windDir reading = 0.0 degree_compassJun 24 19:00:16 weewxpi 
> weewxd: GaugeGenerator: Cannot decode reading of 'None' for gauge 
> 'windDir'Jun 24 19:00:16 weewxpi weewxd: GaugeGenerator: Cannot decode 
> reading of 'None' for gauge 'windDir'Jun 24 19:00:16 weewxpi weewxd: 
> GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'*
>
> This is part of code responsible for this:
>
> try:
> history = int(plot_options.get('history'))
> except:
> pass
> else:
> history_list = []
> windspeed_history_list = []
>
> batch_records = 
> self.db_manager.genBatchRecords(self.lastGoodStamp - history * 60 * 60, 
> self.lastGoodStamp)
>
> for rec in batch_records:
> db_value_tuple = weewx.units.as_value_tuple(rec, 
> columnname)
> history_value = weewx.units.convert(db_value_tuple, 
> target_unit)[0]
>
> try:
> history_list.append(float(history_value))
> except:
> syslog.syslog(syslog.LOG_DEBUG, "GaugeGenerator: 
> Cannot decode reading of '%s' for gauge '%s'"
>   % (history_value, gaugename))
>
>
> Why this happens when wind speed has reading?
>
> 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/fb695639-e5dd-4f0f-b27b-1fd5d68adf07o%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Didier Decoodt]

Perfect !
Thanks

Le mer. 24 juin 2020 à 16:04, Manfred Maier  a
écrit :

> Solved!
> Thanks so much!
>
> Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:
>
>> Can you try the latest belchertown.py file from the devleopment branch? I
>> think I got it working. See screenshot.
>>
>>
>>
>> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>>>
>>> Sent by email. The file has been too big for an upload here (or the
>>> database content isn't allowed?).
>>> Thanks for looking into 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/295f9456-430d-44fb-9c4e-9b61640794e0n%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/CAAvt3%3DR3i2_pV0rfUrgEghTOHyrZ-duJRueHFhpdgY_ZN0jp-Q%40mail.gmail.com.

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Pat]

Good question. I'm not sure that'll work either unless you're able to 
inject that data into your MQTT broker since the station observation table 
is updated by MQTT payloads that match the observation's name. 

What would be idea is a way to have a folder called "hooks", and have weewx 
generate any html.tmpl file within that folder. Then I could use javascript 
to get the contents of those HTML files much like how I am doing today with 
the other data. But that won't work because you have to define the folder 
and template file in skin.conf. If the file is missing, then weewx won't 
process the skin website generation. 

Not sure how best for you to move forward with custom text being updated 
automatically. There's gotta be a way, just need to think it through with 
the limitations in place. 



On Wednesday, June 24, 2020 at 2:44:35 PM UTC-4, Manfred Maier wrote:
>
> So a better strategy for me would be to try to include the hours of 
> sunshine in the station observations?
>
> Pat schrieb am Mittwoch, 24. Juni 2020 um 20:37:13 UTC+2:
>
>> Ok that makes more sense. Right now the reloads are only for images, not 
>> text. 
>>
>> I'm not sure how I'd be able to reliably reload the hook area text. Those 
>> .inc files are only called when the skin is generated, and when the page is 
>> reloaded. The AJAX portion does not reload them (since they're unavailable 
>> to the public because they live in the skins folder).
>>
>>
>> On Wednesday, June 24, 2020 at 2:30:12 PM UTC-4, Manfred Maier wrote:
>>>
>>> It's text.
>>> I'm displaying the amount of sunshine hours on that day. In a somewhat 
>>> dynamic way.
>>>
>>> Here's the index_hook_after_station_info I'm using.
>>>
>>> #set sunshinetime = $day.sunshineTime.sum.raw
>>> #set sunshinetheoretical = $day.sunshineTheoretical.sum.raw
>>> #set ratio = 0 
>>>
>>> #set hours = int($sunshinetime / 60)
>>> #set minutes = int($sunshinetime - ($hours * 60))
>>>
>>> #if $sunshinetheoretical > 0
>>> #set $ratio = $sunshinetime / $sunshinetheoretical
>>> #end if
>>>
>>> #set $hoursstr = str($hours)
>>>
>>> #if $minutes < 10
>>> #set $minutesstr = '0' + str($minutes)
>>> #else
>>> #set $minutesstr = str($minutes)
>>> #end if
>>>
>>> #set $sundurationtext = $hoursstr + ':' + $minutesstr + ' Stunden'
>>>
>>> #if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw == 
>>> 0 and $sunshinetime > 0
>>> #set $suntext = 'Heute gab es insgesamt ' + $sundurationtext + ' 
>>> Sonnenschein.'
>>> #else if $sunshinetheoretical > 0 and 
>>> $current.sunshineTheoretical.raw == 0 and $sunshinetime == 0
>>> #set $suntext = 'Heute gab es leider gar keinen Sonnenschein.'
>>> #else if $ratio >= 0.7
>>> #set $suntext = 'Heute gab es schon ' + $sundurationtext + ' 
>>> Sonnenschein.'
>>> #else if $ratio >= 0.4
>>> #set $suntext = 'Heute gab es bisher ' + $sundurationtext + ' 
>>> Sonnenschein.'
>>> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime 
>>> > 0
>>> #set $suntext = 'Heute gab es erst ' + $sundurationtext + ' 
>>> Sonnenschein.'
>>> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime 
>>> == 0
>>> #set $suntext = 'Heute gab es leider noch keinen Sonnenschein.' 
>>> #else
>>> #set $suntext = ''  
>>> #end if
>>>
>>> #set $dailyrain = $day.rain.sum.raw 
>>>
>>> #if $dailyrain == 0
>>> #set raintext = 'Bisher kein Regen.'
>>> #else 
>>> #set $raintext = 'Bisher ' + str($day.rain.sum) + ' Regen.'
>>> #end if
>>>
>>> 
>>> 
>>> $suntext $raintext
>>> 
>>> 
>>>
>>>

-- 
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/902dbfb7-e42d-4f70-b6f1-81bfbeddb1afo%40googlegroups.com.

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Manfred Maier]

So a better strategy for me would be to try to include the hours of 
sunshine in the station observations?

Pat schrieb am Mittwoch, 24. Juni 2020 um 20:37:13 UTC+2:

> Ok that makes more sense. Right now the reloads are only for images, not 
> text. 
>
> I'm not sure how I'd be able to reliably reload the hook area text. Those 
> .inc files are only called when the skin is generated, and when the page is 
> reloaded. The AJAX portion does not reload them (since they're unavailable 
> to the public because they live in the skins folder).
>
>
> On Wednesday, June 24, 2020 at 2:30:12 PM UTC-4, Manfred Maier wrote:
>>
>> It's text.
>> I'm displaying the amount of sunshine hours on that day. In a somewhat 
>> dynamic way.
>>
>> Here's the index_hook_after_station_info I'm using.
>>
>> #set sunshinetime = $day.sunshineTime.sum.raw
>> #set sunshinetheoretical = $day.sunshineTheoretical.sum.raw
>> #set ratio = 0 
>>
>> #set hours = int($sunshinetime / 60)
>> #set minutes = int($sunshinetime - ($hours * 60))
>>
>> #if $sunshinetheoretical > 0
>> #set $ratio = $sunshinetime / $sunshinetheoretical
>> #end if
>>
>> #set $hoursstr = str($hours)
>>
>> #if $minutes < 10
>> #set $minutesstr = '0' + str($minutes)
>> #else
>> #set $minutesstr = str($minutes)
>> #end if
>>
>> #set $sundurationtext = $hoursstr + ':' + $minutesstr + ' Stunden'
>>
>> #if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw == 
>> 0 and $sunshinetime > 0
>> #set $suntext = 'Heute gab es insgesamt ' + $sundurationtext + ' 
>> Sonnenschein.'
>> #else if $sunshinetheoretical > 0 and 
>> $current.sunshineTheoretical.raw == 0 and $sunshinetime == 0
>> #set $suntext = 'Heute gab es leider gar keinen Sonnenschein.'
>> #else if $ratio >= 0.7
>> #set $suntext = 'Heute gab es schon ' + $sundurationtext + ' 
>> Sonnenschein.'
>> #else if $ratio >= 0.4
>> #set $suntext = 'Heute gab es bisher ' + $sundurationtext + ' 
>> Sonnenschein.'
>> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime 
>> > 0
>> #set $suntext = 'Heute gab es erst ' + $sundurationtext + ' 
>> Sonnenschein.'
>> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime 
>> == 0
>> #set $suntext = 'Heute gab es leider noch keinen Sonnenschein.' 
>> #else
>> #set $suntext = ''  
>> #end if
>>
>> #set $dailyrain = $day.rain.sum.raw 
>>
>> #if $dailyrain == 0
>> #set raintext = 'Bisher kein Regen.'
>> #else 
>> #set $raintext = 'Bisher ' + str($day.rain.sum) + ' Regen.'
>> #end if
>>
>> 
>> 
>> $suntext $raintext
>> 
>> 
>>
>>

-- 
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/a0a4f98d-d748-4bb7-8530-b9aab705a34an%40googlegroups.com.

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Pat]

Ok that makes more sense. Right now the reloads are only for images, not 
text. 

I'm not sure how I'd be able to reliably reload the hook area text. Those 
.inc files are only called when the skin is generated, and when the page is 
reloaded. The AJAX portion does not reload them (since they're unavailable 
to the public because they live in the skins folder).


On Wednesday, June 24, 2020 at 2:30:12 PM UTC-4, Manfred Maier wrote:
>
> It's text.
> I'm displaying the amount of sunshine hours on that day. In a somewhat 
> dynamic way.
>
> Here's the index_hook_after_station_info I'm using.
>
> #set sunshinetime = $day.sunshineTime.sum.raw
> #set sunshinetheoretical = $day.sunshineTheoretical.sum.raw
> #set ratio = 0 
>
> #set hours = int($sunshinetime / 60)
> #set minutes = int($sunshinetime - ($hours * 60))
>
> #if $sunshinetheoretical > 0
> #set $ratio = $sunshinetime / $sunshinetheoretical
> #end if
>
> #set $hoursstr = str($hours)
>
> #if $minutes < 10
> #set $minutesstr = '0' + str($minutes)
> #else
> #set $minutesstr = str($minutes)
> #end if
>
> #set $sundurationtext = $hoursstr + ':' + $minutesstr + ' Stunden'
>
> #if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw == 0 
> and $sunshinetime > 0
> #set $suntext = 'Heute gab es insgesamt ' + $sundurationtext + ' 
> Sonnenschein.'
> #else if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw 
> == 0 and $sunshinetime == 0
> #set $suntext = 'Heute gab es leider gar keinen Sonnenschein.'
> #else if $ratio >= 0.7
> #set $suntext = 'Heute gab es schon ' + $sundurationtext + ' 
> Sonnenschein.'
> #else if $ratio >= 0.4
> #set $suntext = 'Heute gab es bisher ' + $sundurationtext + ' 
> Sonnenschein.'
> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime > 
> 0
> #set $suntext = 'Heute gab es erst ' + $sundurationtext + ' 
> Sonnenschein.'
> #else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime 
> == 0
> #set $suntext = 'Heute gab es leider noch keinen Sonnenschein.' 
> #else
> #set $suntext = ''  
> #end if
>
> #set $dailyrain = $day.rain.sum.raw 
>
> #if $dailyrain == 0
> #set raintext = 'Bisher kein Regen.'
> #else 
> #set $raintext = 'Bisher ' + str($day.rain.sum) + ' Regen.'
> #end if
>
> 
> 
> $suntext $raintext
> 
> 
>
>

-- 
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/99137d3b-deef-4751-98e9-37f8efb6b9b9o%40googlegroups.com.

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Manfred Maier]

It's text.
I'm displaying the amount of sunshine hours on that day. In a somewhat 
dynamic way.

Here's the index_hook_after_station_info I'm using.

#set sunshinetime = $day.sunshineTime.sum.raw
#set sunshinetheoretical = $day.sunshineTheoretical.sum.raw
#set ratio = 0 

#set hours = int($sunshinetime / 60)
#set minutes = int($sunshinetime - ($hours * 60))

#if $sunshinetheoretical > 0
#set $ratio = $sunshinetime / $sunshinetheoretical
#end if

#set $hoursstr = str($hours)

#if $minutes < 10
#set $minutesstr = '0' + str($minutes)
#else
#set $minutesstr = str($minutes)
#end if

#set $sundurationtext = $hoursstr + ':' + $minutesstr + ' Stunden'

#if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw == 0 
and $sunshinetime > 0
#set $suntext = 'Heute gab es insgesamt ' + $sundurationtext + ' 
Sonnenschein.'
#else if $sunshinetheoretical > 0 and $current.sunshineTheoretical.raw 
== 0 and $sunshinetime == 0
#set $suntext = 'Heute gab es leider gar keinen Sonnenschein.'
#else if $ratio >= 0.7
#set $suntext = 'Heute gab es schon ' + $sundurationtext + ' 
Sonnenschein.'
#else if $ratio >= 0.4
#set $suntext = 'Heute gab es bisher ' + $sundurationtext + ' 
Sonnenschein.'
#else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime > 0
#set $suntext = 'Heute gab es erst ' + $sundurationtext + ' 
Sonnenschein.'
#else if $ratio < 0.4 and $sunshinetheoretical > 0 and $sunshinetime == 
0
#set $suntext = 'Heute gab es leider noch keinen Sonnenschein.' 
#else
#set $suntext = ''  
#end if

#set $dailyrain = $day.rain.sum.raw 

#if $dailyrain == 0
#set raintext = 'Bisher kein Regen.'
#else 
#set $raintext = 'Bisher ' + str($day.rain.sum) + ' Regen.'
#end if



$suntext $raintext



-- 
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/7ad319e9-6ece-44e8-9e0b-72e0e55c6ae6n%40googlegroups.com.

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Pat]

Do you have images in your after station info hook? Or just text. 

Right now it's only going to reload images - but I wonder if it should 
reload the entire hook? 

On Wednesday, June 24, 2020 at 11:41:37 AM UTC-4, Pat wrote:
>
> I'll look into this 
>
> On Wednesday, June 24, 2020 at 4:03:18 AM UTC-4, Manfred Maier wrote:
>>
>> Hi Pat,
>> there might be a possible issue with the reload functionality of the 
>> additional index_hook section on the front-page of the skin.
>>
>> I have the following settings in the weewx.conf
>>
>> reload_hook_images = 1
>>
>> reload_images_radar = 300
>>
>> reload_images_hook_asi = 300
>>
>> reload_images_hook_af = -1
>>
>> reload_images_hook_as = -1
>>
>> reload_images_hook_ac = 300
>>
>>
>> Still, the index_hook_after_station_info doesn't reload.
>>
>> Is there anything wrong with this functionality or did I make a mistake 
>> in setting up the index_hook (which is much more likely)?
>>
>> Manfred
>>
>

-- 
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/eeab7a1e-8393-4afc-b595-1d44b34bo%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Rich Bell]

Christian,
What are the symptoms that cause you to have to restart WeeWX when MQTT 
connection is lost with wxmesh? The reason I ask, I tried just 
disconnection the MQTTSubscribe client from the network and then 
reconnecting. It seemed to behave correctly. I am hesitant to stop the 
broker, but I will work on setting up a second broker to do some more 
testing.  
Thanks for any information/help. - 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e89984d2-b087-4276-9e13-193717fd8997o%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Rich Bell]

Well, I haven't heard of having to restart WeeWX when the connection is 
lost, and if that happens I would certainly want to look into fixing that. 
I'll do some experiments to see if I can recreate. 

Sounds like picking the service might be the best long term choice, with 
the caveat about the reconnect logic needing to be verified. But if you 
want to get your feet wet, I would suggest that we get it up and running as 
a driver - perhaps even running from the command line for a bit. The actual 
configuration work is really the same. So you could migrate to the service 
as you get more comfortable or after we prove that lost connections are not 
a problem. 

The following assumes that you install 1.5.4-rc01. This changed the way to 
configure MQTTSubscribe. Once installed, there will be three key sections 
the [MQTTSubscribeDriver]/[MQTTSubscribeService] section. This is the MQTT 
connection information, and I believe this is pretty straight forward. But 
after looking at it, if you have questions let me know.

Next up is the [[topics]] section. Based on the information you posted, I 
think this is what you would want

[[topics]]
 [[[weather]]]   # The topic you are subscribing to
   unit_system = METRICWX # Not sure weather you want METRICWX or METRIC. 
See http://weewx.com/docs/customizing.htm#units
   temp_2m # Name in the MQTT message
   name = extraTemp1 # WeeWX name
   temp_5cm 
name = extraTemp2
   temp_dht22 
name = inTemp
   hum_dht22 
  name = inHumidity
   rain 
name = rain
   geiger 
  name = radiation

Not sure about your TIME field and the value of 0. I left it out and since 
it is missing MQTTSubscribe will use the date/time from the server it is 
running on. There are other options for converting the incoming data, but 
yours looks pretty straight forward.

Last is the [[message_callback]] section. I would call your data 'keyword'. 
If it was json, I would expect quotes around the fieldnames. So, something 
like this

[[message_callback]]
 type = keyword
 keyword_delimiter = "," # The delimiter between the name/value pairs
 keyword_separator = ":" # The separator between the name and the value

There are some additional options when running as a service to attempt to 
only process data that belongs to the loop packet or archive record that is 
being augmented. Over time I have found the defaults to be a bit too 
restrictive, so we might need to configure those a bit.

I haven't tried to run a second instance of WeeWX, so I can't help there. 
But, if you need any more help with MQTTSubscribe, just let me know.
-rich

On Wednesday, 24 June 2020 12:51:43 UTC-4, Christian Peters wrote:
>
> Rich,
>
> that's great. I'm not sure whether I should stay on the driver version or 
> switch to the service versionwhich could make it maybe more easy. 
> But if the MQTTSubscribe as service lost connection and wouldn't 
> reconnect I have to restart the main weewx prog to get it up again!? So 
> maybe a second running instance 
> with MQTTSubscribe is the better choice...? 
> Difficult...I would perfer one instance as I struggle to get a second 
> weewx instance up with systemd at the moment 
>
> So with mosquitto_sub -h 192.168.1.143 -t weather
>
> I got this ( in JSON format I think) :
>
>
> TIME:0,radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00
>
> I mapped in my Python 2 env (weewx2.9, second instance with sql databse) 
> and wxMesh:
>
>  [[label_map]]
>  TIME = dateTime
>  temp_2m = extraTemp1
>  temp_5cm = extraTemp2
>  temp_dht22 = inTemp
>  hum_dht22 = inHumidity
>  rain = rain
>  geiger = radiation
>
> So do you know the syntax for the mapping for MQTTSubscribe? 
>
> As I send the data to the MQTT broker by myself it would be maybe best to 
> use a second instance and tweak the mapping to entrys which are already in 
> the schema.
> So I could stay in the mapping posted above?
>
> Do you set up a second instance of weewx with systemd already...? 
> Any help or syntax examples would be welcome, especially for the format of 
> the label mapping of 
> MQTTSubscribe. I tried weew-multi but dont get the second instance up... 
> Not sure its systemd ready...
>
> Thanks in advance,
>
> Christian 
>
>
>
> Am Mittwoch, 24. Juni 2020 16:12:12 UTC+2 schrieb Rich Bell:
>>
>> Christian,
>>
>> MQTTSubscribe should be able to meet your needs. I know the documentation 
>> is a bit sparse, but I can help get you up and running.
>>
>> The first question you need to answer is whether to run as a service or 
>> driver? From what I am understanding. If you ran as a driver it would 
>> essentially be a replacement for wxmesh. Meaning it would the database 
>> configured for that WeeWX instance. If you ran MQTTSubscribe as a service, 
>> you could augment the data in your other WeeWX instance.
>>
>> The next 

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

['Christian Peters' via weewx-user]

Rich,

that's great. I'm not sure whether I should stay on the driver version or 
switch to the service versionwhich could make it maybe more easy. 
But if the MQTTSubscribe as service lost connection and wouldn't reconnect 
I have to restart the main weewx prog to get it up again!? So maybe a 
second running instance 
with MQTTSubscribe is the better choice...? 
Difficult...I would perfer one instance as I struggle to get a second weewx 
instance up with systemd at the moment 

So with mosquitto_sub -h 192.168.1.143 -t weather

I got this ( in JSON format I think) :

TIME:0,radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00

I mapped in my Python 2 env (weewx2.9, second instance with sql databse) 
and wxMesh:

 [[label_map]]
 TIME = dateTime
 temp_2m = extraTemp1
 temp_5cm = extraTemp2
 temp_dht22 = inTemp
 hum_dht22 = inHumidity
 rain = rain
 geiger = radiation

So do you know the syntax for the mapping for MQTTSubscribe? 

As I send the data to the MQTT broker by myself it would be maybe best to 
use a second instance and tweak the mapping to entrys which are already in 
the schema.
So I could stay in the mapping posted above?

Do you set up a second instance of weewx with systemd already...? 
Any help or syntax examples would be welcome, especially for the format of 
the label mapping of 
MQTTSubscribe. I tried weew-multi but dont get the second instance up... 
Not sure its systemd ready...

Thanks in advance,

Christian 



Am Mittwoch, 24. Juni 2020 16:12:12 UTC+2 schrieb Rich Bell:
>
> Christian,
>
> MQTTSubscribe should be able to meet your needs. I know the documentation 
> is a bit sparse, but I can help get you up and running.
>
> The first question you need to answer is whether to run as a service or 
> driver? From what I am understanding. If you ran as a driver it would 
> essentially be a replacement for wxmesh. Meaning it would the database 
> configured for that WeeWX instance. If you ran MQTTSubscribe as a service, 
> you could augment the data in your other WeeWX instance.
>
> The next question is the format of the incoming data. Is it json, keyword 
> (name=value), or individual (single observation per topic)? Lastly, what 
> name mapping do you need to?
>
> -rich
>
> On Wednesday, 24 June 2020 08:59:25 UTC-4, Christian Peters wrote:
>>
>> Hi,
>>
>> I ran a weewx 3.9. station with Python 2 and a seperate weewx instance 
>> with the wxMesh.py driver. 
>> This works very nice (as far as the broker isn't down or the connection 
>> breaks - then a restart of the weewx instance which holds the wxMesh driver 
>> is needed...!). 
>> As I now switch to Python 3 and weewx 4.x I figured out that the 
>> wxMesh.py driver isn't Python 3 ready? :-( 
>>
>> How can I catch MQTT data into the weewx database from an external broker 
>> ilocated n my home lan?
>>
>> Is this the right extension to use:
>>
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>> ? 
>>
>> What I don't understand: if I will use it as a sevice, in which database 
>> will it put my values? 
>> Is there a mapping needed!? Can I use a seperate database? 
>> Is there a configuration example available or does anybody set up such a 
>> station and could provide the config or give me some advice 
>> howto get the data form the MQTT broker into weewx and the database to 
>> show the values and graphs!?
>> That would be great!
>>
>> Thanks in advance!
>>
>> Regards,
>>
>> Christian 
>>
>

-- 
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/ae339af5-ee32-4b7c-9d31-692d7494923fo%40googlegroups.com.

Re: [weewx-user] howto receive MQTT data from a running broker and put the data into database with weewx..?

[Ken Walker]

I modified two lines in wxMesh.py and it works fine with Python 3.

changed
#!/usr/bin/python

to
#!/user/bin/python3

and

changed
except ValueError, e:

to
except ValueError as e:

> On Jun 24, 2020, at 8:59 AM, 'Christian Peters' via weewx-user 
>  wrote:
> 
> Hi,
> 
> I ran a weewx 3.9. station with Python 2 and a seperate weewx instance with 
> the wxMesh.py driver. 
> This works very nice (as far as the broker isn't down or the connection 
> breaks - then a restart of the weewx instance which holds the wxMesh driver 
> is needed...!). 
> As I now switch to Python 3 and weewx 4.x I figured out that the wxMesh.py 
> driver isn't Python 3 ready? :-( 
> 
> How can I catch MQTT data into the weewx database from an external broker 
> ilocated n my home lan?
> 
> Is this the right extension to use:
> 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe 
> ? 
> 
> What I don't understand: if I will use it as a sevice, in which database will 
> it put my values? 
> Is there a mapping needed!? Can I use a seperate database? 
> Is there a configuration example available or does anybody set up such a 
> station and could provide the config or give me some advice 
> howto get the data form the MQTT broker into weewx and the database to show 
> the values and graphs!?
> That would be great!
> 
> Thanks in advance!
> 
> Regards,
> 
> Christian 
> 
> -- 
> 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/3f984aba-be57-419e-9334-fde2e668a7fdo%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/50E05044-A4EC-469C-84E0-A257CD219D32%40gmail.com.

[weewx-user] Cannot decode reading of 'None' for gauge 'windDir'

[Andrej B.]

Good afternoon,

I use Bootstrap theme with Nick gauges (dajda.net). Weewx ver. 4.1 under 
python 2.7 (Debian Buster)
In my syslog every archive interval I see hundreds messages like: 
GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'
This is only happens when wind speed is not None. Below is logfile part:











*Jun 24 19:00:15 weewxpi weewxd: GaugeGenerator: outTemp reading = 25.5 
degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: inTemp reading = 
24.11 degree_CJun 24 19:00:15 weewxpi weewxd: GaugeGenerator: 
barometer reading = 1022.58763232 mbarJun 24 19:00:15 weewxpi weewxd: 
GaugeGenerator: outHumidity reading = 49.0 percentJun 24 19:00:15 weewxpi 
weewxd: GaugeGenerator: inHumidity reading = 56.0 percentJun 24 19:00:16 
weewxpi weewxd: GaugeGenerator: windSpeed reading = 2.68224 
meter_per_secondJun 24 19:00:16 weewxpi weewxd: GaugeGenerator: windGust 
reading = 6.25856 meter_per_secondJun 24 19:00:16 weewxpi weewxd: 
GaugeGenerator: windDir reading = 0.0 degree_compassJun 24 19:00:16 weewxpi 
weewxd: GaugeGenerator: Cannot decode reading of 'None' for gauge 
'windDir'Jun 24 19:00:16 weewxpi weewxd: GaugeGenerator: Cannot decode 
reading of 'None' for gauge 'windDir'Jun 24 19:00:16 weewxpi weewxd: 
GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'*

This is part of code responsible for this:

try:
history = int(plot_options.get('history'))
except:
pass
else:
history_list = []
windspeed_history_list = []

batch_records = 
self.db_manager.genBatchRecords(self.lastGoodStamp - history * 60 * 60, 
self.lastGoodStamp)

for rec in batch_records:
db_value_tuple = weewx.units.as_value_tuple(rec, columnname)
history_value = weewx.units.convert(db_value_tuple, 
target_unit)[0]

try:
history_list.append(float(history_value))
except:
syslog.syslog(syslog.LOG_DEBUG, "GaugeGenerator: Cannot 
decode reading of '%s' for gauge '%s'"
  % (history_value, gaugename))


Why this happens when wind speed has reading?

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/5e06652d-1b5c-4528-a50d-1f2ae04dd2cdo%40googlegroups.com.
#
# Copyright (c) 2013-2014  Nick Dajda 
#
# Distributed under the terms of the GNU GENERAL PUBLIC LICENSE
#
"""Nick's custom generator for creating visual gauge image files from weewx.

Tested on Weewx release 3.0.1.
Tested with sqlite, may not work with other databases.

WILL NOT WORK WITH Weewx prior to release 3.0.
  -- Use this version for 2.4 - 2.7:  https://github.com/brewster76/fuzzy-archer/releases/tag/v2.0

Directions for use:

1) Put this file in the weewx/bin/user directory.
2) Add user.gaugeengine.GaugeGenerator to the list of Generators in skin.conf.
3) Add a [GaugeGenerator] section to skin.conf.
   Any gauges contained in this section are created when the report generator
   runs.
4) Guage names must match the Weewx field name, e.g. outTemp or barometer
5) Here is an example [GaugeGenerator] section:


#
# Settings for Gauge Generator
#
[GaugeGenerator]
image_width = 160
image_height = 160

# Colors...
#
# Format is 0xBBGGRR, so a pinky-purple color (r=FF, g=00, B=99) which would have
# an HTML tag of #FF0099 is expressed as 0x9900FF
fill_color = 0x4242b4
background_color = 0xff
label_color = 0x00
dial_color = 0x707070
needle_outline_color = 0xb48242
needle_fill_color = 0xb48242   # Leave option out for a transparent needle
text_color = 0xb48242

# How far the gauge extends, e.g. 180 is half a full dial, 270 is three quarters
# This is ignored when plotting wind direction which always uses 360.
# Must be an integer
dial_arc = 270

digitfontsize = 13
labelfontsize = 14

[[outTemp]]
minvalue = -20
maxvalue = 40
majorstep = 10
minorstep = 2
digitformat = %d
history = 24
bins = 90

[[barometer]]
minvalue = 970
maxvalue = 1050
majorstep = 20
minorstep = 5
digitformat = %d
history = 24
bins = 80

[[outHumidity]]
minvalue = 0
maxvalue = 100
majorstep = 20
minorstep = 5
history = 24
bins = 50

[[windSpeed]]
minvalue = 0
maxvalue = 40
majorstep = 10
minorstep = 2
history = 24
bins = 40

[[windGust]]
minvalue = 0
maxvalue = 40
majorstep = 

[weewx-user] Re: Belchertown skin: Reload index_hooks

[Pat]

I'll look into this 

On Wednesday, June 24, 2020 at 4:03:18 AM UTC-4, Manfred Maier wrote:
>
> Hi Pat,
> there might be a possible issue with the reload functionality of the 
> additional index_hook section on the front-page of the skin.
>
> I have the following settings in the weewx.conf
>
> reload_hook_images = 1
>
> reload_images_radar = 300
>
> reload_images_hook_asi = 300
>
> reload_images_hook_af = -1
>
> reload_images_hook_as = -1
>
> reload_images_hook_ac = 300
>
>
> Still, the index_hook_after_station_info doesn't reload.
>
> Is there anything wrong with this functionality or did I make a mistake in 
> setting up the index_hook (which is much more likely)?
>
> Manfred
>

-- 
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/1225f311-f179-4a4e-8011-9124f72d2efdo%40googlegroups.com.

[weewx-user] Re: Belchertown windrose

[Pat]

Take a look at the Belchertown chart's documentation 
.
 
It shows how to add custom graphs - such as windRose.

On Wednesday, June 24, 2020 at 11:23:55 AM UTC-4, Ton Karsten wrote:
>
> On my website with a simulation sensor I don't see a wind rose.
> Does anyone know how to adjust this?
> No idea where to look, can't get out.
> 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/01be15b9-e89a-41e4-ac61-878bdf44a6e2o%40googlegroups.com.

[weewx-user] Belchertown windrose

[Ton Karsten]

On my website with a simulation sensor I don't see a wind rose.
Does anyone know how to adjust this?
No idea where to look, can't get out.
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/7f70898c-ba2c-48d0-963d-1470f6ad72edo%40googlegroups.com.

[weewx-user] Re: Resource busy - raspbian buster, weewx 4 and WMR200

[AsgeirK]

I'm having similar issues after upgrade to 4.1.1

Jun 24 13:22:17 PI-W4 weewx[546] ERROR weewx.drivers.wmr200: USB 
read_device overflow error
Jun 24 13:22:17 PI-W4 weewx[546] ERROR weewx.drivers.wmr200: USB device 
read error
Jun 24 13:22:17 PI-W4 weewx[546] DEBUG weewx.manager: Daily summary version 
is 1.0
Jun 24 13:22:18 PI-W4 weewx[546] INFO weewx.restx: Wunderground-PWS: 
Published record 2020-06-24 13:22:00 CEST (1592997720)
Jun 24 13:22:18 PI-W4 weewx[546] ERROR weewx.drivers.wmr200: USB polling 
thread unexpectedly terminated
Jun 24 13:22:18 PI-W4 weewx[546] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jun 24 13:22:18 PI-W4 weewx[546] INFO weewx.engine: Shutting down StdReport 
thread
Jun 24 13:22:31 PI-W4 weewx[546] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 13.79 seconds
Jun 24 13:22:31 PI-W4 weewx[546] DEBUG weewx.manager: Daily summary version 
is 1.0
Jun 24 13:22:31 PI-W4 systemd[1]: Started Session c1681 of user pi.
Jun 24 13:22:37 PI-W4 weewx[546] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 6.01 seconds
Jun 24 13:22:37 PI-W4 weewx[546] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx
Jun 24 13:22:37 PI-W4 weewx[546] DEBUG weewx.reportengine: Running report 
'SmartphoneReport'
Jun 24 13:22:37 PI-W4 weewx[546] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
'SmartphoneReport'
Jun 24 13:22:37 PI-W4 weewx[546] DEBUG weewx.cheetahgenerator: Using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Jun 24 13:22:37 PI-W4 weewx[546] DEBUG weewx.manager: Daily summary version 
is 1.0
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.cheetahgenerator: Generated 6 
files for report SmartphoneReport in 0.51 seconds
Jun 24 13:22:38 PI-W4 weewx[546] DEBUG weewx.manager: Daily summary version 
is 1.0
Jun 24 13:22:38 PI-W4 weewx[546] ERROR weewx.engine: Unable to shut down 
StdReport thread
Jun 24 13:22:38 PI-W4 weewx[546] DEBUG weewx.restx: Shut down 
Wunderground-PWS thread.
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: USB polling 
thread expired
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog 
received shutdown
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog thread 
exiting
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog thread 
expired
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Received packet 
count live:15445 archive:940 control:1782
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Received 
bytes:1993192 sent bytes:47720
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Packet archive 
queue len:21 live queue len:0
Jun 24 13:22:38 PI-W4 weewx[546] WARNING weewx.drivers.wmr200: Exiting with 
packets still in archive queue cnt:21
Jun 24 13:22:38 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Driver 
gracefully exiting
Jun 24 13:22:38 PI-W4 weewx[546] CRITICAL __main__: Caught WeeWxIOError: 
USB polling thread unexpectedly terminated
Jun 24 13:22:38 PI-W4 weewx[546] CRITICAL __main__:   Waiting 60 
seconds then retrying...
Jun 24 13:22:40 PI-W4 weewx[546] INFO weewx.imagegenerator: Generated 6 
images for report SmartphoneReport in 2.05 seconds
Jun 24 13:22:40 PI-W4 weewx[546] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx/smartphone
.
.
.
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Using pc time 
adjusting archive record time by 3765 sec 2020-06-24 12:20:00 CEST 
(1592994000) => 2020-06-24 13:22:45 CEST (1592997765)
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jun 24 13:23:46 PI-W4 weewx[546] DEBUG weewx.restx: Shut down 
Wunderground-PWS thread.
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: USB polling 
device thread exiting
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: USB polling 
thread expired
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog 
received shutdown
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog thread 
exiting
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Watchdog thread 
expired
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Received packet 
count live:15446 archive:941 control:1784
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Received 
bytes:664 sent bytes:48
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Packet archive 
queue len:0 live queue len:1
Jun 24 13:23:46 PI-W4 weewx[546] WARNING weewx.drivers.wmr200: Exiting with 
packets still in live queue cnt:1
Jun 24 13:23:46 PI-W4 weewx[546] INFO weewx.drivers.wmr200: Driver 
gracefully exiting
Jun 24 13:23:46 PI-W4 weewx[546] CRITICAL __main__: Caught unrecoverable 
exception:
Jun 24 13:23:46 PI-W4 

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[gjr80]

The interceptor driver is python 2/3 compatible. Most likely you only have the 
WeeWX python 3 prerequisites installed and hence running the driver under 
python 2 failed.

Gary 

-- 
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/82bc9b3f-7694-4f55-8802-f7acf2ffd0ceo%40googlegroups.com.

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[John Burricelli]

I got it to work, in addition to your help, I had to change python to 
python3 for some reason

# PYTHONPATH=/usr/share/weewx python3 /usr/share/weewx/user/interceptor.py 
--device=ecowitt-client --mode=listen --port=8000
mapped packet: {'dateTime': 1593010224, 'usUnits': 1, 'pressure': 29.202, 
'inHumidity': 56.0, 'inTemp': 74.8}

On Wednesday, June 24, 2020 at 10:42:03 AM UTC-4, gjr80 wrote:
>
> Your PYTHONPATH needs to include /usr/share/weewx. Try using:
>
> $ PYTHONPATH=/usr/share/weewx python ..
>
>
> Gary
>
> On Wednesday, 24 June 2020 22:13:38 UTC+10, John Burricelli wrote:
>>
>> Also, has anyone been able to run the driver manually?  I get this error 
>> when I try it that way.
>>
>> $ PYTHONPATH=bin python /usr/share/weewx/user/interceptor.py 
>> --device=ecowitt --mode=listen --port=8000
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/user/interceptor.py", line 302, in 
>> import weewx.drivers
>> ImportError: No module named weewx.drivers
>>
>>
>> On Wednesday, June 24, 2020 at 7:51:03 AM UTC-4, John Burricelli wrote:
>>
>>  
>>
>>> I had a decent storm come through last night with nearly 50 reported 
>>> lightning strikes via my ecowitt app.  As far as i can tell however nothing 
>>> is being inserted into the database.
>>>
>>> INSERT INTO archive_day_lightning_energy 
>>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>> INSERT INTO archive_day_lightning_energy 
>>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>> CREATE TABLE archive_day_lightning_noise_count (dateTime INTEGER NOT 
>>> NULL UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime 
>>> INTEGER, sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>>> INSERT INTO archive_day_lightning_noise_count 
>>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>> INSERT INTO archive_day_lightning_noise_count 
>>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>> CREATE TABLE archive_day_lightning_strike_count (dateTime INTEGER NOT 
>>> NULL UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime 
>>> INTEGER, sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>>> INSERT INTO archive_day_lightning_strike_count 
>>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>> INSERT INTO archive_day_lightning_strike_count 
>>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>>
>>> On Wednesday, June 24, 2020 at 12:46:53 AM UTC-4, Gert Andersen wrote:

 Hi Oliver

 I'm using your patched script and it's working fine.

 I insert these fields into th database:

 [[sensor_map_extensions]]
 lightning_strike_count = lightning_num
 lightning_distance = lightning

 These 2 fields are also coming from the sensor:

 lightning_time
 wh57batt

 But can't be mapped right now as far as I can see. There are other 
 lightning types in the extended scheme, but they don't fit with these.

 It could also be very nice, to implement the PASSKEY functionality.

 Gert

 On Tuesday, June 23, 2020 at 9:51:37 PM UTC+2, olicat wrote:
>
> Hi!
>
> Are there any experiences with the adjusted script regarding lightning?
> Does it work for you now?
>
> Regards, Oliver
>
>

-- 
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/ca7f8a4d-ee21-4438-a967-96428b08d14do%40googlegroups.com.

Re: [weewx-user] Wunderground doesn't accept my data

[vince]

On Tuesday, June 23, 2020 at 7:29:03 PM UTC-7, gjr80 wrote:
>
> Apologies to Forrest Gump's mother but the first thing that came into my 
> head was ' Weather Underground is like a box of chocolatesyou never 
> know what your gonna get'
>
>
>>
I lean more toward "WU is as WU does..." or "WU happens..." 

-- 
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/156e66a5-d462-4c9a-be27-0ccead90df18o%40googlegroups.com.

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[gjr80]

Your PYTHONPATH needs to include /usr/share/weewx. Try using:

$ PYTHONPATH=/usr/share/weewx python ..


Gary

On Wednesday, 24 June 2020 22:13:38 UTC+10, John Burricelli wrote:
>
> Also, has anyone been able to run the driver manually?  I get this error 
> when I try it that way.
>
> $ PYTHONPATH=bin python /usr/share/weewx/user/interceptor.py 
> --device=ecowitt --mode=listen --port=8000
> Traceback (most recent call last):
>   File "/usr/share/weewx/user/interceptor.py", line 302, in 
> import weewx.drivers
> ImportError: No module named weewx.drivers
>
>
> On Wednesday, June 24, 2020 at 7:51:03 AM UTC-4, John Burricelli wrote:
>
>  
>
>> I had a decent storm come through last night with nearly 50 reported 
>> lightning strikes via my ecowitt app.  As far as i can tell however nothing 
>> is being inserted into the database.
>>
>> INSERT INTO archive_day_lightning_energy 
>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>> INSERT INTO archive_day_lightning_energy 
>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>> CREATE TABLE archive_day_lightning_noise_count (dateTime INTEGER NOT NULL 
>> UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, 
>> sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> INSERT INTO archive_day_lightning_noise_count 
>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>> INSERT INTO archive_day_lightning_noise_count 
>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>> CREATE TABLE archive_day_lightning_strike_count (dateTime INTEGER NOT 
>> NULL UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime 
>> INTEGER, sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> INSERT INTO archive_day_lightning_strike_count 
>> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>> INSERT INTO archive_day_lightning_strike_count 
>> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>>
>> On Wednesday, June 24, 2020 at 12:46:53 AM UTC-4, Gert Andersen wrote:
>>>
>>> Hi Oliver
>>>
>>> I'm using your patched script and it's working fine.
>>>
>>> I insert these fields into th database:
>>>
>>> [[sensor_map_extensions]]
>>> lightning_strike_count = lightning_num
>>> lightning_distance = lightning
>>>
>>> These 2 fields are also coming from the sensor:
>>>
>>> lightning_time
>>> wh57batt
>>>
>>> But can't be mapped right now as far as I can see. There are other 
>>> lightning types in the extended scheme, but they don't fit with these.
>>>
>>> It could also be very nice, to implement the PASSKEY functionality.
>>>
>>> Gert
>>>
>>> On Tuesday, June 23, 2020 at 9:51:37 PM UTC+2, olicat wrote:

 Hi!

 Are there any experiences with the adjusted script regarding lightning?
 Does it work for you now?

 Regards, Oliver



-- 
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/9fb2ad65-9240-41a1-b851-770f861a8579o%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

[Rich Bell]

Christian,

MQTTSubscribe should be able to meet your needs. I know the documentation 
is a bit sparse, but I can help get you up and running.

The first question you need to answer is whether to run as a service or 
driver? From what I am understanding. If you ran as a driver it would 
essentially be a replacement for wxmesh. Meaning it would the database 
configured for that WeeWX instance. If you ran MQTTSubscribe as a service, 
you could augment the data in your other WeeWX instance.

The next question is the format of the incoming data. Is it json, keyword 
(name=value), or individual (single observation per topic)? Lastly, what 
name mapping do you need to?

-rich

On Wednesday, 24 June 2020 08:59:25 UTC-4, Christian Peters wrote:
>
> Hi,
>
> I ran a weewx 3.9. station with Python 2 and a seperate weewx instance 
> with the wxMesh.py driver. 
> This works very nice (as far as the broker isn't down or the connection 
> breaks - then a restart of the weewx instance which holds the wxMesh driver 
> is needed...!). 
> As I now switch to Python 3 and weewx 4.x I figured out that the wxMesh.py 
> driver isn't Python 3 ready? :-( 
>
> How can I catch MQTT data into the weewx database from an external broker 
> ilocated n my home lan?
>
> Is this the right extension to use:
>
> https://github.com/bellrichm/WeeWX-MQTTSubscribe 
> ? 
>
> What I don't understand: if I will use it as a sevice, in which database 
> will it put my values? 
> Is there a mapping needed!? Can I use a seperate database? 
> Is there a configuration example available or does anybody set up such a 
> station and could provide the config or give me some advice 
> howto get the data form the MQTT broker into weewx and the database to 
> show the values and graphs!?
> That would be great!
>
> Thanks in advance!
>
> Regards,
>
> Christian 
>

-- 
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/b002c36d-72b8-4713-80af-70de78690d9co%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Manfred Maier]

Solved!
Thanks so much! 

Pat schrieb am Mittwoch, 24. Juni 2020 um 15:41:13 UTC+2:

> Can you try the latest belchertown.py file from the devleopment branch? I 
> think I got it working. See screenshot.
>
>
>
> On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>>
>> Sent by email. The file has been too big for an upload here (or the 
>> database content isn't allowed?).
>> Thanks for looking into 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/295f9456-430d-44fb-9c4e-9b61640794e0n%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Pat]

Can you try the latest belchertown.py file from the devleopment branch? I 
think I got it working. See screenshot.



On Wednesday, June 24, 2020 at 8:48:53 AM UTC-4, Manfred Maier wrote:
>
> Sent by email. The file has been too big for an upload here (or the 
> database content isn't allowed?).
> Thanks for looking into 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/1a0d18b3-2e3c-4fa2-969a-d8f215242a21o%40googlegroups.com.

[weewx-user] How to tell weewx to expect metric or US when importing from a text file?

[Ashley Hinton]

Hey everyone.

I'm having a bit of a brain freeze over how to tell Weewx what units 
(metric or US) to expect when importing a temperature figure from a text 
file.
My set up uses Weewx version 3.9.2 running under Python2 (setup.py install 
method) on a Raspberry Pi 4, OS is Raspian Buster (Debian 10)

I have two data sources at the moment:
The main weather station is an Aercus Instruments Weathersleuth which is 
basically a fine offset observer. That uses the Intercepter plugin 
/home/weewx/bin/user/interceptor.py
I also have two extra sensors feeding from another pi on the network using 
the One Wire (OWFS) plugin /home/weewx/bin/user/owfs.py - these are mapped 
as extraTemp1 & 2 and report as Greenhouse and Garage temperatures.

As far as I'm aware all of those report the temperature as metric when 
polled by weewx and I don't recall having to modify anything.

What I want to do is map a third, extraTemp3, to data from a Temper USB 
temperature sensor I've got in the cupboard where the Raspberry Pi sits 
(the one running Weewx) 

All well and good, i've installed a python application which when called 
will report the temperature from the Temper.

> temper-poll

Found 1 devices

Device #0: 39.7°C 103.4°F

I'm sure I can write a bash script to run temper-poll, strip out unwanted 
data, and overwrite the result to a file in /tmp/ (such as cupboard.txt) - 
once happy I'll set up a cron for the script and then a service in 
/home/weewx/bin/user as per the 
example: https://github.com/weewx/weewx/wiki/add-sensor  - modifying as 
needed.

As per notes within weewx.conf [StdConvert] has always remained as US units.

What I can't figure out is how Weeex knows whether the incoming data, from 
any of the sensors across the system, are metric or US? is it specified 
within the service(s) themselves?
I notice further down in the example of adding an extra sensor::

That is, whatever unit system you use in pond.txt, must match the unit 
system used by the incoming record. The unit system used by the incoming 
record will be given by event.record['usUnits']

Does that mean I need to add the above to my new service?

In short:
Both Interceptor and Owfs are presenting temperature data in degrees C, but 
the Weewx [stdConvert] is untouched from default (US)
My reports are in metric, but of course that's just the reports. I could 
change it at any time without affecting the database or the incoming sensor 
data to Weewx.
Do I need to do anything to my new service in /weewx/bin/user/ to specify 
that the data is metric or US depending on what value gets presented from 
/tmp/cupboard.txt ?

I'm reluctant to just try it as I don't want incorrect data, even though 
this is just so I an easily see the temperature of the cupboard where my 
main "server" raspberry pi, router, network switch and a few other bits of 
kit reside. Ignore the alarmingly high temp as the stick is currently 
plugged directly into the pi and its a hot day here - a USB extension cable 
will give a more accurate reading of the ambient temp.

Thanks for any help and guidance and of course apologies in advance if it's 
in the instructions (I did try a search - honest!)

Regards

Ashley


-- 
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/20ca2276-ca92-4d98-aa20-9d0cc78114d9o%40googlegroups.com.

[weewx-user] howto receive MQTT data from a running broker and put the data into database with weewx..?

['Christian Peters' via weewx-user]

Hi,

I ran a weewx 3.9. station with Python 2 and a seperate weewx instance with 
the wxMesh.py driver. 
This works very nice (as far as the broker isn't down or the connection 
breaks - then a restart of the weewx instance which holds the wxMesh driver 
is needed...!). 
As I now switch to Python 3 and weewx 4.x I figured out that the wxMesh.py 
driver isn't Python 3 ready? :-( 

How can I catch MQTT data into the weewx database from an external broker 
ilocated n my home lan?

Is this the right extension to use:

https://github.com/bellrichm/WeeWX-MQTTSubscribe 
? 

What I don't understand: if I will use it as a sevice, in which database 
will it put my values? 
Is there a mapping needed!? Can I use a seperate database? 
Is there a configuration example available or does anybody set up such a 
station and could provide the config or give me some advice 
howto get the data form the MQTT broker into weewx and the database to show 
the values and graphs!?
That would be great!

Thanks in advance!

Regards,

Christian 

-- 
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/3f984aba-be57-419e-9334-fde2e668a7fdo%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Pat]

Interesting. Would one of you guys be able to share you database with me so 
I have test data to use? We haven't had rain in a long time so this would 
be easier to figure out where my math is going wrong. 

On Wednesday, June 24, 2020 at 8:33:33 AM UTC-4, Manfred Maier wrote:
>
> Good catch, Didier!
> I just found that I get the same wrong behavior for my 2019 chart. My 
> station started in July only. And the RainTotal chart shows values for 
> Jan-June.
> It's the second one from the bottom: 
> https://www.wetter-zorneding.de/graphs/?graph=2019
>
>
> didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 14:13:12 UTC+2:
>
>> Please find enclosed:
>> week.jpg graphic
>> month.jpg graphic
>> year.jpg graphic
>> graphs.conf file
>>
>> Le mer. 24 juin 2020 à 13:50, Pat  a écrit :
>>
>>> Please paste your full graph that's broken so I can take a look at 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/2669f288-4099-45af-88e7-5382397bf5b9o%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/7e0b6c3a-d767-47b2-bfd8-f8b054d38879o%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Manfred Maier]

Good catch, Didier!
I just found that I get the same wrong behavior for my 2019 chart. My 
station started in July only. And the RainTotal chart shows values for 
Jan-June.
It's the second one from the 
bottom: https://www.wetter-zorneding.de/graphs/?graph=2019


didier@gmail.com schrieb am Mittwoch, 24. Juni 2020 um 14:13:12 UTC+2:

> Please find enclosed:
> week.jpg graphic
> month.jpg graphic
> year.jpg graphic
> graphs.conf file
>
> Le mer. 24 juin 2020 à 13:50, Pat  a écrit :
>
>> Please paste your full graph that's broken so I can take a look at 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2669f288-4099-45af-88e7-5382397bf5b9o%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/7cdf3ede-4d39-43e5-8277-1353df7d4b88n%40googlegroups.com.

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[John Burricelli]

Also, has anyone been able to run the driver manually?  I get this error 
when I try it that way.

$ PYTHONPATH=bin python /usr/share/weewx/user/interceptor.py 
--device=ecowitt --mode=listen --port=8000
Traceback (most recent call last):
  File "/usr/share/weewx/user/interceptor.py", line 302, in 
import weewx.drivers
ImportError: No module named weewx.drivers


On Wednesday, June 24, 2020 at 7:51:03 AM UTC-4, John Burricelli wrote:

 

> I had a decent storm come through last night with nearly 50 reported 
> lightning strikes via my ecowitt app.  As far as i can tell however nothing 
> is being inserted into the database.
>
> INSERT INTO archive_day_lightning_energy 
> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
> INSERT INTO archive_day_lightning_energy 
> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
> CREATE TABLE archive_day_lightning_noise_count (dateTime INTEGER NOT NULL 
> UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, 
> sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> INSERT INTO archive_day_lightning_noise_count 
> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
> INSERT INTO archive_day_lightning_noise_count 
> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
> CREATE TABLE archive_day_lightning_strike_count (dateTime INTEGER NOT NULL 
> UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, 
> sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> INSERT INTO archive_day_lightning_strike_count 
> VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
> INSERT INTO archive_day_lightning_strike_count 
> VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
>
> On Wednesday, June 24, 2020 at 12:46:53 AM UTC-4, Gert Andersen wrote:
>>
>> Hi Oliver
>>
>> I'm using your patched script and it's working fine.
>>
>> I insert these fields into th database:
>>
>> [[sensor_map_extensions]]
>> lightning_strike_count = lightning_num
>> lightning_distance = lightning
>>
>> These 2 fields are also coming from the sensor:
>>
>> lightning_time
>> wh57batt
>>
>> But can't be mapped right now as far as I can see. There are other 
>> lightning types in the extended scheme, but they don't fit with these.
>>
>> It could also be very nice, to implement the PASSKEY functionality.
>>
>> Gert
>>
>> On Tuesday, June 23, 2020 at 9:51:37 PM UTC+2, olicat wrote:
>>>
>>> Hi!
>>>
>>> Are there any experiences with the adjusted script regarding lightning?
>>> Does it work for you now?
>>>
>>> Regards, Oliver
>>>
>>>

-- 
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/3ef581aa-d4cc-4797-be50-1943f2ffd316o%40googlegroups.com.

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[John Burricelli]

I had a decent storm come through last night with nearly 50 reported 
lightning strikes via my ecowitt app.  As far as i can tell however nothing 
is being inserted into the database.

INSERT INTO archive_day_lightning_energy 
VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
INSERT INTO archive_day_lightning_energy 
VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
CREATE TABLE archive_day_lightning_noise_count (dateTime INTEGER NOT NULL 
UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, 
sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
INSERT INTO archive_day_lightning_noise_count 
VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
INSERT INTO archive_day_lightning_noise_count 
VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
CREATE TABLE archive_day_lightning_strike_count (dateTime INTEGER NOT NULL 
UNIQUE PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, 
sum REAL, count INTEGER, wsum REAL, sumtime INTEGER);
INSERT INTO archive_day_lightning_strike_count 
VALUES(1592884800,NULL,NULL,NULL,NULL,0.0,0,0.0,0);
INSERT INTO archive_day_lightning_strike_count 
VALUES(1592971200,NULL,NULL,NULL,NULL,0.0,0,0.0,0);

On Wednesday, June 24, 2020 at 12:46:53 AM UTC-4, Gert Andersen wrote:
>
> Hi Oliver
>
> I'm using your patched script and it's working fine.
>
> I insert these fields into th database:
>
> [[sensor_map_extensions]]
> lightning_strike_count = lightning_num
> lightning_distance = lightning
>
> These 2 fields are also coming from the sensor:
>
> lightning_time
> wh57batt
>
> But can't be mapped right now as far as I can see. There are other 
> lightning types in the extended scheme, but they don't fit with these.
>
> It could also be very nice, to implement the PASSKEY functionality.
>
> Gert
>
> On Tuesday, June 23, 2020 at 9:51:37 PM UTC+2, olicat wrote:
>>
>> Hi!
>>
>> Are there any experiences with the adjusted script regarding lightning?
>> Does it work for you now?
>>
>> Regards, Oliver
>>
>>

-- 
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/ec7f1305-012d-4e0b-8d15-47e488cc111co%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Pat]

Please paste your full graph that's broken so I can take a look at 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/2669f288-4099-45af-88e7-5382397bf5b9o%40googlegroups.com.

[weewx-user] Belchertown skin: Reload index_hooks

[Manfred Maier]

Hi Pat,
there might be a possible issue with the reload functionality of the 
additional index_hook section on the front-page of the skin.

I have the following settings in the weewx.conf

reload_hook_images = 1

reload_images_radar = 300

reload_images_hook_asi = 300

reload_images_hook_af = -1

reload_images_hook_as = -1

reload_images_hook_ac = 300


Still, the index_hook_after_station_info doesn't reload.

Is there anything wrong with this functionality or did I make a mistake in 
setting up the index_hook (which is much more likely)?

Manfred

-- 
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/28f41b9d-2597-41ea-8ca4-80ea27060a1fn%40googlegroups.com.