Error adding entities for domain select and switch
See original GitHub issueDescription
When installing the new version 4.0.2, I received 2 errors in the logs
Error adding entities for domain select with platform tapo_control
Error while setting up tapo_control platform for select
ValueError: Entity cannot be None
Error adding entities for domain switch with platform tapo_control
Error while setting up tapo_control platform for switch
ValueError: Entity cannot be None
Reproduction Steps
- Update to 4.0.2
- Reboot Home Assistant (2022.10.04)
- Validate Logs
Expected behavior
No errors
If applicable, add error logs.
Logger: homeassistant.components.select
Source: helpers/entity_platform.py:482
Integration: Select ([documentation](https://www.home-assistant.io/integrations/select), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+select%22))
Error adding entities for domain select with platform tapo_control
Error while setting up tapo_control platform for select
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 428, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 482, in _async_add_entity
raise ValueError("Entity cannot be None")
ValueError: Entity cannot be None
Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:482
Integration: Switch ([documentation](https://www.home-assistant.io/integrations/switch), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+switch%22))
Error adding entities for domain switch with platform tapo_control
Error while setting up tapo_control platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 428, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 482, in _async_add_entity
raise ValueError("Entity cannot be None")
ValueError: Entity cannot be None
Device Firmware
1.1.15 Build 211130 Rel.15378n(5553)
Using stream component
Yes
Does camera work via official integrations?
N/A
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HassOS 9.2
Search for similar issues
Yes
Additional information
I tried removing all the entities and the same issue occurs when using 4.0.2.
When rolling back to 3.7.2, no issues.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Error adding entities for domain with platform mqtt ... - GitHub
The problem Getting errors is log on startup stating: Error adding entities for domain sensor with platform mqtt Error adding entities for ......
Read more >Change entity domain? - Home Assistant Community
Is it possible to change the domain on an entity? ... Simply add the light switch template to create new light entities for...
Read more >Fidelity Pointwise On Database Entities
This command creates connectors or domains on the selected entities. Each database curve and each edge of a surface or quilt will have...
Read more >Managing custom domain names in your Azure Active Directory
Set the primary domain name for your Azure AD organization; Add ... Select the name of the domain that you want to be...
Read more >Dwains Dashboard with Mushroom Cards - How to set up
... all details 02:58 Why Areas are important 03:35 Select a theme 04:11 ... all entity cards of a specific domain 24:31 Add...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yes I saw that and they are now greyed out.
Thanks
Awesome. Tested with 4.0.3, issue is now fixed.
Thank you for your great response.