Paulus Schoutsen
Paulus Schoutsen
I think that the approach that MQTT is taking is fine as a solution for now: it uses an options flow and it will update data in the config entry...
From https://github.com/home-assistant/core/pull/3546#discussion_r80850910 I understand that the dev docs are wrong. The problem with making too many things optional is that it will be impossible to show a nice UI, as...
Surprisingly, up to this day, conflicting requirements have been a very small issue for us.
We already offer it partially: Integrations can already bundle and register their own panels and HTTP endpoints.
Some background on this feature: Admins can always subscribe to any event. The reason we have an allow list for non-admins is that we want to make sure that they...
Yes please pick it up :) Feel free to tag me for a review on the PR when it's up. Working on core is a lot more fun than on...
The helper I linked above takes care of that race condition.
So this proposal needs to be tailored down a lot. - If a device has a unique ID, we should use that. - If a device has an IP address,...
Another alternative is that if there is no unique ID, we require integrations to import the config into a config entry so that the config entry ID can be used.
If no unique ID available, make it use the config entry id.