MQTT Asyncronous bidirectional work.

[cordelster]

@jblance I wasn't sure where anyone was at with this yet, so I went ahead and started another development and am running tests and working through it now. I need help testing out this implementation. I have completely reworked the mqtt in libs, and provided a legacy means for scripts that call it, though I don't have a means to test them all, hassd_mqtt does work, as well as sending commands and response. I'm not going to PR it though till I have had some feed back or you tell me otherwise.

https://github.com/cordelster/mpp-solar/tree/mqtt-cmdr2

Updated: link, needs testing.

Overview

The new MQTT system provides a threaded, centralized manager for all MQTT connections with support for bidirectional communication. Key features:

• Single connection per broker: Multiple devices can share the same MQTT broker connection or use different brokers
• Bidirectional communication: Devices can receive and respond(acknowledge) to commands via MQTT (json reponse).
• Thread-safe: All operations are handled in separate threads with proper synchronization.
• Automatic reconnection: Built-in reconnection logic with exponential backoff.
• Broker retention ready, automatically sends cmd_response with retention and qos 1, login with hash ID (using host, user, password) to allow sending commands with qos 1/2 plus retention.
• MQTT default wildcards are allowed.
• Allowed command list per device (regex supported).
• Lagacy MQTT configuration in SETUP plus per device override (multiple broker support).

If you run into any issues, please let me know.

[cordelster]

@jblance, This is about ready to deliver. Is there any reason that you might want to keep the libs/mqttbroker/mqttbrokerc files?
I believe I covered everything in libs/mqttbroker_legacy.py to cover the old framework in case there is any want/need, though I have everything changed to go through the manager.

[jblance]

nope, no reason to keep unwanted or unused stuff

…

On Fri, 20 Jun 2025 at 12:35, Cordel ***@***.***> wrote: @jblance <https://github.com/jblance>, This is about ready to deliver. Is there any reason that you might want to keep the libs/mqttbroker/mqttbrokerc files? I believe I covered everything in libs/mqttbroker_legacy.py to cover the old framework in case there is any want/need, though I have everything changed to go through the manager. — Reply to this email directly, view it on GitHub <#541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVKNU6IFSHBSVSRCWAXIT3ENJLJAVCNFSM6AAAAAB7BKXQ2KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJSGQ4DCNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>