ebusd stopped sending data to mqtt broker

[nixmeer]

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:

2025-06-01 01:15:44.566 [network error] HTTP connect: 337047686=certificate verify failed
2025-06-01 01:15:44.566 [network error] HTTP method: 336462231=shutdown while in init
2025-06-01 01:15:44.566 [main error] invalid configPath URL (connect)

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?

[Brosius18]

hello your certificate expired

[nixmeer]

I read about that in other threads but could not figure out which one. Since mosquitto_pub works, the broker seems to be fine, right?

[Brosius18]

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.

[nixmeer]

Hello again :)
When i tried to dig into renewing the CA bundle, I ran into issues with the SD card in my Pi. After all, I had to setup a new SD card and reinstall everything.