[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

Good morning!
You can use these instructions to add appTemp to your database:
https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database

Just make sure you really have a backup of your database stored.

geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 07:43:08 UTC+2:

> There are errors, a test with $current.appTemp and once with appTemp.
> The appTemp field is not in the database, how can I modify my database?
>
>
> Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:
>
>> Good question. If appTemp doesn't exist in the database, then I would 
>> have thought the entry would be empty or given an error in the syslog. Any 
>> errors?
>>
>>
>> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>>
>>> Ok. I've just seen that appTemp is not part of the standard installation 
>>> of weewx. I've added it later to the database.
>>>
>>> @Pat: In your index.html.tmpl it looks like your are displaying 
>>> $current.appTemp for the "Feels like" temperature. What is used when 
>>> appTemp does not exist in the database? Or is appTemp calculated by weewx 
>>> anyway, but if there isn't a field in the database it's just not stored and 
>>> can't be used for the charts?
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
>>> UTC+2:
>>>
 if appTemp instead of windchill, graphics no longer work


 Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>
> appTemp is best translated with "Gefühlte Temperatur".
>
> I would have to look it up in the weewx code, but I think it's 
> calculated based on temperature, humidity and wind.
> appTemp can be higher or lower than the temperature.
>
> Windchill is normally (always?) lower than the temperature. It's 
> therefore primarily used in winter. At least in the German news I only 
> hear 
> about it in winter.
>
> Heat Index is the opposite. It's normally (always?) higher than the 
> temperature. It useful in the summer.
>
> Other people might want to add or correct me here!
>
> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
> Temperature" in Germany (and hopefully also in Switzerland).
> Have you tried to put appTemp in your chart? Does the value correspond 
> to the other value on your page?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
> UTC+2:
>
>> what is appTemp?
>> windchill corresponds to 'feels like'?
>>
>>
>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>>
>>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>>> figure at the top.
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>> 17:16:32 UTC+2:
>>>
 in graphs.inc is  [[[windchill]]]


 Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>
> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
> "appTemp"?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
> 16:43:53 UTC+2:
>
>> MQTT ist not activ.
>>
>>
>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>
>>> Hi Geni,
>>> do you have MQTT switched on?
>>>
>>> If so, the station observations (top area) display the live 
>>> data. The charts display the temperature of the last archive loop 
>>> (= couple 
>>> of minutes old).
>>>
>>> Manfred
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>> 15:42:15 UTC+2:
>>>
 Why is there a different temperature displayed?

>>>

-- 
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/2cbf5e32-3c3e-4819-abba-306411146754n%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[geni08...@gmail.com]

 There are errors, a test with $current.appTemp and once with appTemp.
The appTemp field is not in the database, how can I modify my database?


Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:

> Good question. If appTemp doesn't exist in the database, then I would have 
> thought the entry would be empty or given an error in the syslog. Any 
> errors?
>
>
> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>
>> Ok. I've just seen that appTemp is not part of the standard installation 
>> of weewx. I've added it later to the database.
>>
>> @Pat: In your index.html.tmpl it looks like your are displaying 
>> $current.appTemp for the "Feels like" temperature. What is used when 
>> appTemp does not exist in the database? Or is appTemp calculated by weewx 
>> anyway, but if there isn't a field in the database it's just not stored and 
>> can't be used for the charts?
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
>> UTC+2:
>>
>>> if appTemp instead of windchill, graphics no longer work
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:

 appTemp is best translated with "Gefühlte Temperatur".

 I would have to look it up in the weewx code, but I think it's 
 calculated based on temperature, humidity and wind.
 appTemp can be higher or lower than the temperature.

 Windchill is normally (always?) lower than the temperature. It's 
 therefore primarily used in winter. At least in the German news I only 
 hear 
 about it in winter.

 Heat Index is the opposite. It's normally (always?) higher than the 
 temperature. It useful in the summer.

 Other people might want to add or correct me here!

 As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
 Temperature" in Germany (and hopefully also in Switzerland).
 Have you tried to put appTemp in your chart? Does the value correspond 
 to the other value on your page?

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
 UTC+2:

> what is appTemp?
> windchill corresponds to 'feels like'?
>
>
> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>
>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>> figure at the top.
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
>> UTC+2:
>>
>>> in graphs.inc is  [[[windchill]]]
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:

 Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
 "appTemp"?

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
 16:43:53 UTC+2:

> MQTT ist not activ.
>
>
> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>
>> Hi Geni,
>> do you have MQTT switched on?
>>
>> If so, the station observations (top area) display the live data. 
>> The charts display the temperature of the last archive loop (= 
>> couple of 
>> minutes old).
>>
>> Manfred
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>> 15:42:15 UTC+2:
>>
>>> Why is there a different temperature displayed?
>>>
>>

-- 
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/d127a121-7e1e-4160-a865-3bb9c2a60290n%40googlegroups.com.
Jun 26 07:30:28 Wetter-Raspi weewx[12838] INFO user.belchertown: version 1.1
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'user.belchertown.HighchartsJsonGenerator'
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: 
  Error trying to use database binding wx_binding to graph observation 
appTemp. Error was: appTemp.
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: 
File "/usr/share/weewx/user/belchertown.py", line 1825, in 
get_observation_data
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: 
  (time_start_vt, time_stop_vt, obs_vt) = 
archive.getSqlVectors(TimeSpan(start_ts, end_ts), obs_lookup, aggregate_type, 
aggregate_interval)
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/manager.py", line 452, in getSqlVectors
Jun 26 07:30:37 Wetter-Raspi weewx[12838] ERROR 

[weewx-user] Re: Weewx fails to start

['Ron Walker' via weewx-user]

Thanks for your reply.  The weather station consists of an arduino 
microcontroller reading sensors and sending data to the pi, which places it 
in a CSV file.  I'm using fileparse in weewx to read the file.  You were 
correct in your assessment!  I looked through the CSV file and found 
entries with a 'nan' value for my second temperature sensor, which was 
bad!  Replacing the sensor resolved the issue.

For future reference, what information should I include in a post like this?

Thanks again!


On Thursday, June 25, 2020 at 4:53:39 PM UTC-4, Ron Walker wrote:
>
> Hi All,
>
> I am using weewx 3.9.1 on a Raspberry pi.  Up until yesterday, the system 
> was running fine.  I had stopped the pi yesterday to move it to a new 
> location.  Today when I attempted to start the program, I get the following 
> error and then it quits.  Any help pointing me in the right direction to a 
> resolution would be greatly appreciated!
>
> Error output:.
>
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 890, in main
> engine.run()
>   File "/usr/share/weewx/weewx/engine.py", line 191, in run
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> callback(event)
>   File "/usr/share/weewx/weewx/engine.py", line 546, in new_loop_packet
> self.accumulator.addRecord(event.packet, add_hilo=self.loop_hilo)
>   File "/usr/share/weewx/weewx/accum.py", line 256, in addRecord
> func(self, record, obs_type, add_hilo, weight)
>   File "/usr/share/weewx/weewx/accum.py", line 315, in add_value
> self[obs_type].addSum(val, weight=weight)
>   File "/usr/share/weewx/weewx/accum.py", line 93, in addSum
> raise ValueError("accum: ScalarStats.addSum expected float or int, got 
> %s" % val)
> ValueError: accum: ScalarStats.addSum expected float or int, got nan
>
>
> Thanks in advance!! 
>

-- 
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/6eab7637-65be-4971-b0a2-19bead2b98fao%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[rich T]

Take a look @ https://github.com/poblabs/weewx-belchertown

https://belchertownweather.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/7b8864dc-f56f-40df-9ea7-e3f6d3049bb9o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I should add, the gauges at https://www.paloaltoweather.com/LiveSeasonsGauges 
do not use my extension.  They use Gary Roderick’s:
https://github.com/gjr80/weewx-realtime_gauge-data

Gary’s extension was the inspiration behind the loopdata extension.  loopdata 
simply lets one pick and choose the observations and target any report.

> On Jun 25, 2020, at 5:51 PM, John Kline  wrote:
> 
> 
> BTW, I have the following screen up on two tablets in my house.  It’s great 
> for checking how fast the wind is currently blowing or how hard it’s 
> currently raining.
> 
> https://www.paloaltoweather.com/weatherboard/
> 
>>> On Jun 25, 2020, at 5:32 PM, Richard Zimmerman  wrote:
>>> 
>> 
>> Thanks John.  I see how your web site updates every couple seconds.  That's 
>> fantastic!  I'll dig into the extension
>> -- 
>> 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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%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/D9D3C425-3790-41F3-9012-1C87BEFA1529%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

BTW, I have the following screen up on two tablets in my house.  It’s great for 
checking how fast the wind is currently blowing or how hard it’s currently 
raining.

https://www.paloaltoweather.com/weatherboard/

> On Jun 25, 2020, at 5:32 PM, Richard Zimmerman  wrote:
> 
> 
> Thanks John.  I see how your web site updates every couple seconds.  That's 
> fantastic!  I'll dig into the extension
> -- 
> 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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%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/FD7807F2-94ED-4F04-8B40-7780093BD7D4%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Richard Zimmerman]

Thanks John.  I see how your web site updates every couple seconds.  That's 
fantastic!  I'll dig into the extension

-- 
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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I have an extension you could try:
https://github.com/chaunceygardiner/weewx-loopdata

I use it to update many pages on my site (https://www.paloaltoweather.com/), 
including current conditions at.

It’s relatively simple to install.  You specify the report to target (e.g., 
SeasonsReport), and it will do the proper conversions to match the report and 
write a file of items you pick on every loop cycle.

Cheers,
John

> On Jun 25, 2020, at 5:12 PM, Richard Zimmerman  wrote:
> 
> 
> I hate to post this here as it's likely a simple question, but I've been 
> unable to find an answer from searching.  I'm brand new to weewx having used 
> wview for over a decade.  So I have the generic setup and a Davis Vantage 
> Pro2.  My archive interval is 300s.  Is there a way to have certain data on 
> the web page update more frequently than every 5 minutes?  I'm especially 
> interested in the "Current Conditions" section as I'll frequently bring up 
> the page after feeling a strong gust to see what the speed was, but I have to 
> wait 5 minutes before the page updates.
> 
> I figure I could change the archive interval in the main config file, but I 
> don't really know what changing it to something different than on the console 
> would do.  Furthermore, the graphs don't really have to update more 
> frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
> way to have those data update on LOOP packets rather than ARCHIVE?
> 
> 
> -- 
> 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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%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/8E859B9C-86D4-4429-B08B-2B6D6FF74E6D%40johnkline.com.

[weewx-user] Update interval less than 300 seconds?

[Richard Zimmerman]

I hate to post this here as it's likely a simple question, but I've been 
unable to find an answer from searching.  I'm brand new to weewx having 
used wview for over a decade.  So I have the generic setup and a Davis 
Vantage Pro2.  My archive interval is 300s.  Is there a way to have certain 
data on the web page update more frequently than every 5 minutes?  I'm 
especially interested in the "Current Conditions" section as I'll 
frequently bring up the page after feeling a strong gust to see what the 
speed was, but I have to wait 5 minutes before the page updates.

I figure I could change the archive interval in the main config file, but I 
don't really know what changing it to something different than on the 
console would do.  Furthermore, the graphs don't really have to update more 
frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
way to have those data update on LOOP packets rather than ARCHIVE?


-- 
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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%40googlegroups.com.

[weewx-user] Re: calculate rainRate for second rain gauge...?

[gjr80]

Hi,

As you have found adding hailRate to [StdWXCalculate] [[Calculations]] does 
nothing as StdWXCalculate does not know how to calculate hailRate. It was 
not specifically raised to address this issue but issue #491 
, if it continues down the path 
it is presently on, will likely see StdWXCalculate evolve such that the 
user will be able to define their own rate based derived observations (just 
like rainRate) via a few config lines in weewx.conf. If you can hang on 
until (hopefully) the next WeeWX point release you should see this feature 
added (provided I can get it past Tom and provided the next point release 
does not come out too soon :) ). Since your hailRate observation would be a 
derived one, and given that wee_database now has the ability to backfill 
derived observations, the delay should not see you miss any data.

If you really do want to implement your derived hailRate now you would need 
to modify the current StdWXCalculate behaviour or write a separate service 
to calculate hailRate.

Gary

On Friday, 26 June 2020 05:04:21 UTC+10, Christian Peters wrote:
>
> Hi, 
>
> I read form a second rain gauge via filpile rain values/data into the data 
> base value 'hail', as there is no second rain1, rain2...
> As it is in the same group as rain all should be fine. 
> It works if I query 
> $day.hail.sum
> it works.
>
> But if I query 
> $current.hailRate
> I got N/A. It's not provided by the gauge an I think i has to be 
> calculated by software.
>
> I tried that to get the hailRate:
>
> [StdWXCalculate]
> 
> [[Calculations]]
> # How to calculate derived quantities.  Possible values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> hailRate = software
>
> but it seems not implemented!? Any chance to get the calculation of 
> rainRate (hailRate) for my second gauge by software calculation working!? 
>
>
> Thanks in advance.
>
> 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/21c7d8ba-112c-456d-91f2-5b99e5563417o%40googlegroups.com.

Re: [weewx-user] Weewx fails to start

[Tom Keffer]

You're not giving us a lot of information about your system.

In Python, a 'nan' ("not a number") is not returned by any function unless
one of the inputs to the function is a nan. That means one of your sensors
probably emitted a 'nan', either directly as a value (unlikely), or by
emitting a string with the literal characters 'nan'.

But, again, it's impossible to say anything without knowing more about your
system.

I will add one thing: V4.x includes a protection against ingesting nans.
Good reason to upgrade.

-tk



On Thu, Jun 25, 2020 at 1:53 PM 'Ron Walker' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi All,
>
> I am using weewx 3.9.1 on a Raspberry pi.  Up until yesterday, the system
> was running fine.  I had stopped the pi yesterday to move it to a new
> location.  Today when I attempted to start the program, I get the following
> error and then it quits.  Any help pointing me in the right direction to a
> resolution would be greatly appreciated!
>
> Error output:
>
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 890, in main
> engine.run()
>   File "/usr/share/weewx/weewx/engine.py", line 191, in run
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> callback(event)
>   File "/usr/share/weewx/weewx/engine.py", line 546, in new_loop_packet
> self.accumulator.addRecord(event.packet, add_hilo=self.loop_hilo)
>   File "/usr/share/weewx/weewx/accum.py", line 256, in addRecord
> func(self, record, obs_type, add_hilo, weight)
>   File "/usr/share/weewx/weewx/accum.py", line 315, in add_value
> self[obs_type].addSum(val, weight=weight)
>   File "/usr/share/weewx/weewx/accum.py", line 93, in addSum
> raise ValueError("accum: ScalarStats.addSum expected float or int, got
> %s" % val)
> ValueError: accum: ScalarStats.addSum expected float or int, got nan
>
>
> Thanks in advance!!
>
> --
> 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/3da3a69c-7e1a-4a86-ae97-6b86adc7f028o%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/CAPq0zEA_yr0OGZqpd3yZ25ZRf6xwz8FLMTaLAfHcjWFTdDPWdg%40mail.gmail.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[gjr80]

Just to clarify, as of v3.7.0 tag $current will pull data from the record 
included in the NEW_ARCHIVE_RECORD event rather than querying the database for 
the last record. This means, for example, you can use $current.appTemp in a 
report without actually having field appTemp in the database (provided appTemp 
is being calculated and added to the archive record by a service such as 
StdWXCalculate). Of course, you cannot plot appTemp without including appTemp 
in the database as you need those historical records.

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/97470bbd-e9e8-4242-b55a-f79d73a79ad4o%40googlegroups.com.

[weewx-user] Weewx fails to start

['Ron Walker' via weewx-user]

Hi All,

I am using weewx 3.9.1 on a Raspberry pi.  Up until yesterday, the system 
was running fine.  I had stopped the pi yesterday to move it to a new 
location.  Today when I attempted to start the program, I get the following 
error and then it quits.  Any help pointing me in the right direction to a 
resolution would be greatly appreciated!

Error output:

Traceback (most recent call last):
  File "/usr/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/usr/share/weewx/weewx/engine.py", line 890, in main
engine.run()
  File "/usr/share/weewx/weewx/engine.py", line 191, in run
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
callback(event)
  File "/usr/share/weewx/weewx/engine.py", line 546, in new_loop_packet
self.accumulator.addRecord(event.packet, add_hilo=self.loop_hilo)
  File "/usr/share/weewx/weewx/accum.py", line 256, in addRecord
func(self, record, obs_type, add_hilo, weight)
  File "/usr/share/weewx/weewx/accum.py", line 315, in add_value
self[obs_type].addSum(val, weight=weight)
  File "/usr/share/weewx/weewx/accum.py", line 93, in addSum
raise ValueError("accum: ScalarStats.addSum expected float or int, got 
%s" % val)
ValueError: accum: ScalarStats.addSum expected float or int, got nan


Thanks in advance!! 

-- 
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/3da3a69c-7e1a-4a86-ae97-6b86adc7f028o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Pat]

Good question. If appTemp doesn't exist in the database, then I would have 
thought the entry would be empty or given an error in the syslog. Any 
errors?

On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>
> Ok. I've just seen that appTemp is not part of the standard installation 
> of weewx. I've added it later to the database.
>
> @Pat: In your index.html.tmpl it looks like your are displaying 
> $current.appTemp for the "Feels like" temperature. What is used when 
> appTemp does not exist in the database? Or is appTemp calculated by weewx 
> anyway, but if there isn't a field in the database it's just not stored and 
> can't be used for the charts?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
> UTC+2:
>
>> if appTemp instead of windchill, graphics no longer work
>>
>>
>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>>
>>> appTemp is best translated with "Gefühlte Temperatur".
>>>
>>> I would have to look it up in the weewx code, but I think it's 
>>> calculated based on temperature, humidity and wind.
>>> appTemp can be higher or lower than the temperature.
>>>
>>> Windchill is normally (always?) lower than the temperature. It's 
>>> therefore primarily used in winter. At least in the German news I only hear 
>>> about it in winter.
>>>
>>> Heat Index is the opposite. It's normally (always?) higher than the 
>>> temperature. It useful in the summer.
>>>
>>> Other people might want to add or correct me here!
>>>
>>> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
>>> Temperature" in Germany (and hopefully also in Switzerland).
>>> Have you tried to put appTemp in your chart? Does the value correspond 
>>> to the other value on your page?
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
>>> UTC+2:
>>>
 what is appTemp?
 windchill corresponds to 'feels like'?


 Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>
> Try to change it to [[[appTemp]]]. It then should correspond to the 
> figure at the top.
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
> UTC+2:
>
>> in graphs.inc is  [[[windchill]]]
>>
>>
>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>>
>>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>>> "appTemp"?
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>> 16:43:53 UTC+2:
>>>
 MQTT ist not activ.


 Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>
> Hi Geni,
> do you have MQTT switched on?
>
> If so, the station observations (top area) display the live data. 
> The charts display the temperature of the last archive loop (= couple 
> of 
> minutes old).
>
> Manfred
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
> 15:42:15 UTC+2:
>
>> Why is there a different temperature displayed?
>>
>

-- 
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/e846d98e-d9b7-48c6-970e-db7b2bfffe30o%40googlegroups.com.

[weewx-user] calculate rainRate for second rain gauge...?

['Christian Peters' via weewx-user]

Hi, 

I read form a second rain gauge via filpile rain values/data into the data 
base value 'hail', as there is no second rain1, rain2...
As it is in the same group as rain all should be fine. 
It works if I query 
$day.hail.sum
it works.

But if I query 
$current.hailRate
I got N/A. It's not provided by the gauge an I think i has to be calculated 
by software.

I tried that to get the hailRate:

[StdWXCalculate]

[[Calculations]]
# How to calculate derived quantities.  Possible values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

hailRate = software

but it seems not implemented!? Any chance to get the calculation of 
rainRate (hailRate) for my second gauge by software calculation working!? 


Thanks in advance.

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/510b-7c00-4f97-bcd4-e327342ba60ao%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

Ok. I've just seen that appTemp is not part of the standard installation of 
weewx. I've added it later to the database.

@Pat: In your index.html.tmpl it looks like your are displaying 
$current.appTemp for the "Feels like" temperature. What is used when 
appTemp does not exist in the database? Or is appTemp calculated by weewx 
anyway, but if there isn't a field in the database it's just not stored and 
can't be used for the charts?

geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 UTC+2:

> if appTemp instead of windchill, graphics no longer work
>
>
> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>
>> appTemp is best translated with "Gefühlte Temperatur".
>>
>> I would have to look it up in the weewx code, but I think it's calculated 
>> based on temperature, humidity and wind.
>> appTemp can be higher or lower than the temperature.
>>
>> Windchill is normally (always?) lower than the temperature. It's 
>> therefore primarily used in winter. At least in the German news I only hear 
>> about it in winter.
>>
>> Heat Index is the opposite. It's normally (always?) higher than the 
>> temperature. It useful in the summer.
>>
>> Other people might want to add or correct me here!
>>
>> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
>> Temperature" in Germany (and hopefully also in Switzerland).
>> Have you tried to put appTemp in your chart? Does the value correspond to 
>> the other value on your page?
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
>> UTC+2:
>>
>>> what is appTemp?
>>> windchill corresponds to 'feels like'?
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:

 Try to change it to [[[appTemp]]]. It then should correspond to the 
 figure at the top.

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
 UTC+2:

> in graphs.inc is  [[[windchill]]]
>
>
> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>
>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>> "appTemp"?
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
>> UTC+2:
>>
>>> MQTT ist not activ.
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:

 Hi Geni,
 do you have MQTT switched on?

 If so, the station observations (top area) display the live data. 
 The charts display the temperature of the last archive loop (= couple 
 of 
 minutes old).

 Manfred

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
 15:42:15 UTC+2:

> Why is there a different temperature displayed?
>


-- 
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/535406cd-365b-41c1-8c1b-4afb5ebdd5bcn%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

if appTemp instead of windchill, graphics no longer work

Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>
> appTemp is best translated with "Gefühlte Temperatur".
>
> I would have to look it up in the weewx code, but I think it's calculated 
> based on temperature, humidity and wind.
> appTemp can be higher or lower than the temperature.
>
> Windchill is normally (always?) lower than the temperature. It's therefore 
> primarily used in winter. At least in the German news I only hear about it 
> in winter.
>
> Heat Index is the opposite. It's normally (always?) higher than the 
> temperature. It useful in the summer.
>
> Other people might want to add or correct me here!
>
> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
> Temperature" in Germany (and hopefully also in Switzerland).
> Have you tried to put appTemp in your chart? Does the value correspond to 
> the other value on your page?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
> UTC+2:
>
>> what is appTemp?
>> windchill corresponds to 'feels like'?
>>
>>
>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>>
>>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>>> figure at the top.
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
>>> UTC+2:
>>>
 in graphs.inc is  [[[windchill]]]


 Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>
> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
> "appTemp"?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
> UTC+2:
>
>> MQTT ist not activ.
>>
>>
>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>
>>> Hi Geni,
>>> do you have MQTT switched on?
>>>
>>> If so, the station observations (top area) display the live data. 
>>> The charts display the temperature of the last archive loop (= couple 
>>> of 
>>> minutes old).
>>>
>>> Manfred
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>> 15:42:15 UTC+2:
>>>
 Why is there a different temperature displayed?

>>>

-- 
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/2df4e6f4-95fe-4849-b74c-f09d308808f0o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

appTemp is best translated with "Gefühlte Temperatur".

I would have to look it up in the weewx code, but I think it's calculated 
based on temperature, humidity and wind.
appTemp can be higher or lower than the temperature.

Windchill is normally (always?) lower than the temperature. It's therefore 
primarily used in winter. At least in the German news I only hear about it 
in winter.

Heat Index is the opposite. It's normally (always?) higher than the 
temperature. It useful in the summer.

Other people might want to add or correct me here!

As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
Temperature" in Germany (and hopefully also in Switzerland).
Have you tried to put appTemp in your chart? Does the value correspond to 
the other value on your page?

geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 UTC+2:

> what is appTemp?
> windchill corresponds to 'feels like'?
>
>
> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>
>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>> figure at the top.
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
>> UTC+2:
>>
>>> in graphs.inc is  [[[windchill]]]
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:

 Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
 "appTemp"?

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
 UTC+2:

> MQTT ist not activ.
>
>
> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>
>> Hi Geni,
>> do you have MQTT switched on?
>>
>> If so, the station observations (top area) display the live data. The 
>> charts display the temperature of the last archive loop (= couple of 
>> minutes old).
>>
>> Manfred
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
>> UTC+2:
>>
>>> Why is there a different temperature displayed?
>>>
>>

-- 
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/ab7bde57-3489-4fc4-8238-b8c8839a6123n%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

what is appTemp?
windchill corresponds to 'feels like'?


Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>
> Try to change it to [[[appTemp]]]. It then should correspond to the figure 
> at the top.
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
> UTC+2:
>
>> in graphs.inc is  [[[windchill]]]
>>
>>
>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>>
>>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>>> "appTemp"?
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
>>> UTC+2:
>>>
 MQTT ist not activ.


 Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>
> Hi Geni,
> do you have MQTT switched on?
>
> If so, the station observations (top area) display the live data. The 
> charts display the temperature of the last archive loop (= couple of 
> minutes old).
>
> Manfred
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
> UTC+2:
>
>> Why is there a different temperature displayed?
>>
>

-- 
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/399fe36b-7987-4d1c-b7ed-8ace3fb07c31o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[vince]

On Thursday, June 25, 2020 at 8:16:32 AM UTC-7, Geni 0815 wrote:
>
> in graphs.inc is  [[[windchill]]]
>
>
>
One item is wind chill (sometimes called 'feels like'), the other is 
outside temperature.
They are usually different if you have any wind.

-- 
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/d09d4e90-ff9a-4c91-82ae-137de2fbb957o%40googlegroups.com.

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

[Troy Roberts]

I tried filling in the "must_have" sections with "inTemp" and it still 
didn't work.

On Thursday, June 25, 2020 at 7:41:40 AM UTC-4, Gazza wrote:
>
>
> I have just added this sensor to my test system and noticed that the 
> bme280wx extension was updated a few weeks ago to be python3 compatible 
> though I am still running python2.
>
> Mine seems to be working fine, I have an SDR station with extra Onewire 
> sensors and now the BME280 pressure sensor.
>
> The barometer graph and the current conditions text is getting data but I 
> had to edit the skins.conf to add inTemp and inHumidity back in to graphs 
> as I had removed those item as they were not being used.
>
> The only other thing I had to change was the i2c address of my BME280 
> module, it was set to 0x77.
>
> [Bme280wx]  # Options for extension for BME280 
> pressure/temperature/humidity sensor
>
> temperature_must_have = ""
> humidityKeys = inHumidity
> pressureKeys = pressure
> pressure_must_have = outTemp
> i2c_port = 1
> humidity_must_have = ""
> i2c_address = 0x77
> usUnits = US
> temperatureKeys = inTemp
>
>
>
> Another 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/7d07aa53-95b9-498e-b917-b6b5de6f1638o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

Try to change it to [[[appTemp]]]. It then should correspond to the figure 
at the top.

geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 UTC+2:

> in graphs.inc is  [[[windchill]]]
>
>
> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>
>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>> "appTemp"?
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
>> UTC+2:
>>
>>> MQTT ist not activ.
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:

 Hi Geni,
 do you have MQTT switched on?

 If so, the station observations (top area) display the live data. The 
 charts display the temperature of the last archive loop (= couple of 
 minutes old).

 Manfred

 geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
 UTC+2:

> Why is there a different temperature displayed?
>


-- 
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/153a05a9-003b-408f-a0aa-2d454db0f0fen%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

in graphs.inc is  [[[windchill]]]

Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>
> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
> "appTemp"?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
> UTC+2:
>
>> MQTT ist not activ.
>>
>>
>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>
>>> Hi Geni,
>>> do you have MQTT switched on?
>>>
>>> If so, the station observations (top area) display the live data. The 
>>> charts display the temperature of the last archive loop (= couple of 
>>> minutes old).
>>>
>>> Manfred
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
>>> UTC+2:
>>>
 Why is there a different temperature displayed?

>>>

-- 
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/0d62de32-015f-4014-8067-70b1b739b351o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
"appTemp"?

geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 UTC+2:

> MQTT ist not activ.
>
>
> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>
>> Hi Geni,
>> do you have MQTT switched on?
>>
>> If so, the station observations (top area) display the live data. The 
>> charts display the temperature of the last archive loop (= couple of 
>> minutes old).
>>
>> Manfred
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
>> UTC+2:
>>
>>> Why is there a different temperature displayed?
>>>
>>

-- 
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/4a13b415-9e5e-4d8d-a3d1-eaa480b960a5n%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

MQTT ist not activ.

Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>
> Hi Geni,
> do you have MQTT switched on?
>
> If so, the station observations (top area) display the live data. The 
> charts display the temperature of the last archive loop (= couple of 
> minutes old).
>
> Manfred
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
> UTC+2:
>
>> Why is there a different temperature displayed?
>>
>

-- 
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/f9382978-ad3b-4b79-b06a-d749926ee6d4o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Manfred Maier]

Hi Geni,
do you have MQTT switched on?

If so, the station observations (top area) display the live data. The 
charts display the temperature of the last archive loop (= couple of 
minutes old).

Manfred

geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 UTC+2:

> Why is there a different temperature displayed?
>

-- 
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/8a13fa81-aa5b-48e7-b025-6d3b6f433c35n%40googlegroups.com.

[weewx-user] Belchertown Difference for the same temperature type

[Geni 0815]

Why is there a different temperature displayed?

-- 
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/d13ff833-c555-42ec-af4a-06907cef5f00o%40googlegroups.com.

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

[gjr80]

Hi,

There is one simple rule when adding/altering fields in a loop 
packet/archive record; always take note of the unit system used by the 
packet/record. Loop packets are emitted by the driver using a unit system 
of the drivers choice, it does not matter what unit system is used and it 
need bear no resemblance to the unit system used in the database or in any 
reports (the StdConvert service takes care of converting packets/records to 
the unit system used by the database and there are mechanisms within the 
StdReport service for converting to whatever display units the user wishes 
to use). If a WeeWX service wants to add a field to the loop packet that 
service should check the unit system used in the packet and then convert 
the data to be added to the appropriate units before adding the data to the 
packet. In some cases it does not matter (eg humidity, radiation, direction 
all use the same units across all unit systems) but obviously it matters 
for temperatures, speeds, pressures etc. You can certainly have your 
external source provide temperatures in C if your driver is emitting 
temperatures in C but what happens if you get a new station/driver that 
emits F? Such a chnage would result in your C data being treated as if it 
was in F.

So back to your system. The service that you write will need to do a number 
of things. First it needs to read your data and know what units are being 
used (units could be hard coded in your service or read from the external 
source - its your source so you control it). Then you need to check the 
unit system used in the record you are augmenting and convert your data to 
the units used in the record. Finally you add the converted data to the 
record. Using the example you linked your code might look something like 
(untested):

import syslog
import weewx
import weewx.units
from weewx.wxengine import StdService

class PondService(StdService):
def __init__(self, engine, config_dict):
super(PondService, self).__init__(engine, config_dict)  
d = config_dict.get('PondService', {})
self.filename = d.get('filename', '/var/tmp/pond.txt')
syslog.syslog(syslog.LOG_INFO, "pond: using %s" % self.filename)
self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_file)

def read_file(self, event):
try:
with open(self.filename) as f:
value = f.read()
value = float(value)
syslog.syslog(syslog.LOG_DEBUG, "pond: found value of %s" % 
value)
except Exception as e:
syslog.syslog(syslog.LOG_ERR, "pond: cannot read value: %s" % e)
else
value_vt = weewx.units.ValueTuple(value, 'degree_C', 
'group_temperature')
conv_value_vt = weewx.units.convertStd(value_vt, event.record[
'usUnits'])
event.record['extraTemp1'] = conv_value_vt.value

I have highlighted the changes in yellow. Firstly we import weewx.units as 
we are going ot use some of the unit conversion functions that reside in 
the WeeWX units module. The changed use of float() lets us make use of the 
existing try..except to catch the error that would occur if the data read 
cannot be converted to a number. The code indented under 'else' is executed 
if the try..except does not encounter an error, in other words the data is 
read and successfully converted to a number. Looking at the 'else' code in 
detail, first we express the imported data as a ValueTuple, this is a three 
element tuple that defines a value, its units and the unit group it belongs 
to. This is necessary to use the WeeWX unit conversion functions. In this 
case we know our imported data is in C and is a temperature. We then call 
the convertStd function to convert that ValueTuple into the units used by 
that particualr unit group in that particular packet. There may be no 
conversion needed, but we know now that irrespective of the unit system 
used in event.record, conv_value_vt contains our imported data in the same 
temperature units used in event.record. So we can just simply add the value 
to the record.

Hopefully that gives you some hints on a way ahead.

Gary

On Wednesday, 24 June 2020 23:03:19 UTC+10, Ashley Hinton wrote:
>
> 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.

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

[Gazza]

Just a quick followup, this thread was also about a similar issue about 
missing data: https://groups.google.com/forum/#!topic/weewx-user/MycfgX74P1Y

The solution is to not leave the "*_must_have = " line blank, it needs to 
have a value.

I have added outTemp to both lines and now the additional temperature and 
humidity data is showing up.


The other 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/9d227307-f1dc-40f2-b488-0db663e82f33o%40googlegroups.com.

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

[Gazza]

I have just added this sensor to my test system and noticed that the 
bme280wx extension was updated a few weeks ago to be python3 compatible 
though I am still running python2.

Mine seems to be working fine, I have an SDR station with extra Onewire 
sensors and now the BME280 pressure sensor.

The barometer graph and the current conditions text is getting data but I 
had to edit the skins.conf to add inTemp and inHumidity back in to graphs 
as I had removed those item as they were not being used.

The only other thing I had to change was the i2c address of my BME280 
module, it was set to 0x77.

[Bme280wx]  # Options for extension for BME280 
pressure/temperature/humidity sensor

temperature_must_have = ""
humidityKeys = inHumidity
pressureKeys = pressure
pressure_must_have = outTemp
i2c_port = 1
humidity_must_have = ""
i2c_address = 0x77
usUnits = US
temperatureKeys = inTemp



Another 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/261f08ba-1e97-4cd3-9c67-b3841b8c42c0o%40googlegroups.com.

Re: [weewx-user] Cydia pomonella

[Chuck Rhode]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 23 Jun 2020 10:46:56 -0700
Tom Keffer  wrote:

> I don't see why the new xtypes facility
> 
> can't be used to calculate your version of growing degree days. It
> allows you to define new types.

I'll pursue this.  Thanks.

- -- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 60° — Wind W 3 mph

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAl70i9oACgkQYNv8YqSjllI8eACcDmQ3yTAz5E332lvzWNwybCUv
ab4AnizLC2ju1cahhgnZ+7qVy4Oomzoe
=X3b9
-END PGP SIGNATURE-

-- 
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/20200625063450.21f61449%40quixote.LacusVeris.com.

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

[Manfred Maier]

A new installation of the entire skin fixed it.

I have no idea what went wrong with the old one. My suspicion would be that 
there was some encoding issue with a file. 

Something I noticed after the new installation:
* In the old version of the weewx.conf, I had included the DarkSky secret 
key in quotation marks
* After the re-install of the development skin, those quotation marks were 
gone
--> This caused a weird behavior: When triggering a report with wee_reports 
everything worked fine. But in the next regular report loop, the DarkSky 
forecast disappeared . With a wee_reports it came back. And disappeared 
again in the next regular reporting cycle.
* Putting back the quotation marks fixed this issue


Pat schrieb am Mittwoch, 24. Juni 2020 um 23:19:04 UTC+2:

> 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