-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Configuration failed after HA core 2025.2 update #287
Comments
Good evening, I also have the same problem, it is not communicating nor am I able to make a new call from the home assistant to Hon |
Yes, same issue here after the update. |
A workaround is here. I did not need to remove and reinstall the integration, but all steps prior to that are required - including making sure you extract and install BOTH certificates as they are chained together. My device is a Hoover HWASH-500 (UK). |
Unfortunately, DS devices are no longer recognized by Home Assistant for me either after the latest update. |
Same here... :( |
Unfortunately, I have the same problem. After the update, I can no longer log in to the integration Hon |
same problem on |
Same problem Core |
Having the same problem too |
Is this project dead? |
Almost, there are a few people maintaining other forks. I suspect Haier is behind this, like last time... Refer to: |
This one is working well for my climate : https://github.com/gvigroux/hon |
Hi, after HA core 2025.2 update hOn integration no longer provides any entity. The device is recognized (including serial number and other information), but there is no usable entity. Below is the information provided in the log.
Registratore: homeassistant.helpers.typing
Fonte: helpers/deprecation.py:222
Prima occorrenza: 17:23:21 (1 occorrenze)
Ultimo accesso: 17:23:21
HomeAssistantType was used from hon, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'hon' custom integration
The text was updated successfully, but these errors were encountered: