core: Daikin key error in 2023.7.2
The problem
Hi, I was having problems with the previous version that caused the zones not function. Didn’t bother me too much but since I updated to the 2023.72, the intergration fails. I’ve tried to delete the intergration and install again but it fails to setup. Also tried moving the dongle to the main network, this also does not help.
Any help is appreciated. Cheers
What version of Home Assistant Core has the issue?
2023.7.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
dakin
Link to integration documentation on our website
https://www.home-assistant.io/integrations/daikin
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.config_entries
Source: components/daikin/__init__.py:142
First occurred: 5:48:34 pm (4 occurrences)
Last logged: 5:52:41 pm
Error setting up entry 192.168.5.225 for daikin
Error setting up entry Daikin for daikin
Error setting up entry 192.168.1.225 for daikin
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 390, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/daikin/__init__.py", line 56, in async_setup_entry
await async_migrate_unique_id(hass, entry, daikin_api)
File "/usr/src/homeassistant/homeassistant/components/daikin/__init__.py", line 142, in async_migrate_unique_id
new_name = api.device.values["name"]
~~~~~~~~~~~~~~~~~^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pydaikin/values.py", line 24, in __getitem__
return self._data[key]
~~~~~~~~~~^^^^^
KeyError: 'name'
Additional information
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 4
- Comments: 28 (14 by maintainers)
@home-assistant close
@home-assistant rename Daikin key error in 2023.7.2
This particular issue is fixed in https://github.com/home-assistant/core/pull/96575.
I’ll close this and duplicate devices have to be discussed in #96809.
The update to 2023.7.3 did not fix this. I still have a duplicate device. My original device is unavailable and the duplicate appears to be working.
There does not appear to be a way to delete the older device so that I can rename the new entities.
Hopefully this will be solved with the above PR.