core: Daikin breaking changes - renaming devices
The problem
The Daikin integration has some breaking changes with 2023.6.0b.
The upgrade creates new devices and markes the legacy devices as unavailable.
https://discord.com/channels/330944238910963714/427516175237382144/1113968404311842929
Daikin integration behaving poorly in beta:
added new devices with new names, replacing old devices which are no longer available - breaking change added weird switches to the new devices.
I only have one device upstairs and one downstairs but it is now showing two upstairs and two downstairs.
Old device was named: climate.daikin_ap33073 New device named: climate.downstairs
What version of Home Assistant Core has the issue?
core-2023.6.b.1
What was the last working version of Home Assistant Core?
core-2023.5
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Daikin
Link to integration documentation on our website
https://rc.home-assistant.io/integrations/daikin
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2023-06-02 09:13:21.275 DEBUG (MainThread) [pydaikin.daikin_base] Updating ['aircon/get_sensor_info', 'aircon/get_control_info', 'aircon/get_zone_setting']
2023-06-02 09:13:21.788 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,err=0,htemp=-,otemp=-
2023-06-02 09:13:21.899 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,pow=0,mode=1,operate=1,bk_auto=2,stemp=23,dt1=23,dt2=24,f_rate=5,dfr1=5,dfr2=5,f_airside=0,airside1=0,airside2=0,f_auto=0,auto1=0,auto2=0,f_dir=0,dfd1=0,dfd2=0,filter_sign_info=0,cent=0,en_cent=0,remo=2
2023-06-02 09:13:22.020 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,zone_name=-%3b-%3b-%3b-%3b-%3b-%3b-%3b-,zone_onoff=0%3b0%3b0%3b0%3b0%3b0%3b0%3b0
2023-06-02 09:12:23.856 DEBUG (MainThread) [pydaikin.daikin_base] Updating ['aircon/get_sensor_info', 'aircon/get_control_info', 'aircon/get_zone_setting']
2023-06-02 09:12:23.985 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,err=0,htemp=-,otemp=-
2023-06-02 09:12:24.100 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,pow=1,mode=1,operate=1,bk_auto=2,stemp=23,dt1=23,dt2=24,f_rate=5,dfr1=5,dfr2=5,f_airside=0,airside1=0,airside2=0,f_auto=0,auto1=0,auto2=0,f_dir=0,dfd1=0,dfd2=0,filter_sign_info=0,cent=0,en_cent=0,remo=2
2023-06-02 09:12:24.212 DEBUG (MainThread) [pydaikin.daikin_airbase] Parsing ret=OK,zone_name=%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d,zone_onoff=0%3b0%3b0%3b0%3b0%3b0%3b0%3b0
Additional information
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 27 (20 by maintainers)
Would need to ve careful with this, as other parts of the world such as ours does not use airbase. We use daikin mobile controller.
I think I have found the issue, on init the Airbase class isn’t updating common/basic_info which has the device name. https://bitbucket.org/mustang51/pydaikin/pull-requests/66
@balloob @fredrike I have found the problem in pydaikin. I have created a pull request which solves this issue https://bitbucket.org/mustang51/pydaikin/pull-requests/63
It gets the name field from /skyfi/common/basic_info so will work with other apps too. By default it is the same as the ssid. The issue was introduced by #35767
The naming should be the same as the airbase app which is not working. I am currently working on a fix.
Same issue as Purcell. First it broke my automation because of previous changes had to manually fix this one and this from 2023.06.2 ruined it again
I don’t know if it’s related, but since upgrading and reconfiguring my units after deleting everything following that duplication issue, now my daily energy usage doesn’t get populated. Just sits at zero.
I’ll build a new version in a few hours…