Implementing docker secrets, MQTT TLS connections, MQTT publishing and option to redact lat/long data

[gummigroda]

This PR will add the following features:

• Allow connection to MQTT broker with TLS enabled
• Allow connection to MQTT broker on non standard port (1883)
• Option to not sending Latitude and Longitude to ABRP
• Option to output data to a MQTT Topic of choice, including:
  • Status of the script
  • Last successful update
  • Last status
  • Last error
• Option to use Docker secrets for USER_TOKEN and MQTT_PASSWORD to prevent using sensitive data in environment variables.

[fetzu]

Hey @gummigroda, fantastic PR! Thank you very much!
I just had a few changes I wanted to make to the PR, but I'm somehow unable to publish them. Could you please enable the "allow edits" flag in the PR?

I'm also wondering what your reasoning is behind the script also publishing MQTT data itself? Do you have a specific use case in mind? (My initial concern that it would make it too confusing and create feature creep, but your implementation is light and elegant enough.)

[gummigroda]

Hi,
Edits are now allowed.

The rationale behind adding data back to MQTT is that I'm using that to trigger events when errors occur and restart the container and just monitor what data does end up in ABPR as I find that easer than parsing the output from the script.
I've no problem if this is removed from the PR, but as a default setting, this is just extra code and not a requirement.

Thanks.

[fetzu]

Thanks for your answer; I will leave it in with the small changes I made.

If it's OK with you, I'll merge this into main and wait 1–2 weeks before making a release; it will be accessible through the :beta tag for testing.

Thanks again for the great PR 🚀 !

[gummigroda]

👍 All good.