[weewx-user] Re: My WH24 wind cup stops moving

2021-05-23 Thread stefa...@gmail.com
It looks like you'll need an Allen key and a small Phillips screwdriver. 
Check out this link: 
Instructions for Replacing the Anemometer 



On Sunday, 23 May 2021 at 02:37:52 UTC-4 bth...@gmail.com wrote:

> The wind cup stops moving. Is there any way to fix it? Thanks
>
> What kind of screw for the wind cup? I can't find a suitable screwdriver.

-- 
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/2d931e65-7159-400d-a6bf-301543002c3en%40googlegroups.com.


Re: [weewx-user] Re: My WH24 wind cup stops moving

2021-05-23 Thread bthoven
Thank you.

On Sun, 23 May 2021, 20:27 stefa...@gmail.com,  wrote:

> It looks like you'll need an Allen key and a small Phillips screwdriver.
> Check out this link:
> Instructions for Replacing the Anemometer
> 
>
>
> On Sunday, 23 May 2021 at 02:37:52 UTC-4 bth...@gmail.com wrote:
>
>> The wind cup stops moving. Is there any way to fix it? Thanks
>>
>> What kind of screw for the wind cup? I can't find a suitable screwdriver.
>
> --
> 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/4jerqbGvj1E/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/2d931e65-7159-400d-a6bf-301543002c3en%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/CAMQ4M75Vv%2BHB0KKuPD2Uy4h5nJGC4AcMRnYZ7KuD%3D-V3uvDJDg%40mail.gmail.com.


[weewx-user] Re: Lightning Data Stored in weewx.sdb

2021-05-23 Thread Eric K
I am seeing a weird problem with the lightning distance value, where the 
distance gets stuck reporting 10!

I copied the [[Corrections]] scheme shown earlier in this thread.  
I'm pretty sure I got it right, because it works most of the time.

##

[SDR]
# This section is for the software-defined radio driver.
# collect data from Acurite Atlas sensor

# The driver to use
driver = user.sdr
cmd = rtl_433 -R 40 -M utc -F json

[[sensor_map]]
outTemp = temperature.0011.AcuriteAtlasPacket
outHumidity = humidity.0011.AcuriteAtlasPacket
windSpeed = wind_speed.0011.AcuriteAtlasPacket
windDir = wind_dir.0011.AcuriteAtlasPacket
UV = uv.0011.AcuriteAtlasPacket
luminosity = lux.0011.AcuriteAtlasPacket
Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
lightning_distance = strike_distance.0011.AcuriteAtlasPacket
windBatteryStatus = battery.0011.AcuriteAtlasPacket

[[deltas]]
rain = Atlas_rain_total
lightning_strike_count = Atlas_strike_count

[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None

##

But, I've now seen several storms with lightning and and the 
lightinig_distance value gets stuck reporting 10 forever after!
I see the 10 repeating in the database, so I believe that weewx is 
generating that number and sending it into the database.

Here's a look in the database using DB Browser for SQLite.  
Note how a distance value of 5.64705882352941 from the Acurite Atlas 
appears and then it's 10 thereafter.
You can see the lightning_strike_count is zero.  
The "else None" part of the condition statement appears to stop working?

[image: ksnip_20210523-32.png]

On Thursday, July 23, 2020 at 5:55:55 AM UTC-5 tarob...@gmail.com wrote:

> Thank you for the detailed explanation Gary! I have added the 
>> [Accumulator] section to my weewx.conf for lightning_strike_count -> 
>> extractor = sum and lightning_distance -> extractor = min. Now to wait for 
>> another storm.
>
>
> -Troy 
>

-- 
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/74c16b1a-a35c-4f3d-b630-c31d965900fen%40googlegroups.com.


[weewx-user] Re: Lightning Data Stored in weewx.sdb

2021-05-23 Thread Eric K
Here's a relevant section of the log which shows the Acurite Atlas 
lightning sensor sending the last distance (10) reading over and over.  
This is expected Acurite Atlas behavior, and the reason we have to put the 
"if > 0 else None" statement in our [[Corrections]] section.

Referring back to the 5.64705882352941 value seen in my database:
I wonder if weewx isn't expecting a decimal reading to be in 
lightning_distance?
And that sends it into confusion?

May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: lines=['{"time" 
: "2021-05-23 15:56:20", "model" : "Acurite-Atlas", "id" : 17, "channel" : 
"A", "sequence_num" : 0, "battery_ok" : 1, "message_type" : 38, 
"wind_avg_mi_h" : 4.000, "wind_dir_deg" : 190.000, "rain_in" : 2.040, 
"strike_count" : 45, "strike_distance" : 10, "exception" : 0, "raw_msg" : 
"c011668205f9cc8baab8"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
"Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 1, 
"battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
"wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
"strike_distance" : 10, "exception" : 0, "raw_msg" : 
"c411668205f9cc8baabc"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
"Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 2, 
"battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
"wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
"strike_distance" : 10, "exception" : 0, "raw_msg" : 
"c811668205f9cc8baac0"}\n']
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
'dateTime': 1621785380, 'usUnits': 1}
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
(Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
'dateTime': 1621785380, 'usUnits': 1}
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
(Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
'dateTime': 1621785380, 'usUnits': 1}
May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
(Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
May 23 10:56:27 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: lines=[]
May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
(Service) MessageCallbackProvider data-> incoming topic: 
tele/BMP280/SENSOR, QOS: 0, retain: 0, payload: 
b'{"Time":"2021-05-23T10:56:30","BMP280":{"Temperature":20.2,"Pressure":985.1},"PressureUnit":"hPa","TempUnit":"C"}'
May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
(Service) TopicManager data-> incoming tele/BMP280/SENSOR: appTemp1: 20.2, 
barometer: 985.1


On Sunday, May 23, 2021 at 11:19:26 AM UTC-5 Eric K wrote:

> I am seeing a weird problem with the lightning distance value, where the 
> distance gets stuck reporting 10!
>
> I copied the [[Corrections]] scheme shown earlier in this thread.  
> I'm pretty sure I got it right, because it works most of the time.
>
>
> ##
>
> [SDR]
> # This section is for the software-defined radio driver.
> # collect data from Acurite Atlas sensor
> 
> # The driver to use
> driver = user.sdr
> cmd = rtl_433 -R 40 -M utc -F json
> 
> [[sensor_map]]
> outTemp = temperature.0011.AcuriteAtlasPacket
> outHumidity = humidity.0011.AcuriteAtlasPacket
> windSpeed = wind_speed.0011.AcuriteAtlasPacket
> windDir = wind_dir.0011.AcuriteAtlasPacket
> UV = uv.0011.AcuriteAtlasPacket
> luminosity = lux.0011.AcuriteAtlasPacket
> Atlas_rain_total = rain_total.0011.AcuriteAtlasPacket
> Atlas_strike_count = strike_count.0011.AcuriteAtlasPacket
> lightning_distance = strike_distance.0011.AcuriteAtlasPacket
> windBatteryStatus = batte

Re: [weewx-user] Re: Volunteer translators needed!

2021-05-23 Thread Karen K
This is the german translation of the Standard skin.

There is a problem. "at" translates to "um", if it is a time, but "at" 
translates to "am" if it is a date. If it is date and time together, it 
depends what comes first. 

Examples:
17,5°C um 14:48:49
29,2°C am 10.05.2021 (um) 16:23:35 ("um" is optional there)

tke...@gmail.com schrieb am Donnerstag, 20. Mai 2021 um 15:24:15 UTC+2:

> Thanks. However, I already have a French translation. 
>
> Would you be willing to do the translation for the Standard skin? It is 
> attached.
>
> On Wed, May 19, 2021 at 3:18 PM Lo LL  wrote:
>
>> Hope it helps.
>> Au revoir.
>>
>> Le mardi 18 mai 2021 à 18:41:21 UTC+2, Vetti52 a écrit :
>>
>>> I did some tracing back. Now I think, that the history report stanza in 
>>> skin.conf was introduced by the alltime module. Not sure yet. The beaufort 
>>> texts might be a result of a copy/paste action from a source, I found 
>>> somewhere here in the forum, ages ago
>>> BTW, in index.html.tmpl, where the history report belongs to, the part >> id="history_widget" class="widget"> needs translations also, which seem 
>>> not to be covered by the en.conf file. But maybe, this was another place, 
>>> where the alltime module introduced some text.
>>> Somewhen I started to translate everything into German, that I found to 
>>> be presented as text on the web site. I found it in weewx.conf, 
>>> index.html.tmpl,  skin.conf, all forecast and alltime related files. I did 
>>> not look at where these labels came from in original. Anyway, now I know 
>>> about them, in case updates will mess up with my translations. 
>>>
>>> But you have a good source for your de.conf file already. So there is no 
>>> need that I contribute that part.
>>> tke...@gmail.com schrieb am Dienstag, 18. Mai 2021 um 16:48:02 UTC+2:
>>>
 Thanks.

 Where does [HistoryReport] come from? It's not part of anything in 
 WeeWX that I can tell.

 Same with the Beaufort texts.

 And, I agree, converting a skin is a right pain. 

 On Tue, May 18, 2021 at 7:38 AM Vetti52  wrote:

> I found an entry in skin.conf missing in en.conf:
> For German:
> [HistoryReport]
> monthnames = Jan, Feb, Mar, Apr, Mai, Jun, Jul, Aug, Sep, Okt, 
> Nov, Dez
>
> and some translations for Beaufort as text version would also be 
> helpful. 
> Here is my german version, used in current.inc:
> #if $varExists('day.windSpeed') and $current.windSpeed.raw is not None
>   #if $current.windSpeed.beaufort.raw == 0
> #set $word_current_beaufort = 'Windstille'
>   #elif $current.windSpeed.beaufort.raw == 1
> #set $word_current_beaufort = 'Leiser Zug'
>   #elif $current.windSpeed.beaufort.raw  == 2
> #set $word_current_beaufort = 'Leichte Brise'
>   #elif $current.windSpeed.beaufort.raw == 3
> #set $word_current_beaufort = 'Schwache Brise'
>   #elif $current.windSpeed.beaufort.raw == 4
> #set $word_current_beaufort = 'Mäßige Brise'
>   #elif $current.windSpeed.beaufort.raw == 5
> #set $word_current_beaufort = 'Frische Brise'
>   #elif $current.windSpeed.beaufort.raw == 6
> #set $word_current_beaufort = 'Starker Wind'
>   #elif $current.windSpeed.beaufort.raw == 7
> #set $word_current_beaufort = 'Steifer Wind'
>   #elif $current.windSpeed.beaufort.raw == 8
> #set $word_current_beaufort = 'Stürmischer Wind'
>   #elif $current.windSpeed.beaufort.raw == 9
> #set $word_current_beaufort = 'Sturm'
>   #elif $current.windSpeed.beaufort.raw == 10
> #set $word_current_beaufort = 'Schwerer Sturm'
>   #elif $current.windSpeed.beaufort.raw == 11
> #set $word_current_beaufort = 'Orkanartiger Sturm'
>   #elif $current.windSpeed.beaufort.raw == 12
> #set $word_current_beaufort = 'Orkan'
>   #else
> #set $word_current_beaufort = 'N/A'
>   #end if
>
> And, well, the modules, I have in use, alltime seasons and forecast, 
> which have their own extra labelling text built in, are always a pain to 
> keep them uptodate with seasons skin. Adopting all kind of those modules 
> to 
> the new version might be laborious and take some time. Sigh...
>
>
>
> tke...@gmail.com schrieb am Sonntag, 16. Mai 2021 um 03:16:15 UTC+2:
>
>> Thank you for the Greek translations!
>>
>> While it would be nice, maintaining native language instructions is 
>> way beyond the capabilities of this all-volunteer project!
>>
>> On Sat, May 15, 2021 at 3:03 PM Δημήτρης Βήχος  
>> wrote:
>>
>>> i think greek users , need greek instructions  , german users need 
>>> german instructions etc. with this thought , my instructions in 
>>> github are in greek. 
>>> however this is my greek translate in en.conf . 
>>>
>>> Στις Σάββατο, 15 Μαΐου 2021 στις 11:10:16 μ.μ. UTC+3, ο χρήστης 
>>> kk44...@gmail.c

[weewx-user] Re: Lightning Data Stored in weewx.sdb

2021-05-23 Thread gjr80
I think you might find the [[Corrections]] stanza belongs under 
[StdCalibrate]  rather 
than the SDR driver.

Gary
On Monday, 24 May 2021 at 02:32:14 UTC+10 Eric K wrote:

> Here's a relevant section of the log which shows the Acurite Atlas 
> lightning sensor sending the last distance (10) reading over and over.  
> This is expected Acurite Atlas behavior, and the reason we have to put the 
> "if > 0 else None" statement in our [[Corrections]] section.
>
> Referring back to the 5.64705882352941 value seen in my database:
> I wonder if weewx isn't expecting a decimal reading to be in 
> lightning_distance?
> And that sends it into confusion?
>
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
> lines=['{"time" : "2021-05-23 15:56:20", "model" : "Acurite-Atlas", "id" : 
> 17, "channel" : "A", "sequence_num" : 0, "battery_ok" : 1, "message_type" : 
> 38, "wind_avg_mi_h" : 4.000, "wind_dir_deg" : 190.000, "rain_in" : 2.040, 
> "strike_count" : 45, "strike_distance" : 10, "exception" : 0, "raw_msg" : 
> "c011668205f9cc8baab8"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
> "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 1, 
> "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
> "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
> "strike_distance" : 10, "exception" : 0, "raw_msg" : 
> "c411668205f9cc8baabc"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
> "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 2, 
> "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
> "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
> "strike_distance" : 10, "exception" : 0, "raw_msg" : 
> "c811668205f9cc8baac0"}\n']
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
> 'dateTime': 1621785380, 'usUnits': 1}
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
> 'dateTime': 1621785380, 'usUnits': 1}
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
> 'dateTime': 1621785380, 'usUnits': 1}
> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
> May 23 10:56:27 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: lines=[]
> May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
> (Service) MessageCallbackProvider data-> incoming topic: 
> tele/BMP280/SENSOR, QOS: 0, retain: 0, payload: 
> b'{"Time":"2021-05-23T10:56:30","BMP280":{"Temperature":20.2,"Pressure":985.1},"PressureUnit":"hPa","TempUnit":"C"}'
> May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
> (Service) TopicManager data-> incoming tele/BMP280/SENSOR: appTemp1: 20.2, 
> barometer: 985.1
>
>
> On Sunday, May 23, 2021 at 11:19:26 AM UTC-5 Eric K wrote:
>
>> I am seeing a weird problem with the lightning distance value, where the 
>> distance gets stuck reporting 10!
>>
>> I copied the [[Corrections]] scheme shown earlier in this thread.  
>> I'm pretty sure I got it right, because it works most of the time.
>>
>>
>> ##
>>
>> [SDR]
>> # This section is for the software-defined radio driver.
>> # collect data from Acurite Atlas sensor
>> 
>> # The driver to use
>> driver = user.sdr
>> cmd = rtl_433 -R 40 -M utc -F json
>> 
>> [[sensor_map]]
>> outTemp = temperature.0011.AcuriteAtlasPacket
>> outHumidity = humidity.0011.AcuriteAtlasPacket
>> windSpeed = wind_speed.0011.AcuriteAtlasPacket
>> win

[weewx-user] Help getting Tempest setup with Weewx on Pi running Debian

2021-05-23 Thread Cookie
Hello 

Apologies it has been twenty years since I have used Unix so these may be 
dumb questions.

I have successfully installed the Weewx software onto my PI using Debian 
Ver 10. Using the SUDO command brings back memories! 

Can anyone recommend a stable driver for the Tempest? I have tried this one 
https://github.com/captain-coredump/weatherflow-udp. And not much luck. I 
am assuming that you put the IP address in weatherflow-udp.py in the usr 
file. I have added it there and it times out. I can't find anywhere to put 
the IP address in the weewx.conf file. Perhaps I am putting it in the wrong 
area? If someone could tell me what driver and what line that would be of 
help.

I would rather pull the data from the Tempest API but could not find a 
driver. 

Any help appreciated. I have burned about 5 hours on this today. 

Essentially I am trying to get my Tempest to connect directly to CWOP. I 
know Tempest already pushed to CWOP through its API. I desire to have this 
eventually publish to a website that my son can utilise for a project that 
he is working on that would pull the data from CWOP.

Many 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/6be07df6-770c-423b-9c59-69485ca6c904n%40googlegroups.com.


[weewx-user] Re: Lightning Data Stored in weewx.sdb

2021-05-23 Thread Eric K
Thanks for the pointer.  
I also had a [[Corrections]] sections under [StdCalibrate].

I just moved the lightning_distance correction to the [StdCalibrate] 
section.
We'll see if that helps.

Isn't it odd that it worked, when the lightning_distance was something 
other than 10?


On Sunday, May 23, 2021 at 3:10:54 PM UTC-5 gjr80 wrote:

> I think you might find the [[Corrections]] stanza belongs under 
> [StdCalibrate]  rather 
> than the SDR driver.
>
> Gary
> On Monday, 24 May 2021 at 02:32:14 UTC+10 Eric K wrote:
>
>> Here's a relevant section of the log which shows the Acurite Atlas 
>> lightning sensor sending the last distance (10) reading over and over.  
>> This is expected Acurite Atlas behavior, and the reason we have to put 
>> the "if > 0 else None" statement in our [[Corrections]] section.
>>
>> Referring back to the 5.64705882352941 value seen in my database:
>> I wonder if weewx isn't expecting a decimal reading to be in 
>> lightning_distance?
>> And that sends it into confusion?
>>
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
>> lines=['{"time" : "2021-05-23 15:56:20", "model" : "Acurite-Atlas", "id" : 
>> 17, "channel" : "A", "sequence_num" : 0, "battery_ok" : 1, "message_type" : 
>> 38, "wind_avg_mi_h" : 4.000, "wind_dir_deg" : 190.000, "rain_in" : 2.040, 
>> "strike_count" : 45, "strike_distance" : 10, "exception" : 0, "raw_msg" : 
>> "c011668205f9cc8baab8"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
>> "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 1, 
>> "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
>> "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
>> "strike_distance" : 10, "exception" : 0, "raw_msg" : 
>> "c411668205f9cc8baabc"}\n', '{"time" : "2021-05-23 15:56:20", "model" : 
>> "Acurite-Atlas", "id" : 17, "channel" : "A", "sequence_num" : 2, 
>> "battery_ok" : 1, "message_type" : 38, "wind_avg_mi_h" : 4.000, 
>> "wind_dir_deg" : 190.000, "rain_in" : 2.040, "strike_count" : 45, 
>> "strike_distance" : 10, "exception" : 0, "raw_msg" : 
>> "c811668205f9cc8baac0"}\n']
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
>> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
>> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
>> 'dateTime': 1621785380, 'usUnits': 1}
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
>> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
>> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
>> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
>> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
>> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
>> 'dateTime': 1621785380, 'usUnits': 1}
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
>> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
>> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
>> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: 
>> packet={'windSpeed': 4.0, 'windDir': 190.0, 'Atlas_rain_total': 2.04, 
>> 'Atlas_strike_count': 45, 'lightning_distance': 10, 'windBatteryStatus': 0, 
>> 'dateTime': 1621785380, 'usUnits': 1}
>> May 23 10:56:24 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>> (Service) data-> final packet is 2021-05-23 10:56:20 CDT (1621785380): 
>> Atlas_rain_total: 2.04, Atlas_strike_count: 45, dateTime: 1621785380, 
>> lightning_distance: 10, lightning_strike_count: 0, rain: 0.0, usUnits: 1, 
>> windBatteryStatus: 0, windDir: 190.0, windSpeed: 4.0
>> May 23 10:56:27 Ubuntu20-WEEWX weewx[14069] DEBUG user.sdr: lines=[]
>> May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>> (Service) MessageCallbackProvider data-> incoming topic: 
>> tele/BMP280/SENSOR, QOS: 0, retain: 0, payload: 
>> b'{"Time":"2021-05-23T10:56:30","BMP280":{"Temperature":20.2,"Pressure":985.1},"PressureUnit":"hPa","TempUnit":"C"}'
>> May 23 10:56:29 Ubuntu20-WEEWX weewx[14069] DEBUG user.MQTTSubscribe: 
>> (Service) TopicManager data-> incoming tele/BMP280/SENSOR: appTemp1: 20.2, 
>> barometer: 985.1
>>
>>
>> On Sunday, May 23, 2021 at 11:19:26 AM UTC-5 Eric K wrote:
>>
>>> I am seeing a weird problem with the lightning distance value, where the 
>>> distance gets stuck reporting 10!
>>>
>>> I copied the [[Corrections]] scheme shown earlier in this thread.  
>>> I'm pretty sure I got it right, because it works most of the time.
>>>
>>>
>>> ##
>>>
>>> [SDR]
>

[weewx-user] Re: Help getting Tempest setup with Weewx on Pi running Debian

2021-05-23 Thread mbat...@gmail.com
I'm using https://github.com/jjvdgeer/weatherflow-udp


On Sunday, May 23, 2021 at 4:27:25 PM UTC-5 corey...@gmail.com wrote:

> Hello 
>
> Apologies it has been twenty years since I have used Unix so these may be 
> dumb questions.
>
> I have successfully installed the Weewx software onto my PI using Debian 
> Ver 10. Using the SUDO command brings back memories! 
>
> Can anyone recommend a stable driver for the Tempest? I have tried this 
> one https://github.com/captain-coredump/weatherflow-udp. And not much 
> luck. I am assuming that you put the IP address in weatherflow-udp.py in 
> the usr file. I have added it there and it times out. I can't find anywhere 
> to put the IP address in the weewx.conf file. Perhaps I am putting it in 
> the wrong area? If someone could tell me what driver and what line that 
> would be of help.
>
> I would rather pull the data from the Tempest API but could not find a 
> driver. 
>
> Any help appreciated. I have burned about 5 hours on this today. 
>
> Essentially I am trying to get my Tempest to connect directly to CWOP. I 
> know Tempest already pushed to CWOP through its API. I desire to have this 
> eventually publish to a website that my son can utilise for a project that 
> he is working on that would pull the data from CWOP.
>
> Many 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/66a88432-fd53-4898-97a5-f53a7ec52a61n%40googlegroups.com.


[weewx-user] Re: Help getting Tempest setup with Weewx on Pi running Debian

2021-05-23 Thread vince
There are many threads here on this as well as in the Weatherflow forums, 
with working examples people (including me) have posted many times.

The docs for the driver 
at https://github.com/captain-coredump/weatherflow-udp have an example 
weewx.conf snippet for the original Air+Sky WeatherFlow station.   You want 
to replace the sensor_map section with the Tempest example that is 
at 
https://github.com/captain-coredump/weatherflow-udp/blob/master/sample_Tempest_sensor_map.

You need to edit those examples to use 'your' Tempest serial number which 
will be of a format similar to the example of ST-0025

-- 
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/4009b611-5864-42c8-bf21-2cf4f810f7dbn%40googlegroups.com.


Re: [weewx-user] Re: Volunteer translators needed!

2021-05-23 Thread Tom Keffer
Thanks, Karen.

On Sun, May 23, 2021 at 11:52 AM Karen K  wrote:

> This is the german translation of the Standard skin.
>
> There is a problem. "at" translates to "um", if it is a time, but "at"
> translates to "am" if it is a date. If it is date and time together, it
> depends what comes first.
>
> Examples:
> 17,5°C um 14:48:49
> 29,2°C am 10.05.2021 (um) 16:23:35 ("um" is optional there)
>
> tke...@gmail.com schrieb am Donnerstag, 20. Mai 2021 um 15:24:15 UTC+2:
>
>> Thanks. However, I already have a French translation.
>>
>> Would you be willing to do the translation for the Standard skin? It is
>> attached.
>>
>> On Wed, May 19, 2021 at 3:18 PM Lo LL  wrote:
>>
>>> Hope it helps.
>>> Au revoir.
>>>
>>> Le mardi 18 mai 2021 à 18:41:21 UTC+2, Vetti52 a écrit :
>>>
 I did some tracing back. Now I think, that the history report stanza in
 skin.conf was introduced by the alltime module. Not sure yet. The beaufort
 texts might be a result of a copy/paste action from a source, I found
 somewhere here in the forum, ages ago
 BTW, in index.html.tmpl, where the history report belongs to, the part >>> id="history_widget" class="widget"> needs translations also, which
 seem not to be covered by the en.conf file. But maybe, this was another
 place, where the alltime module introduced some text.
 Somewhen I started to translate everything into German, that I found to
 be presented as text on the web site. I found it in weewx.conf,
 index.html.tmpl,  skin.conf, all forecast and alltime related files. I did
 not look at where these labels came from in original. Anyway, now I know
 about them, in case updates will mess up with my translations.

 But you have a good source for your de.conf file already. So there is
 no need that I contribute that part.
 tke...@gmail.com schrieb am Dienstag, 18. Mai 2021 um 16:48:02 UTC+2:

> Thanks.
>
> Where does [HistoryReport] come from? It's not part of anything in
> WeeWX that I can tell.
>
> Same with the Beaufort texts.
>
> And, I agree, converting a skin is a right pain.
>
> On Tue, May 18, 2021 at 7:38 AM Vetti52  wrote:
>
>> I found an entry in skin.conf missing in en.conf:
>> For German:
>> [HistoryReport]
>> monthnames = Jan, Feb, Mar, Apr, Mai, Jun, Jul, Aug, Sep, Okt,
>> Nov, Dez
>>
>> and some translations for Beaufort as text version would also be
>> helpful.
>> Here is my german version, used in current.inc:
>> #if $varExists('day.windSpeed') and $current.windSpeed.raw is not None
>>   #if $current.windSpeed.beaufort.raw == 0
>> #set $word_current_beaufort = 'Windstille'
>>   #elif $current.windSpeed.beaufort.raw == 1
>> #set $word_current_beaufort = 'Leiser Zug'
>>   #elif $current.windSpeed.beaufort.raw  == 2
>> #set $word_current_beaufort = 'Leichte Brise'
>>   #elif $current.windSpeed.beaufort.raw == 3
>> #set $word_current_beaufort = 'Schwache Brise'
>>   #elif $current.windSpeed.beaufort.raw == 4
>> #set $word_current_beaufort = 'Mäßige Brise'
>>   #elif $current.windSpeed.beaufort.raw == 5
>> #set $word_current_beaufort = 'Frische Brise'
>>   #elif $current.windSpeed.beaufort.raw == 6
>> #set $word_current_beaufort = 'Starker Wind'
>>   #elif $current.windSpeed.beaufort.raw == 7
>> #set $word_current_beaufort = 'Steifer Wind'
>>   #elif $current.windSpeed.beaufort.raw == 8
>> #set $word_current_beaufort = 'Stürmischer Wind'
>>   #elif $current.windSpeed.beaufort.raw == 9
>> #set $word_current_beaufort = 'Sturm'
>>   #elif $current.windSpeed.beaufort.raw == 10
>> #set $word_current_beaufort = 'Schwerer Sturm'
>>   #elif $current.windSpeed.beaufort.raw == 11
>> #set $word_current_beaufort = 'Orkanartiger Sturm'
>>   #elif $current.windSpeed.beaufort.raw == 12
>> #set $word_current_beaufort = 'Orkan'
>>   #else
>> #set $word_current_beaufort = 'N/A'
>>   #end if
>>
>> And, well, the modules, I have in use, alltime seasons and forecast,
>> which have their own extra labelling text built in, are always a pain to
>> keep them uptodate with seasons skin. Adopting all kind of those modules 
>> to
>> the new version might be laborious and take some time. Sigh...
>>
>>
>>
>> tke...@gmail.com schrieb am Sonntag, 16. Mai 2021 um 03:16:15 UTC+2:
>>
>>> Thank you for the Greek translations!
>>>
>>> While it would be nice, maintaining native language instructions is
>>> way beyond the capabilities of this all-volunteer project!
>>>
>>> On Sat, May 15, 2021 at 3:03 PM Δημήτρης Βήχος 
>>> wrote:
>>>
 i think greek users , need greek instructions  , german users need
 german instructions etc. with this thought , my instructions in
 github are in greek.
>>

Re: [weewx-user] Re: Help getting Tempest setup with Weewx on Pi running Debian

2021-05-23 Thread Cookie
Thanks. I didn’f pick up on that nuisance and will give a try.

Mobile: +44 (0) 7738 843 740
Email: co...@coreycook.com

From: weewx-user@googlegroups.com  on behalf of 
vince 
Sent: Monday, May 24, 2021 12:20:10 AM
To: weewx-user 
Subject: [weewx-user] Re: Help getting Tempest setup with Weewx on Pi running 
Debian

There are many threads here on this as well as in the Weatherflow forums, with 
working examples people (including me) have posted many times.

The docs for the driver at https://github.com/captain-coredump/weatherflow-udp 
have an example weewx.conf snippet for the original Air+Sky WeatherFlow 
station.   You want to replace the sensor_map section with the Tempest example 
that is at 
https://github.com/captain-coredump/weatherflow-udp/blob/master/sample_Tempest_sensor_map.

You need to edit those examples to use 'your' Tempest serial number which will 
be of a format similar to the example of ST-0025


--
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/XPK1BCZZkNI/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/4009b611-5864-42c8-bf21-2cf4f810f7dbn%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/LO4P123MB53357EDF2832EA59250A1724F6269%40LO4P123MB5335.GBRP123.PROD.OUTLOOK.COM.