Sample Config MQTT Sensors for V7 and V8 firmware incorrect

[goostincain]

Hey there. Thanks for your work.

I have been trying to get the MQTT sensors to work in Home Assistant and it wasn't working. I had to change the following to make it work for me:

From state_topic: "envoy/json"

To state_topic: "/envoy/json"

the leading slash is needed.

[vk2him]

Hey, thanks for using the addon and the message.

I can see what's happened here - someone reported a while ago that if the envoy mqtt topic starts with a leading slash, if you use mqtt explorer then the envoy topic is indented and doesn't look "logical". By removing the leading slash, it appears in the far left column as seen in this example:

If you include the slash it looks like this which is indented into a "blank" topic:

I modified the sensor templates in the readme file to remove the slash from the topic, but I didn't remove the slash from the default configuration within the add-on which caused this issue for you. Instead of modifying the sensors by adding the slash, you can remove the slash from the addon configuration :

I'll modify the readme shortly so the sensors have the slash which matches the addon configuration, as if I change the default configuration by removing the slash, it will be a breaking change for anyone who like you have sensors that require the slash.

Sorry for the hassle, cheers

[goostincain]

Sounds good, and makes sense. There’s nothing quite like banging your head on a keyboard for a slash! ;)Justin On Dec 1, 2023, at 1:41 PM, Ian Mills @.***> wrote: Hey, thanks for using the addon and the message. I can see what's happened here - someone reported a while ago that if the envoy mqtt topic starts with a leading slash, if you use mqtt explorer then the envoy topic is indented and doesn't look "logical". By removing the leading slash, it appears in the far left column as seen in this example: image.png (view on web) If you include the slash it looks like this which is indented into a "blank" topic: image.png (view on web) I modified the sensor templates in the readme file to remove the slash from the topic, but I didn't remove the slash from the default configuration within the add-on which caused this issue for you. Instead of modifying the sensors by adding the slash, you can remove the slash from the addon configuration : image.png (view on web) I'll modify the readme shortly so the sensors have the slash which matches the addon configuration, as if I change the default configuration by removing the slash, it will be a breaking change for anyone who like you have sensors that require the slash. Sorry for the hassle, cheers

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[leah-potato]

That one got me too! Should have checked here first 🤦‍♀️

[networkerict]

Argggh...... I have been troubleshooting it for 2 hours before deciding to check here. It was driving me crazy. It works now as expected.... ;-)

sigh....

[vk2him]

Sorry for the very long delay in me updating the documentation, and the frustration caused to you to fault find. I just updated the documentation so the template snow have

state_topic: "/envoy/json"