Closed MichelFR closed 9 months ago
I fix the same problem
2023-09-13 11:59:02.005 WARNING (MainThread) [custom_components.dreame_vacuum] Integration start failed: Traceback (most recent call last): File "/config/custom_components/dreame_vacuum/coordinator.py", line 471, in _async_update_data await self.hass.async_add_executor_job(self._device.update) File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/dreame_vacuum/dreame/device.py", line 1937, in update self.connect_device() File "/config/custom_components/dreame_vacuum/dreame/device.py", line 1497, in connect_device self._request_properties() File "/config/custom_components/dreame_vacuum/dreame/device.py", line 461, in _request_properties return self._handle_properties(results) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/dreame_vacuum/dreame/device.py", line 428, in _handle_properties callback0 File "/config/custom_components/dreame_vacuum/coordinator.py", line 279, in _low_water_warning_changed low_water_warning = self._device.status.low_water_warning_description ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'DreameVacuumDeviceStatus' object has no attribute 'low_water_warning_description'
2023-09-13 11:59:02.745 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Дюша Метёлкин' for dreame_vacuum integration not ready yet: 'DreameVacuumDeviceStatus' object has no attribute 'low_water_warning_description'; Retrying in background
Adding water, rebooting the robot and Home assist solve the problem
Issue causes integration to not to start when a low water warning is present on the device. States will not update if low water warning occures after the integration has started until warning is cleared. It will be fixed on v2.0.0b6.
Looks like this issue was not fixed on the v2.0.0b6.
Reappeared for me now.
2023-11-06 22:44:44.971 INFO (MainThread) [custom_components.dreame_vacuum] Integration loading: Dreamy
2023-11-06 22:44:44.972 INFO (MainThread) [custom_components.dreame_vacuum] Integration starting...
2023-11-06 22:44:47.855 WARNING (MainThread) [custom_components.dreame_vacuum] Integration start failed: Traceback (most recent call last):
File "/config/custom_components/dreame_vacuum/coordinator.py", line 471, in _async_update_data
await self.hass.async_add_executor_job(self._device.update)
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 1990, in update
self.connect_device()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 1518, in connect_device
self._request_properties()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 464, in _request_properties
return self._handle_properties(results)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 431, in _handle_properties
callback[0](callback[1])
File "/config/custom_components/dreame_vacuum/coordinator.py", line 282, in _low_water_warning_changed
{EVENT_LOW_WATER: description[0], "code": low_water_warning.value},
^^^^^^^^^^^
UnboundLocalError: cannot access local variable 'description' where it is not associated with a value
@enkama this will be fixed on v2.0.0b7
.
@enkama this will be fixed on
v2.0.0b7
.
ETA on release date? Rough estimate is OK (this week/next week/next month/early next year). This is something that my automations rely on, as my vacuums work based on area vacuumed today.
New version released. https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b9
It doesn't work for me. The integration doesn't crash, but the water level does not update after a refill. Restarting the integration does not work. I'll have a look later today to see how long it takes for the error to clear.
It doesn't work for me. The integration doesn't crash, but the water level does not update after a refill. Restarting the integration does not work. I'll have a look later today to see how long it takes for the error to clear.
Low water warning does not reset automatically, you have to dismiss the persistent notification or press button.clear_warning
for clearing the low water warning from the device. Alternatively you can clear the warning from the app by dismissing its warning message.
Describe the bug When the water gets low the integration crashes and does not work anymore. Im Running the beta
To Reproduce Wait till the water is low.
Expected behavior It should not crash and notify.
Screenshots
Additional Information (please complete the following information)