Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQTT AD - Option to globaly exclude config node #3571

Closed
MuadDibVV opened this issue Jan 31, 2024 · 9 comments
Closed

MQTT AD - Option to globaly exclude config node #3571

MuadDibVV opened this issue Jan 31, 2024 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@MuadDibVV
Copy link

Hello,

We have now all the config parameters on objects but it creates too many devices on my system (MQTT AD creations).
Is it possible to have a global parameter to avoid sending creation request for all this config parameters ?

@MuadDibVV MuadDibVV added the enhancement New feature or request label Jan 31, 2024
@robertsLando
Copy link
Member

@MuadDibVV What software is managing the MQTT discovery? Home assistant? Domoticz? Openhab?

cc @ccutrer

@apella12
Copy link
Contributor

apella12 commented Feb 1, 2024

FWIW- As a temporary workaround ; 1) From the Node Homeassistant tab I disabled all the HA-device discoveries, then enabled the ones I was using (need ZUI 9.8), put in the Store (for persistence) 2) Set the Home Assistant tab to manual discovery "saved" 3) Using MQTT explorer deleted all the homeassistant topics. 4) Back to ZUI, turn off manual discovery and hit save again.

Did this a couple of days ago, so might not remember order exactly, but you get the idea.

I also think it could be good if the config items could be disabled by default, then up to the user to add the ones that are needed

@MuadDibVV
Copy link
Author

@MuadDibVV What software is managing the MQTT discovery? Home assistant? Domoticz? Openhab?

cc @ccutrer

Domoticz

@ccutrer
Copy link
Contributor

ccutrer commented Feb 1, 2024

I would recommended opening a feature (or bug!) request with Domoticz to handle enabled_by_default: false, then. In the meantime, it doesn't seem like the worst thing in the world for zwave-js-ui to have an option to not publish enabled_by_default: false entities.

@robertsLando
Copy link
Member

It sounds to me more like an issue on Domoticz but yeah in the meanwhile I could simply skip sending publish when that is set to false in the meanwhile... maybe I could make this opt in with an env var?

@Claude2666
Copy link

Indeed. It would be nice to have a global option to disable the config topics as now they create a huge amount of extra devices, which most people have no use for. I think zwavejs-ui does an excellent job in setting up the configuration of the devices. In my case, for 99% of the settings, the defaults are used and the few other settings are set once at inclusion and never changed anymore. 

So it would be really help to have a global option to disable the config items for people who have no need for them, keeping their configuration less complex. For now, I stick to an older version of zwavejs-ui.

Thanks for this great software.

@robertsLando
Copy link
Member

Ok so I will add an env var to disable this, ok?

@apella12
Copy link
Contributor

apella12 commented Apr 3, 2024

It is possible to deal with today by using "manual discovery" and then disabling the individual HA "devices" you don't want to see, then use the discovery as needed. I'd see the value for someone who doesn't have manual discovery enabled and adds a new device with lots of configs. Having the enabled by default: false HA devices automatically disabled could save them from dealing with those devices afterward. FWIW

@Claude2666
Copy link

Indeed, an option or an environment variable to disable it would be highly appreciated. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants