Changing the 'mqtt-convention' crashes the QA.

[alexander-vitishchenko]

Changing the 'mqtt-convention' crashes the QA.

[jandejongh]

Thanks for the explanation Alexander. I'm totally OK with the home assistant convention.
I'm stuffing data into Mosquitto, then Telegraf/InfluxDB/Grafana.
Everything works fine; HC3+QA stable as a rock.

[alexander-vitishchenko]

Hi @jandejongh!

"mqttConvention" variable is about choosing the MQTT integration type, like HC3 <-> Home Assistant, or HC3 <-> Homie.

This variable accepts only the following values at the moment:

1. "home-assistant" to enable Home Assistant MQTT - https://www.home-assistant.io/integrations/mqtt/
2. "homie" to enable POC (prove of concept) grade implementation for Homie MQTT specification - https://homieiot.github.io/
3. "debug" - placeholder for custom/developer needs in the future

So yes, "mqttConvention" does indirectly influence MQTT topic prefix, but there is no direct control given through QuickApp variable, because Home Assistant and Homie specifications force me to use "homeassistant" and "homie" prefixes respectively.

I'd suggest to stick to Home Assistant MQTT convention even if you don't use Home Assistant => it is the most comprehensive mqtt convention implementation for this QuickApp. It has some "bells and whistles" you may not need... but at the same time you can simply ignore the events/attributes you don't need.

If Home Assistant MQTT convention is something what doesn't work for you... the alternative would be to try Homie specification, as it seems to be vendor agnostic, but also the current implementation is limited in functionality. Another alternative would be to extend "debug" implementation to render all HC3 events to MQTT without any translation of the data model - simple for implementation, and rendering all the HC3 events to MQTT "as is".

Let me know your exact needs and we see what implementation approach would be the best fit.

Thank you!
Alexander

P.S.: apologies for late reply as I only finished my accommodation in Berlin

[alexander-vitishchenko]

Not a bug / expected behavior

MQTT prefixes are predefined by Home Assistant & Homie specifications. Using customer prefixes are possible with custom MQTT implementation if there is no way to rely on standard implementation