Replies: 2 comments 1 reply
-
hello your certificate expired |
Beta Was this translation helpful? Give feedback.
1 reply
-
it means: ebusd tried to fetch config files via HTTPS The TLS handshake failed because the SSL certificate on the server or the CA bundle in your device is outdated/missing Since it can’t fetch configs, --scanconfig fails and the whole run breaks That’s why mosquitto_pub still works — your MQTT connection is fine, but ebusd never gets that far because it aborts on the HTTPS config fetch. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
at some point in February, ebusd stopped sending information via mqtt to my broker. The command that had been working for the past 2 years is
/usr/bin/ebusd -d enh:/dev/ttyAMA0 --scanconfig --latency=10 -l /var/log/ebusd.log --log=bus:info --address=ff --accesslevel=* --mqttjson --mqttport=1883 --mqtthost=monheator.cloud --mqttuser=***** --mqttpass=***** --mqttlog --mqtttopic=whrd
now this produces the following output:
I tested the connection to the broker using
mosquitto_pub
and the same username/password which worked perfectly fine.Does anyone have a clue what's going here?
Beta Was this translation helpful? Give feedback.
All reactions