Closed TheBrickster closed 7 years ago
Based on there being a fix that you've identified, are you comfortable making the change and submitting a PR?
I confirm the issue and I'll submit a PR soon.
One possible other workaround is to enable continuous monitoring
on the Dyson devices (not tested yet, can not confirm).
Hi Charles, I am unable to comment on the HA forum - apparently a 3 post limit for newbies...
I've turned on continuous monitoring, and after a short while the dashboard reflected that the humidity detected is 49% (the same as reported in my app).
Also, to check that it was a viable workaround, I left continuous monitoring switched on, and reverted the setting back to
REQUIREMENTS = ['libpurecoollink==0.2.0']
I was able to start HASS without any issues.
However, for my purposes, I will switch it back to 0.3.0 so I don't need to leave continuous monitoring switched on.
Sorry for the delay, I just submit a PR to fix this issue if devices are configured with standby monitoring disable.
Home Assistant release (
hass --version
): 0.49.0Python release (
python3 --version
): Python 3.5.2Component/platform: Dyson
Description of problem: dyson.py script is expecting a numeric value for the "humidity sensor" reading, however when provided with "OFF" the script crashes and HASS does not load.
Expected: It is expected that the dyson.py script can cope with the status provided by the humidity sensor and allow HASS to load without issue.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info: Discussed on https://community.home-assistant.io/t/dyson-link-action-and-sensor/10145/65
The fix was to edit the file/components/dyson.py
and update the line
REQUIREMENTS = ['libpurecoollink==0.2.0']
With
REQUIREMENTS = ['libpurecoollink==0.3.0']