-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Daikin integration duplicated #36635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
daikin documentation |
Same problem here with HA 111.1 |
I'm terrible sorry for this issue. As my Daikin unit doesn't support Zeroconf I implemented that support in blind. @MartinHjelmare, would it be ok to use say https://pypi.org/project/getmac/, during the zeroconf flow to resolve the hostname to a mac? The other solution would be to check if hostname is available (it might be for some units) and use that instead of mac for unique id but that would require a lot of work. |
Yes, that's ok. But be aware that getting the mac address of a host successfully depends on the network set up, and might not work in all cases. |
I don't think Zeroconf works if the network isn't set up 🙈 . |
Would be great if someone with a Zeroconf device could test: #36704 |
Below is a debug log from HA 111.1 without #36704
|
Thanks! It is as I suspected, the old discovery method is interfering with the new Zeroconf discovery. This runs the patch in a docker container: |
The problem
I have not daikin in yaml mode, removed it with 0.110, after 0.111 upgrade i see 2 new daikin integration discovered...... so i removed my configured daikin thinking a configuration issue, restarted, and now i see 4 daikin integration. 2 ignorable, 2 not ignorable.
for now fixed configuring 2 not ignorable and ignore other 2.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: