I don’t know, check the docs for each integration. If the configuration is through the ui, they do support unique_id and you don’t need to do anything. If the configuration is yaml and unqiue_id is absent, then it does not support unique_ids.
Unfortunately, this is not the case.
E.g. Scripts afaik, whyever in opposite to automation, even if created only in UI, do not have them and cannot be assigned to areas.
And yes, I only found them for templates and mqtt. But hoped, that there are already more but the doc is only not up2date.
Yes it is. It’s a requirement for config flow. If you configure the integration through the UI, each entity will have a unique_id.
If you configure the integration through yaml, typically it will not have a unique_id.
Scripts are unique as they don’t have unique_id’s.
Hm, yes, that was my point. Created via UI, but do not have it, in oposite to your rule.
Why do automation have them and/or how to assign scripts to areas in this case?
Scripts are part of the core. You asked about integrations
You can’t. I don’t know why scripts don’t have them.
No. I asked for however defined/created entities.
I want to add an area to my group.office entity. Unfortunately, this doesn’t have a unique ID.
for light groups i use the uniqiqe id in yaml and use this gui dialog (unique ID required):
I cannot set a unique ID with groups in yaml (like with lights). How can I add a area to my group.office entity?
Groups don’t accept unique_ids, so you can’t assign it an area
See:-
For something that may work using templates to add the ID’s
That won’t work for groups because it’s in the group domain. Your link is a template sensor, so that will only add a unique_id to items in the sensor domain.
it doesn’t really matter because light, cover, etc groups are configurable through the UI in 2022.4 when it releases. Only groups in the group domain won’t have a unqiue_id.
As with most problems in HA there are many answers, so I will be as specific as possible in this question.
I used YAML to connect my SWANN cameras to HA and can use them as previews and live feeds in dashboards.
Since using Dwains dashboard i found I really need to set the area each camera is in.
Because of the unique id problem HA will not allow this so how do i set the area in YAML ?
You can’t. Your entity needs a unique id.
Ok i figured out I could use pretty much the same format that I used in YAML and bring my cameras into HA with generic camera and then it would let me assign them to a room or area. Thank you for the answer and I home this helps someone else.
How do you add a reading from a sensor without an unique ID to Grafana? I’ve struggled with this before like 10 times, searched around, found an answer, forgot what it was, and started over again lol.
But admittedly, I am a real noob.
I don’t use grafana, but it has been around longer than unique ids, so there must be a way.
This is the most recent stuff I have seen on Grafana Statistics in Home Assistant with InfluxDB and Grafana - YouTube - I don’t normally encourage youtube tutorials, but perhaps worth a look.
Thanks!
I got it to work adding something like “unique_id: aaa_bbb_ccc” to the the modbus configuration.
I tried to find a solution in all the responses but it is really not clear.
I have the same problem with my Dyson air purifier hot and cool.
I added it succesfully, it worked and on a day it gave me this message:
I tried to find a way to solve it but I didn’t find it so I deleted the Dyson configuration/integration.
This worked but all entities are not gone
They are still in my list??
And as you can see I cannot do anything with them. They are in error mode and you cannot change them or delete them or whatever
When I try to add the dyson integration again, this also doesn’t work anymore.
I get this message when I want to install it:
So I have the feeling that i am completely f*cked now.
Can anyone tell me clearly what I can do please?
I am new in the whole configuration and IT business but I try to learn so please explain me the steps how to solve this.
Thank you.
Regards
Then do as it says and provide the address.
Edit: is this a custom integration? Ask on the author’s GitHub.
I’m using the Dyson integration below without those problems. This repo is a continuation of a different integration that is no longer maintained.