Closed Xitro01 closed 8 months ago
You could just disable the entity from HA UI instead of modify the code. If you attach integration diagnostics I will check if there is a way to understand if this sensor is available or not.
smartthinq_sensors-c877247abeff40b13de0d777c095de3b-Airconditioner-50b9fa0937b72643ace0be6c2f022be1.json.txt Hereby the diagnostics.
Disabling the humidity entity did not solve my issue. The problem lies in the "current_humidity" attribute inside climate.airconditioner.
Thanks in advance!
This issue should be fixed in last release, please check and report here.
This issue should be fixed in last release, please check and report here.
Just updated and rebooted, this solves my issue. Thanks alot for your quick fix! Hopefully this does not affect others that actually do have a humidity sensor in their airconditioners.
Hopefully this does not affect others that actually do have a humidity sensor in their airconditioners.
I hope so too, the idea is that humidity=0 just do not make sense. In the case of new issue I will compare diagnostics of device with humidity sensors and yours to try to find a different way👍
Hi,
My airconditioning unit does not support humidity. So the value in "current_humidity" shows as 0. Which is also sent to my HomeKit, which thinks the humidity in that room is 0%.
Is it possible to not show this value? If the humidity value that you get is "0" that it removes current_humidity completely?
For now (workaround) I just removed this part in climate.py:
Thanks in advance!