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
TargetHumidifierDehumidifierState error and most of the times I can not shut off with HA switch. #16
Comments
Hi @u20p17, What model of dehumidifier do you have. Can you also get some debug logs
The other problem the error is coming from HomeKit Accessory Protocol pyhap. If you are able to activate and get some debug logs for that library and corresponding integration, we can try to understand why. |
Hi, Now i change the log level and restarted HA. Now i get a different error before the old error:
From the NetHomePlus App it is possible to control the humidifier. |
Hi @u20p17, I have the same dehumidifier. The error above occurs while trying to discover the device via UDP, but there is no response. Can you ping it from your home assistant machine? |
Hi, regarding the homekit error attached a debug log: Hope this helps... :) |
Hello, I always have the problem, e.g. when I update HA or simply install something that requires a restart, that the devices say goodbye and the integration reports an error. |
The error you have seen is already known bug in library used by Home Assistant There is nothing that can be done in this integration to avoid it. Good news is that is being fixed in just released https://github.com/ikalchev/HAP-python/releases/tag/v4.4.0 so it should come in one of the coming releases of Home Assistant. |
Version of the custom_component
V0.5.0
Configuration
Describe the bug
Saw this error in the logs. I can see the sensor data, but most of the times when I disable the fan/humidifier with the switch in HA it changes to on state back again (after some seconds) and does not get shut off. Not sure if this is related to the error in the log file.
Debug log
The text was updated successfully, but these errors were encountered: