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

[kac...@gmail.com]

How I hate Google Groups. It looks like I answer only to you Michael. 
To be short - your explanation helps me a lot. Thank you. 

I have one more question. Here is how I do it now when I want to change 
something manually (for example the rain rate - which is quite often a 
problem). 

1. Stop service on Raspberry PI. 
2. Copy WEEWX.SBD to my PC and open it with DB Browser for SQLite. 
3. Using the website https://www.epochconverter.com/ find the approximate 
dateTime to find the position in the database and change the number in the 
table "archive". 
4. After your explanation from yesterday change the number in the table 
"archive_day_rainRate". 
5. Write the changes to the file and copy it back to Raspberry PI. 
6. Start the Weewx service. 

Is there any better way?

On Tuesday, 25 July 2023 at 07:45:43 UTC+2 michael.k...@gmx.at wrote:

> 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/20beccae-a7c5-402e-8e10-305ac9abb425n%40googlegroups.com.

Re: [weewx-user] Seasons skin, multiple WH51 sensors - wrong units

[paulth...@gmail.com]

Thanks Rainer!

extensions.py was indeed the missing piece I needed to get the right units.

Cheers,
Paul.

On Saturday, 22 July 2023 at 11:08:14 UTC+10 Rainer Lang wrote:

> Assuming you assign your WH51 sensors to the SoilMoist1 thru SoilMoist4 
> database fields, be via a fieldmap extension or a StdCalibrate/Corrections 
> entry in weewx.conf,
> you will also have to add some changes to extensions.py (in 
> /usr/share/weewx/user or /home/weewx  depending on your installation):
> (I also assume you are using an extended Interceptor driver for weewx to 
> read the HP2551 consol posts)
> *import weewx.units *
> *weewx.units.obs_group_dict['soilMoist1'] = 'group_percent'* 
> *weewx.units.obs_group_dict['soilMoist2'] = 'group_percent'*
>
> for each of the four available soilMoist fields in the wsview_extended 
> database schema, you will need to make such an entry
> (but only if you have another WH51 sensor) if you want their readings 
> shown in % rather than in cb
> if you have more than four WH51 (and want to save their values in the 
> database), you will either need to repurpose other not used fields in the 
> wsview_extended database schema or create additional columns in your 
> database e.g. by the help of the wee_database tool
>
> (the entry/line "*import weewx.units*"  needs to be there only once; if 
> it's already there, you don't need to add it a second time !) 
>
> weewx needs to restarted after having made the changes to extensions.py
>
> On 21.07.2023 17:07, paulth...@gmail.com wrote:
>
> I bought a HP2551 weather station to replace my old, trusty but crusty 
> WH3081.
>
> I went with the Seasons skin, because it was the only one that seemed to 
> recognise the  WH51 moisture sensor.  I followed some Internet instructions 
> to display the WH51 readings as a percentage instead of "cb"; job done.
>
> I recently bought a second WH51 sensor, and added it to weewx.conf in the 
> same way (soil_moisture_percent) as the first sensor; it stubbornly 
> displays as "cb".
>
> Any ideas?
>
> Cheers!
>
> -- 
> 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/c2587160-ce5a-4227-afff-9959e2d55a9an%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/8e4f525a-24d6-4d22-98a8-a666e068749fn%40googlegroups.com.

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

[Kevin Crivelli]

I get that in theory and I think I got close to setting that up right
before but could you give me some more details on your setup? Do you just
make like anl cname for the mqtt like mqtt.yourdnsname.com and turn off
proxy for it. Here's the thing tho, I'm using a public mqtt server. Thought
that would get around it.. I'm just confused but on the right track

On Tue, Jul 25, 2023, 9:47 PM gary@gmail.com 
wrote:

> If you read their docs/faq carefully, you will note that a ws/wss
> connection is not supported.
> I get around this by proxying all except the mqtt server. That one is the
> same server, just a different cname.
> Give that a try. It is the only 'solution' I could come up with.
>
> On Monday, July 24, 2023 at 11:49:06 AM UTC-4 Kevin Davis wrote:
>
>> 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+...@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/94e58efa-9a56-4141-9758-7ec8ecf4548bn%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/CAG3iCAyuyS4XRYTUkG%2B%2BcYO0FDjnXnUt6%3DmdFnkTvFnMJy0xBg%40mail.gmail.com.

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

[gary....@gmail.com]

If you read their docs/faq carefully, you will note that a ws/wss 
connection is not supported.
I get around this by proxying all except the mqtt server. That one is the 
same server, just a different cname.
Give that a try. It is the only 'solution' I could come up with.

On Monday, July 24, 2023 at 11:49:06 AM UTC-4 Kevin Davis wrote:

> 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+...@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/94e58efa-9a56-4141-9758-7ec8ecf4548bn%40googlegroups.com.

[weewx-user] Re: Bootstrap - MQTT Filtering

[vince]

If you use MQTTSubscribe you can ignore fields within a subscribed topic. 
 Look at the examples on the extension's github site and look for "ignore = 
true" in the example files there.

On Tuesday, July 25, 2023 at 12:12:18 PM UTC-7 michael.k...@gmx.at wrote:

No, currently filtering is not possible for messages with a JSON payload, 
at least none that I am aware of (and I am the author of this part). You 
can file an issue https://github.com/brewster76/fuzzy-archer/issues and I 
can take this as into account as a new feature for a future version. It 
makes sense to implement this feature.

I never had the need for such a feature, because I do filtering and mapping 
on the source side and I don't want to emit data from inside the house to 
the public.

-- 
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/f6e71a48-3ba6-476c-9cd0-321d3e068d92n%40googlegroups.com.

[weewx-user] Re: Bootstrap - MQTT Filtering

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

No, currently filtering is not possible for messages with a JSON payload, 
at least none that I am aware of (and I am the author of this part). You 
can file an issue https://github.com/brewster76/fuzzy-archer/issues and I 
can take this as into account as a new feature for a future version. It 
makes sense to implement this feature.

I never had the need for such a feature, because I do filtering and mapping 
on the source side and I don't want to emit data from inside the house to 
the public.


Michael schrieb am Dienstag, 25. Juli 2023 um 20:17:58 UTC+2:

> Hi,
>
> is it possible to filter the input of the data via MQTT within the 
> bootstrap skin for the live weather data?
> There are multiple MQTT sources being queried, some of the data is being 
> queried under the same name (outTemp, outHumidity, etc).
> I have entered the following under /home/weewx/skins/Bootstrap/skin.conf:
>
>
> [JSONGenerator]
> enabled = true
> timespan = 27
> [[MQTT]]
> [[[connections]]]
> public_mqtt
> broker_connection = ws://192.168.xx.xx:9001
> [topics]
>   [[weather-stat1/loop]]
>   type = JSON
>   [[weather-stat2/loop]]
>   type = JSON
>
> both stations provide partial data for the same fields via MQTT.
> I would like to exclude the input for outTemp for stat1, or define data 
> field for data field what should be processed for the bootstrap live data.
>
> In the file: /home/weewx/skins/Bootstrap/skin.conf I found the following. 
> Could be exactly what I am looking for. Unfortunately I can't get along 
> with the implementation
>
>
> #Example
> #hiveMQ_public
> #broker_connection = ws://broker.hivemq.com:8000/mqtt # 
> unencrypted websocket connection without credentials
> #[topics]
> # # topic with type plain has just the value as 
> payload, you have to specify a payload_key to match a gauge/chart dataset
> # [[example/sensor/temp]]
> # type = plain
> # payload_key = outTemp_C # matches gauge outTemp 
> and outTemp dataset in outTemp chart
> # [[example/sensor/humi]]
> # type = plain
> # payload_key = outHumidity # matches gauge 
> outHumidity and outHumidity dataset in outHumidity chart
>
>
> Is filtering of the data possible?
>
> Michael

-- 
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/87797d9b-865b-4078-bc42-a078e90271f4n%40googlegroups.com.

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

[Tom Keffer]

If your question is a general one, and not specific to the Belchertown
skin, you already have a thread going on this topic.
https://groups.google.com/g/weewx-user/c/8jmtc7RASgo/m/9WQ5vhbjAQAJ

Or, is your question specific to the Belchertown skin? In that case, I'm
not familiar enough with the skin to help you.

On Tue, Jul 25, 2023 at 8:55 AM enu...@gmail.com  wrote:

> It seems easy but i don't get it. I try with aggregate_type =
> max_ge(25,"degree_C") buy it don't work
> 
> Responder a todos
> Responder al autor
> Reenviar
>
>
> El lunes, 24 de julio de 2023 a las 16:29:10 UTC+2, enu...@gmail.com
> escribió:
>
>> 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/9de082d7-1298-4382-829d-910c8db567cdn%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/CAPq0zEBZ%3DDM7HFa29bskw%3DHd%3D-DnMcEiZcg8X-6-Bs1CwHLtMg%40mail.gmail.com.

[weewx-user] Bootstrap - MQTT Filtering

[Michael]

Hi,

is it possible to filter the input of the data via MQTT within the 
bootstrap skin for the live weather data?
There are multiple MQTT sources being queried, some of the data is being 
queried under the same name (outTemp, outHumidity, etc).
I have entered the following under /home/weewx/skins/Bootstrap/skin.conf:


[JSONGenerator]
enabled = true
timespan = 27
[[MQTT]]
[[[connections]]]
public_mqtt
broker_connection = ws://192.168.xx.xx:9001
[topics]
  [[weather-stat1/loop]]
  type = JSON
  [[weather-stat2/loop]]
  type = JSON

both stations provide partial data for the same fields via MQTT.
I would like to exclude the input for outTemp for stat1, or define data 
field for data field what should be processed for the bootstrap live data.

In the file: /home/weewx/skins/Bootstrap/skin.conf I found the following. 
Could be exactly what I am looking for. Unfortunately I can't get along 
with the implementation


#Example
#hiveMQ_public
#broker_connection = ws://broker.hivemq.com:8000/mqtt # 
unencrypted websocket connection without credentials
#[topics]
# # topic with type plain has just the value as 
payload, you have to specify a payload_key to match a gauge/chart dataset
# [[example/sensor/temp]]
# type = plain
# payload_key = outTemp_C # matches gauge outTemp 
and outTemp dataset in outTemp chart
# [[example/sensor/humi]]
# type = plain
# payload_key = outHumidity # matches gauge 
outHumidity and outHumidity dataset in outHumidity chart


Is filtering of the data possible?

Michael

-- 
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/8576fd36-de19-48e2-84d9-7f2a9fd6062an%40googlegroups.com.

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

[enu...@gmail.com]

It seems easy but i don't get it. I try with aggregate_type = 
max_ge(25,"degree_C") buy it don't work

Responder a todos
Responder al autor
Reenviar


El lunes, 24 de julio de 2023 a las 16:29:10 UTC+2, enu...@gmail.com 
escribió:

> 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/9de082d7-1298-4382-829d-910c8db567cdn%40googlegroups.com.

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

[enu...@gmail.com]

I try with aggregate_type = max_ge(25,"degree_C") buy it don't work

El lunes, 24 de julio de 2023 a las 16:29:10 UTC+2, enu...@gmail.com 
escribió:

> 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/8f4fd06e-7270-4fde-a882-2d06b86039a8n%40googlegroups.com.

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

[Timothy LeCoq]

Thank you Vince. I will look at those docs. Appreciate the help

On Monday, July 24, 2023 at 10:14:36 PM UTC-5 vince wrote:

> 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/c0c53be4-09e6-401c-993e-70981dc8c241n%40googlegroups.com.

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

[Stefan Gliessmann]

SOLVED!

[image: Screenshot 2023-07-25 at 11.44.40.png]

Thank you, Jacques, for pointing out that I had two (2) weewx to mqtt
extensions installed. 
Once I removed both and reinstalled the one from
https://github.com/matthewwall/weewx-mqtt, modified the weewx.conf
accordingly and restarted WeeWX, I had the green dot and data receiving!

I do highly appreciate your patience with me! 

Thank you all again,
Stefan


On Tue, Jul 25, 2023 at 10:35 AM Jacques Terrettaz 
wrote:

> It seems that you have 2 mqtt extensions installed :
>
> *mqtt  0.24  Upload weather data to MQTT server.*
>
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
>
> Which one is active ?
>
> Le 25 juil. 2023 à 10:25, Stefan Gliessmann 
> a écrit :
>
> the current main version 0.24
>
> sudo wee_extension --list
> Extension NameVersion   Description
> *mqtt  0.24  Upload weather data to MQTT server.*
> GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
> LAN/Wi-Fi Gateway API.
> Belchertown   1.3.1 A clean modern skin with real time streaming
> updates and interactive charts. Modeled after BelchertownWeather.com
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
> How did you grep the weather/loop mqtt message on your system?
>
>
>
> On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
> wrote:
>
>> It should look like : weather/loop. The loop topic is a json containing
>> all the data aggregated  and is apparently not generated with your setup.
>>
>> Here is an exemple of the content of a weather/loop mqtt message for my
>> station : {"dateTime": "1690272486.0", "barometer_mbar":
>> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
>> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
>> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
>> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
>> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
>> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
>> "21.668", "leafTemp2_C": "18.332", "outHumidity":
>> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
>> "125.0", "stormRain_cm": "0.3902", "stormStart":
>> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
>> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
>> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
>> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
>> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
>> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
>> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
>> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
>> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
>> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
>> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
>> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
>> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
>> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
>> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
>> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
>> "14.312901895429865", "heatindex_C": "19.1672225", "humidex_C":
>> "22.828243781966584", "inDewpoint_C": "13.129089961868337",
>> "maxSolarRad_Wpm2": "598.7311131756545", "windchill_C":
>> "19.28", "outVaporP_mbar": "16.311027360815487", "outSVP_mbar":
>> "22.343873097007513", "outMixingRatio_gram_per_kilogram":
>> "10.713127603866752", "outEquiTemp_C": "44.3435366864702", "outThetaE_C":
>> "47.69725228025629", "outHumAbs_microgram_per_meter_cubed":
>> "12085709.924432162", "sunshineThreshold_Wpm2": "413.9737112655241",
>> "sunshineDay": "53.43", "radiationISS_Wpm2": "111.0",
>> "OutTemp-1h_C": "18.332", "OutTemp-24h_C": "20.33",
>> "OutHumidity-24h": "78.0", "sunAlt": "39.25159793354046", "extraTemp4_C":
>> "19.946", "windSpeed2_kph": "4.828032", "windDir2": "123.0",
>> "windGust2_kph": "9.656064", "windGustDir2": "106.0", "wllrain_cm":
>> "0.01999878", "hourRain_cm": "0.0", "rain24_cm": "0.759953640001",
>> "usUnits": "16.0"}
>>
>>
>> What version of the weewx mqtt extension are you running ?
>>
>>
>> Le 25 juil. 2023 à 10:03, Stefan Gliessmann 
>> a écrit :
>>
>> GE - could you expand on your statement: "referenced topic not listed in
>> the topics of published messages"?
>>
>> what should mqtt_websockets_topic look like? e.g. =
>> weather/inTemp_degree_C/loop?
>>
>> TIA,
>> Stefan
>>
>> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>>
>>> referenced topic not listed in the topics of published 

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

[Stefan Gliessmann]

OMG - what did I do there?
I will first remove the MQTT 0.2.0 one.
I don't remember that installation :(

Glad, you asked me which version I run ... LOL

On Tue, Jul 25, 2023 at 10:35 AM Jacques Terrettaz 
wrote:

> It seems that you have 2 mqtt extensions installed :
>
> *mqtt  0.24  Upload weather data to MQTT server.*
>
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
>
> Which one is active ?
>
> Le 25 juil. 2023 à 10:25, Stefan Gliessmann 
> a écrit :
>
> the current main version 0.24
>
> sudo wee_extension --list
> Extension NameVersion   Description
> *mqtt  0.24  Upload weather data to MQTT server.*
> GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
> LAN/Wi-Fi Gateway API.
> Belchertown   1.3.1 A clean modern skin with real time streaming
> updates and interactive charts. Modeled after BelchertownWeather.com
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
> How did you grep the weather/loop mqtt message on your system?
>
>
>
> On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
> wrote:
>
>> It should look like : weather/loop. The loop topic is a json containing
>> all the data aggregated  and is apparently not generated with your setup.
>>
>> Here is an exemple of the content of a weather/loop mqtt message for my
>> station : {"dateTime": "1690272486.0", "barometer_mbar":
>> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
>> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
>> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
>> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
>> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
>> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
>> "21.668", "leafTemp2_C": "18.332", "outHumidity":
>> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
>> "125.0", "stormRain_cm": "0.3902", "stormStart":
>> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
>> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
>> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
>> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
>> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
>> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
>> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
>> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
>> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
>> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
>> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
>> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
>> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
>> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
>> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
>> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
>> "14.312901895429865", "heatindex_C": "19.1672225", "humidex_C":
>> "22.828243781966584", "inDewpoint_C": "13.129089961868337",
>> "maxSolarRad_Wpm2": "598.7311131756545", "windchill_C":
>> "19.28", "outVaporP_mbar": "16.311027360815487", "outSVP_mbar":
>> "22.343873097007513", "outMixingRatio_gram_per_kilogram":
>> "10.713127603866752", "outEquiTemp_C": "44.3435366864702", "outThetaE_C":
>> "47.69725228025629", "outHumAbs_microgram_per_meter_cubed":
>> "12085709.924432162", "sunshineThreshold_Wpm2": "413.9737112655241",
>> "sunshineDay": "53.43", "radiationISS_Wpm2": "111.0",
>> "OutTemp-1h_C": "18.332", "OutTemp-24h_C": "20.33",
>> "OutHumidity-24h": "78.0", "sunAlt": "39.25159793354046", "extraTemp4_C":
>> "19.946", "windSpeed2_kph": "4.828032", "windDir2": "123.0",
>> "windGust2_kph": "9.656064", "windGustDir2": "106.0", "wllrain_cm":
>> "0.01999878", "hourRain_cm": "0.0", "rain24_cm": "0.759953640001",
>> "usUnits": "16.0"}
>>
>>
>> What version of the weewx mqtt extension are you running ?
>>
>>
>> Le 25 juil. 2023 à 10:03, Stefan Gliessmann 
>> a écrit :
>>
>> GE - could you expand on your statement: "referenced topic not listed in
>> the topics of published messages"?
>>
>> what should mqtt_websockets_topic look like? e.g. =
>> weather/inTemp_degree_C/loop?
>>
>> TIA,
>> Stefan
>>
>> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>>
>>> referenced topic not listed in the topics of published messages
>>> *⊣GE⊢*
>>>
>>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>>> wrote:
>>>
>>> mqtt_websockets_topic = weather/loop
>>>
>>>
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" 

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

[Stefan Gliessmann]

https://github.com/matthewwall/weewx-mqtt

Yes, I use the one from Matthew Wall ...

I am just about to remove and reinstall it ;)

On Tue, Jul 25, 2023 at 10:29 AM Jacques Terrettaz 
wrote:

> Are you using this extension : https://github.com/michael-slx/weewx-mqtt.
> ?
>
> If yes, this extension does not generate a "loop" json topic needed by the
> Belchertown skin. In that case, you have to use the following extension :
> https://github.com/matthewwall/weewx-mqtt/tree/master
>
> Le 25 juil. 2023 à 10:03, Stefan Gliessmann 
> a écrit :
>
> GE - could you expand on your statement: "referenced topic not listed in
> the topics of published messages"?
>
> what should mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>
>> referenced topic not listed in the topics of published messages
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>> wrote:
>>
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
> 
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/89EEBE22-7B54-4AAA-89C6-BF9E60E7B00B%40gmail.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/CACXWM9QYaTTOcRBgAyk25bXzdcmgEaZk51nkwtDFGLN1jMCVAg%40mail.gmail.com.

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

[Jacques Terrettaz]

It seems that you have 2 mqtt extensions installed :

> mqtt  0.24  Upload weather data to MQTT server.
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT 
> broker

Which one is active ?

> Le 25 juil. 2023 à 10:25, Stefan Gliessmann  a 
> écrit :
> 
> the current main version 0.24
> 
> sudo wee_extension --list
> Extension NameVersion   Description
> mqtt  0.24  Upload weather data to MQTT server.
> GW10000.5.0b5   WeeWX driver for devices using the Ecowitt 
> LAN/Wi-Fi Gateway API.
> Belchertown   1.3.1 A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT 
> broker
> 
> How did you grep the weather/loop mqtt message on your system?
> 
> 
> 
> On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz  > wrote:
>> It should look like : weather/loop. The loop topic is a json containing all 
>> the data aggregated  and is apparently not generated with your setup.
>> 
>> Here is an exemple of the content of a weather/loop mqtt message for my 
>> station : {"dateTime": "1690272486.0", "barometer_mbar": 
>> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity": 
>> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672", 
>> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C": 
>> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C": 
>> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C": 
>> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C": 
>> "21.668", "leafTemp2_C": "18.332", "outHumidity": 
>> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2": 
>> "125.0", "stormRain_cm": "0.3902", "stormStart": "1690149600.0", 
>> "dayRain_cm": "0.01999878", "monthRain_cm": "3.69977435", 
>> "yearRain_cm": "35.67782352006", "dayET_cm": "0.03048", "monthET": 
>> "4.03", "yearET": "18.16", "soilMoist1_centibar": "51.0", 
>> "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0", "insideAlarm": 
>> "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0", "outsideAlarm2": "0.0", 
>> "extraAlarm1": "0.0", "extraAlarm2": "0.0", "extraAlarm3": "0.0", 
>> "extraAlarm4": "0.0", "extraAlarm5": "0.0", "extraAlarm6": "0.0", 
>> "extraAlarm7": "0.0", "extraAlarm8": "0.0", "soilLeafAlarm1": "0.0", 
>> "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0", "soilLeafAlarm4": "0.0", 
>> "txBatteryStatus": "0.0", "consBatteryVoltage_volt": "3.89", "forecastIcon": 
>> "3.0", "forecastRule": "192.0", "sunrise": "1690258020.0", "sunset": 
>> "1690312440.0", "rain_cm": "0.0", "windGust_kph": "17.702784", 
>> "windGustDir": "190.0", "pressure_mbar": "963.8859943175378", 
>> "altimeter_mbar": "1008.0216245072318", "appTemp_C": "19.08558834080051", 
>> "beaufort_count": "2.0", "cloudbase_meter": "993.9764167741055", 
>> "dewpoint_C": "14.312901895429865", "heatindex_C": "19.1672225", 
>> "humidex_C": "22.828243781966584", "inDewpoint_C": "13.129089961868337", 
>> "maxSolarRad_Wpm2": "598.7311131756545", "windchill_C": "19.28", 
>> "outVaporP_mbar": "16.311027360815487", "outSVP_mbar": "22.343873097007513", 
>> "outMixingRatio_gram_per_kilogram": "10.713127603866752", "outEquiTemp_C": 
>> "44.3435366864702", "outThetaE_C": "47.69725228025629", 
>> "outHumAbs_microgram_per_meter_cubed": "12085709.924432162", 
>> "sunshineThreshold_Wpm2": "413.9737112655241", "sunshineDay": 
>> "53.43", "radiationISS_Wpm2": "111.0", "OutTemp-1h_C": 
>> "18.332", "OutTemp-24h_C": "20.33", 
>> "OutHumidity-24h": "78.0", "sunAlt": "39.25159793354046", "extraTemp4_C": 
>> "19.946", "windSpeed2_kph": "4.828032", "windDir2": "123.0", 
>> "windGust2_kph": "9.656064", "windGustDir2": "106.0", "wllrain_cm": 
>> "0.01999878", "hourRain_cm": "0.0", "rain24_cm": "0.759953640001", 
>> "usUnits": "16.0"}
>> 
>> 
>> What version of the weewx mqtt extension are you running ?
>> 
>> 
>>> Le 25 juil. 2023 à 10:03, Stefan Gliessmann >> > a écrit :
>>> 
>>> GE - could you expand on your statement: "referenced topic not listed in 
>>> the topics of published messages"?
>>> 
>>> what should mqtt_websockets_topic look like? e.g. = 
>>> weather/inTemp_degree_C/loop?
>>> 
>>> TIA,
>>> Stefan
>>> 
>>> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
 referenced topic not listed in the topics of published messages
 ⊣GE⊢
 
> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann > 
> wrote:
> 
> mqtt_websockets_topic = weather/loop
 
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> 

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

[Jacques Terrettaz]

Are you using this extension : https://github.com/michael-slx/weewx-mqtt. ?

If yes, this extension does not generate a "loop" json topic needed by the 
Belchertown skin. In that case, you have to use the following extension : 
https://github.com/matthewwall/weewx-mqtt/tree/master

> Le 25 juil. 2023 à 10:03, Stefan Gliessmann  a 
> écrit :
> 
> GE - could you expand on your statement: "referenced topic not listed in the 
> topics of published messages"?
> 
> what should mqtt_websockets_topic look like? e.g. = 
> weather/inTemp_degree_C/loop?
> 
> TIA,
> Stefan
> 
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>> referenced topic not listed in the topics of published messages
>> ⊣GE⊢
>> 
>>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann > 
>>> wrote:
>>> 
>>> mqtt_websockets_topic = weather/loop
>> 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%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/89EEBE22-7B54-4AAA-89C6-BF9E60E7B00B%40gmail.com.

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

[Stefan Gliessmann]

Thank you, GE!
I appreciate your help. the topic was configured according the different
guides online.

On Tue, Jul 25, 2023 at 10:11 AM Graham Eddy  wrote:

> i don’t use belchertown or that mqtt driver so i don’t know the details.
> my observation is that the report belchertown seems to be waiting on topic
> ‘’weather/loop’’ (i don’t know the syntax but it’s a reasonable
> presumption), but when you printed all the messages being published, none
> had that topic → belchertown quite rightly is not reporting receiving any
> messages
> *⊣GE⊢*
>
> On 25 Jul 2023, at 6:03 pm, Stefan Gliessmann 
> wrote:
>
> GE - could you expand on your statement: "referenced topic not listed in
> the topics of published messages"?
>
> what should mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>
>> referenced topic not listed in the topics of published messages
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>> wrote:
>>
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
> --
> 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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
> 
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/87896D52-4563-457D-A539-A436ACCAEF10%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/CACXWM9QPHOb1rS4jQmcRX2g9p4O0miz79W63p6ZZcVEACXz99A%40mail.gmail.com.

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

[Stefan Gliessmann]

the current main version 0.24

sudo wee_extension --list
Extension NameVersion   Description
*mqtt  0.24  Upload weather data to MQTT server.*
GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
LAN/Wi-Fi Gateway API.
Belchertown   1.3.1 A clean modern skin with real time streaming
updates and interactive charts. Modeled after BelchertownWeather.com
MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
broker

How did you grep the weather/loop mqtt message on your system?



On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
wrote:

> It should look like : weather/loop. The loop topic is a json containing
> all the data aggregated  and is apparently not generated with your setup.
>
> Here is an exemple of the content of a weather/loop mqtt message for my
> station : {"dateTime": "1690272486.0", "barometer_mbar":
> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
> "21.668", "leafTemp2_C": "18.332", "outHumidity":
> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
> "125.0", "stormRain_cm": "0.3902", "stormStart":
> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
> "14.312901895429865", "heatindex_C": "19.1672225", "humidex_C":
> "22.828243781966584", "inDewpoint_C": "13.129089961868337",
> "maxSolarRad_Wpm2": "598.7311131756545", "windchill_C":
> "19.28", "outVaporP_mbar": "16.311027360815487", "outSVP_mbar":
> "22.343873097007513", "outMixingRatio_gram_per_kilogram":
> "10.713127603866752", "outEquiTemp_C": "44.3435366864702", "outThetaE_C":
> "47.69725228025629", "outHumAbs_microgram_per_meter_cubed":
> "12085709.924432162", "sunshineThreshold_Wpm2": "413.9737112655241",
> "sunshineDay": "53.43", "radiationISS_Wpm2": "111.0",
> "OutTemp-1h_C": "18.332", "OutTemp-24h_C": "20.33",
> "OutHumidity-24h": "78.0", "sunAlt": "39.25159793354046", "extraTemp4_C":
> "19.946", "windSpeed2_kph": "4.828032", "windDir2": "123.0",
> "windGust2_kph": "9.656064", "windGustDir2": "106.0", "wllrain_cm":
> "0.01999878", "hourRain_cm": "0.0", "rain24_cm": "0.759953640001",
> "usUnits": "16.0"}
>
>
> What version of the weewx mqtt extension are you running ?
>
>
> Le 25 juil. 2023 à 10:03, Stefan Gliessmann 
> a écrit :
>
> GE - could you expand on your statement: "referenced topic not listed in
> the topics of published messages"?
>
> what should mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>
>> referenced topic not listed in the topics of published messages
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>> wrote:
>>
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
> 
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups 

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

[Jacques Terrettaz]

It should look like : weather/loop. The loop topic is a json containing all the 
data aggregated  and is apparently not generated with your setup.

Here is an exemple of the content of a weather/loop mqtt message for my station 
: {"dateTime": "1690272486.0", "barometer_mbar": "1006.4684246818595", 
"inTemp_C": "24.218", "inHumidity": "50.0", "outTemp_C": 
"19.28", "windSpeed_kph": "8.04672", "windSpeed10_kph": "6.437376", 
"windDir": "197.0", "extraTemp1_C": "26.664", "extraTemp2_C": 
"27.22", "extraTemp3_C": "23.89", "soilTemp1_C": 
"21.668", "soilTemp2_C": "18.332", "soilTemp3_C": 
"21.668", "leafTemp1_C": "21.668", "leafTemp2_C": 
"18.332", "outHumidity": "73.0", "rainRate_cm_per_hour": "0.0", 
"UV": "1.3", "radiation_Wpm2": "125.0", "stormRain_cm": "0.3902", 
"stormStart": "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm": 
"3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm": 
"0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar": "51.0", 
"soilMoist3_centibar": "41.0", "leafWet1_count": "0.0", "insideAlarm": "0.0", 
"rainAlarm": "0.0", "outsideAlarm1": "0.0", "outsideAlarm2": "0.0", 
"extraAlarm1": "0.0", "extraAlarm2": "0.0", "extraAlarm3": "0.0", 
"extraAlarm4": "0.0", "extraAlarm5": "0.0", "extraAlarm6": "0.0", 
"extraAlarm7": "0.0", "extraAlarm8": "0.0", "soilLeafAlarm1": "0.0", 
"soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0", "soilLeafAlarm4": "0.0", 
"txBatteryStatus": "0.0", "consBatteryVoltage_volt": "3.89", "forecastIcon": 
"3.0", "forecastRule": "192.0", "sunrise": "1690258020.0", "sunset": 
"1690312440.0", "rain_cm": "0.0", "windGust_kph": "17.702784", "windGustDir": 
"190.0", "pressure_mbar": "963.8859943175378", "altimeter_mbar": 
"1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count": 
"2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C": 
"14.312901895429865", "heatindex_C": "19.1672225", "humidex_C": 
"22.828243781966584", "inDewpoint_C": "13.129089961868337", "maxSolarRad_Wpm2": 
"598.7311131756545", "windchill_C": "19.28", "outVaporP_mbar": 
"16.311027360815487", "outSVP_mbar": "22.343873097007513", 
"outMixingRatio_gram_per_kilogram": "10.713127603866752", "outEquiTemp_C": 
"44.3435366864702", "outThetaE_C": "47.69725228025629", 
"outHumAbs_microgram_per_meter_cubed": "12085709.924432162", 
"sunshineThreshold_Wpm2": "413.9737112655241", "sunshineDay": 
"53.43", "radiationISS_Wpm2": "111.0", "OutTemp-1h_C": 
"18.332", "OutTemp-24h_C": "20.33", "OutHumidity-24h": 
"78.0", "sunAlt": "39.25159793354046", "extraTemp4_C": "19.946", 
"windSpeed2_kph": "4.828032", "windDir2": "123.0", "windGust2_kph": "9.656064", 
"windGustDir2": "106.0", "wllrain_cm": "0.01999878", "hourRain_cm": "0.0", 
"rain24_cm": "0.759953640001", "usUnits": "16.0"}


What version of the weewx mqtt extension are you running ?


> Le 25 juil. 2023 à 10:03, Stefan Gliessmann  a 
> écrit :
> 
> GE - could you expand on your statement: "referenced topic not listed in the 
> topics of published messages"?
> 
> what should mqtt_websockets_topic look like? e.g. = 
> weather/inTemp_degree_C/loop?
> 
> TIA,
> Stefan
> 
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>> referenced topic not listed in the topics of published messages
>> ⊣GE⊢
>> 
>>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann > 
>>> wrote:
>>> 
>>> mqtt_websockets_topic = weather/loop
>> 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%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/9A92BF07-E68B-42F3-BB12-3CB530267CBD%40gmail.com.

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

[Graham Eddy]

i don’t use belchertown or that mqtt driver so i don’t know the details.
my observation is that the report belchertown seems to be waiting on topic 
‘’weather/loop’’ (i don’t know the syntax but it’s a reasonable presumption), 
but when you printed all the messages being published, none had that topic → 
belchertown quite rightly is not reporting receiving any messages
⊣GE⊢

> On 25 Jul 2023, at 6:03 pm, Stefan Gliessmann  
> wrote:
> 
> GE - could you expand on your statement: "referenced topic not listed in the 
> topics of published messages"?
> 
> what should mqtt_websockets_topic look like? e.g. = 
> weather/inTemp_degree_C/loop?
> 
> TIA,
> Stefan
> 
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>> referenced topic not listed in the topics of published messages
>> ⊣GE⊢
>> 
>>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann > 
>>> wrote:
>>> 
>>> mqtt_websockets_topic = weather/loop
>> 
> 
> 
> -- 
> 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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%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/87896D52-4563-457D-A539-A436ACCAEF10%40geddy.au.

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

[Stefan Gliessmann]

GE - could you expand on your statement: "referenced topic not listed in 
the topics of published messages"?

what should mqtt_websockets_topic look like? e.g. = 
weather/inTemp_degree_C/loop?

TIA,
Stefan

On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:

> referenced topic not listed in the topics of published messages
> *⊣GE⊢*
>
> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann  
> wrote:
>
> mqtt_websockets_topic = weather/loop
>
>
>

-- 
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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com.

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

[Graham Eddy]

referenced topic not listed in the topics of published messages
⊣GE⊢

> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann  
> wrote:
> 
> mqtt_websockets_topic = weather/loop

-- 
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/FEF21BDE-DF2D-4861-AEDF-BE99B8C17C39%40geddy.au.

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

[Stefan Gliessmann]

This is what I get:

teffi@weewx:~$ *mosquitto_sub -v -t "#" -h 192.168.178.190*
weather/connection_status online
weather/connection_status online
weather/dateTime_unix_epoch 1690270081
weather/inTemp_degree_C 24.2
weather/outTemp_degree_C 15.799
weather/inHumidity_percent 53
weather/outHumidity_percent 75
weather/pressure_mbar 996.7
weather/relbarometer 996.7
weather/luminosity 8013.0
weather/uvradiation 6.4
weather/UV_uv_index 0
weather/rain_cm 0.0
weather/stormRain_cm 0.35003
weather/rainRate_cm_per_hour 0.0
weather/dayRain_cm 0.0
weather/weekRain 3.8
weather/monthRain_cm 1.8103
weather/yearRain_cm 1.8103
weather/windDir_degree_compass 346
weather/windSpeed_km_per_hour 3.9600098425441494
weather/windGust_km_per_hour 5.400013421651113
weather/daymaxwind 4.1
weather/wh65_batt 0
weather/wh65_sig 4
weather/radiation_watt_per_meter_squared 63.24388318863457
weather/altimeter_mbar 1000.3356188974249
weather/appTemp_degree_C 15.463360560056334
weather/barometer_mbar 1000.2272009128795
weather/cloudbase_meter 581.6088849469353
weather/dewpoint_degree_C 11.375139081484333
weather/heatindex_degree_C 15.3938887
weather/humidex_degree_C 17.74032194160783
weather/inDewpoint_degree_C 14.004795683252373
weather/maxSolarRad_watt_per_meter_squared 496.46758917662
weather/windchill_degree_C 15.799
weather/usUnits 16

So, weewx prodcasts the weather thru the mqtt broker mosquitto :)
Yet still, Belchertown skin remains waiting for data

Here is my [StdReport] [[Belchertown]] [[[Extras]]] stanza in weewx.conf:

#--- MQTT Websockets (for Real Time Streaming) Options ---
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 = 5tefan4U
disconnect_live_website_visitor = 180

On Tue, Jul 25, 2023 at 3:52 AM 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+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 a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Scp2wA2qOw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/749B9857-ACE8-4069-87AF-55F0BDB55EFF%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/CACXWM9TFy4CPMDz%3DWpFsev9zYvMok4MJkP_2ThLnSGECXeQTtw%40mail.gmail.com.

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

[Stefan Gliessmann]

Dear Vince,

you mean something like this?


Jul 24, 2023, 1:51:16 PM (19 hours ago) 
to weewx-user
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/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 Tuesday, July 25, 2023 at 5:15:54 AM UTC+2 vince wrote:

> 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