MQTT configuration is now in a dict for easier management

[andreasbrett]

Improved usability for configuring the MQTT component based on a comment in the blog post mentioned here #1353 (reply in thread). Settings are now in a dict that allows commenting out unused configuration parameters (like e.g. mqttCA, mqttCert, mqttKey).

Thanks @splitti for the blog post and the hint that this could be improved.

Note: this is branched off of the to-be-merged #1496. Hope both can be merged in the upcoming 2.4 release.

[pabera]

@andreasbrett Would you also develop the MQTT extension for future3? 🤓

[andreasbrett]

Yes, this is on my list. Will wait a moment until futur3 is a bit less alpha though. Shouldn't be too many modifications but I only want to do it once the code base is more stable.

[ghost]

Yes, this is on my list. Will wait a moment until futur3 is a bit less alpha though. Shouldn't be too many modifications but I only want to do it once the code base is more stable.

Great! In Future3 we already have a Publisher Concept for immediate status publishing. No polling involved. So, the only thing a MQTT must do is listen to the publisher and translate the publish messages into the MQTT format. Vice versa for commands from MQTT to RPC. So this is a fair change from the Version 2. Still, it will be relatively easy to integrate. The hard question will be whether to support the "old" MQTT topic names or switch to the topic names of the new Publisher. Once you want to start, feel free to drop me a message in the chat. I could point you to a good starting point (if needed).

[MiczFlor]

Hi @andreasbrett
there is one conflict in this pull request now:

                # publish event "card_swiped"
<<<<<<< patch-5
                client.publish(config.get("mqttBaseTopic") + "/event/card_swiped", payload=cardid)
=======
                client.publish(mqttBaseTopic + "/event/card_swiped", payload=cardid)
>>>>>>> develop
                print(" --> Publishing event card_swiped = " + cardid)

[andreasbrett]

Hi @andreasbrett there is one conflict in this pull request now:

                # publish event "card_swiped"
<<<<<<< patch-5
                client.publish(config.get("mqttBaseTopic") + "/event/card_swiped", payload=cardid)
=======
                client.publish(mqttBaseTopic + "/event/card_swiped", payload=cardid)
>>>>>>> develop
                print(" --> Publishing event card_swiped = " + cardid)

@MiczFlor this should be fine now

[MiczFlor]

Merging -- but I can't test it myself... :) sorry...