binsentsu

It seems that the data reading sequence for battery etc does not complete and somewhere hangs (unless your log snipped was not complete) The log should end with 'data reading...

Looks like position_template must be added in the discovery configuration of MqttConnector. Value must be the same as current value in value_template. I assume value_template can be left for backwards...

No problem. I will check it this weekend.

According to the docs of the mqtt library, the close event is emmitted from the upon disconnection. Do you see disconnections in your broker log also?

Your mqtt url is included within the scan device list because of using wrong command. Use: ./am43ctrl 02b62c22d6bc -d --url mqtt://192.168.178.5:1883 -u username -p password

Did you run the command through sudo?

Looks like characteristic discovery for characteristic fe51 does not return a value in your installation. You have it all the time?

Do you get any battery and position values into your mqtt broker/homeassistant? Haven't got this error a single time in 4 months log on 2 devices. Are you running on...

Hi, isn't this only useful if you would run am43ctrl on the same unit your homeassistant is running on? I noticed that the BLE range of these devices is pretty...

Sorry, but I'm not that acquainted with docker stuff. OpenMQTTGateway indeed only supports reading from BLE as far as I can see. In my opinion an ESPHome solution would be...