Mosquitto 2.0 error after configuration

Wolfgang_S · August 10, 2022, 8:36am

This issue since OH 2.5

[binding-mqtt - 2.5.3]Broker settings Certificate/PubKey pinning

opened 10:05PM - 15 Apr 20 UTC

bug

## Expected Behavior When the options Certificate and PubKey pinning are enab…led, in the MQTT Broker settings, the fields "Certificate Hash" and "Public key Hash" should be automatically filled, and the hashes should be valid until the certificate and the key are the same. ## Current Behavior If OH is restarted, the connection with the broker shouldn't be made until you blank the fields "Certificate Hash" and "Public key Hash"; the same hashes are recreated and the connection could be estabilished. If the Certificate and PubKey pinning are disabled, everything works fine even after a reboot. ## Steps to Reproduce (for Bugs) 1. Configure MQTT Broker in OH in order to use TLS (I use Mosquitto) 2. Enable Certificate and PubKey pinning 3. The first connection should be fine 4. Reboot OH 5. Check the status of the connection between OH and the broker ## Context I was configuring OH and all the other MQTT devices in order to use TLS to connect the broker ## Your Environment * Version used: docker image openhab:latest-debian

could be the root cause of the problem as it seems not to be fixed yet.