Re: [weewx-user] wewwx new variables

[Tom Keffer]

*Accumulators *

On Sun, Jul 23, 2023 at 10:08 PM Graham Eddy  wrote:

> values like rain - and, in my own case, energy created by solar panel
> inverter - need to be summed not averaged over the archive interval.
> the default accumulator for a data_type is averaging, so you need to
> specify your new data_type explicitly as summed - in my case,
> ‘’weewx.conf'' has:
>
> [Accumulator]
>
> [[gen_energy]]
>
> extractor = sum
>
> not sure where this is documented. other types are average, last, first,
> ...
> *⊣GE⊢*
>
> On 24 Jul 2023, at 3:24 am, maria gourniezaki 
> wrote:
>
> How to distinguish between accumulative fields and now accumulative ones?
>
>
> --
> 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/B8E0470F-5B45-4347-9674-73829A8F70F9%40geddy.au
> 
> .
>

-- 
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/CAPq0zECEbN__Ecm83uOn4ZxfyXf9oT9xb3WvA0MAJmFiDWVgqg%40mail.gmail.com.

Re: [weewx-user] wewwx new variables

[maria gourniezaki]

Thanks, very good wiki indee

On Mon, Jul 24, 2023 at 2:12 PM Tom Keffer  wrote:

> *Accumulators *
>
> On Sun, Jul 23, 2023 at 10:08 PM Graham Eddy  wrote:
>
>> values like rain - and, in my own case, energy created by solar panel
>> inverter - need to be summed not averaged over the archive interval.
>> the default accumulator for a data_type is averaging, so you need to
>> specify your new data_type explicitly as summed - in my case,
>> ‘’weewx.conf'' has:
>>
>> [Accumulator]
>>
>> [[gen_energy]]
>>
>> extractor = sum
>>
>> not sure where this is documented. other types are average, last, first,
>> ...
>> *⊣GE⊢*
>>
>> On 24 Jul 2023, at 3:24 am, maria gourniezaki 
>> wrote:
>>
>> How to distinguish between accumulative fields and now accumulative ones?
>>
>>
>> --
>> 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/B8E0470F-5B45-4347-9674-73829A8F70F9%40geddy.au
>> 
>> .
>>
> --
> 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/CAPq0zECEbN__Ecm83uOn4ZxfyXf9oT9xb3WvA0MAJmFiDWVgqg%40mail.gmail.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/CADU%3DJBc2nG2dK-8qJ84tM727uQRXXM%2Bp5vTm%2BL3hJ8O1%2BP7e6g%40mail.gmail.com.

[weewx-user] Re: MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thank you all for providing input / sharing your configurations.
I made the suggested changes and more, but still belchertown displays 
Connected. Waiting for data ...
I have attached all configs / logs / checks I could think of below.

Thanks again for your input in advance!
Stefan


These are my current configs:

*mosquitto*:
*/etc/mosquitto/acl:*
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user teffi

*/etc/mosquitto/mosquitto.conf *
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /run/mosquitto/mosquitto.pid

#persistence true
#persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d

*/etc/mosquitto/conf.d/myconfig.conf *
persistence false

allow_anonymous true
password_file /etc/mosquitto/passwd

acl_file /etc/mosquitto/acl

# mqtt
listener 1883
protocol mqtt

# websockets
listener 9001
protocol websockets

*/etc/mosquitto/acl*
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user teffi
topic weather/#

*MQTT in WeeWX:*
[StdRESTful]
[[MQTT]]

# Enable/disable this service
enable = true

# Hostname/IP of MQTT broker
host = 192.168.178.190
server_url = mqtt://teffi:@localhost:1883/

# Credentials
user = teffi
password = 

# Prefix for topics
topic = weather
unit_system = METRIC
binding = archive,loop
aggregation = aggregate

*checking if WeeWX serves mosquitto with info:*
*mosquitto_sub -h 192.168.178.190 -t weather/#*
online
online
1690198935
24.6
23.9
53
54
993.7
993.7
11377.0
8.9
0
0.0
0.0
0.0
0.0
0.3
1.46
1.46
294
6.480016105981334
9.360023264195261
7.1
0
4
89.7947908445146
997.3266279778212
23.910163208269463
997.1205287280834
1262.3292207924262
14.015863559854884
23.75
27.2746765106266
14.37423758808152
859.4544718145543
23.9
16

*Belchertown skin receiving MQTT topic /weather/#*
[StdReport]
[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true

[[[Extras]]]
#--- MQTT Websockets (for Real Time Streaming) Options ---
#log_failure = True 
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.178.190
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/loop
mqtt_websockets_username = teffi
mqtt_websockets_password = 
disconnect_live_website_visitor = 180

*Checking if it works in webpage:*
*http://localhost/weewx/belchertown/* or weewxhi.de

Connected. Waiting for data. Last Updated July 24, 2023, 1:20:00 PM

The webpage never receives data.


*mosquitto.log shows connections:*
*sudo more /var/log/mosquitto/mosquitto.log *

1690197817: mosquitto version 2.0.11 starting
1690197817: Config loaded from /etc/mosquitto/mosquitto.conf.
1690197817: Opening ipv4 listen socket on port 1883.
1690197817: Opening ipv6 listen socket on port 1883.
1690197817: Opening websockets listen socket on port 9001.
1690197817: mosquitto version 2.0.11 running
1690197822: New connection from 192.168.178.190:36367 on port 1883.
1690197822: New client connected from 192.168.178.190:36367 as 
weewx_e353ae0d (p2, c1, k60, u'teffi').
1690197840: New client connected from :::192.168.178.190:59900 as 
website819759641 (p2, c1, k60, u'teffi').
1690197884: Client website819759641 closed its connection.
1690197884: Client  closed its connection.
1690197886: New client connected from :::192.168.178.190:52896 as 
website398593267 (p2, c1, k60, u'teffi').
1690198918: New connection from 192.168.178.190:36078 on port 1883.
1690198918: New client connected from 192.168.178.190:36078 as 
auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA (p2, c1, k60).
1690198939: Client auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA disconnected.
1690199057: New client connected from :::192.168.178.64:57281 as 
website924402803 (p2, c1, k60, u'teffi').
On Sunday, July 23, 2023 at 4:01:07 PM UTC+2 Claudio wrote:

> this is my config, 
> no ssl / read user = all
>
> Belchertown skin.conf
>
>
>  # MQTT Websockets defaults
>
> mqtt_websockets_enabled = 1
>
> mqtt_websockets_host = public IP (no local IP)
>
> mqtt_websockets_port = 9001
>
> mqtt_websockets_ssl = 0
>
> mqtt_websockets_topic = weather/loop
>
> mqtt_websockets_username = ""
>
> mqtt_websockets_password = ""
>
> disconnect_live_website_visitor = 180
>
> weewx weewx.conf
>
> [[MQTT]]
>
>
> server_url = mqtt://user:password@localhost:1883/
>
> topic = weather
>
> unit_system = METRIC
>
>

[weewx-user] Re: MQTT / Belchertown / Connected. Waiting for data.

[mh081...@gmail.com]

Hi,

it doesnt work with localhost. Think, you start your Browser localy so your 
Loca Browser try to mqqt to localhost. And there is no mwtt server.

>From My weewx config (the MQTT part). Think i configured my mqtt and 
Webssite with https.

##weewx.conf#
[[MQTT]]
server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
topic = weather
unit_system = METRIC
binding = archive, loop
aggregation = aggregate
log_success = False
log_failure = True
[[[tls]]]
tls_version = tlsv12
ca_certs = /etc/ssl/certs/ca-certificates.crt
[[[inputs]]]
dayRain
name = dayRain_mm
units = mm
rainRate
name = rainRate_mm_per_hour
units = mm_per_hour

[[Belchertown]]

[[[Extras]]]


#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = gw.martenhinrichs.de
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 1
mqtt_websockets_topic = weather/loop





#mosquitto.conf
allow_anonymous true
password_file /etc/mosquitto/passwd
acl_file /etc/mosquitto/acl
persistence false

# mqtt
listener 1883 
listener 8883
certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
protocol mqtt

# websockets
listener 9001
certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
protocol websockets






Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:

> Thank you all for providing input / sharing your configurations.
> I made the suggested changes and more, but still belchertown displays 
> Connected. Waiting for data ...
> I have attached all configs / logs / checks I could think of below.
>
> Thanks again for your input in advance!
> Stefan
>
>
> These are my current configs:
>
> *mosquitto*:
> */etc/mosquitto/acl:*
> # Allow anonymous access to the sys
> topic read $SYS/#
>
> # Allow anonymous to read weather
> topic read weather/#
>
> # weewx readwrite to the loop
> user teffi
>
> */etc/mosquitto/mosquitto.conf *
> # Place your local configuration in /etc/mosquitto/conf.d/
> #
> # A full description of the configuration file is at
> # /usr/share/doc/mosquitto/examples/mosquitto.conf.example
>
> pid_file /run/mosquitto/mosquitto.pid
>
> #persistence true
> #persistence_location /var/lib/mosquitto/
>
> log_dest file /var/log/mosquitto/mosquitto.log
>
> include_dir /etc/mosquitto/conf.d
>
> */etc/mosquitto/conf.d/myconfig.conf *
> persistence false
>
> allow_anonymous true
> password_file /etc/mosquitto/passwd
>
> acl_file /etc/mosquitto/acl
>
> # mqtt
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> */etc/mosquitto/acl*
> # Allow anonymous access to the sys
> topic read $SYS/#
>
> # Allow anonymous to read weather
> topic read weather/#
>
> # weewx readwrite to the loop
> user teffi
> topic weather/#
>
> *MQTT in WeeWX:*
> [StdRESTful]
> [[MQTT]]
>
> # Enable/disable this service
> enable = true
>
> # Hostname/IP of MQTT broker
> host = 192.168.178.190
> server_url = mqtt://teffi:@localhost:1883/
>
>
> # Credentials
> user = teffi
> password = 
>
> # Prefix for topics
>
> topic = weather
> unit_system = METRIC
> binding = archive,loop
> aggregation = aggregate
>
> *checking if WeeWX serves mosquitto with info:*
> *mosquitto_sub -h 192.168.178.190 -t weather/#*
> online
> online
> 1690198935
> 24.6
> 23.9
> 53
> 54
> 993.7
> 993.7
> 11377.0
> 8.9
> 0
> 0.0
> 0.0
> 0.0
> 0.0
> 0.3
> 1.46
> 1.46
> 294
> 6.480016105981334
> 9.360023264195261
> 7.1
> 0
> 4
> 89.7947908445146
> 997.3266279778212
> 23.910163208269463
> 997.1205287280834
> 1262.3292207924262
> 14.015863559854884
> 23.75
> 27.2746765106266
> 14.37423758808152
> 859.4544718145543
> 23.9
> 16
>
> *Belchertown skin receiving MQTT topic /weather/#*
> [StdReport]
> [[Belchertown]]
> skin = Belchertown
> HTML_ROOT = /var/www/html/weewx/belchertown
> enable = true
>
> [[[Extras]]]
> #--- MQTT Websockets (for Real Time Streaming) Options ---
> #log_failure = True 
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = 192.168.178.190
> mqtt_websockets_port = 9001
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = weather/loop
> mqtt_websockets_username = teffi
> mqtt_websockets_password = 
> disconnect_live_web

Re: [weewx-user] Re: MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thank you for the feedback.
I changed "localhost" to the IP of the MQTT broker as suggested.
It did not fix it ...

As far as I understand that section is for uploading weewx data to the mqtt
broker.
That part works well as I can read the weather with an mqtt client.

It is the Belchertown skin part which connects to the MQTT Brocker with
websocket, but it cannot receive data for updates ...

I am really puzzled ...

On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
wrote:

> Hi,
>
> it doesnt work with localhost. Think, you start your Browser localy so
> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>
> From My weewx config (the MQTT part). Think i configured my mqtt and
> Webssite with https.
>
> ##weewx.conf#
> [[MQTT]]
> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
> topic = weather
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
> [[[tls]]]
> tls_version = tlsv12
> ca_certs = /etc/ssl/certs/ca-certificates.crt
> [[[inputs]]]
> dayRain
> name = dayRain_mm
> units = mm
> rainRate
> name = rainRate_mm_per_hour
> units = mm_per_hour
>
> [[Belchertown]]
>
> [[[Extras]]]
>
>
> #--- MQTT Websockets (for Real Time Streaming) Options ---
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = gw.martenhinrichs.de
> mqtt_websockets_port = 9001
> mqtt_websockets_ssl = 1
> mqtt_websockets_topic = weather/loop
>
>
>
>
>
> #mosquitto.conf
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
> persistence false
>
> # mqtt
> listener 1883
> listener 8883
> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
> protocol mqtt
>
> # websockets
> listener 9001
> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
> protocol websockets
>
>
>
>
>
>
> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>
>> Thank you all for providing input / sharing your configurations.
>> I made the suggested changes and more, but still belchertown displays
>> Connected. Waiting for data ...
>> I have attached all configs / logs / checks I could think of below.
>>
>> Thanks again for your input in advance!
>> Stefan
>>
>>
>> These are my current configs:
>>
>> *mosquitto*:
>> */etc/mosquitto/acl:*
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>>
>> # Allow anonymous to read weather
>> topic read weather/#
>>
>> # weewx readwrite to the loop
>> user teffi
>>
>> */etc/mosquitto/mosquitto.conf *
>> # Place your local configuration in /etc/mosquitto/conf.d/
>> #
>> # A full description of the configuration file is at
>> # /usr/share/doc/mosquitto/examples/mosquitto.conf.example
>>
>> pid_file /run/mosquitto/mosquitto.pid
>>
>> #persistence true
>> #persistence_location /var/lib/mosquitto/
>>
>> log_dest file /var/log/mosquitto/mosquitto.log
>>
>> include_dir /etc/mosquitto/conf.d
>>
>> */etc/mosquitto/conf.d/myconfig.conf *
>> persistence false
>>
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>
>> acl_file /etc/mosquitto/acl
>>
>> # mqtt
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> */etc/mosquitto/acl*
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>>
>> # Allow anonymous to read weather
>> topic read weather/#
>>
>> # weewx readwrite to the loop
>> user teffi
>> topic weather/#
>>
>> *MQTT in WeeWX:*
>> [StdRESTful]
>> [[MQTT]]
>>
>> # Enable/disable this service
>> enable = true
>>
>> # Hostname/IP of MQTT broker
>> host = 192.168.178.190
>> server_url = mqtt://teffi:@localhost:1883/
>>
>>
>> # Credentials
>> user = teffi
>> password = 
>>
>> # Prefix for topics
>>
>> topic = weather
>> unit_system = METRIC
>> binding = archive,loop
>> aggregation = aggregate
>>
>> *checking if WeeWX serves mosquitto with info:*
>> *mosquitto_sub -h 192.168.178.190 -t weather/#*
>> online
>> online
>> 1690198935
>> 24.6
>> 23.9
>> 53
>> 54
>> 993.7
>> 993.7
>> 11377.0
>> 8.9
>> 0
>> 0.0
>> 0.0
>> 0.0
>> 0.0
>> 0.3
>> 1.46
>> 1.46
>> 294
>> 6.480016105981334
>> 9.360023264195261
>> 7.1
>> 0
>> 4
>> 89.7947908445146
>> 997.3266279778212
>> 23.910163208269463
>> 997.1205287280834
>> 1262.3292207924262
>> 14.015863559854884
>> 23.75
>> 27.2746765106266
>> 14.374237588081

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Jacques Terrettaz]

Two things to consider :


1)  when opening your website from local network :  your mqtt broker is using 
port 9001 for websockets. If it doesn't works , you may have to verify that 
this port 9001 is not blocked by a firewall.  
2)  when opening your website from internet (http://weewxhi.de 
) .i.e outside your local network :  mqtt_websockets_host = 
192.168.178.190  is a local network IP address that cannot be accessed from 
outside. You should use  a dynamic dns service (no-ip, dyndns or other) to 
create a redirection from internet to your mqtt broker, and configure your 
router and firewall accordingly.




> Le 24 juil. 2023 à 15:06, Stefan Gliessmann  a 
> écrit :
> 
> Thank you for the feedback.
> I changed "localhost" to the IP of the MQTT broker as suggested.
> It did not fix it ...
> 
> As far as I understand that section is for uploading weewx data to the mqtt 
> broker.
> That part works well as I can read the weather with an mqtt client.
> 
> It is the Belchertown skin part which connects to the MQTT Brocker with 
> websocket, but it cannot receive data for updates ...
> 
> I am really puzzled ...
> 
> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>   > wrote:
>> Hi,
>> 
>> it doesnt work with localhost. Think, you start your Browser localy so your 
>> Loca Browser try to mqqt to localhost. And there is no mwtt server.
>> 
>> From My weewx config (the MQTT part). Think i configured my mqtt and 
>> Webssite with https.
>> 
>> ##weewx.conf#
>> [[MQTT]]
>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/ 
>> 
>> topic = weather
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = False
>> log_failure = True
>> [[[tls]]]
>> tls_version = tlsv12
>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>> [[[inputs]]]
>> dayRain
>> name = dayRain_mm
>> units = mm
>> rainRate
>> name = rainRate_mm_per_hour
>> units = mm_per_hour
>> 
>> [[Belchertown]]
>> 
>> [[[Extras]]]
>> 
>> 
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = gw.martenhinrichs.de 
>> 
>> mqtt_websockets_port = 9001
>> mqtt_websockets_ssl = 1
>> mqtt_websockets_topic = weather/loop
>> 
>> 
>> 
>> 
>> 
>> #mosquitto.conf
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>> persistence false
>> 
>> # mqtt
>> listener 1883 
>> listener 8883
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem 
>> 
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem 
>> 
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem 
>> 
>> protocol mqtt
>> 
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem 
>> 
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem 
>> 
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem 
>> 
>> protocol websockets
>> 
>> 
>> 
>> 
>> 
>> 
>> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>>> Thank you all for providing input / sharing your configurations.
>>> I made the suggested changes and more, but still belchertown displays 
>>> Connected. Waiting for data ...
>>> I have attached all configs / logs / checks I could think of below.
>>> 
>>> Thanks again for your input in advance!
>>> Stefan
>>> 
>>> 
>>> These are my current configs:
>>> 
>>> mosquitto:
>>> /etc/mosquitto/acl:
>>> # Allow anonymous access to the sys
>>> topic read $SYS/#
>>> 
>>> # Allow anonymous to read weather
>>> topic read weather/#
>>> 
>>> # weewx readwrite to the loop
>>> user teffi
>>> 
>>> /etc/mosquitto/mosquitto.conf 
>>> # Place your local configuration in /etc/mosquitto/conf.d/
>>> #
>>> # A full description of the configuration file is at
>>> # /usr/share/doc/mosquitto/examples/mosquitto.conf.example
>>> 
>>> pid_file /run/mosquitto/mosquitto.pid
>>> 
>>> #persistence true
>>> #persistence_location /var/lib/mosquitto/
>>> 
>>> log_dest file /var/log/mosquitto/mosquitto.log
>>> 
>>> include_dir /etc/mosquitto/conf.d
>>> 
>>> /etc/mosquitto/conf.d/myconfig.conf 
>>> persistence false
>>> 
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> 
>>> acl_file /etc/mosquitto/acl
>>> 
>>> # mqtt
>>> listener 1883
>>> protocol mqtt
>>> 
>>> 

[weewx-user] GW1100-WS90 :Missing rainfall values

[didier belin]

I can no longer find the rainfall values in weewx. all others are visible 
via the seasons skin. Equipment used: ecowitt g1100; ws90.
sue ecowitt.net: no problem everything is indicated. via the command.
PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok nothing 
seems to be missing.
I don't see where in weewx.conf or skin.conf, I have to go see

-- 
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/7cda68c1-170e-4c37-a23b-290800c0bd0fn%40googlegroups.com.

[weewx-user] Graph with the days at more than a certain temperature in the month or in the year in Belchertown

[enu...@gmail.com]

Is there a way to make a graphic like the one I ask for with the bechertown 
skin?
I do not get it

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/963fdc16-b2cc-42cc-b247-b3c069f19c51n%40googlegroups.com.

[weewx-user] Re: GW1100-WS90 :Missing rainfall values

[didier belin]

Despite modifying weewx.conf , as quoted in another post


weewx.conf 


poll_interval = 20
# The driver to use:
driver = user.gw1000
ip_address = 192.168.X.X
port = 45000
[[field_map_extensions]]
rain = p_rain
stormRain = p_rainevent
rainRate = p_rainrate
dayRain = p_rainday
weekRain = p_rainweek
monthRain = p_rainmonth
yearRain = p_rainyear

. 

2023-07-24 16:33:21 CEST (1690209201): 'dateTime': '1690209201', 
'daymaxwind': '5.2', 'dayRain': '8.0', 'extraHumid1': '56', 'extraHumid2': 
'85', 'extraHumid3': '67', 'extraTemp1': '24.9', 'extraTemp2': '19.2', 
'extraTemp3': '22.0', 'extraTemp9': '19.1', 'inHumidity': '65', 'inTemp': 
'21.9', 'leafWet1': '0', 'lightning_distance': '27', 
'lightning_last_det_time': '1690191720', 'lightning_strike_count': '0', 
'lightningcount': '9', 'luminosity': '36350.0', 'monthRain': '43.5', 
'outHumidity': '76', 'outTemp': '19.9', 'pm2_5': '4.0', 'pm2_51_24h_avg': 
'2.0', 'pressure': '997.3', 'rain': '0.0', 'rainRate': '0.0', 
'relbarometer': '997.3', 'soilMoist1': '41', 'stormRain': '12.1', 
'usUnits': '17', 'UV': '2', 'uvradiation': '54.0', 'weekRain': '12.4', 
'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch2_batt': '0', 
'wh31_ch2_sig': '4', 'wh31_ch3_batt': '0', 'wh31_ch3_sig': '4', 
'wh41_ch1_batt': '4', 'wh41_ch1_sig': '4', 'wh51_ch1_batt': '1.3', 
'wh51_ch1_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '301', 
'windGust': '3.2', 'windSpeed': '1.5', 'wn34_ch1_batt': '1.6', 
'wn34_ch1_sig': '4', 'wn35_ch1_batt': '1.54', 'wn35_ch1_sig': '4', 
'ws90_batt': '2.58', 'ws90_sig': '4', 'yearRain': '92.8'
Le lundi 24 juillet 2023 à 15:31:31 UTC+2, didier belin a écrit :

> I can no longer find the rainfall values in weewx. all others are visible 
> via the seasons skin. Equipment used: ecowitt g1100; ws90.
> sue ecowitt.net: no problem everything is indicated. via the command.
> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok nothing 
> seems to be missing.
> I don't see where in weewx.conf or skin.conf, I have to go see
>

-- 
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/f3116941-04ca-4987-a23d-ba1756570540n%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thanks, Jaques!

wrt
*1)  when opening your website from local network :  your mqtt broker is
using port 9001 for websockets. If it doesn't works , you may have to
verify that this port 9001 is not blocked by a firewall.  *
9001 is not blocked by the firewall on 192.168.178.190
I can receive the via 9001 on my iPhone with an Matt client the values

*2)  when opening your website from internet (http://weewxhi.de
) .i.e outside your local network
:  mqtt_websockets_host = 192.168.178.190  is a local network IP address
that cannot be accessed from outside. You should use  a dynamic dns service
(no-ip, dyndns or other) to create a redirection from internet to your mqtt
broker, and configure your router and firewall accordingly.*
Yeah - I have dyndns enabled and just opened 9001 on my router, too.

Unfortunately, it continues to say "Connected. Waiting for data."

Does a Belchertown config file override weewx.conf settings somewhere?


On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz 
wrote:

> Two things to consider :
>
>
> 1)  when opening your website from local network :  your mqtt broker is
> using port 9001 for websockets. If it doesn't works , you may have to
> verify that this port 9001 is not blocked by a firewall.
> 2)  when opening your website from internet (http://weewxhi.de) .i.e
> outside your local network :  mqtt_websockets_host = 192.168.178.190  is
> a local network IP address that cannot be accessed from outside. You should
> use  a dynamic dns service (no-ip, dyndns or other) to create a redirection
> from internet to your mqtt broker, and configure your router and firewall
> accordingly.
>
>
>
>
> Le 24 juil. 2023 à 15:06, Stefan Gliessmann 
> a écrit :
>
> Thank you for the feedback.
> I changed "localhost" to the IP of the MQTT broker as suggested.
> It did not fix it ...
>
> As far as I understand that section is for uploading weewx data to the
> mqtt broker.
> That part works well as I can read the weather with an mqtt client.
>
> It is the Belchertown skin part which connects to the MQTT Brocker with
> websocket, but it cannot receive data for updates ...
>
> I am really puzzled ...
>
> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
> wrote:
>
>> Hi,
>>
>> it doesnt work with localhost. Think, you start your Browser localy so
>> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>>
>> From My weewx config (the MQTT part). Think i configured my mqtt and
>> Webssite with https.
>>
>> ##weewx.conf#
>> [[MQTT]]
>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
>> topic = weather
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = False
>> log_failure = True
>> [[[tls]]]
>> tls_version = tlsv12
>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>> [[[inputs]]]
>> dayRain
>> name = dayRain_mm
>> units = mm
>> rainRate
>> name = rainRate_mm_per_hour
>> units = mm_per_hour
>>
>> [[Belchertown]]
>>
>> [[[Extras]]]
>>
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = gw.martenhinrichs.de
>> mqtt_websockets_port = 9001
>> mqtt_websockets_ssl = 1
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
>>
>>
>> #mosquitto.conf
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>> persistence false
>>
>> # mqtt
>> listener 1883
>> listener 8883
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>> protocol websockets
>>
>>
>>
>>
>>
>>
>> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>>
>>> Thank you all for providing input / sharing your configurations.
>>> I made the suggested changes and more, but still belchertown displays
>>> Connected. Waiting for data ...
>>> I have attached all configs / logs / checks I could think of below.
>>>
>>> Thanks again for your input in advance!
>>> Stefan
>>>
>>>
>>> These are my current configs:
>>>
>>> *mosquitto*:
>>> */etc/mosquitto/acl:*
>>> # Allow anonymous access to the sys
>>> topic read $SYS/#
>>>
>>> # Allow anonymous to read weather
>>> topic read weather/#
>>>
>>> # weewx readwrite to the loop
>>> user teffi
>>>
>>> */etc/mosquitto/mosquitto.conf *
>>> # Place your local configuration in /etc/mosquitto/conf.d/
>>>

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Jacques Terrettaz]

>> 9001 is not blocked by the firewall on 192.168.178.190
>> I can receive the via 9001 on my iPhone with an Matt client the values 

So have a look at your browser console to detect any websocket or javascript 
errors that can occur


> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
> 
> Unfortunately, it continues to say "Connected. Waiting for data." 

If you have a dyndns host configured, such as X.dyndns.org 
 , that redirects to your mqtt broker, you have to 
configure  : 
mqtt_websockets_host = X.dyndns.org


> Le 24 juil. 2023 à 16:40, Stefan Gliessmann  a 
> écrit :
> 
> Thanks, Jaques!
> 
> wrt
> 1)  when opening your website from local network :  your mqtt broker is using 
> port 9001 for websockets. If it doesn't works , you may have to verify that 
> this port 9001 is not blocked by a firewall.  
> 9001 is not blocked by the firewall on 192.168.178.190
> I can receive the via 9001 on my iPhone with an Matt client the values
> 
> 2)  when opening your website from internet (http://weewxhi.de 
> ) .i.e outside your local network :  mqtt_websockets_host 
> = 192.168.178.190  is a local network IP address that cannot be accessed from 
> outside. You should use  a dynamic dns service (no-ip, dyndns or other) to 
> create a redirection from internet to your mqtt broker, and configure your 
> router and firewall accordingly.
> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
> 
> Unfortunately, it continues to say "Connected. Waiting for data." 
> 
> Does a Belchertown config file override weewx.conf settings somewhere? 
> 
> 
> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz  > wrote:
>> Two things to consider :
>> 
>> 
>> 1)  when opening your website from local network :  your mqtt broker is 
>> using port 9001 for websockets. If it doesn't works , you may have to verify 
>> that this port 9001 is not blocked by a firewall.  
>> 2)  when opening your website from internet (http://weewxhi.de 
>> ) .i.e outside your local network :  
>> mqtt_websockets_host = 192.168.178.190  is a local network IP address that 
>> cannot be accessed from outside. You should use  a dynamic dns service 
>> (no-ip, dyndns or other) to create a redirection from internet to your mqtt 
>> broker, and configure your router and firewall accordingly.
>> 
>> 
>> 
>> 
>>> Le 24 juil. 2023 à 15:06, Stefan Gliessmann >> > a écrit :
>>> 
>>> Thank you for the feedback.
>>> I changed "localhost" to the IP of the MQTT broker as suggested.
>>> It did not fix it ...
>>> 
>>> As far as I understand that section is for uploading weewx data to the mqtt 
>>> broker.
>>> That part works well as I can read the weather with an mqtt client.
>>> 
>>> It is the Belchertown skin part which connects to the MQTT Brocker with 
>>> websocket, but it cannot receive data for updates ...
>>> 
>>> I am really puzzled ...
>>> 
>>> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>>>  >> > wrote:
 Hi,
 
 it doesnt work with localhost. Think, you start your Browser localy so 
 your Loca Browser try to mqqt to localhost. And there is no mwtt server.
 
 From My weewx config (the MQTT part). Think i configured my mqtt and 
 Webssite with https.
 
 ##weewx.conf#
 [[MQTT]]
 server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/ 
 
 topic = weather
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate
 log_success = False
 log_failure = True
 [[[tls]]]
 tls_version = tlsv12
 ca_certs = /etc/ssl/certs/ca-certificates.crt
 [[[inputs]]]
 dayRain
 name = dayRain_mm
 units = mm
 rainRate
 name = rainRate_mm_per_hour
 units = mm_per_hour
 
 [[Belchertown]]
 
 [[[Extras]]]
 
 
 #--- MQTT Websockets (for Real Time Streaming) Options ---
 mqtt_websockets_enabled = 1
 mqtt_websockets_host = gw.martenhinrichs.de 
 
 mqtt_websockets_port = 9001
 mqtt_websockets_ssl = 1
 mqtt_websockets_topic = weather/loop
 
 
 
 
 
 #mosquitto.conf
 allow_anonymous true
 password_file /etc/mosquitto/passwd
 acl_file /etc/mosquitto/acl
 persistence false
 
 # mqtt
 listener 1883 
 listener 8883
 certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem 
 
 

Re: [weewx-user] Re: GW1100-WS90 :Missing rainfall values

['Rainer Lang' via weewx-user]

maybe weewx is not the culprit 

did you set the piezo rain priority in your GW1100 ? (-->Rain totals --> 
Rainfall data priority --> Piezoelectric Rain Gauge)


On 24.07.2023 16:38, didier belin wrote:

Despite modifying weewx.conf , as quoted in another post


weewx.conf


poll_interval = 20
    # The driver to use:
    driver = user.gw1000
    ip_address = 192.168.X.X
    port = 45000
    [[field_map_extensions]]
        rain = p_rain
        stormRain = p_rainevent
        rainRate = p_rainrate
        dayRain = p_rainday
        weekRain = p_rainweek
        monthRain = p_rainmonth
        yearRain = p_rainyear

.

2023-07-24 16:33:21 CEST (1690209201): 'dateTime': '1690209201', 
'daymaxwind': '5.2', 'dayRain': '8.0', 'extraHumid1': '56', 
'extraHumid2': '85', 'extraHumid3': '67', 'extraTemp1': '24.9', 
'extraTemp2': '19.2', 'extraTemp3': '22.0', 'extraTemp9': '19.1', 
'inHumidity': '65', 'inTemp': '21.9', 'leafWet1': '0', 
'lightning_distance': '27', 'lightning_last_det_time': '1690191720', 
'lightning_strike_count': '0', 'lightningcount': '9', 'luminosity': 
'36350.0', 'monthRain': '43.5', 'outHumidity': '76', 'outTemp': 
'19.9', 'pm2_5': '4.0', 'pm2_51_24h_avg': '2.0', 'pressure': '997.3', 
'rain': '0.0', 'rainRate': '0.0', 'relbarometer': '997.3', 
'soilMoist1': '41', 'stormRain': '12.1', 'usUnits': '17', 'UV': '2', 
'uvradiation': '54.0', 'weekRain': '12.4', 'wh31_ch1_batt': '0', 
'wh31_ch1_sig': '4', 'wh31_ch2_batt': '0', 'wh31_ch2_sig': '4', 
'wh31_ch3_batt': '0', 'wh31_ch3_sig': '4', 'wh41_ch1_batt': '4', 
'wh41_ch1_sig': '4', 'wh51_ch1_batt': '1.3', 'wh51_ch1_sig': '4', 
'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '301', 'windGust': 
'3.2', 'windSpeed': '1.5', 'wn34_ch1_batt': '1.6', 'wn34_ch1_sig': 
'4', 'wn35_ch1_batt': '1.54', 'wn35_ch1_sig': '4', 'ws90_batt': 
'2.58', 'ws90_sig': '4', 'yearRain': '92.8'

Le lundi 24 juillet 2023 à 15:31:31 UTC+2, didier belin a écrit :

I can no longer find the rainfall values in weewx. all others are
visible via the seasons skin. Equipment used: ecowitt g1100; ws90.
sue ecowitt.net : no problem everything is
indicated. via the command.
PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok
nothing seems to be missing.
I don't see where in weewx.conf or skin.conf, I have to go see

--
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/f3116941-04ca-4987-a23d-ba1756570540n%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/1a7d834c-f7c0-c54e-b6a8-26c36c95f7e2%40gmail.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Jacques Terrettaz]

Another point to check :

Please verify in your mosquitto acl file (/etc/mosquitto/acl) that the user 
"teffi" has read permission for the topic "weather"

> Le 24 juil. 2023 à 16:40, Stefan Gliessmann  a 
> écrit :
> 
> Thanks, Jaques!
> 
> wrt
> 1)  when opening your website from local network :  your mqtt broker is using 
> port 9001 for websockets. If it doesn't works , you may have to verify that 
> this port 9001 is not blocked by a firewall.  
> 9001 is not blocked by the firewall on 192.168.178.190
> I can receive the via 9001 on my iPhone with an Matt client the values
> 
> 2)  when opening your website from internet (http://weewxhi.de 
> ) .i.e outside your local network :  mqtt_websockets_host 
> = 192.168.178.190  is a local network IP address that cannot be accessed from 
> outside. You should use  a dynamic dns service (no-ip, dyndns or other) to 
> create a redirection from internet to your mqtt broker, and configure your 
> router and firewall accordingly.
> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
> 
> Unfortunately, it continues to say "Connected. Waiting for data." 
> 
> Does a Belchertown config file override weewx.conf settings somewhere? 
> 
> 
> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz  > wrote:
>> Two things to consider :
>> 
>> 
>> 1)  when opening your website from local network :  your mqtt broker is 
>> using port 9001 for websockets. If it doesn't works , you may have to verify 
>> that this port 9001 is not blocked by a firewall.  
>> 2)  when opening your website from internet (http://weewxhi.de 
>> ) .i.e outside your local network :  
>> mqtt_websockets_host = 192.168.178.190  is a local network IP address that 
>> cannot be accessed from outside. You should use  a dynamic dns service 
>> (no-ip, dyndns or other) to create a redirection from internet to your mqtt 
>> broker, and configure your router and firewall accordingly.
>> 
>> 
>> 
>> 
>>> Le 24 juil. 2023 à 15:06, Stefan Gliessmann >> > a écrit :
>>> 
>>> Thank you for the feedback.
>>> I changed "localhost" to the IP of the MQTT broker as suggested.
>>> It did not fix it ...
>>> 
>>> As far as I understand that section is for uploading weewx data to the mqtt 
>>> broker.
>>> That part works well as I can read the weather with an mqtt client.
>>> 
>>> It is the Belchertown skin part which connects to the MQTT Brocker with 
>>> websocket, but it cannot receive data for updates ...
>>> 
>>> I am really puzzled ...
>>> 
>>> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>>>  >> > wrote:
 Hi,
 
 it doesnt work with localhost. Think, you start your Browser localy so 
 your Loca Browser try to mqqt to localhost. And there is no mwtt server.
 
 From My weewx config (the MQTT part). Think i configured my mqtt and 
 Webssite with https.
 
 ##weewx.conf#
 [[MQTT]]
 server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/ 
 
 topic = weather
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate
 log_success = False
 log_failure = True
 [[[tls]]]
 tls_version = tlsv12
 ca_certs = /etc/ssl/certs/ca-certificates.crt
 [[[inputs]]]
 dayRain
 name = dayRain_mm
 units = mm
 rainRate
 name = rainRate_mm_per_hour
 units = mm_per_hour
 
 [[Belchertown]]
 
 [[[Extras]]]
 
 
 #--- MQTT Websockets (for Real Time Streaming) Options ---
 mqtt_websockets_enabled = 1
 mqtt_websockets_host = gw.martenhinrichs.de 
 
 mqtt_websockets_port = 9001
 mqtt_websockets_ssl = 1
 mqtt_websockets_topic = weather/loop
 
 
 
 
 
 #mosquitto.conf
 allow_anonymous true
 password_file /etc/mosquitto/passwd
 acl_file /etc/mosquitto/acl
 persistence false
 
 # mqtt
 listener 1883 
 listener 8883
 certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem 
 
 cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem 
 
 keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem 
 
 protocol mqtt
 
 # websockets
 listener 9001
 certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem 
 
 cafile /etc/letsencrypt

Re: [weewx-user] Re: GW1100-WS90 :Missing rainfall values

[didier belin]

the priority is the one you specified. As mentioned above on the 
ecowitt.net system, it works and on another interface (the weewx system is 
being tested): https://www.bel1.eu/pwsWD/index.php it also works

Le lundi 24 juillet 2023 à 17:00:54 UTC+2, Rainer Lang a écrit :

> maybe weewx is not the culprit 
>
> did you set the piezo rain priority in your GW1100 ? (-->Rain totals --> 
> Rainfall 
> data priority --> Piezoelectric Rain Gauge)
> On 24.07.2023 16:38, didier belin wrote:
>
> Despite modifying weewx.conf , as quoted in another post
>
>
> weewx.conf 
> 
>
> poll_interval = 20
> # The driver to use:
> driver = user.gw1000
> ip_address = 192.168.X.X
> port = 45000
> [[field_map_extensions]]
> rain = p_rain
> stormRain = p_rainevent
> rainRate = p_rainrate
> dayRain = p_rainday
> weekRain = p_rainweek
> monthRain = p_rainmonth
> yearRain = p_rainyear
>
> . 
>
> 2023-07-24 16:33:21 CEST (1690209201): 'dateTime': '1690209201', 
> 'daymaxwind': '5.2', 'dayRain': '8.0', 'extraHumid1': '56', 'extraHumid2': 
> '85', 'extraHumid3': '67', 'extraTemp1': '24.9', 'extraTemp2': '19.2', 
> 'extraTemp3': '22.0', 'extraTemp9': '19.1', 'inHumidity': '65', 'inTemp': 
> '21.9', 'leafWet1': '0', 'lightning_distance': '27', 
> 'lightning_last_det_time': '1690191720', 'lightning_strike_count': '0', 
> 'lightningcount': '9', 'luminosity': '36350.0', 'monthRain': '43.5', 
> 'outHumidity': '76', 'outTemp': '19.9', 'pm2_5': '4.0', 'pm2_51_24h_avg': 
> '2.0', 'pressure': '997.3', 'rain': '0.0', 'rainRate': '0.0', 
> 'relbarometer': '997.3', 'soilMoist1': '41', 'stormRain': '12.1', 
> 'usUnits': '17', 'UV': '2', 'uvradiation': '54.0', 'weekRain': '12.4', 
> 'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch2_batt': '0', 
> 'wh31_ch2_sig': '4', 'wh31_ch3_batt': '0', 'wh31_ch3_sig': '4', 
> 'wh41_ch1_batt': '4', 'wh41_ch1_sig': '4', 'wh51_ch1_batt': '1.3', 
> 'wh51_ch1_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '301', 
> 'windGust': '3.2', 'windSpeed': '1.5', 'wn34_ch1_batt': '1.6', 
> 'wn34_ch1_sig': '4', 'wn35_ch1_batt': '1.54', 'wn35_ch1_sig': '4', 
> 'ws90_batt': '2.58', 'ws90_sig': '4', 'yearRain': '92.8'
> Le lundi 24 juillet 2023 à 15:31:31 UTC+2, didier belin a écrit :
>
>> I can no longer find the rainfall values in weewx. all others are visible 
>> via the seasons skin. Equipment used: ecowitt g1100; ws90.
>> sue ecowitt.net: no problem everything is indicated. via the command.
>> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok 
>> nothing seems to be missing.
>> I don't see where in weewx.conf or skin.conf, I have to go see
>>
> -- 
> 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/f3116941-04ca-4987-a23d-ba1756570540n%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/0354375b-0523-46b6-b5cf-db0a19e3c32fn%40googlegroups.com.

[weewx-user] Re: GW1100-WS90 :Missing rainfall values

[gjr80]

Descriptions can help but 'it doesn't work' does not provide much to go on. 
You say ' *I can no longer find the rainfall values in weewx*', this 
implies that you were seeing rainfall from your WS90 appearing in WeeWX at 
some stage? Is this correct or has it never worked? What exactly is it you 
are not seeing? For example, 'there was 8mm of rain today but WeeWX shows 
0mm on the main Seasons page and the rain plot shows nothing',

You are correct in that you need to add some [[field_map_extensions]] 
entries to have WS90 rainfall data appear in the 'standard' WeeWX rain 
related fields. When did you add these entries? Just now or some time ago? 
If 'just now' WeeWX will not have seen any earlier WS90 rainfall so I would 
not be surprised to see a lack of WS90 rainfall data appearing in WeeWX.

On Monday, 24 July 2023 at 16:00:54 UTC+1 lang@googlemail.com wrote:

did you set the piezo rain priority in your GW1100 ? (-->Rain totals --> 
Rainfall 
data priority --> Piezoelectric Rain Gauge)

Rainfall data priority is not the issue here, WeeWX does not use (nor need) 
the setting irrespective of what rain gauges are in use

Gary 
On Monday, 24 July 2023 at 15:38:58 UTC+1 belin@gmail.com wrote:

> Despite modifying weewx.conf , as quoted in another post
>
>
> weewx.conf 
> 
>
> poll_interval = 20
> # The driver to use:
> driver = user.gw1000
> ip_address = 192.168.X.X
> port = 45000
> [[field_map_extensions]]
> rain = p_rain
> stormRain = p_rainevent
> rainRate = p_rainrate
> dayRain = p_rainday
> weekRain = p_rainweek
> monthRain = p_rainmonth
> yearRain = p_rainyear
>
> . 
>
> 2023-07-24 16:33:21 CEST (1690209201): 'dateTime': '1690209201', 
> 'daymaxwind': '5.2', 'dayRain': '8.0', 'extraHumid1': '56', 'extraHumid2': 
> '85', 'extraHumid3': '67', 'extraTemp1': '24.9', 'extraTemp2': '19.2', 
> 'extraTemp3': '22.0', 'extraTemp9': '19.1', 'inHumidity': '65', 'inTemp': 
> '21.9', 'leafWet1': '0', 'lightning_distance': '27', 
> 'lightning_last_det_time': '1690191720', 'lightning_strike_count': '0', 
> 'lightningcount': '9', 'luminosity': '36350.0', 'monthRain': '43.5', 
> 'outHumidity': '76', 'outTemp': '19.9', 'pm2_5': '4.0', 'pm2_51_24h_avg': 
> '2.0', 'pressure': '997.3', 'rain': '0.0', 'rainRate': '0.0', 
> 'relbarometer': '997.3', 'soilMoist1': '41', 'stormRain': '12.1', 
> 'usUnits': '17', 'UV': '2', 'uvradiation': '54.0', 'weekRain': '12.4', 
> 'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch2_batt': '0', 
> 'wh31_ch2_sig': '4', 'wh31_ch3_batt': '0', 'wh31_ch3_sig': '4', 
> 'wh41_ch1_batt': '4', 'wh41_ch1_sig': '4', 'wh51_ch1_batt': '1.3', 
> 'wh51_ch1_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '301', 
> 'windGust': '3.2', 'windSpeed': '1.5', 'wn34_ch1_batt': '1.6', 
> 'wn34_ch1_sig': '4', 'wn35_ch1_batt': '1.54', 'wn35_ch1_sig': '4', 
> 'ws90_batt': '2.58', 'ws90_sig': '4', 'yearRain': '92.8'
> Le lundi 24 juillet 2023 à 15:31:31 UTC+2, didier belin a écrit :
>
>> I can no longer find the rainfall values in weewx. all others are visible 
>> via the seasons skin. Equipment used: ecowitt g1100; ws90.
>> sue ecowitt.net: no problem everything is indicated. via the command.
>> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok 
>> nothing seems to be missing.
>> I don't see where in weewx.conf or skin.conf, I have to go see
>>
>

-- 
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/ba53db21-1421-4bdf-bcdb-492b71376be3n%40googlegroups.com.

[weewx-user] MQTT issues with sites hosted through cloudflare

[Kevin Crivelli]

I have been able to get MQTT to work via my local address inside my network 
however when I attempt to do this at my website https://kevinheaven.net 
which goes through cloudflare I am unable to get this to work. I had 
discovered that cloudflare does not support the ports that mqtt work 
through. I am wondering if anyone else has run into this issue and if so 
has found a work around for it. I am using a public MQTT broker hive.mq.

-- 
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/0a014d25-6dc5-432c-b53e-0d6ccc299288n%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

user "teffi" has readwrite permission

in Firefox inspect error console there are no errors wrt websocket or
javascript errors ... (only errors with geolocation & uncaught type error
in context with windy.com)



On Mon, Jul 24, 2023 at 5:04 PM Jacques Terrettaz 
wrote:

> Another point to check :
>
> Please verify in your mosquitto acl file (/etc/mosquitto/acl) that the
> user "teffi" has read permission for the topic "weather"
>
> Le 24 juil. 2023 à 16:40, Stefan Gliessmann 
> a écrit :
>
> Thanks, Jaques!
>
> wrt
> *1)  when opening your website from local network :  your mqtt broker is
> using port 9001 for websockets. If it doesn't works , you may have to
> verify that this port 9001 is not blocked by a firewall.  *
> 9001 is not blocked by the firewall on 192.168.178.190
> I can receive the via 9001 on my iPhone with an Matt client the values
>
> *2)  when opening your website from internet (http://weewxhi.de
> ) .i.e outside your local network
> :  mqtt_websockets_host = 192.168.178.190  is a local network IP address
> that cannot be accessed from outside. You should use  a dynamic dns service
> (no-ip, dyndns or other) to create a redirection from internet to your mqtt
> broker, and configure your router and firewall accordingly.*
> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
>
> Unfortunately, it continues to say "Connected. Waiting for data."
>
> Does a Belchertown config file override weewx.conf settings somewhere?
>
>
> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz 
> wrote:
>
>> Two things to consider :
>>
>>
>> 1)  when opening your website from local network :  your mqtt broker is
>> using port 9001 for websockets. If it doesn't works , you may have to
>> verify that this port 9001 is not blocked by a firewall.
>> 2)  when opening your website from internet (http://weewxhi.de) .i.e
>> outside your local network :  mqtt_websockets_host = 192.168.178.190  is
>> a local network IP address that cannot be accessed from outside. You should
>> use  a dynamic dns service (no-ip, dyndns or other) to create a redirection
>> from internet to your mqtt broker, and configure your router and firewall
>> accordingly.
>>
>>
>>
>>
>> Le 24 juil. 2023 à 15:06, Stefan Gliessmann 
>> a écrit :
>>
>> Thank you for the feedback.
>> I changed "localhost" to the IP of the MQTT broker as suggested.
>> It did not fix it ...
>>
>> As far as I understand that section is for uploading weewx data to the
>> mqtt broker.
>> That part works well as I can read the weather with an mqtt client.
>>
>> It is the Belchertown skin part which connects to the MQTT Brocker with
>> websocket, but it cannot receive data for updates ...
>>
>> I am really puzzled ...
>>
>> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> it doesnt work with localhost. Think, you start your Browser localy so
>>> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>>>
>>> From My weewx config (the MQTT part). Think i configured my mqtt and
>>> Webssite with https.
>>>
>>> ##weewx.conf#
>>> [[MQTT]]
>>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
>>> topic = weather
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> log_success = False
>>> log_failure = True
>>> [[[tls]]]
>>> tls_version = tlsv12
>>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>>> [[[inputs]]]
>>> dayRain
>>> name = dayRain_mm
>>> units = mm
>>> rainRate
>>> name = rainRate_mm_per_hour
>>> units = mm_per_hour
>>>
>>> [[Belchertown]]
>>>
>>> [[[Extras]]]
>>>
>>>
>>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = gw.martenhinrichs.de
>>> mqtt_websockets_port = 9001
>>> mqtt_websockets_ssl = 1
>>> mqtt_websockets_topic = weather/loop
>>>
>>>
>>>
>>>
>>>
>>> #mosquitto.conf
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>> persistence false
>>>
>>> # mqtt
>>> listener 1883
>>> listener 8883
>>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>>> protocol websockets
>>>
>>>
>>>
>>>
>>>
>>>
>>> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>>>
 Thank you all for providing input / 

Re: [weewx-user] MQTT issues with sites hosted through cloudflare

[Kevin Davis]

Do you know what ports ARE available to you?  You can change the port from
1883 in config.xml.

-Kevin

On Mon, Jul 24, 2023 at 8:20 AM Kevin Crivelli 
wrote:

> I have been able to get MQTT to work via my local address inside my
> network however when I attempt to do this at my website
> https://kevinheaven.net which goes through cloudflare I am unable to get
> this to work. I had discovered that cloudflare does not support the ports
> that mqtt work through. I am wondering if anyone else has run into this
> issue and if so has found a work around for it. I am using a public MQTT
> broker hive.mq.
>
> --
> 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/0a014d25-6dc5-432c-b53e-0d6ccc299288n%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/CAHiQ_B34SwkhL7qJnTcSwg3WvO3Pukq3%3DXfN8111-Vj1o6rK0w%40mail.gmail.com.

[weewx-user] Re: GW1100-WS90 :Missing rainfall values

[didier belin]

You're right, I was too impatient. I hadn't really paid attention to the 
rain data, because there was none except as of today. I only modified the 
weewx.conf file and more particularly the "gw1000" part today and therefore 
had to wait for the system to receive them;
Thanks for your help
Le lundi 24 juillet 2023 à 17:19:01 UTC+2, gjr80 a écrit :

> Descriptions can help but 'it doesn't work' does not provide much to go 
> on. You say ' *I can no longer find the rainfall values in weewx*', this 
> implies that you were seeing rainfall from your WS90 appearing in WeeWX at 
> some stage? Is this correct or has it never worked? What exactly is it you 
> are not seeing? For example, 'there was 8mm of rain today but WeeWX shows 
> 0mm on the main Seasons page and the rain plot shows nothing',
>
> You are correct in that you need to add some [[field_map_extensions]] 
> entries to have WS90 rainfall data appear in the 'standard' WeeWX rain 
> related fields. When did you add these entries? Just now or some time ago? 
> If 'just now' WeeWX will not have seen any earlier WS90 rainfall so I would 
> not be surprised to see a lack of WS90 rainfall data appearing in WeeWX.
>
> On Monday, 24 July 2023 at 16:00:54 UTC+1 lang@googlemail.com wrote:
>
> did you set the piezo rain priority in your GW1100 ? (-->Rain totals --> 
> Rainfall 
> data priority --> Piezoelectric Rain Gauge)
>
> Rainfall data priority is not the issue here, WeeWX does not use (nor 
> need) the setting irrespective of what rain gauges are in use
>
> Gary 
> On Monday, 24 July 2023 at 15:38:58 UTC+1 belin@gmail.com wrote:
>
>> Despite modifying weewx.conf , as quoted in another post
>>
>>
>> weewx.conf 
>> 
>>
>> poll_interval = 20
>> # The driver to use:
>> driver = user.gw1000
>> ip_address = 192.168.X.X
>> port = 45000
>> [[field_map_extensions]]
>> rain = p_rain
>> stormRain = p_rainevent
>> rainRate = p_rainrate
>> dayRain = p_rainday
>> weekRain = p_rainweek
>> monthRain = p_rainmonth
>> yearRain = p_rainyear
>>
>> . 
>>
>> 2023-07-24 16:33:21 CEST (1690209201): 'dateTime': '1690209201', 
>> 'daymaxwind': '5.2', 'dayRain': '8.0', 'extraHumid1': '56', 'extraHumid2': 
>> '85', 'extraHumid3': '67', 'extraTemp1': '24.9', 'extraTemp2': '19.2', 
>> 'extraTemp3': '22.0', 'extraTemp9': '19.1', 'inHumidity': '65', 'inTemp': 
>> '21.9', 'leafWet1': '0', 'lightning_distance': '27', 
>> 'lightning_last_det_time': '1690191720', 'lightning_strike_count': '0', 
>> 'lightningcount': '9', 'luminosity': '36350.0', 'monthRain': '43.5', 
>> 'outHumidity': '76', 'outTemp': '19.9', 'pm2_5': '4.0', 'pm2_51_24h_avg': 
>> '2.0', 'pressure': '997.3', 'rain': '0.0', 'rainRate': '0.0', 
>> 'relbarometer': '997.3', 'soilMoist1': '41', 'stormRain': '12.1', 
>> 'usUnits': '17', 'UV': '2', 'uvradiation': '54.0', 'weekRain': '12.4', 
>> 'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch2_batt': '0', 
>> 'wh31_ch2_sig': '4', 'wh31_ch3_batt': '0', 'wh31_ch3_sig': '4', 
>> 'wh41_ch1_batt': '4', 'wh41_ch1_sig': '4', 'wh51_ch1_batt': '1.3', 
>> 'wh51_ch1_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 'windDir': '301', 
>> 'windGust': '3.2', 'windSpeed': '1.5', 'wn34_ch1_batt': '1.6', 
>> 'wn34_ch1_sig': '4', 'wn35_ch1_batt': '1.54', 'wn35_ch1_sig': '4', 
>> 'ws90_batt': '2.58', 'ws90_sig': '4', 'yearRain': '92.8'
>> Le lundi 24 juillet 2023 à 15:31:31 UTC+2, didier belin a écrit :
>>
>>> I can no longer find the rainfall values in weewx. all others are 
>>> visible via the seasons skin. Equipment used: ecowitt g1100; ws90.
>>> sue ecowitt.net: no problem everything is indicated. via the command.
>>> PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver:ok 
>>> nothing seems to be missing.
>>> I don't see where in weewx.conf or skin.conf, I have to go see
>>>
>>

-- 
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/4f4b5628-890c-48e6-8c32-6397f8fb9f04n%40googlegroups.com.

Re: [weewx-user] Weewx, Vantage Vue - without electricity

[kac...@gmail.com]

Holly Shit. 
I wrote a long answer this morning but ... it looks like I made a mistake 
:-(

To be short - my main problem was because in the Weewx database wasn't a 
record of where the max speed was. I can see it on my console (66 km/h), 
but not in my database. 
I tried to correct this manually in the database, and now I have a new 
problem. 
It will be described in its own topic :-)

On Friday, 21 July 2023 at 12:23:41 UTC+2 Greg Troxel wrote:

> "kac...@gmail.com"  writes:
>
> > Vantage Vue sensors send data to its console. It works fine, I have data 
> > which are then used by Weewx and published on the website (every 15 
> > minutes). 
> > In the last weeks, we have had many storms here and electricity is down. 
> At 
> > that time, the Vantage Vue works with batteries. With WEE_DEVICE INFO I 
> can 
> > see the interval is set to 10 (minutes?). 
> > After the electricity comes, I use WEE_DEVICE DUMP to get all data into 
> the 
> > database. But while there was a really strong wind, the results are 
> > strange. Well, not strange, but it looks like there are only some 
> records 
> > there and the wind gust are far from real. 
> >
> > How do I get better results? The main problem is the wind. There are 
> gusts 
> > and after some seconds/minutes everything can be different.
> > Changing interval? I know this uses more memory ... 
>
> My understanding is that the standard approach for archive interval is 5
> minutes, but 10 minutes is also reasonable as you get twice the time
> interval that the computer can be down wihtout data loss. IMHO there is
> nothing wrong with 10. (But I am using 5 with a VP2.)
>
> You said website 15 minutes and archive interval 10. This doesn't make
> sense; weewx naturally generates reports every archive interval.
>
> The driver should fetch the archive records and put them in the database
> automatically. You should not have to run wee_device manually.
>
> Be very careful that you have time synchronization ok on your computer.
> If it's a toy computer like a PI :-)  then make sure that
> you either have bought and installed a RTC module or that you have
> scripts to ensure that it has the correct time *before* you start weewx.
>
>
> You describe the data, but you didn't provide it or a link. Measuring
> wind seems tricky and it seems like quite a leap to conclude that the
> hardware must have measured what you expected and that the data
> processing and weewx is to blame.
>
> My wind sensor is too close to the house, and I don't worry about it.
> But I would expect that the archive record contains average wind for the
> interval and the max speed over the interval. So 10 vs 5 should only
> have less granular info, not miss gusts.
>

-- 
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/1cea9673-0734-4162-83dc-d2d3fa6f2d40n%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Jacques Terrettaz]

One point : if you have the "Connected. Waiting for data."  message, this 
indicates that the websockets connection is successful. If no further data is 
received, this may indicate that the expected topic "weather/loop" is not 
existing.

You may try to use a software such as mqtt explorer (http://mqtt-explorer.com/) 
to inspect your mqtt broker and the topics published 

> Le 24 juil. 2023 à 17:32, Stefan Gliessmann  a 
> écrit :
> 
> user "teffi" has readwrite permission
> 
> in Firefox inspect error console there are no errors wrt websocket or 
> javascript errors ... (only errors with geolocation & uncaught type error in 
> context with windy.com )
> 
> 
> 
> On Mon, Jul 24, 2023 at 5:04 PM Jacques Terrettaz  > wrote:
>> Another point to check :
>> 
>> Please verify in your mosquitto acl file (/etc/mosquitto/acl) that the user 
>> "teffi" has read permission for the topic "weather"
>> 
>>> Le 24 juil. 2023 à 16:40, Stefan Gliessmann >> > a écrit :
>>> 
>>> Thanks, Jaques!
>>> 
>>> wrt
>>> 1)  when opening your website from local network :  your mqtt broker is 
>>> using port 9001 for websockets. If it doesn't works , you may have to 
>>> verify that this port 9001 is not blocked by a firewall.  
>>> 9001 is not blocked by the firewall on 192.168.178.190
>>> I can receive the via 9001 on my iPhone with an Matt client the values
>>> 
>>> 2)  when opening your website from internet (http://weewxhi.de 
>>> ) .i.e outside your local network :  
>>> mqtt_websockets_host = 192.168.178.190  is a local network IP address that 
>>> cannot be accessed from outside. You should use  a dynamic dns service 
>>> (no-ip, dyndns or other) to create a redirection from internet to your mqtt 
>>> broker, and configure your router and firewall accordingly.
>>> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
>>> 
>>> Unfortunately, it continues to say "Connected. Waiting for data." 
>>> 
>>> Does a Belchertown config file override weewx.conf settings somewhere? 
>>> 
>>> 
>>> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz >> > wrote:
 Two things to consider :
 
 
 1)  when opening your website from local network :  your mqtt broker is 
 using port 9001 for websockets. If it doesn't works , you may have to 
 verify that this port 9001 is not blocked by a firewall.  
 2)  when opening your website from internet (http://weewxhi.de 
 ) .i.e outside your local network :  
 mqtt_websockets_host = 192.168.178.190  is a local network IP address that 
 cannot be accessed from outside. You should use  a dynamic dns service 
 (no-ip, dyndns or other) to create a redirection from internet to your 
 mqtt broker, and configure your router and firewall accordingly.
 
 
 
 
> Le 24 juil. 2023 à 15:06, Stefan Gliessmann  > a écrit :
> 
> Thank you for the feedback.
> I changed "localhost" to the IP of the MQTT broker as suggested.
> It did not fix it ...
> 
> As far as I understand that section is for uploading weewx data to the 
> mqtt broker.
> That part works well as I can read the weather with an mqtt client.
> 
> It is the Belchertown skin part which connects to the MQTT Brocker with 
> websocket, but it cannot receive data for updates ...
> 
> I am really puzzled ...
> 
> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>   > wrote:
>> Hi,
>> 
>> it doesnt work with localhost. Think, you start your Browser localy so 
>> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>> 
>> From My weewx config (the MQTT part). Think i configured my mqtt and 
>> Webssite with https.
>> 
>> ##weewx.conf#
>> [[MQTT]]
>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/ 
>> 
>> topic = weather
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = False
>> log_failure = True
>> [[[tls]]]
>> tls_version = tlsv12
>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>> [[[inputs]]]
>> dayRain
>> name = dayRain_mm
>> units = mm
>> rainRate
>> name = rainRate_mm_per_hour
>> units = mm_per_hour
>> 
>> [[Belchertown]]
>> 
>> [[[Extras]]]
>> 
>> 
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[vince]

Stefan - check your MQTT publish stanza of weewx.conf and make sure that 
you are publishing to the topic that you have Belchertown trying to 
subscribe to.

>From your first post you had a log extract saying:

Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/inHumidity_percent

So I'm wondering if you need to set Belchertown to look for "
weather/weewx/loop" rather than the typical "weather/loop"

I think you have a mismatch in what you are publishing vs. what you are 
trying to subscribe to.

On Monday, July 24, 2023 at 10:55:08 AM UTC-7 Jacques Terrettaz wrote:

> One point : if you have the "Connected. Waiting for data."  message, this 
> indicates that the websockets connection is successful. If no further data 
> is received, this may indicate that the expected topic "weather/loop" is 
> not existing.
>
> You may try to use a software such as mqtt explorer (
> http://mqtt-explorer.com/) to inspect your mqtt broker and the topics 
> published 
>
> Le 24 juil. 2023 à 17:32, Stefan Gliessmann  a 
> écrit :
>
> user "teffi" has readwrite permission
>
> in Firefox inspect error console there are no errors wrt websocket or 
> javascript errors ... (only errors with geolocation & uncaught type error 
> in context with windy.com)
>
>
>
> On Mon, Jul 24, 2023 at 5:04 PM Jacques Terrettaz  
> wrote:
>
>> Another point to check :
>>
>> Please verify in your mosquitto acl file (/etc/mosquitto/acl) that the 
>> user "teffi" has read permission for the topic "weather"
>>
>> Le 24 juil. 2023 à 16:40, Stefan Gliessmann  a 
>> écrit :
>>
>> Thanks, Jaques!
>>
>> wrt
>> *1)  when opening your website from local network :  your mqtt broker is 
>> using port 9001 for websockets. If it doesn't works , you may have to 
>> verify that this port 9001 is not blocked by a firewall.  *
>> 9001 is not blocked by the firewall on 192.168.178.190
>> I can receive the via 9001 on my iPhone with an Matt client the values
>>
>> *2)  when opening your website from internet (http://weewxhi.de 
>> ) .i.e outside your local network 
>> :  mqtt_websockets_host = 192.168.178.190  is a local network IP address 
>> that cannot be accessed from outside. You should use  a dynamic dns service 
>> (no-ip, dyndns or other) to create a redirection from internet to your mqtt 
>> broker, and configure your router and firewall accordingly.*
>> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
>>
>> Unfortunately, it continues to say "Connected. Waiting for data." 
>>
>> Does a Belchertown config file override weewx.conf settings somewhere? 
>>
>>
>> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz  
>> wrote:
>>
>>> Two things to consider :
>>>
>>>
>>> 1)  when opening your website from local network :  your mqtt broker is 
>>> using port 9001 for websockets. If it doesn't works , you may have to 
>>> verify that this port 9001 is not blocked by a firewall.  
>>> 2)  when opening your website from internet (http://weewxhi.de) .i.e 
>>> outside your local network :  mqtt_websockets_host = 192.168.178.190 
>>>  is a local network IP address that cannot be accessed from outside. You 
>>> should use  a dynamic dns service (no-ip, dyndns or other) to create a 
>>> redirection from internet to your mqtt broker, and configure your router 
>>> and firewall accordingly.
>>>
>>>
>>>
>>>
>>> Le 24 juil. 2023 à 15:06, Stefan Gliessmann  a 
>>> écrit :
>>>
>>> Thank you for the feedback.
>>> I changed "localhost" to the IP of the MQTT broker as suggested.
>>> It did not fix it ...
>>>
>>> As far as I understand that section is for uploading weewx data to the 
>>> mqtt broker.
>>> That part works well as I can read the weather with an mqtt client.
>>>
>>> It is the Belchertown skin part which connects to the MQTT Brocker with 
>>> websocket, but it cannot receive data for updates ...
>>>
>>> I am really puzzled ...
>>>
>>> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com  
>>> wrote:
>>>
 Hi,

 it doesnt work with localhost. Think, you start your Browser localy so 
 your Loca Browser try to mqqt to localhost. And there is no mwtt server.

 From My weewx config (the MQTT part). Think i configured my mqtt and 
 Webssite with https.

 ##weewx.conf#
 [[MQTT]]
 server_url = mqtt://pi:pass...@gw.martenhinrichs.de:8883/ 
 
 topic = weather
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate
 log_success = False
 log_failure = True
 [[[tls]]]
 tls_version = tlsv12
 ca_certs = /etc/ssl/certs/ca-certificates.crt
 [[[inputs]]]
 dayRain
 name = dayRain_mm
 units = mm
 rainRate
 name = rainRate_mm_per_hour

[weewx-user] Re: GW1100-WS90 :Missing rainfall values

[gjr80]

That will be it. You will see rainfall data from the GW1100/WS90 appearing 
in cumulative fields like dayRain, weekRain, monthRain and yearRain; but 
WeeWX does not record this (cumulative) data. Rather, WeeWX records the 
total rain seen per archive period. To calculate this WeeWX takes the 
difference between the value of one of these cumulative values (default is 
yearRain) at the end and start of an archive period. So whilst you might 
see rainfall data appearing in these cumulative fields, you will not see 
any WS90 rainfall data appearing in WeeWX reports until there is rainfall 
recorded (1) whilst WeeWX is running and (2) after the additional entries 
were added to [[field_map_extensions]]. 

I have been (long) working on a wiki page for Ecowitt gateway driver wiki 
that explains the handling of rainfall for the Ecowitt tipping gauges and 
the WS90, I guess I need to get that finalised and published.

Gary

On Monday, 24 July 2023 at 18:08:15 UTC+1 belin@gmail.com wrote:

You're right, I was too impatient. I hadn't really paid attention to the 
rain data, because there was none except as of today. I only modified the 
weewx.conf file and more particularly the "gw1000" part today and therefore 
had to wait for the system to receive them;
Thanks for your help

-- 
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/861c30d2-f28a-4e42-a815-a5d8b848c268n%40googlegroups.com.

Re: [weewx-user] Humidex N/A

[Invisible Man]

oh ok strange then. I must have changed it one day and forgot about it... 

On Monday, July 24, 2023 at 2:46:31 AM UTC+2 Tom Keffer wrote:

> ... and that is indeed the default. 
>
> https://github.com/weewx/weewx/blob/master/weewx.conf#L370
>
> On Sun, Jul 23, 2023 at 9:35 AM Invisible Man  
> wrote:
>
>> yes, that's what I did, and it works just great. IMHO, the default option 
>> should be "prefer_hardware" for everything. That should normally suit 
>> nearly all situations.
>>
>> -- Axelle.
>>
>> On Sunday, July 23, 2023 at 1:59:23 PM UTC+2 Tom Keffer wrote:
>>
>>> Yes. If you specify 'hardware', then WeeWX will not calculate it at all. 
>>> It depends on the value being supplied by the hardware.
>>>
>>> Usually you want "prefer_hardware". Same with the other calculations. I 
>>> would change them all.
>>>
>>> On Sun, Jul 23, 2023 at 4:07 AM Invisible Man  
>>> wrote:
>>>
 Hello Tom,

 I am using an EcoWitt HP2551 (station_type = Interceptor) and WeeWx 
 4.10.2
 In StdWXCalculate I have the following: I see that heat index is 
 expected to be provided by my hardware (which obviously doesn't). I 
 suppose 
 I can just change that to software, or prefer_hardware?

 ```
 [StdWXCalculate]
 [[Calculations]]
 # Derived quantities are calculated by this service.  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
 
 pressure = prefer_hardware
 barometer = prefer_hardware
 altimeter = prefer_hardware
 windchill = hardware
 heatindex = hardware
 dewpoint = prefer_hardware
 inDewpoint = prefer_hardware
 rainRate = hardware
 maxSolarRad = prefer_hardware
 cloudbase = prefer_hardware
 humidex = prefer_hardware
 appTemp = prefer_hardware
 ET = prefer_hardware
 windrun = prefer_hardware
 ```

 Thanks,
 Axelle
 On Friday, July 21, 2023 at 1:12:43 AM UTC+2 Tom Keffer wrote:

> For most weather stations, heat index is a derived quantity, so it 
> must be calculated in software.
>
> What kind of hardware?
>
> What version of WeeWX are you using?
>
> What is in the section [StdWXCalculate] in weewx.conf?
>
> -tk
>
>
>
> On Thu, Jul 20, 2023 at 1:39 PM Invisible Man  
> wrote:
>
>> Hi,
>>
>> My weather station has both current temperature and current humidity, 
>> but it continuously displays *N/A for humidex* (or is it heat index) 
>> ?
>>
>> My template uses this:
>> ```
>> Humidex: $current.heatindex
>> ```
>> and my `skin.conf` translates heatindex to Humidex:
>> ```
>> [[Generic]]
>> # Generic labels, keyed by an observation type.
>> barometer  = Barometre
>> dewpoint   = Point de rosee
>> heatindex  = Humidex
>> ```
>> I'm not sure I'm doing the right thing. 
>> If I query the database : 
>>
>> ```
>> sqlite> select barometer, pressure,outTemp,outHumidity,heatindex from 
>> archive where dateTime = 1689884400;
>> 1010.28419008758|998.764391620552|24.8|93.0|> heatindex from archive where dateTime = 1689884400;
>> ```
>> Notice I do have values for everything *except* heatindex (no value).
>> Why don't I have any value? How can I enable it?
>>
>> Thanks
>>
>> PS. I'm using Weewx 4.10.2 on a RPi.
>>
>>
>> -- 
>> 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/b47986e2-ae87-41c7-89c3-032447c75e59n%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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/90b5c374-f6ae-4795-842d-4e0eb43c846dn%40googlegroups.com
  
 
 .

>>> -- 
>> You recei

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being 
published
⊣GE⊢

> On 25 Jul 2023, at 5:08 am, vince  wrote:
> 
> I think you have a mismatch in what you are publishing vs. what you are 
> trying to subscribe to.

-- 
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/686A219D-75B5-431B-9044-215355744BDF%40geddy.au.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Graham Eddy]

i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus 
authentication if any
⊣GE⊢

> On 25 Jul 2023, at 11:47 am, Graham Eddy  wrote:
> 
> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** being 
> published
> ⊣GE⊢
> 
>> On 25 Jul 2023, at 5:08 am, vince  wrote:
>> 
>> I think you have a mismatch in what you are publishing vs. what you are 
>> trying to subscribe to.
> 
> 
> -- 
> 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/686A219D-75B5-431B-9044-215355744BDF%40geddy.au
>  
> .

-- 
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/749B9857-ACE8-4069-87AF-55F0BDB55EFF%40geddy.au.

[weewx-user] Belchertown on version 5.0 weewx

[Timothy LeCoq]

Going through the weewx version 5 documentation at.
https://weewx.com/docs/5.0/usersguide/installing-weewx/
Is it possible to install another skin such as Belchertown on weewx version 
5?
I don't see the wee_extension installer or am I wrong?
Thank you for weewx and all the support on this forum.

-- 
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/a53ab3b5-72dd-4b7b-a3c3-c57a3ea7b6f4n%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[Greg from Oz]

I am running V5:
https://weather.ubeaut.work/
and also
https://weather.ubeaut.work/wdc
So yes you can have more than one skin.

On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:

> Going through the weewx version 5 documentation at.
> https://weewx.com/docs/5.0/usersguide/installing-weewx/
> Is it possible to install another skin such as Belchertown on weewx 
> version 5?
> I don't see the wee_extension installer or am I wrong?
> Thank you for weewx and all the support on this forum.
>

-- 
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/b9286bfb-b191-412f-915c-1c86085a3cb4n%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[Timothy LeCoq]

Thank you for the reply
where is the wee_extension installer located to install the belchertown 
skin?
In version 4.x it was located under scripts, but I don't see the scripts 
directory.
Or am I wrong?
Thanks

On Monday, July 24, 2023 at 9:17:25 PM UTC-5 Greg from Oz wrote:

> I am running V5:
> https://weather.ubeaut.work/
> and also
> https://weather.ubeaut.work/wdc
> So yes you can have more than one skin.
>
> On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:
>
>> Going through the weewx version 5 documentation at.
>> https://weewx.com/docs/5.0/usersguide/installing-weewx/
>> Is it possible to install another skin such as Belchertown on weewx 
>> version 5?
>> I don't see the wee_extension installer or am I wrong?
>> Thank you for weewx and all the support on this forum.
>>
>

-- 
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/95e81023-e996-405b-b529-b8aa96b6cba9n%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[Greg from Oz]

Because it is in a virtual environmet: 
https://weewx.com/docs/5.0/quickstarts/pip/#install-in-a-virtual-environment
you run: source ~/weewx-venv/bin/activate (that puts you in the virtual 
environment)

If you type wee_ and hit tab twice you should see:
weectlwee_database  wee_debug wee_devicewee_import   
 wee_reports   weewxd

The commands are here in bin.
~/weewx-venv/bin

and your data is in:
~/weewx-data

I haven't used the wee_extension under V5 as I just copied all my V4 data 
configs etc to the relevant directories in V5.


On Tuesday, 25 July 2023 at 12:21:08 UTC+10 Timothy LeCoq wrote:

> Thank you for the reply
> where is the wee_extension installer located to install the belchertown 
> skin?
> In version 4.x it was located under scripts, but I don't see the scripts 
> directory.
> Or am I wrong?
> Thanks
>
> On Monday, July 24, 2023 at 9:17:25 PM UTC-5 Greg from Oz wrote:
>
>> I am running V5:
>> https://weather.ubeaut.work/
>> and also
>> https://weather.ubeaut.work/wdc
>> So yes you can have more than one skin.
>>
>> On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:
>>
>>> Going through the weewx version 5 documentation at.
>>> https://weewx.com/docs/5.0/usersguide/installing-weewx/
>>> Is it possible to install another skin such as Belchertown on weewx 
>>> version 5?
>>> I don't see the wee_extension installer or am I wrong?
>>> Thank you for weewx and all the support on this forum.
>>>
>>

-- 
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/36dab9a3-e627-400c-9589-ad479271b633n%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[Timothy LeCoq]

Thank you again,  but I am sorry to say that I do not see the wee_extension 
installer in the list that I can find. According to the belchertown install 
instructions, it seems to be required to use the wee_extension installer. 

On Monday, July 24, 2023 at 9:31:50 PM UTC-5 Greg from Oz wrote:

> Because it is in a virtual environmet: 
> https://weewx.com/docs/5.0/quickstarts/pip/#install-in-a-virtual-environment
> you run: source ~/weewx-venv/bin/activate (that puts you in the virtual 
> environment)
>
> If you type wee_ and hit tab twice you should see:
> weectlwee_database  wee_debug wee_devicewee_import   
>  wee_reports   weewxd
>
> The commands are here in bin.
> ~/weewx-venv/bin
>
> and your data is in:
> ~/weewx-data
>
> I haven't used the wee_extension under V5 as I just copied all my V4 data 
> configs etc to the relevant directories in V5.
>
>
> On Tuesday, 25 July 2023 at 12:21:08 UTC+10 Timothy LeCoq wrote:
>
>> Thank you for the reply
>> where is the wee_extension installer located to install the belchertown 
>> skin?
>> In version 4.x it was located under scripts, but I don't see the scripts 
>> directory.
>> Or am I wrong?
>> Thanks
>>
>> On Monday, July 24, 2023 at 9:17:25 PM UTC-5 Greg from Oz wrote:
>>
>>> I am running V5:
>>> https://weather.ubeaut.work/
>>> and also
>>> https://weather.ubeaut.work/wdc
>>> So yes you can have more than one skin.
>>>
>>> On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:
>>>
 Going through the weewx version 5 documentation at.
 https://weewx.com/docs/5.0/usersguide/installing-weewx/
 Is it possible to install another skin such as Belchertown on weewx 
 version 5?
 I don't see the wee_extension installer or am I wrong?
 Thank you for weewx and all the support on this forum.

>>>

-- 
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/214e437f-be6b-4e92-8d6a-f38898c4fe0cn%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[Greg from Oz]

Yes it is NOT there. Sorry I thought I saw it but that may have been on my 
V4/5 server that I kept the V4 on just in case.

I guess you just manually install the extension?

Like I said I haven't done it in V5. Good luck.

On Tuesday, 25 July 2023 at 12:46:22 UTC+10 Timothy LeCoq wrote:

> Thank you again,  but I am sorry to say that I do not see the 
> wee_extension installer in the list that I can find. According to the 
> belchertown install instructions, it seems to be required to use the 
> wee_extension installer. 
>
> On Monday, July 24, 2023 at 9:31:50 PM UTC-5 Greg from Oz wrote:
>
>> Because it is in a virtual environmet: 
>> https://weewx.com/docs/5.0/quickstarts/pip/#install-in-a-virtual-environment
>> you run: source ~/weewx-venv/bin/activate (that puts you in the virtual 
>> environment)
>>
>> If you type wee_ and hit tab twice you should see:
>> weectlwee_database  wee_debug wee_devicewee_import   
>>  wee_reports   weewxd
>>
>> The commands are here in bin.
>> ~/weewx-venv/bin
>>
>> and your data is in:
>> ~/weewx-data
>>
>> I haven't used the wee_extension under V5 as I just copied all my V4 data 
>> configs etc to the relevant directories in V5.
>>
>>
>> On Tuesday, 25 July 2023 at 12:21:08 UTC+10 Timothy LeCoq wrote:
>>
>>> Thank you for the reply
>>> where is the wee_extension installer located to install the belchertown 
>>> skin?
>>> In version 4.x it was located under scripts, but I don't see the scripts 
>>> directory.
>>> Or am I wrong?
>>> Thanks
>>>
>>> On Monday, July 24, 2023 at 9:17:25 PM UTC-5 Greg from Oz wrote:
>>>
 I am running V5:
 https://weather.ubeaut.work/
 and also
 https://weather.ubeaut.work/wdc
 So yes you can have more than one skin.

 On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:

> Going through the weewx version 5 documentation at.
> https://weewx.com/docs/5.0/usersguide/installing-weewx/
> Is it possible to install another skin such as Belchertown on weewx 
> version 5?
> I don't see the wee_extension installer or am I wrong?
> Thank you for weewx and all the support on this forum.
>


-- 
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/8fea2099-7607-4caf-a51d-30bbd52e15ban%40googlegroups.com.

[weewx-user] Re: Belchertown on version 5.0 weewx

[vince]

Version 5 has different syntax.
Try:
weectl extension install 

If you are running with a pip installation in a python virtual environment, 
you need to activate the venv before running the weectl command.  You will 
likely need to install more python modules into the venv as well (most 
likely paho-mqtt if you use websockets and MQTT to make Belchertown live).

weectl docs are at https://weewx.com/docs/5.0/utilities/weectl-extension/ 
at this moment in time.

On Monday, July 24, 2023 at 7:46:22 PM UTC-7 Timothy LeCoq wrote:

> Thank you again,  but I am sorry to say that I do not see the 
> wee_extension installer in the list that I can find. According to the 
> belchertown install instructions, it seems to be required to use the 
> wee_extension installer. 
>
> On Monday, July 24, 2023 at 9:31:50 PM UTC-5 Greg from Oz wrote:
>
>> Because it is in a virtual environmet: 
>> https://weewx.com/docs/5.0/quickstarts/pip/#install-in-a-virtual-environment
>> you run: source ~/weewx-venv/bin/activate (that puts you in the virtual 
>> environment)
>>
>> If you type wee_ and hit tab twice you should see:
>> weectlwee_database  wee_debug wee_devicewee_import   
>>  wee_reports   weewxd
>>
>> The commands are here in bin.
>> ~/weewx-venv/bin
>>
>> and your data is in:
>> ~/weewx-data
>>
>> I haven't used the wee_extension under V5 as I just copied all my V4 data 
>> configs etc to the relevant directories in V5.
>>
>>
>> On Tuesday, 25 July 2023 at 12:21:08 UTC+10 Timothy LeCoq wrote:
>>
>>> Thank you for the reply
>>> where is the wee_extension installer located to install the belchertown 
>>> skin?
>>> In version 4.x it was located under scripts, but I don't see the scripts 
>>> directory.
>>> Or am I wrong?
>>> Thanks
>>>
>>> On Monday, July 24, 2023 at 9:17:25 PM UTC-5 Greg from Oz wrote:
>>>
 I am running V5:
 https://weather.ubeaut.work/
 and also
 https://weather.ubeaut.work/wdc
 So yes you can have more than one skin.

 On Tuesday, 25 July 2023 at 12:06:07 UTC+10 Timothy LeCoq wrote:

> Going through the weewx version 5 documentation at.
> https://weewx.com/docs/5.0/usersguide/installing-weewx/
> Is it possible to install another skin such as Belchertown on weewx 
> version 5?
> I don't see the wee_extension installer or am I wrong?
> Thank you for weewx and all the support on this forum.
>


-- 
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/8b02366e-281f-488e-b8e9-674eb01be3den%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[vince]

If Stefan would just post his MQTT and Belchertown stanzas from weewx.conf 
we could cut to the chase here and just tell him where things aren't 
configured correctly

On Monday, July 24, 2023 at 6:52:05 PM UTC-7 Graham Eddy wrote:

> i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus 
> authentication if any
> *⊣GE⊢*
>
> On 25 Jul 2023, at 11:47 am, Graham Eddy  wrote:
>
> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** 
> being published
> *⊣GE⊢*
>
> On 25 Jul 2023, at 5:08 am, vince  wrote:
>
> I think you have a mismatch in what you are publishing vs. what you are 
> trying to subscribe to.
>
>
>
> -- 
> 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/686A219D-75B5-431B-9044-215355744BDF%40geddy.au
>  
> 
> .
>
>
>

-- 
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/69df8811-a11e-46b7-aea6-7901f49dd0fdn%40googlegroups.com.

[weewx-user] Max results - where there they come from?

[kac...@gmail.com]

I had some problems with connections and also physical shocks on sensors. 
So, I stopped the Weewx service, copy the file /var/lib/weewx/weewx.sdb to 
my PC. I opened it with SQLiteDatabaseBrowser and change some extreme 
(unreal) results. For example wind and also rainRate which was caused by 
the son's ball :-)
After that, I copy the file back onto my server and start the Weewx service 
again. 
Now some changes are properly shown (for example in graphs), but the max 
results are old (unreal). I don't understand how this is calculated. I even 
tried "xstats" and it also shows old (unreal) max results. I checked again 
in the database and there are no old results there. 

Any idea how to get rid of "unreal" results which should not apear in the 
database (and AFAIK they are not there anymore)?

Here is the monthly graph where (for example) where we can see wind (VETER) 
max on the 18th and 19th of July. It was 65 km/h:
https://izo.amebis.si/belchertown/graphs/?graph=month

Here is a summary where the max wind for July 2023 is 50 km/h:
https://izo.amebis.si/belchertown/

It is similar to the rain rate. Max is 13107.0 mm/hr (unreal and I can't 
find this result in the database (I sorted the rain rate column, tried to 
check for the particular time ... there is no such data anymore). 

Regards.

-- 
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/755e9139-02ef-47e0-93c9-94c604411f74n%40googlegroups.com.

[weewx-user] Re: Max results - where there they come from?

[michael.k...@gmx.at]

The values are in the "archive_day_*" tables in the database. These tables 
contain a dateTime values,  min and max values as well as their exact time 
(depending on the source), sum and weighted sum values and a count. When 
you change a value in the archive table by hand, it won't show up there, 
thus not show up in any statistics in the front end, as long as you don't 
fix this in the proper way. 
See https://weewx.com/docs/latest/utilities.htm#wee_database_utility for a 
description of a tool that does it the proper way. Be aware, that some 
actions might lead to loss in precision. For instance, the "exact time" I 
mentioned before is then changed to the dateTime of the archive value, e.g. 
when you maximum gust occurred at 8:33pm using a 5 min archive_interval, it 
might happen, that after running the tool you maximum gust will be shown at 
8:35pm. Or, if your maximum temp was at 4:32pm showing 30,1°C with a single 
loop value of 30,1°C, and all other loop values were 30,0°C in that 
archive_interval, after running the tool, it might be, that your maximum 
will read as 30,0°C at 1:15pm, if that was the first interval that day, 
that had 30,0°C.

kac...@gmail.com schrieb am Dienstag, 25. Juli 2023 um 06:37:12 UTC+2:

> I had some problems with connections and also physical shocks on sensors. 
> So, I stopped the Weewx service, copy the file /var/lib/weewx/weewx.sdb to 
> my PC. I opened it with SQLiteDatabaseBrowser and change some extreme 
> (unreal) results. For example wind and also rainRate which was caused by 
> the son's ball :-)
> After that, I copy the file back onto my server and start the Weewx 
> service again. 
> Now some changes are properly shown (for example in graphs), but the max 
> results are old (unreal). I don't understand how this is calculated. I even 
> tried "xstats" and it also shows old (unreal) max results. I checked again 
> in the database and there are no old results there. 
>
> Any idea how to get rid of "unreal" results which should not apear in the 
> database (and AFAIK they are not there anymore)?
>
> Here is the monthly graph where (for example) where we can see wind 
> (VETER) max on the 18th and 19th of July. It was 65 km/h:
> https://izo.amebis.si/belchertown/graphs/?graph=month
>
> Here is a summary where the max wind for July 2023 is 50 km/h:
> https://izo.amebis.si/belchertown/
>
> It is similar to the rain rate. Max is 13107.0 mm/hr (unreal and I can't 
> find this result in the database (I sorted the rain rate column, tried to 
> check for the particular time ... there is no such data anymore). 
>
> Regards.

-- 
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/03961e5c-4026-4b72-a6d4-073fa528a2b7n%40googlegroups.com.