search

zivillian / ism7mqtt

GNU General Public License v3.0
61 stars 11 forks source link

Had to downgrade from 0.16 to 0.15 #103

Closed m6w6 closed 7 months ago

m6w6 commented 7 months ago

Not sure yet what happened, but I had to donwgrade from .16 to .15

The topic tree in MQTT looks the same at a first glance, but Homeassistant stopped updating with the new version and immediately resumed after downgrading to .15

Screenshot 2024-03-24 at 22 07 38 Screenshot 2024-03-24 at 22 25 53 Screenshot 2024-03-24 at 22 29 54
zivillian commented 7 months ago

@b3nn0 fyi

b3nn0 commented 7 months ago

Hard to say much without any proper information.. logging of the addon? Discovery topics? Tried a restart of HA or the addon? 0.0.16 works just fine for me...

zivillian commented 7 months ago

@b3nn0 good to hear, that at least 50% of the installation are ok ;-)

@m6w6 can you show the full MQTT tree, the corresponding part of the homeassistant autodiscovery tree and share the logs?

zivillian commented 7 months ago

after looking closely at the mqtt explorer screenshot, it seems that there is JSON published: grafik

v0.0.16 changed the handling of the home assistant discovery id in 57082dc (#101)

@m6w6 are you running a standalone ism7mqtt, the ism7mqtt docker image or the HA Addon?

m6w6 commented 7 months ago

They definitely look different:

Screenshot 2024-03-25 at 12 27 52 Screenshot 2024-03-25 at 12 34 14

EDIT: I'm running separate homeassistant/mosquitto/ism7mqtt containers on Unraid.

alexkno79 commented 7 months ago

Reading container I assume it‘s docker based. So you may pass either the HASS-ID or set the separate + retain environment variables

zivillian commented 7 months ago

The environment variable ISM7_HOMEASSISTANT_ID is initialized as an empty string in the ism7mqtt docker container. v0.0.16 changed the behaviour to ignore empty values for ISM7_HOMEASSISTANT_ID - so if you want separate topics you need to either set the environment variable ISM7_HOMEASSISTANT_ID to a non empty value or ISM7_SEPARATE (and maybe also ISM7_RETAIN) to true.

m6w6 commented 7 months ago

After taking the last screenshots and looking at #101, I suspected it, but I just proved that -s|--separate fixes the issue for me.

I'm using command flags instead of env vars, though.

Thanks!

EDIT: ~Ugh, wait a sec...~ Nope, looks good! It's hard to tell due to the huge latency of the ISM. Is there any value in decreasing the interval setting?