MQTT Data Setup/Config

[gary-hammer]

I like the skin, but I'm lost in how to setup my MQTT data for this skin.
I did take a quick look at the skin.conf, but get lost in the MQTT details.

[mKainzbauer]

I'v added a wiki page https://github.com/brewster76/fuzzy-archer/wiki/MQTT-setup
Does it help you? Let me know how I can improve it.

[gary-hammer]

I attempted to edit skin.conf for live data.
I get a failure from the report generator:
Mar 07 06:05:16 wx-tab weewxd[2774]: weewx[2774] ERROR weewx.reportengine: Failed to read skin configuration file /home/wx/weewx-data/skins/Bootstrap/skin.conf for report 'Bootstrap': Parsing failed with several errors. First error at line 712. Mar 07 06:05:16 wx-tab weewxd[2774]: weewx[2774] ERROR weewx.reportengine: Syntax error: Parsing failed with several errors. First error at line 712. Mar 07 06:05:16 wx-tab weewxd[2774]: weewx[2774] ERROR weewx.reportengine: **** Report ignored

This is the line, looks like that name can't be used.
[[windSpeed]]

[mKainzbauer]

When parsing fails, there is a more basic error with the config file. Probably anything dangling or missing like a bracket [ or so.
If you copied it from the wiki, maybe it's caused by a mistake in the instructions. We'll figure it out. Can you post your skin.conf please?

[gary-hammer]

There is a duplicate at line 665 as well.
Didn't know which should be left in the file. If I comment this one out, then I get the error at 712.
Attaching as skin.conf.txt

skin.conf.txt

[mKainzbauer]

See the attachment for a working sin.conf, containing the edit I assume you wanted to make. Diff it with the old version, to see what I have changed.
skin.conf.txt

[gary-hammer]

Do I need to edit skin.conf directly or can I use weewx.conf?
skin.conf will be overwritten with any skin update whereas weewx.conf will not.

[mKainzbauer]

My bad, only weewx.conf is backed up, that's correct. I guess it is possible to do the same for skin.conf with the installer. Anyway, I don't want to put skin specific stuff in the weewx.conf file. Settings from there are overridden by the skin's settings, then by the setting in the language file. Especially when you customize templates and other things, I'd go the forking way. Then. you can version control your customization.

[gary-hammer]

The skins I have used use settings from weewx.conf, then skin.conf
It's the only way that you can configure your personalized settings in weewx.conf and have them take effect.

I'd guess there may be a few people who would want to fork a repo to have settings they wish, but very few.

[mKainzbauer]

For me, I don't know how to solve that. Letting the installer augment the settings to weewx.conf, they will be overwritten by the next istall. Yes, there is an automatic backup, but still.
Messing up weewx.conf with skin specific stuff is something I'd like to avoid.
Settings in lang/xx.conf override settings in skin.conf override settings in weewx.conf. After all, you have a whole, big mess of distributed configurations that are easy to get lost in.
I'll check, if i can make a backup of the skin.conf on install.

Anyway, I enourage anyone, who is a little bit familiar with git, to fork and version control his own skin customization.

Fork => update fork master with sync fork
Branch fork master and deploy from this branch
Cherry pick from forked master into your deploy branch
wee_extesion -- install <your_deploy_branch.zip>

[gary-hammer]

I think you have a misconception about what I asked and also how weewx processes skins.
What I asked is if I can put my customization (in this case the MQTT setup) in the skin's stanza in weewx.conf
Not the entire skin config.
Then, when you have a skin update, those changes will not be lost.
Check this for how the skin info is processed by weewx.
https://weewx.com/docs/customizing.htm#Processing_order
It is just the opposite of what you state.

I have not lost any skin or driver config in 10 years of running weewx.
There is no skin that does a backup of its files and I don't think it is possible. Especially with the new pip method of install with version 5 of weewx.

As for me, I'm a simple user. I have a skin I'd like to use. I download the zip, wee_extension, edit weewx.conf for my install, restart weewx, done.

Why would I want to go through the git process to install and update a skin that needs me to add my local, unique config?

[mKainzbauer]

Ah, OK... you are right, thank you for pointing that out. I wasn't aware of the exact details.

So: yes, just go for it and configure your weewx.conf like

[StdReport]
    ...
    [[Bootstrap]]
        skin = Bootstrap
        lang = en
        enable = true
        [[[JSONGenerator]]]
            [[[[MQTT]]]]
                [[[[[connections]]]]]
                    [[[[[[public_mqtt]]]]]]
                        broker_connection = ws://wx-lan:9001
                        [[[[[[[topics]]]]]]]
                            [[[[[[[[weather/loop]]]]]]]]

I'll point out this possibility in the howto. It is working with the skin as is.

So, why going to the git process? If you customize stats, history tables, history colors, templates, languages, units overrides in languages (that's what many users do, every single thing) it is very easy to get lost without version control. And putting all this into weewx.conf - my personal opinion - is not an option, not to mention it isn't possible for customized templates.

If you just use the "vanilla" skin, I agree, no need of version control.

[gary-hammer]

No, I edited the skin.conf I'll post it in about 2 hours.

…

On Tue, Mar 7, 2023, 6:42 AM mKainzbauer ***@***.***> wrote: When parsing fails, there is a more basic error with the config file. Probably anything dangling or missing like a bracket [ or so. If you copied it from the wiki, maybe it's caused by a mistake in the instructions. We'll figure it out. Can you post your skin.conf please? — Reply to this email directly, view it on GitHub <#91 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADCEBJNTW7HM5WBZD4XSECLW24NI3ANCNFSM6AAAAAAVQQXNLY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gary-hammer]

Ok, with your corrected skin.conf no errors when run.
Where was the issue?
It wasn't obvious during a quick comparison.

[mKainzbauer]

I didn't analyze it thoroughly, but the duplicate [LiveGauges] section was for sure a problem. Other than that it might be, that ist was an issues with the white spaces, but I don't know exactly whats the impact when using ConfigObj (the Software that is used parsing the config files).

[Ecloud44]

Hi ,
Ihave enable MQTT service ,i follewed https://github.com/brewster76/fuzzy-archer/wiki/MQTT-setup

But something wrong in my side , i don"t understand

See bellow my setup , My MQTT server work for with the belchertown skin
Any ideas
Regards
Remy

weewx.conf

[[MQTT]]

    server_url = mqtt://myuser:password:@localhost:1883/
    topic = weather
    unit_system = METRIC
    binding = archive, loop
    aggregation = aggregate

I have enable ssl encryption

[[Bootstrap]]
skin = Bootstrap
enable = true
lang = fr
HTML_ROOT = /var/www/html/Bootstrap

Skin.conf

[JSONGenerator]
enabled = true
timespan = 27
[[MQTT]]
[[[connections]]]
[[[[public_mqtt]]]]
broker_connection = wss://myweatherstation.fr:9001 # wss (encrypted) websocket connection
[[[[[topics]]]]]
[[[[[[weather/loop]]]]]]
type = JSON

Change payload_key to METRIC

[[outTemp]] #choose weewx field name
#gaugeName = My custom name # optional, default is the obs_type's label. Not translated.
payload_key = outTemp_C # outTemp_C if target_unit 'METRICWX', or 'METRIC'
minvalue = 0
maxvalue = 100
splitnumber = 10 # choose a splitnumber fitting minvalue and maxvalue: e.g.: 0/100: 10, for -20/40: 6
lineColor = '#428bca', '#b44242' # colors are RGBa
lineColorUntil = 32, maxvalue # color from start of gauge to value, change color of gauge ring to show important marks: 32 is f>
decimals = 1 # decimals for current value in gauge

[mKainzbauer]

First of all, I'd recommend not to change skin.conf, override any customization you make in weewx.conf. It makes updating easier.

Second, you need to publish data to the the same server in the backend as in the front end, having configured locathost in the backen and myweatherstation.fr will not work (unless you forward the data in a way I don't know to the public server)

Third, does the public server need a user and a password? If so, you need to provide it. Take into consideration, that these credentials are exposed to the front end, so configure a read-only user for that purpose only.

The section in weewx.conf should read like

[StdReport]
    
  
    [[WhateverYouChoseForYourSkin]]

        
        [[[JSONGenerator]]]
            
            [[[[MQTT]]]]
                [[[[[connections]]]]]
                    [[[[[[my_mqtt_with_public_tokens]]]]]]
                        broker_connection = wss://myweatherstation.fr:9001 # wss (encrypted) websocket connection
                        mqtt_username = your_username
                        mqtt_password = your_password
                        [[[[[[[topics]]]]]]]
                            [[[[[[[[weather/loop]]]]]]]]
                                type = JSON

[Ecloud44]

Hi ,
I am sorry ,I followed you recommendation ,but it doesn't work

I remove customization in skin.conf . My server ip address 192.168.3.150 .

the most strang think , it's working for Belchertown !
I have one server MQTT for two skin , it is a problem ?

Thank for your time

Regards
Remy

see bellow my weewx.conf

Weewx.conf

[StdRESTful]

[[MQTT]]

    server_url = mqtt://myuser:mypassword@localhost:1883/
    topic = weather
    unit_system = METRIC
    binding = archive, loop
    aggregation = aggregate


[[Bootstrap]]
    skin = Bootstrap
    enable = true
    lang = fr
    HTML_ROOT = /var/www/html/Bootstrap

#****************************************
[[[JSONGenerator]]]
[[[[MQTT]]]]
[[[[[connections]]]]]
[[[[my_mqtt_with_public_tokens]]]]
broker_connection = wss://192.168.3.150:9001
mqtt_username = myuser
mqtt_password = mypassword
[[[[[topics]]]]]
[[[[[[weather/loop]]]]]]
type = JSON
#*******************************************

[mKainzbauer]

I don't know how Belchertown is dealing with MQTT configuration, but one thing is for sure: if you configure weewx to publish to a local MQTT server and configure Bootstrap to subscribe a public MQTT server and there is no other connection between those two, it cannot work. And if you configure a local IP, it can only work on the local network.

Are you sure the local ip, port and wss is correct? What does the browser console say? What kind of MQTT Server are you using locally? Is it configured for ws(s)?

[Ecloud44]

My server MQTT is mosquitto in my DMZ
i followed french guide to install it
https://momh.fr/mosquitto-un-broker-mqtt
That all , i can't say more .

[mKainzbauer]

Does your mosquitto.conf contain these lines?

listener 9001 0.0.0.0
protocol websockets

What about the console log after a refresh in the browser?

[Ecloud44]

there you go

websockets

listener 9001
certfile /etc/ssl/inodes.fr_ssl_certificate.cer
keyfile /etc/ssl/_.inodes.fr_private_key.key
protocol websocket

[Ecloud44]

Hi ,
I have modify : listener 9001 0.0.0.0 in mosqitto.conf

and modify my weewx.conf

[[MQTT]]
        [[[connections]]]
            [[[[public_mqtt]]]]
                            broker_connection = wss://mypublicipdns:9001 # wss (encrypted) websocket connection
                            [[[[[topics]]]]]
            #                      # JSON topics hold their value(s) in a JSON object. Every key can be matched to a gauge/chart data>
                                  [[[[[[weather/loop]]]]]]
                                      type = JSON

Now i have a connection from LAN and Internet , before i don't have any connection

tail -f /var/log/mosquitto/mosquitto.log

1735046236: Client mqttjs_c0ce5602 closed its connection.
1735046236: New client connected from ::ffff:192.168.2.196:52354 as mqttjs_d7d1b82b (p2, c1, k60).
1735046344: New client connected from ::ffff:92.184.97.241:33638 as mqttjs_c9a668aa (p2, c1, k60).

Should be work , i will check later , now the weather is very very quiet

Thank a lot , for your time and patience
Regards
Remy

[Ecloud44]

Hi ,
Just wind direction work , i have forget something ?
Regards

[mKainzbauer]

Many possible reasons for that, one reason: wind readings might be updated more often than other readings. another reason: the payload keys from MQTT don't match. In your browser, put a breakpoint on line 74 of site.js and check the keys in the JPayload Object:

[Ecloud44]

Hi ,
You right the payload keys from MQTT don't match.
I suppose i have to modify payload key in skin.conf ?

[mKainzbauer]

You better override them in your weewx.conf. You don't have to reconfigure every gauge and chart, only what's needed to change the payload keys. If you do that in skin.conf, everything will be overwritten when you update the skin to the next version.

[Ecloud44]

please give me a example

[mKainzbauer]

What's your payload key for outTemp?

[Ecloud44]

Hi ,
my payload key is : outTemp_C

[mKainzbauer]

Using METRICWX something like that should work:

[StdReport]
    
    [[Bootstrap]]
        
        [[[LiveGauges]]]
            [[[[outTemp]]]]
                payload_key = outTemp_C
            
            [[[[barometer]]]]
                payload_key = barometer_mbar
            
            [[[[windSpeed]]]]
                payload_key = windSpeed_mps
                maxvalue = 100
                splitnumber = 5
                lineColorUntil = 75, maxvalue
            
            [[[[windGust]]]]
                payload_key = windGust_mps
                maxvalue = 160
                splitnumber = 8
                lineColorUntil = 75, maxvalue
        
        [[[LiveCharts]]]
            # This list determines which tables will appear on the week charts page, as well as in which order.
            live_chart_items = outTemp, barometer, rain, outHumidity, wind, windDir
            
            [[[[outTemp]]]]
                [[[[[outTemp]]]]]
                    payload_key = outTemp_C
                [[[[[dewpoint]]]]]
                    payload_key = dewpoint_C
            
            [[[[barometer]]]]
                [[[[[barometer]]]]]
                    payload_key = barometer_mbar
            
            [[[[rain]]]]
                [[[[[rain]]]]]
                    payload_key = rain_mm
                [[[[[p_rain]]]]]
                    plotType = bar
                    aggregateType = sum
                    aggregateInterval = 1800
                    payload_key = p_rain_mm
                    showMaxMarkPoint = false
                    showMinMarkPoint = false
                    showAvgMarkLine = false
                    lineColor = "#428bca77"
                    decimals = 1
            
            [[[[wind]]]]
                [[[[[windSpeed]]]]]
                    payload_key = windSpeed_mps
                [[[[[windGust]]]]]
                    payload_key = windGust_mps

[Ecloud44]

Thank a lot for your time
Now i have another issue , with the latest weewx.conf , it is funny

I will build another virtual machine , to test different parameters.
thank again