Every time I restart Hassio in Lovelace I get the message “entity unavailable : …name of device”
When I use the original switch, the entity gets available again.
So it seems that Hassio has to receive the signal before it’s get recognized again .
Anyone knows how to solve this ?
I use the latest version.
I thought I posted this question before , but can not find it again and did not get any reaction. So apologizing for repeating.
Whats in the yaml file? You user auto add option: true ??
Then it will automatic put IT in your unused devices. But when you want to keep it. You must copy the code of that device and past it in your yaml file. Then you Will keep it forever. Also after a reboot.
I mean that all these devices are not mine. Somebody push on the button en HA put them in de Unused Identities. When you want to use them after a reboot then you must pick up the code. And make it static in you config file. Otherwise you must push the button everytime after rebooting the system.
I am sorry, but I still don’t know what I am doing wrong.
I think I make my entities static by defining them in switches.yaml for example.
When the switches are displayed as they should be and I look in unused entities they are under switches , and after a reboot they are still there, but then
in a lovelace view I get this
This is how it should be (just an example of two of the entities)
So in what config file should I put them to stay as available device. I modify the lovelace_ui.yaml manually by the way and don’t use the configurator.
I will look to it. I have allways use the full name of the entity. This is for example a name when I look at the states of some devices . Didi it change recently ?
You don’t have a light.studeerkamer or light.schakelaar_ongebruikt therefore, your light configuration is not working, and HA can’t restore the states and so on
Thank you. I finally understand where I go wrong.
I allways thought ( and in my remembrance I used to do it that way) I could use the name as mentioned under states, in lovelace_ui as entity name.
In my previous configurations I did not add them to lights.yaml.
Never mind, it works now.
Thank you, i will try that out!
Do i have to !include the light.yaml in the configuration.yaml? When i try to do that i get an error.
Thnx again! Grtz John
i’ve got it!
al the entities i want to place in te light.yaml but i forgot - platform: rflink
automatic_add: true to type in this file. now all is in the right file and it works!! thnx again