robovac
robovac copied to clipboard
X8 not working?
Tried to get this working with the X8, but its only adding a single entity. Battery, that always shows as unavailable
Tried multiple versions of the integration. Any idea why its not working?
Raspberry Pi 4 Core 2025.2.1 Supervisor 2025.02.0 Operating System 14.2 Frontend 20250205.0
Same issue here :(
@CodeFoodPixels Any idea why this is not working with the X8?
I think this repo is no longer maintained :(
@DominicMuir as I replied to your other issue, I've not had the time because of family health matters.
I unfortunately can't comment on why this isn't working with the X8, I don't have an X8 so can't test it.
Description looks the same as #103. May be related to #105 and #68.
I'm seeing the same issue with a newly added 30C. In wonder if this is related to Eufys plans to integrate all of their products under a the single 'Eufy' app. I'll see if I can troubleshoot a bit more and provide some more info.
Edit: The logs unfortunately don't show anything of interest however I've noticed my phone app is also showing the same errors even after a re-install. I think this is a Eufy Account issue somehow.
@KieranDrain - I have a 30C too - would be keen to understand if you manage to get to the bottom of this :)
I have an X8 Hybrid, I added the model code "T2262T11" into the file "/homeassistant/custom_components/robovac/robovac.py" under "ROBOVAC_SERIES" as per the below and everything seems to be working.
ROBOVAC_SERIES = { "C": [ "T2103", "T2117", "T2118", "T2119", "T2120", "T2123", "T2128", "T2130", "T2132", ], "G": [ "T1250", "T2250", "T2251", "T2252", "T2253", "T2254", "T2150", "T2255", "T2256", "T2257", "T2258", "T2259", "T2270", "T2272", "T2273", ], "L": ["T2181", "T2182", "T2190", "T2192", "T2193", "T2194"], "X": ["T2261", "T2262", "T2320", "T2262T11"],
@StarShip2016 what version of the integration are you running? My robovac.py doesnt have a ROBOVAC_SERIES section.
I'm currently using v1.2.11
Unfortunately still shows the same :(
X8 Pro SES is TT2276, looks like T2266 for the non SES model.
With those codes added see more than just the unknown battery, but still ultimately an error:
Had this in the logs:
2025-04-10 19:57:09.404 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 1. Reason: Timed out waiting for response to sequence number 772814620
2025-04-10 19:58:09.121 WARNING (MainThread) [custom_components.robovac.vacuum] Update errored. Current update failure count: 2. Reason: Timed out waiting for response to sequence number 772874644
But it did not reappear on a reboot with custom_components.robovac.vacuum logging set to DEBUG. After a reboot the battery did show a state of 0, rather than unknown.
Update for my issues: The forked version is working absolutely fine: https://github.com/damacus/robovac
I am getting errors trying to use Damascus's one:
Traceback (most recent call last):
File "/config/custom_components/robovac/tuyalocaldiscovery.py", line 86, in datagram_received
padded_data = decryptor.update(data_bytes) + decryptor.finalize()
~~~~~~~~~~~~~~~~~~^^
ValueError: The length of the provided data is not a multiple of the block length.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1243, in _read_ready
self._protocol.datagram_received(data, addr)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/config/custom_components/robovac/tuyalocaldiscovery.py", line 92, in datagram_received
data_str_value = data_bytes.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc5 in position 0: invalid continuation byte