Thx for your great hints. The weewx-mqtt configuration was correct. I was
listening to the topic weewx but if you read (AND really understand AND
follow ;-) the documentation, it is published on <topic name>/loop and <topic
name>/observation_<units>.
Here is the output of weewx/loop payload arriving every 5 minutes:
{ "dateTime": "1609226100.0", "windLinkStatus": "1.0", "windBatteryStatus":
"0.0", "rainLinkStatus": "0.0", "rainBatteryStatus": "0.0", "uvLinkStatus":
"1.0", "uvBatteryStatus": "0.0", "inTemp_C": "23.970689655172414",
"inHumidity": "38.0", "outTemp_C": "2.603448275862065", "outHumidity":
"84.0", "outTempBatteryStatus": "0.0", "outLinkStatus": "0.0",
"extraTemp1_C": "23.000000000000025", "extraHumid1": "39.0",
"extraBatteryStatus1": "0.0", "extraLinkStatus1": "0.0", "extraTemp2_C":
"21.299999999999986", "extraHumid2": "43.0", "extraBatteryStatus2": "0.0",
"extraLinkStatus2": "0.0", "extraTemp3_C": "25.165517241379295",
"extraHumid3": "65.62068965517241", "extraBatteryStatus3": "0.0",
"extraLinkStatus3": "0.0", "extraTemp4_C": "21.62068965517242",
"extraHumid4": "43.0", "extraBatteryStatus4": "0.0", "extraLinkStatus4":
"0.0", "rainTotal": "218.0166668040001", "rain_cm": "0.0",
"barometer_mbar": "948.5258620689654", "forecast": "4.0", "storm": "0.0",
"pressure_mbar": "916.376047509162", "altimeter_mbar": "947.8952290346878",
"cloudbase_meter": "582.7279829856743", "dewpoint_C": "0.1756150230575394",
"heatindex_C": "2.603448275862065", "humidex_C": "2.603448275862065",
"inDewpoint_C": "8.76924066086359", "rainRate_cm_per_hour": "0.0",
"interval_minute": "5.0", "hourRain_cm": "0.0", "rain24_cm":
"0.21166666679999935", "dayRain_cm": "0.1411111112000185", "usUnits":
"16.0" }
... the floating point number with 22 digits are little bit overkill.
Thx so much - issue closed ;-)
[email protected] schrieb am Montag, 28. Dezember 2020 um 20:47:19 UTC+1:
> A couple more things to check out.
> 1. If my memory is correct the mqtt extension publishes ‘aggregate’ (json
> format) to <topic name>/loop and individual to <topic
> name>/observation_<units>. So after the simple pub/sub test, try
> subscribing to weewx/# and see what you get.
> 2. From your log snippet you are publishing on archive record generation.
> Which from your log is 300 seconds. So, will need to wait for this to
> happen before anything will be published.
> rich
>
> On Monday, 28 December 2020 at 14:07:50 UTC-5 vince wrote:
>
>> I'd start in weewx.conf by setting debug=1 at the top, and in your MQTT
>> section set log_success=true and log_failure=true. Then restart weewx and
>> check your logs.
>>
>> A better test of your MQTT is to publish in one shell and subscribe in
>> another. Just open two windows.
>>
>> In one shell: mosquito_pub -h homeassistant.local -t weewx -u
>> mqtt-local -P <password> -m "hello world"
>> In the other: mosquito_sub -h homeassistant.local -t weewx -u
>> mqtt-local -P <password>
>>
>> You should see 'hello world' appear in the shell that is subscribing.
>>
>>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/130691f9-ce1d-41c4-891c-d0ae22848826n%40googlegroups.com.
