Closed andrewfg closed 3 years ago
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/mqtt-strange-logger-warnings-on-oh-shutdown/121228/16
I think I may already have found a solution. I will test it for a while, and then open a Pull Request.
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/oh3-mqtt-somtimes-issues-after-starting/113104/10
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/oh3-mqtt-somtimes-issues-after-starting/113104/12
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/broken-homeassistant-mqtt-discovery/125102/8
The MQTT AbstractBrokerHandler produces erroneous logger warnings when OH is being shutdown for the EspMilight, HomeAssistant, and Homie, discovery services. The messages are either "Tried to unsubscribe .. but topic not registered at all." or "Tried to unsubscribe .. but topic not registered for listener". See logs below.
One hypothesis may be that the over-riding EspMilight, HomeAssistant, and Homie classes are implementing discovery services which are (un)subscribing their respective topics (or not), and that the overidden AbstractBrokerHandler base class is not being made aware of the success or failure of this. Or something like that :)
Homie
HomeAssistant
EspMilight