Open 7leman7 opened 12 months ago
eldigo
commented
12 months ago Same kind of issue the with the Roborock S8 as well.
HA version 9.1
Entities are missing. Mop mode for example. No docking status on the status entity Device not showing as a vacuum at all.
roled back to HA version 9.0.
Lash-L
commented
12 months ago Same kind of issue the with the Roborock S8 as well.
HA version 9.1
Entities are missing. Mop mode for example. No docking status on the status entity Device not showing as a vacuum at all.
roled back to HA version 9.0.
Did you get any errors?
eldigo
commented
12 months ago This what I found in the log. As it was not starting up properly, I removed the intergration and adding it again to discover the intergration is broken
2023-09-10 08:40:09.772 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry xxxxxxxxx@xxxxxx for roborock
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/roborock/__init__.py", line 45, in async_setup_entry
network_results = await asyncio.gather(
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 489, in get_networking
return await self.send_command(RoborockCommand.GET_NETWORK_INFO, return_type=NetworkInfo)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 389, in send_command
response = await self._send_command(method, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 207, in _send_command
return await self.send_message(roborock_message)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 185, in send_message
(response, err) = await async_response
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 321, in _wait_response
raise RoborockTimeout(f"id={request_id} Timeout after {QUEUE_TIMEOUT} seconds") from None
roborock.exceptions.RoborockTimeout: id=32219 Timeout after 4 seconds
2023-09-10 08:40:15.312 WARNING (MainThread) [homeassistant.components.kodi.media_player] Unable to connect to Kodi via websocket
2023-09-10 15:55:35.717 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry roeland@eldigo.nl for roborock
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/roborock/__init__.py", line 45, in async_setup_entry
network_results = await asyncio.gather(
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 489, in get_networking
return await self.send_command(RoborockCommand.GET_NETWORK_INFO, return_type=NetworkInfo)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 389, in send_command
response = await self._send_command(method, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 207, in _send_command
return await self.send_message(roborock_message)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 185, in send_message
(response, err) = await async_response
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 321, in _wait_response
raise RoborockTimeout(f"id={request_id} Timeout after {QUEUE_TIMEOUT} seconds") from None
roborock.exceptions.RoborockTimeout: id=28560 Timeout after 4 seconds
2023-09-10 15:58:08.714 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Notification Roborock replacements' trigger: In 'numeric_state' condition: no entity specified
2023-09-10 15:58:08.718 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Notification Roborock replacements' trigger: In 'numeric_state' condition: no entity specified
2023-09-10 15:58:08.720 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Notification Roborock replacements' trigger: In 'numeric_state' condition: no entity specified
2023-09-10 15:58:08.720 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Notification Roborock replacements' trigger: In 'numeric_state' condition: no entity specified
2023-09-10 15:58:41.207 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 495, in async_add_entities
tasks = [
^
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 495, in <listcomp>
tasks = [
^
File "/usr/src/homeassistant/homeassistant/components/roborock/vacuum.py", line 64, in <genexpr>
RoborockVacuum(slugify(device_id), coordinator)
File "/usr/src/homeassistant/homeassistant/components/roborock/vacuum.py", line 96, in __init__
self._attr_fan_speed_list = self._device_status.fan_power.keys()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'keys'
2023-09-10 15:58:49.598 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'homeassistant.components.roborock.time.RoborockTimeEntity'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+roborock%22
2023-09-10 15:58:49.599 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'homeassistant.components.roborock.time.RoborockTimeEntity'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+roborock%22
Jezza34000
commented
12 months ago Hi ! I noticed this but it's not a bug! In fact, even if the application displays the red LED which indicates a fault, the error is not reported in the "get_status". Alert came back up when the robot encountered a problem and couldn't continue its action... I know it's strange behavior.
Try this: Empty clean water -> Start a cleaning -> The Robot goes into error and this time the error will be shown on the integration
Let me know the result ...
mich1978
commented
11 months ago First off, thanks to the creators of this integration. 👍 I am currently using the most recent version via the Hacs integration.
I have an S8+ and am also having issues with sensors not updating correctly. The sensors/attributes I have noticed that are not updating correctly are the waterBoxCarriageStatus and mopForbiddenEnable. The mop mount status updates correctly in the Roborock app when I add or remove the mop mount.
7leman7
commented
10 months ago I'm happy to report that with the last version of integration the sensor roborock_dock_status seems to work for me. At least I'm finally seeing the low water notification for the dock (sensor.roborock_dock_status statie is water_empty) even before the vacuum itself shows error due to insufficient water.
rossi75
commented
10 months ago I'm happy to report that with the last version of integration the sensor roborock_dock_status seems to work for me. At least I'm finally seeing the low water notification for the dock (sensor.roborock_dock_status statie is water_empty) even before the vacuum itself shows error due to insufficient water.
For my S7 pro ultra, this does not work. I looked into the debug logs, and found that this is not reported back to the integration. Further, those states are also not being displayed within the roborock app
But... the roborock app shows some more sensors within its maintenance setting, called water filter and cleaning brush. Both are located on the station, not on the vacuum itself So maybe there is an additional request that could be send to the roborock API to get the details for the stations state?
Version of the custom_component
1.0.11, installed via HACS
What vacuum are you using?
Roborock S8 Pro Ultra
Describe the bug
A number of sensors are created upon adding a new S8 Pro Ultra vacuum, incl: Dock Dust Collection Mode Dock Washing Mode Dock Status Expected behavior is that the first 2 change to "1" when the dock is in respective mode and otherwise are "0". The last one is expected to show "OK" when no dock-related warnings are there and change to something else upon dock errors ocurring. Observed behavior is that for me Dock Dust Collection Mode = 0 and Dock Washing Mode = 1 in all cases (even if the dock is actually collecting dust). Dock Status is always "OK" for me (even if there is actually a warning due to e.g. low clean water level - visible in the app and also via red LED indicator on the dock itself).
Also, the vacuum entity has dockErrorStatus attribute for which the expected behavior is: ok = 0 duct_blockage = 34 water_empty = 38 waste_water_tank_full = 39 dirty_tank_latch_open = 44 no_dustbin = 46 source: https://github.com/humbertogontijo/python-roborock/blob/main/roborock/code_mappings.py#L225-L226 Observed behavior is actually that dockErrorStatus = 0 (even if there is actually a warning due to e.g. low clean water level - visible in the app and also via red LED indicator on the dock itself).
Debug log