You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like something is wrong with mini_dateutil.py or something that mini_dateutil.py calls on line 163.
It appears to be preventing the integration from working.
I Rolled back to 2024.12.0 and got the error with the vacuum not being supported. I rolled up to 2024.12.1 and got the same results as with 2024.12.2. It was working on 2024.12.1 after I upgraded the first time. I'm not sure what's going on with that.
I have removed the integration on 2024.12.2, then restarted the home assistant container, and then added the integration, set it up with no troubles, and it found the vacuum, but the entities are all still "unavailable" with the same log errors.
On which deebot device (vacuum) you have the issue?
Deebot N8+ (7bryc5)
Which version of the deebot-client are you using?
9.3.0
Country
US
Continent
NA
Anything in the logs that might be useful for us?
: py.warnings
Source: components/ecovacs/__init__.py:3
First occurred: 9:32:48 AM (1 occurrences)
Last logged: 9:32:48 AM
/usr/local/lib/python3.13/site-packages/sleekxmppfs/thirdparty/mini_dateutil.py:163: SyntaxWarning: invalid escape sequence '\s' _iso8601_parser = re.compile("""
2024-12-12 09:33:15.261 WARNING (MainThread) [deebot_client.command] No response received for command "getStats". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:15.262 WARNING (MainThread) [deebot_client.command] No response received for command "getPos". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:15.513 WARNING (MainThread) [deebot_client.command] No response received for command "getNetInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:32.080 WARNING (MainThread) [homeassistant.components.zwave_js.services] This service is deprecated in favor of the ping button entity. Service calls will still work for now but the service will be removed in a future release
2024-12-12 09:33:35.348 WARNING (MainThread) [deebot_client.command] No response received for command "getChargeState". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:35.350 WARNING (MainThread) [deebot_client.command] No response received for command "getCleanInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:55.436 WARNING (MainThread) [deebot_client.command] No response received for command "getWaterInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:55.437 WARNING (MainThread) [deebot_client.command] No response received for command "getCachedMapInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:33:55.690 WARNING (MainThread) [deebot_client.command] No response received for command "getVolume". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:15.523 WARNING (MainThread) [deebot_client.command] No response received for command "getTotalStats". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:15.527 WARNING (MainThread) [deebot_client.command] No response received for command "getCleanCount". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:15.774 WARNING (MainThread) [deebot_client.command] No response received for command "getBattery". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:35.608 WARNING (MainThread) [deebot_client.command] No response received for command "getLifeSpan". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:35.611 WARNING (MainThread) [deebot_client.command] No response received for command "getError". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:35.862 WARNING (MainThread) [deebot_client.command] No response received for command "getAdvancedMode". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:55.698 WARNING (MainThread) [deebot_client.command] No response received for command "getBreakPoint". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:55.699 WARNING (MainThread) [deebot_client.command] No response received for command "getCarpertPressure". This can happen if the device has network issues or does not support the command
2024-12-12 09:34:55.948 WARNING (MainThread) [deebot_client.command] No response received for command "getCleanPreference". This can happen if the device has network issues or does not support the command
2024-12-12 09:35:15.782 WARNING (MainThread) [deebot_client.command] No response received for command "getTrueDetect". This can happen if the device has network issues or does not support the command
2024-12-12 09:35:15.812 WARNING (MainThread) [deebot_client.command] No response received for command "getSpeed". This can happen if the device has network issues or does not support the command
2024-12-12 09:35:16.038 WARNING (MainThread) [deebot_client.command] No response received for command "getCachedMapInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:35:35.867 WARNING (MainThread) [deebot_client.command] No response received for command "getMajorMap". This can happen if the device has network issues or does not support the command
2024-12-12 09:35:35.897 WARNING (MainThread) [deebot_client.command] No response received for command "getMapTrace". This can happen if the device has network issues or does not support the command
2024-12-12 09:40:41.097 WARNING (MainThread) [deebot_client.command] No response received for command "getStats". This can happen if the device has network issues or does not support the command
2024-12-12 09:40:41.104 WARNING (MainThread) [deebot_client.command] No response received for command "getNetInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:40:41.133 WARNING (MainThread) [deebot_client.command] No response received for command "getPos". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:01.182 WARNING (MainThread) [deebot_client.command] No response received for command "getWaterInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:01.198 WARNING (MainThread) [deebot_client.command] No response received for command "getCachedMapInfo". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:01.232 WARNING (MainThread) [deebot_client.command] No response received for command "getVolume". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:21.284 WARNING (MainThread) [deebot_client.command] No response received for command "getTotalStats". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:21.325 WARNING (MainThread) [deebot_client.command] No response received for command "getBattery". This can happen if the device has network issues or does not support the command
2024-12-12 09:41:21.326 WARNING (MainThread) [deebot_client.command] No response received for command "getCleanCount". This can happen if the device has network issues or does not support the command
Additional information
No response
The text was updated successfully, but these errors were encountered:
Checks
The problem
It looks like something is wrong with mini_dateutil.py or something that mini_dateutil.py calls on line 163.
It appears to be preventing the integration from working.
I Rolled back to 2024.12.0 and got the error with the vacuum not being supported. I rolled up to 2024.12.1 and got the same results as with 2024.12.2. It was working on 2024.12.1 after I upgraded the first time. I'm not sure what's going on with that.
I have removed the integration on 2024.12.2, then restarted the home assistant container, and then added the integration, set it up with no troubles, and it found the vacuum, but the entities are all still "unavailable" with the same log errors.
On which deebot device (vacuum) you have the issue?
Deebot N8+ (7bryc5)
Which version of the deebot-client are you using?
9.3.0
Country
US
Continent
NA
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: