Re: [weewx-user] Re: windRun charts?

[pannetron]

Maybe I'll punt on windrun and just look at average windspeed...

On Tuesday, June 4, 2024 at 8:42:07 AM UTC-6 pannetron wrote:

> That much I knew, and it's the easy part.  What I want help with is adding 
> windrun as, I guess, an aggregate type. I think that's core weewx. Here's 
> the relevant traceback. You can see that xtypes.get_series() failed to find 
> an aggregate type for windrun:
>
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 
> 'user.belchertown.HighchartsJsonGenerator'
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
>   Error trying to use database binding wx_binding to graph observation 
> windrun. Error was: 'windrun' or 'max'.
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
> File "/usr/share/weewx/user/belchertown.py", line 2335, in 
> get_observation_data
> Jun  4 08:05:17 pi4-3 wee_reports[25376] 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  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/manager.py", line 612, in getSqlVectors
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
>   return weewx.xtypes.get_series(obs_type, timespan, self,
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/xtypes.py", line 116, in get_series
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
>   raise weewx.UnknownType(msg)
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
>   weewx.UnknownType: 'windrun' or 'max'
> Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine:  
>
> So now I'm reading the XTypes documentation to learn how to add windrun: 
> https://github.com/weewx/weewx/wiki/xtypes
>
>
> Just add a section that looks like the others, naming it something 
> [unique] and referencing the windrun element.
>
> Something like the following (untested):
>
> [[chart123]]
> title = Wind Run
> [[[windrun]]]
>
> Pat has extensive documentation at 
> https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
>  
> with examples.
>
>

-- 
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/2be8f695-8e96-4808-aa63-856da9d0b64cn%40googlegroups.com.

Re: [weewx-user] Re: windRun charts?

[pannetron]

That much I knew, and it's the easy part.  What I want help with is adding 
windrun as, I guess, an aggregate type. I think that's core weewx. Here's 
the relevant traceback. You can see that xtypes.get_series() failed to find 
an aggregate type for windrun:

Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
  Error trying to use database binding wx_binding to graph observation 
windrun. Error was: 'windrun' or 'max'.
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
File "/usr/share/weewx/user/belchertown.py", line 2335, in 
get_observation_data
Jun  4 08:05:17 pi4-3 wee_reports[25376] 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  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/manager.py", line 612, in getSqlVectors
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
  return weewx.xtypes.get_series(obs_type, timespan, self,
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/xtypes.py", line 116, in get_series
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
  raise weewx.UnknownType(msg)
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine: 
  weewx.UnknownType: 'windrun' or 'max'
Jun  4 08:05:17 pi4-3 wee_reports[25376] ERROR weewx.reportengine:  

So now I'm reading the XTypes documentation to learn how to add 
windrun: https://github.com/weewx/weewx/wiki/xtypes


Just add a section that looks like the others, naming it something [unique] 
and referencing the windrun element.

Something like the following (untested):

[[chart123]]
title = Wind Run
[[[windrun]]]

Pat has extensive documentation at 
https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
 
with examples.

-- 
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/6c7925c1-9a60-4bee-b388-d1daf91a97ffn%40googlegroups.com.

[weewx-user] windRun charts?

[pannetron]

Where may I find references for calculating and plotting daily, monthly, 
etc. charts for windrun?  Specifically for the Belchertown skin?  My docs 
searches came up empty.

Thanks!

Russ

-- 
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/48265e45-9122-4214-82fb-a8c3bb95ed05n%40googlegroups.com.

Re: [weewx-user] Best Davis station for my buck, and purpose?

[pannetron]

Scaled Instruments is a great suggestion.  I just ordered a Davis 6312 
console, he has a few left.

On Tuesday, December 19, 2023 at 12:57:12 PM UTC-7 Nate Bargmann wrote:

> If you're intending on new, check with Scaled Instruments:
> https://www.scaledinstruments.com for pricing. It's likely he can
> assemble a package that includes the ISS and the classic 6312 console
> (the new 6313 console cannot be connected to directly by WeeWX, as I
> understand it and has a lot of issues to be resolved).
>
> You would almost certainly want a third party logger so you don't pay
> for the Davis software which you'd almost certainly never use, and the
> Davis logger that only comes with the software.
>
> - Nate
>
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
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/f757fad0-1cea-486c-8cc2-46c44230db70n%40googlegroups.com.

Re: [weewx-user] Re: Belchertown & MQTT

[pannetron]

On Thursday, July 20, 2023 at 4:29:36 AM UTC-6 Mark Fraser wrote:

On 19/07/2023 15:46, pannetron wrote: 
> 
> Yes, the "outside URL" of your MQTT broker must map to a public IP.  All 
> 192.168... IP addresses are non-routable, private IP addresses.  If you 
> don't have a permanent, public IP address, you may be able to use 
> Dynamic DNS from one of the services that offers that to register a 
> public URL that maps to whatever your Internet service provider tells 
> you to use as your public IP. 


So, I should use my hopto.org URL with the port that is for MQTT (1883)?


hopto.org looks okay but you should still use 9001 as the port to have your 
router forward MQTT requests to, 
assuming that's how you have your MQTT broker set up. The 1883 port is 
usually used to publish data to the 
broker, 9001 is used for clients subscribing to data from the broker.  The 
weewx server sends to 1883, the 
Belchertown skin pulls from port 9001.

-- 
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/e3bd2629-2100-48fd-8e85-4cd61e19796dn%40googlegroups.com.

[weewx-user] Re: Belchertown & MQTT

[pannetron]

Yes, the "outside URL" of your MQTT broker must map to a public IP.  All 
192.168... IP addresses are non-routable, private IP addresses.  If you 
don't have a permanent, public IP address, you may be able to use Dynamic 
DNS from one of the services that offers that to register a public URL that 
maps to whatever your Internet service provider tells you to use as your 
public IP.
On Wednesday, July 19, 2023 at 5:55:59 AM UTC-6 Claudio wrote:

> this must be your public ip
> mqtt_websockets_host = 192.168.2.107 
>
> Il giorno mercoledì 19 luglio 2023 alle 12:43:16 UTC+2 Mark Fraser ha 
> scritto:
>
>> I've been using the Belchertown skin with my own MQTT server for a while 
>> now and it works fine when I'm on the same network, but if I try to 
>> access it remotely it doesn't do live updates. I've also setup port 
>> forwarding on my router. 
>>
>> In weewx.conf I have, 
>> [[MQTT]] 
>> server_url = mqtt://username:pass...@192.168.2.107:1883/ 
>>  
>> topic = weather 
>> log_success = False 
>> log_failure = True 
>> unit_system = METRIC 
>> binding = archive, loop 
>> aggregation = aggregate 
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options --- 
>> mqtt_websockets_enabled = 1 
>> mqtt_websockets_host = 192.168.2.107 
>> mqtt_websockets_port = 9001 
>> mqtt_websockets_ssl = 0 
>> mqtt_websockets_topic = weather/loop 
>> # disconnect_live_website_visitor = 180 
>>
>> Do I need to add: 
>> mqtt_username = "weewxMQTTuser" 
>> mqtt_password = "weewxMQTTpass" 
>> Or is there something else I'm missing? 
>>
>

-- 
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/f59e0593-c0fd-431d-8095-4cf567c9d3e4n%40googlegroups.com.

Re: [weewx-user] Belchertown graphs stopped working

[pannetron]

I also downloaded local copies and made the changes to the Belchertown 
code.  Hopefully the Highcharts license agreements permit downloading the 
code.

On Wednesday, April 26, 2023 at 11:26:42 AM UTC-6 vince wrote:

> Thanks for the heads-up here.  I'd have never found it in the belchertown 
> issues.
>
> I tested both workarounds.  Switching to newer highcharts works yet does 
> have the font change issues.  I went with @roe-dl's original workaround in 
> the github issue to grab a local copy of the required pieces of highcharts 
> rather than relying on downloading it every time and hoping that upstream 
> doesn't break anything.
>
>

-- 
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/eaa41288-e3fb-411a-9771-7f222be20670n%40googlegroups.com.

Re: [weewx-user] Belchertown graphs stopped working

[pannetron]

Thanks for that link!!

Russ

On Wednesday, April 26, 2023 at 8:32:54 AM UTC-6 Didier Decoodt wrote:

> see https://github.com/poblabs/weewx-belchertown/issues/881
>
> Le mer. 26 avr. 2023 à 16:30, pannetron  a écrit :
>
>> Yesterday my Belchertown skin version 1.2 on weewx 4.10.2 stopped 
>> generating graphs.  With debug turned on, there are no error messages.  
>> Before yesterday everything was working perfectly for months, no recent 
>> changes on my end.  It appears that the Belchertown skin may  access some 
>> other internet resources to generate its graphs - might one of those have 
>> changed?   
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f2941161-93af-4659-9cdb-d605f958494cn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f2941161-93af-4659-9cdb-d605f958494cn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Quel temps fait-il à Auffargis <https://meteo-auffargis.decoodt.eu> ?
>

-- 
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/530a53d8-7b40-4ab2-87fe-0a9a3e81d694n%40googlegroups.com.

[weewx-user] Belchertown graphs stopped working

[pannetron]

Yesterday my Belchertown skin version 1.2 on weewx 4.10.2 stopped 
generating graphs.  With debug turned on, there are no error messages.  
Before yesterday everything was working perfectly for months, no recent 
changes on my end.  It appears that the Belchertown skin may  access some 
other internet resources to generate its graphs - might one of those have 
changed?  

-- 
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/f2941161-93af-4659-9cdb-d605f958494cn%40googlegroups.com.

Re: [weewx-user] Re: What directory are the drivers stored in? Texas Wx Intruments driver question

[pannetron]

Dale,

If you replace your /usr/share/weewx/user/twi.py with the one I emailed you 
a while back, you should be good to go.  I created a pull request to have 
my fixes incorporated into the official version, you can find my fork 
at https://github.com/pannetron/weewx-twi.  Both versions hard code the 
baud rate at 19200.  Make sure you can putty to the station at that baud 
rate.  If you're stuck on 9600, simply change the string "19200" in twi.py 
to "9600".  After copying and/or changing twi.py, I restart weewx using the 
"sudo /etc/init.d/weewx restart" method.  My corrected version of twi.py 
has been working perfectly for me for several months now.  If you're in an 
area where you experience negative outdoor temperatures, you'll also 
benefit from a bug fix for TWI firmware that I developed years ago for 
wview and ported into the weewx twi.py driver.  I poll my station every 5 
seconds vs. the default 15 so my MQTT real-time stream is updated more 
often to display more of our crazy winds.  You can see my data at 
https://panneton.net/weather.

Cheers,

Russ

On Wednesday, March 22, 2023 at 5:02:00 PM UTC-6 DR wrote:

> This is very helpful, thank you.
>
> Dale
>
>
>

-- 
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/f8f7ec1d-0838-4a14-b0b2-28bc8ba51999n%40googlegroups.com.

Re: [weewx-user] Corrections for barometric pressure from TWI station

[pannetron]

I've added and committed my proposed changes to twi.py but I can't push my 
changes in order to create a PR -- I get this error: remote: Permission to 
matthewwall/weewx-twi.git denied to <...>; fatal: unable to access 
'https://github.com/matthewwall/weewx-twi.git/': The requested URL returned 
error: 403.  Any pointers?

On Thursday, January 19, 2023 at 12:16:36 PM UTC-7 pannetron wrote:

> I've left my local twi.py reporting what the station reports as 
> "barometer".  I'm pretty sure the station actually reports a calculated 
> "altimeter" from its pressure sensor.  To review, I calibrated my console 
> to display local pressure adjusted to my altitude.  If I let the driver 
> report values as "pressure" weewx reports crazy high calculated values for 
> barometer and altimeter.When I change the twi.py -- or the simulator -- 
> to report only "altimeter", I get nothing in the barometer and pressure 
> archive records.  My weewx.conf is configure to expect "altimeter" from 
> hardware and both barometer and pressure from software.  Where should I 
> look to see why weewx is not calculating barometer and pressure from 
> altimeter?  I'm fluent in python.  I'd prefer this approach to configuring 
> the twi.py driver to insert the stations readings into "pressure" and then 
> having to put a large negative offset in weewx,conf to "correct" the 
> pressure value.  Does the calculation of barometer and pressure from 
> altimeter require some time span of altimeter values?
>
> On Monday, January 9, 2023 at 3:21:50 PM UTC-7 Jeff A. D. wrote:
>
>> Barometer uses outdoor temperature for correction.  Indoor pressure for 
>> all practical purposes is the same as outdoor pressure which is determined 
>> by the weather.
>>
>> But again, if the algorithm is the same as for the original VP, then the 
>> barometer corrections depending on temperature at high altitude are pretty 
>> meaningless, at least to me.   Maybe you would get better readings using a 
>> more consistent indoor reading, but that's not the way it's meant to work 
>> and wouldn't give true barometer readings, for whatever they're worth.  
>> Altimeter is far more meaningful in my opinion, and seems to be what 
>> stations around here use.
>>
>> On Monday, January 9, 2023 at 2:44:36 PM UTC-7 pannetron wrote:
>>
>>> Good catch.  No, the station has no input for altitude.  And I was wrong 
>>> about setting the tags in twi.py to "altitude" -- that caused issues with 
>>> the Belchertown skin I use and the value reported to PWSWeather.  I changed 
>>> the tags to "barometer" and things work okay now but I'm left unsure what 
>>> errors that may introduce into calculated station pressure and altitude 
>>> pressure values.  That's something I can live with.  Seems only a few folks 
>>> use a TWI station so maybe this is good enough as long as the hack is made 
>>> known as a caveat? 
>>>
>>> I suspect the station displays and reports "gauge pressure."  I manually 
>>> adjusted the station's barometer calibration for my altitude so the console 
>>> display is meaningful for comparisons with other stations around me and 
>>> agrees with my Kestrel 3000.  The values reported to CWOP compare very 
>>> well with neighboring stations.  Some day I may play with setting the tags 
>>> in twi.py back to "pressure" and, as others suggested, use a calibration 
>>> calculation in weewx.conf to get back to true "gauge pressure".  
>>>
>>> One of my questions remains unanswered: since the barometric sensor is 
>>> indoors, should SLP adjustments for temperature use indoor or outdoor 
>>> temperature?
>>>
>>> BTW, Tom, thanks so much for your replies and work on weeWX!!!
>>>
>>> Russ
>>>
>>> On Mon, Jan 9, 2023 at 12:55 PM Tom Keffer  wrote:
>>>
>>>> Sounds good.
>>>>
>>>> Just a reality check: if your instrument emits altimeter pressure, then 
>>>> there must be a way of setting altitude in the instrument. Hope that's 
>>>> true.
>>>>
>>>> On Mon, Jan 9, 2023 at 7:23 AM pannetron  wrote:
>>>>
>>>>> Update on a revised twi.py.  Changing the genLoopPacket "tags" from 
>>>>> "pressure" to "altimeter"  from values parsed  from the station reports 
>>>>> did 
>>>>> the trick.  After some previous changes from strings to binary strings, 
>>>>> there was a bug with how wind_d

Re: [weewx-user] Corrections for barometric pressure from TWI station

[pannetron]

I've left my local twi.py reporting what the station reports as 
"barometer".  I'm pretty sure the station actually reports a calculated 
"altimeter" from its pressure sensor.  To review, I calibrated my console 
to display local pressure adjusted to my altitude.  If I let the driver 
report values as "pressure" weewx reports crazy high calculated values for 
barometer and altimeter.When I change the twi.py -- or the simulator -- 
to report only "altimeter", I get nothing in the barometer and pressure 
archive records.  My weewx.conf is configure to expect "altimeter" from 
hardware and both barometer and pressure from software.  Where should I 
look to see why weewx is not calculating barometer and pressure from 
altimeter?  I'm fluent in python.  I'd prefer this approach to configuring 
the twi.py driver to insert the stations readings into "pressure" and then 
having to put a large negative offset in weewx,conf to "correct" the 
pressure value.  Does the calculation of barometer and pressure from 
altimeter require some time span of altimeter values?

On Monday, January 9, 2023 at 3:21:50 PM UTC-7 Jeff A. D. wrote:

> Barometer uses outdoor temperature for correction.  Indoor pressure for 
> all practical purposes is the same as outdoor pressure which is determined 
> by the weather.
>
> But again, if the algorithm is the same as for the original VP, then the 
> barometer corrections depending on temperature at high altitude are pretty 
> meaningless, at least to me.   Maybe you would get better readings using a 
> more consistent indoor reading, but that's not the way it's meant to work 
> and wouldn't give true barometer readings, for whatever they're worth.  
> Altimeter is far more meaningful in my opinion, and seems to be what 
> stations around here use.
>
> On Monday, January 9, 2023 at 2:44:36 PM UTC-7 pannetron wrote:
>
>> Good catch.  No, the station has no input for altitude.  And I was wrong 
>> about setting the tags in twi.py to "altitude" -- that caused issues with 
>> the Belchertown skin I use and the value reported to PWSWeather.  I changed 
>> the tags to "barometer" and things work okay now but I'm left unsure what 
>> errors that may introduce into calculated station pressure and altitude 
>> pressure values.  That's something I can live with.  Seems only a few folks 
>> use a TWI station so maybe this is good enough as long as the hack is made 
>> known as a caveat? 
>>
>> I suspect the station displays and reports "gauge pressure."  I manually 
>> adjusted the station's barometer calibration for my altitude so the console 
>> display is meaningful for comparisons with other stations around me and 
>> agrees with my Kestrel 3000.  The values reported to CWOP compare very 
>> well with neighboring stations.  Some day I may play with setting the tags 
>> in twi.py back to "pressure" and, as others suggested, use a calibration 
>> calculation in weewx.conf to get back to true "gauge pressure".  
>>
>> One of my questions remains unanswered: since the barometric sensor is 
>> indoors, should SLP adjustments for temperature use indoor or outdoor 
>> temperature?
>>
>> BTW, Tom, thanks so much for your replies and work on weeWX!!!
>>
>> Russ
>>
>> On Mon, Jan 9, 2023 at 12:55 PM Tom Keffer  wrote:
>>
>>> Sounds good.
>>>
>>> Just a reality check: if your instrument emits altimeter pressure, then 
>>> there must be a way of setting altitude in the instrument. Hope that's true.
>>>
>>> On Mon, Jan 9, 2023 at 7:23 AM pannetron  wrote:
>>>
>>>> Update on a revised twi.py.  Changing the genLoopPacket "tags" from 
>>>> "pressure" to "altimeter"  from values parsed  from the station reports 
>>>> did 
>>>> the trick.  After some previous changes from strings to binary strings, 
>>>> there was a bug with how wind_dir values were parsed so I fixed that, too. 
>>>>  
>>>> After a few more days of testing, I'll submit a PR.
>>>>
>>>> On Sunday, January 8, 2023 at 10:45:43 AM UTC-7 pannetron wrote:
>>>>
>>>>> On Sun, Jan 8, 2023 at 4:51 AM Tom Keffer  wrote:
>>>>>
>>>>>> It sounds like the TWI instrument is emitting "altimeter" or 
>>>>>> "barometer", but the driver is labelling it "pressure" (i.e., gauge 
>>>>>> pressure). So, weewx feels the need to "correct" it to SLP, resulting in 
>>>>>> your enormous pressures.
>>&

Re: [weewx-user] Corrections for barometric pressure from TWI station

[pannetron]

Update on a revised twi.py.  Changing the genLoopPacket "tags" from 
"pressure" to "altimeter"  from values parsed  from the station reports did 
the trick.  After some previous changes from strings to binary strings, 
there was a bug with how wind_dir values were parsed so I fixed that, too.  
After a few more days of testing, I'll submit a PR.

On Sunday, January 8, 2023 at 10:45:43 AM UTC-7 pannetron wrote:

> On Sun, Jan 8, 2023 at 4:51 AM Tom Keffer  wrote:
>
>> It sounds like the TWI instrument is emitting "altimeter" or "barometer", 
>> but the driver is labelling it "pressure" (i.e., gauge pressure). So, weewx 
>> feels the need to "correct" it to SLP, resulting in your enormous pressures.
>>
>> I would recommend filing an issue at the TWI repository 
>> <https://github.com/matthewwall/weewx-twi>. Expect it to take a while. 
>> Matthew is swamped.
>>
>> Or, better yet, do a fork and submit a PR.
>>
>> Cloned weewx-twi, working on a revised driver.  The current driver is 
> populating loop packets with "pressure" while the station reports 
> "altitude"... 
>

-- 
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/98794c13-7fe5-4475-b164-439a4c2e08a4n%40googlegroups.com.

[weewx-user] Corrections for barometric pressure from TWI station

[pannetron]

Newbie here, coming from wview, and using a Texas Weather Instruments 
station.  I've adjusted my console to display -- and report via its serial 
port -- an "altimeter" version of my barometric pressure so I can most 
easily compare my readings with other stations.  Using the default weewx 
configuration, it must assume the reported pressure is gauge pressure since 
the calculated altimeter reading is up over 41"!  At my home's altitude of 
8258', my gauge pressure is around 22.15".  It seems that I have two 
options for configuring weewx to see my correct barometric pressure.  One 
is to set the 
[StdWXCalculate] like this:

[[Calculations]]

pressure = software
altimeter = hardware
barometer = software
   
My other option to let weewx assume the pressure my station reports is 
gauge pressure and apply a correction offset of approximately -8".  Which 
option is the preferred method?

One final question.  Since my barometric pressure sensor is indoors in the 
console, should the temperature used for corrections be indoor or outdoor 
temperature?

Thanks, Russ.

-- 
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/24d0dfc1-2931-4c53-98e7-38b739954164n%40googlegroups.com.

Re: [weewx-user] Re: weewx server?

[pannetron]

If you host a public website from a personal Linux server, as I do, look 
into using fail2ban as a way to detect and block some bad actor bots.  My 
implementation currently has about 2500 IPs blocked because they were 
looking for typical webserver security flaws.

On Wednesday, January 4, 2023 at 11:11:49 AM UTC-7 do...@dougjenkins.com 
wrote:

> Glad some of you find this useful.
>
> I have been using this method since it came out this summer (July 2022). I 
> run my infrastructure (Web Server, WeeWX, MQTT, MariaDB) as containers in 
> one stack in its own network all in Docker. I do this to limit what the 
> cloudflare tunnel can access on my network (just WeeWx stuff). All of this 
> works in docker in one stack and one YAML file!
>
> Like Tom Lawerence mentioned in the video I attached, you have to put 
> Cloudflare in your "circle of trust" as you are depending on them for both 
> the client and server/edge side of the tunnel. You have to make that 
> determination on your own if you are comfortable with that.
>
> As other methods mentioned here, they are all great alternatives. I was 
> not aware adafriut offered a dashboard to present your data. That can be a 
> good alternative than going through the hassle of hosting a full website 
> for your station.
>
> If I get a free moment in a few weeks, I can post a step-by-step article 
> on onboarding your WeeWX weather station as a public website using 
> Cloudflare. I think it can help a lot of users who struggle with the 
> network & security setup.
>
> DDJ
>
> On Wed, Jan 4, 2023 at 12:49 PM vince  wrote:
>
>> On Tuesday, January 3, 2023 at 6:41:01 PM UTC-8 do...@dougjenkins.com 
>> wrote:
>>
>>> If you are willing to roll up your sleeves and get technical, serving 
>>> your website at home can be done safely and securely without changing your 
>>> firewall. There are some steps to do, but at the end it will save you money 
>>> and it will give you some real-world IT experience.
>>>
>>>
>> Very cool - thanks for the pointer to the video.  I hadn't previously 
>> figured out the Zero Trust terminology enough to try the tunnel stuff. I'll 
>> have to try the tunnel thing too 
>>
>> For the original poster, Doug's steps 1-3 are very easy.  I'd previously 
>> done that using Google Domains ($12/year).
>>
>> Note - you probably still want to possibly harden your weewx webserver a 
>> bit.  There are zillions of bots trying to attack web servers 'especially' 
>> all things WordPress.  If you go just with a vanilla weewx setup you're 
>> likely in very good shape straight out of the box.  Cool cheap option for 
>> sure.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/56afd382-a9ba-49e7-831f-2813872d6db0n%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/276e98bc-7206-4581-bbfb-51d24133e409n%40googlegroups.com.