Replies: 3 comments 1 reply
-
I see that MQTTSubscribe is creating loop packets. The next thing to verify is the content of the archive records that WeeWX creates. The easiest way is to run WeeWX from the command line and look for lines that start with REC: |
Beta Was this translation helpful? Give feedback.
-
Hello rich, an thanks for your advice. From the commad line I got the following output. I can find REC, but I guess it doesn't work correctly:
Would be grateful for some further help! - Thanks and regards Daniel |
Beta Was this translation helpful? Give feedback.
-
Thanks. I see three problems.
This is because the fields only have 3
We should get the MQTTSubscribe error fixed before you ask for help with the other two. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm using the WeeWX-MQTTSubscribe extension on my first WeeWX-Server, running in a docker container. So I'm still a newbie in stuff like this.
I can aready receive data from my MQTT-Broker, but I can see no results in the Report. I use the Belchertown skin.
Did I do a wrong configuration? Here is a part of the Debug-Logs:
An here the configuration in weewx.conf:
and
So can you help me with the configuration? Did I forget something important?
I testet my setup with the "Simulator" driver. With Simulator I coud find values in the graphs on the Belchertown-Skin.
Thanks for your help in advance and best regards - Daniel
Beta Was this translation helpful? Give feedback.
All reactions