Support for L60 SE #85

meanandpinchy · 2024-06-01T19:18:08Z

The unit is detected, but has no entities except for battery, which is "unavailable". Please add support for the L60 SE.

mumpers68 · 2024-06-15T21:35:09Z

I second the support for the L60 SES!

stoozak · 2024-06-19T14:25:28Z

yes, please!

Harm-Veraa · 2024-06-25T19:07:08Z

I was looking into this, seems the TUYA_CODES are incorrect for this robovac. Yet to firgure out any of the codes, except for battery life, which is 163. Is there any documentation about these codes available?

For reference, this is a response when the device is doing nothing: {'151': True, '156': True, '158': 'Turbo', '159': aTrue, '160': False, '161': 41, '163': 99}

stoozak · 2024-06-25T19:16:31Z

,

Where do we plug these in? Happy to test and feedback.

Harm-Veraa · 2024-06-25T19:22:49Z

Depends if you have main branch or better-dps branch. For main branch they are at the top of the 'vacuum' file, if I am not mistaken (currently on the other branch). On better-dps branch they are at the specific file for your vacuum. In our case this is T2278 (or at least for me, I have the hybrid, not sure if it's different but otherwise I expect T2277).

In both cases, before it will even load, you need to add your vacuum. In the better-dps branch you copy the specific model file and add it to the list of vacs in init. In the main you can check the robovac file and add it to the list of 'L' models.

If you are on better-dps branch, also make sure to make a comment for extra features (as they crash currently, possible because code is incorrect, not sure).

robovac_features = 0; # RoboVacEntityFeature.CLEANING_TIME | RoboVacEntityFeature.CLEANING_AREA | RoboVacEntityFeature.DO_NOT_DISTURB | RoboVacEntityFeature.AUTO_RETURN | RoboVacEntityFeature.ROOM | RoboVacEntityFeature.ZONE | RoboVacEntityFeature.BOOST_IQ | RoboVacEntityFeature.MAP | RoboVacEntityFeature.CONSUMABLES

After all of this, a logger can be added to log everything. If you change the code of the battery to 161, you'll see that one works in the home panel.

Harm-Veraa · 2024-06-25T19:36:58Z

It's curious, if I start the robot or do something with it, the status does not change according to the Logger. Perhaps another api call is required?

Harm-Veraa · 2024-06-25T20:01:39Z

Should the developer read this, and willing to look into it. Some more messages from the device, when I start it via the Eufy app. It looks like it's encrypted. I noticed that '179' has 4 values which would match potential states the device is in. (positioning, cleaning, heading home, charging). These only reported after a first run tho.

{'151': True, '156': True, '158': 'Turbo', '159': True, '160': False, '161': 41, '163': 99, '177': 'DAjZhNCLlIztzgFSAA==', '153': 'BBADGgA=', '178': 'DQiuzqvylIztzgESAR8=', '152': 'AggG', '179': 'FhIUEhIIEBABIGMozsPsswYwgcTsswY=', '173': 'GAoSMgoKAggBEgQIARgPOgQKAggBEgIIAQ==', '176': 'JgoAGgBSCBoAIgIIASoAWDBiFAoSCghOcjE4X0lvVBoGEKnC7LMG', '169': 'xxx'}

stoozak · 2024-06-25T20:14:02Z

Righto, so using the DPS branch I copied the 2273 config and renamed it to 2277 and added the reference to the model number in init.

Using 161 the battery shows as 0%, and log shows the following:


2024-06-25 21:10:21.757 ERROR (MainThread) [homeassistant.components.vacuum] Error adding entity vacuum.fred for domain vacuum with platform robovac
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/locks.py", line 386, in acquire
    await fut
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/config/custom_components/robovac/tuyalocalapi.py", line 911, in async_recieve
    await self._recieve_task
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 519, in wait_for
    async with timeouts.timeout(timeout):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 600, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 914, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1354, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/robovac/vacuum.py", line 297, in async_added_to_hass
    await self.async_forced_update()
  File "/config/custom_components/robovac/vacuum.py", line 326, in async_forced_update
    await self.async_update_vacuum()
  File "/config/custom_components/robovac/vacuum.py", line 322, in async_update_vacuum
    await self.vacuum.async_get()
  File "/config/custom_components/robovac/tuyalocalapi.py", line 763, in async_get
    response = await self.async_recieve(message)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/robovac/tuyalocalapi.py", line 923, in async_recieve
    raise ResponseTimeoutException(
custom_components.robovac.tuyalocalapi.ResponseTimeoutException: Timed out waiting for response to sequence number 818946
2024-06-25 21:10:26.827 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bfb2df8ed89ef1ee85zulu] Processing queue. Current length: 1
2024-06-25 21:10:26.827 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bfb2df8ed89ef1ee85zulu] Sending to bfb2df8ed89ef1ee85zulu (192.168.10.18:6668): Message(0x9, b'', 0, <Device bfb2df8ed89ef1ee85zulu (192.168.10.18:6668)>)
2024-06-25 21:10:26.828 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bfb2df8ed89ef1ee85zulu] Connecting to bfb2df8ed89ef1ee85zulu (192.168.10.18:6668)
2024-06-25 21:10:26.836 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bfb2df8ed89ef1ee85zulu] Received message from bfb2df8ed89ef1ee85zulu (192.168.10.18:6668): Message(0x9, b'', 0, None)

Harm-Veraa · 2024-06-25T20:19:35Z

I also get this error sometimes, seems to be when I clicked a button and then the sequence number goes haywire.. Not sure tho. In any case, the last 3 messages show it is working. At least the communication part is.. Can you try 163 for battery? That is what I have currently.

Harm-Veraa · 2024-06-25T20:28:15Z

One thing to add. Battery wont show in a default card (when the device is so-called offline). Go to the device info itself under settings -> devices. Should show there.

stoozak · 2024-06-25T21:01:54Z

Hmmm, no luck. It still shows 0%. I also don't seem to get the log state with the encrypted numbers that you got.

Harm-Veraa · 2024-06-26T05:03:04Z

Did you enable debug logging?

stoozak · 2024-06-26T12:51:58Z

Afraid so :(

Harm-Veraa · 2024-06-26T12:55:55Z

Mhh okay odd. I don't know why it won't work for you.. when I have more time I might look into it further. Should I find a proper solution I'll see if I can create a PR

stoozak · 2024-06-26T14:40:02Z

Some of these codes may be helpful: #42 (comment)

JohnD76 · 2024-07-08T14:26:52Z

1 for the LS60 SES integration please.

JohnD76 · 2024-07-11T11:59:54Z

I am having similar issues, my L60SES replaces a 15C MAX. I have removed the Eufy integration from HACS and rebooted. Amended the robots file to include the T2277 model number and when adding a device for some reason it identifies the L60SES and the name of the robot, burt gives it the MAC address of the old robot (15C MAX), even though this is removed from the Eufy app.....

I can't control the robot or see the battery status sadly via HA.

maximoei · 2024-07-25T09:54:01Z

Hi all! Good news: I've been able to get my L60 SES to work in Home assistant!

Ugly-but-working code is here https://github.com/maximoei/robovac/tree/L60-support
This version very much breaks supports for all other Robovacs, so quite some work is still needed to get it integrated back into the repo - any help is appreciated! I added config files for T2267 (L60), T2277 (L60 SES), T2278 (L60 SES Hybrid). I own the T2277 (L60 SES), so other are fully untested.

So:

L60 (and probably many others) have a new control mechanism, which is based on encrypted/protobuf values. These have been reverse engineered before by people from IObroker.net - git @TA2k
Some further values I found here @terabyte128
Lots of values still not unencrypted, you can help! Potentially approach is to move to real protobuf support, but for now a few hard coded messages are sufficient

What is the integration able to do:

Start auto clean, pause and return to dock (UI/card)
Change fan speed (UI/card)
See battery status (UI/card)
Locate the robot (UI/card)
Change volume (service)
Change boost IQ (service)

Very much not supported:

Room / Zone clean
Mopping related features
See map

I'll try to work this back into the better-dps branch, but any help here is appreciated. Happy to hear your feedback as well!

Harm-Veraa · 2024-07-25T10:14:48Z

Nice! How did you find out the codes?

IainPHay · 2024-07-25T11:25:01Z

This is great to see, I have cleaned out the old integration and installed this but I still only see just the battery entity. I just have the L60

maximoei · 2024-07-25T11:54:05Z

Nice! How did you find out the codes?

Via the other work I referenced. Some of the error codes by seeing what is being logged in the integration

This is great to see, I have cleaned out the old integration and installed this but I still only see just the battery entity. I just have the L60

Sometimes it only starts reporting detailed state after I start (and stop) a cleaning cycle from the app. After that, session seems to 'stick'. Also, if you have errors in your log, please share

IainPHay · 2024-07-25T11:57:16Z

Thanks for the feedback, must admit I'd not thought of triggering it via the app. I'll give that a try and see if it grabs the info

Harm-Veraa · 2024-07-25T12:37:04Z

Nice! How did you find out the codes?

Via the other work I referenced. Some of the error codes by seeing what is being logged in the integration

This is great to see, I have cleaned out the old integration and installed this but I still only see just the battery entity. I just have the L60

Sometimes it only starts reporting detailed state after I start (and stop) a cleaning cycle from the app. After that, session seems to 'stick'. Also, if you have errors in your log, please share

Interesting! I also tried this but for me every response seemed encrypted or something.. glad you figured it out !

asportnoy · 2024-07-25T13:18:19Z

Was able to get my L60 SES (T2277) working on your fork. Nice work! Will test a full run later tonight.

Had to make 2 minor changes to get it running:

Add the model to vacuums/__init__.py, was previously missing
vaccuums/T2267.py had the wrong class name causing an import error - updated it to match the file name

Important

The fork was updated to fix these issues in this commit. These changes are no longer necessary.

IainPHay · 2024-07-25T14:23:24Z

Was able to get my L60 SES (T2277) working on your fork. Nice work! Will test a full run later tonight.

Had to make 2 minor changes to get it running:

Add the model to vacuums/__init__.py, was previously missing

vaccuums/T2267.py had the wrong class name causing an import error - updated it to match the file name

That second bit helped me out, thanks! I have it running now but it always shows error despite being controllable but it's a massive improvement on just having the battery status :)

jb123567 · 2024-07-25T19:19:39Z

Was able to get my L60 SES (T2277) working on your fork. Nice work! Will test a full run later tonight.

Had to make 2 minor changes to get it running:

Add the model to vacuums/__init__.py, was previously missing

vaccuums/T2267.py had the wrong class name causing an import error - updated it to match the file name

That second bit helped me out, thanks! I have it running now but it always shows error despite being controllable but it's a massive improvement on just having the battery status :)

I'm having the L60 remaining unavailable, what exactly did you change in the file?

asportnoy · 2024-09-03T22:11:48Z

You need to check out the L60-support branch, which I don't think you can do from HACS.

In my case, I cloned it and installed it in the custom components folder manually (via terminal).

Yorin1 · 2024-09-04T19:29:55Z

You need to check out the L60-support branch, which I don't think you can do from HACS.

In my case, I cloned it and installed it in the custom components folder manually (via terminal).

I started in "https://github.com/maximoei/robovac/tree/L60-support" and hit the green "code" button. I now have the files on my HD (using Git desktop). I copied the contents from "custom_components/robovac" into the HA "custom_components/robovac" folder (using the "file editor" add-on) and rebooted HA. However after adding the integration it is again the same issue (error in the log and just the not available battery entity). The error message is identical to what DesertNomadBear posted last week.

When you say you installed it in custom components manually, do you mean you copied the files to that folder or is there more to it? Also besides the folder "custom_components" there are other files and folders that come with the clone. Do you have to do anything with those or does only the folder "custom_components" matter?

asportnoy · 2024-09-04T22:53:53Z

Check the custom_components/robovac/vacuums folder and look for a T2277.py file. If it's not there, it means you're not actually on the correct branch.

If you are actually on the correct branch, I need to see the file tree to understand how you did it. Also make sure you uninstalled the prior version first to make sure they're not conflicting and still using the old version somehow.

Yorin1 · 2024-09-05T19:19:38Z

Check the custom_components/robovac/vacuums folder and look for a T2277.py file. If it's not there, it means you're not actually on the correct branch.

If you are actually on the correct branch, I need to see the file tree to understand how you did it. Also make sure you uninstalled the prior version first to make sure they're not conflicting and still using the old version somehow.

Thanks a lot! You pointed me to where I got it wrong with your comments.

For anybody who might be struggling with this as well. I used GitHub Desktop to open the Robovac repository, then selected the right branch (this is where I went wrong before). If you then hit "show in explorer" you are taken to all the files. Copy everything under "custom_components" to the same directory in your HA instance and reboot (I used the file editor add-on in HA to copy files from my HD to the RPi 4 that runs my HA). After rebooting you search for the Robovac integration and once it's added you need to start a cleaning run from the Eufy app to have the device become active in HA.

Not really that hard once you figure out what to do. Copying all the files one-by-one was a bit tedious, but this only needs to be done once. I suppose that using the terminal there are easier ways to copy the files at once.

pnm1977 · 2024-09-08T09:37:39Z

It is not in the latest integration, you need to use this fork for now

@maximoei - Any idea if it's possible to send the do not disturb command for on and off on this fork and have you managed to work out how it's done? The entity seems stable when controlling the on/off via the app and the string is unique based on the set schedule in the app.

Casper9228 · 2024-09-10T18:13:58Z

@maximoei Hoi!
I was wondering if you could give me a push into the right direction, although hijacking this issue a little bit. I have a X8 Pro SES (T2276G11) that I was hoping to set up with your L60 branch. Unfortunately, after two days of tinkering, I just don't seem to be able to set it up.... This is my error log:

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/robovac/tuyalocalapi.py", line 911, in async_recieve
    await self._recieve_task
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 519, in wait_for
    async with timeouts.timeout(timeout):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 595, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 909, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1365, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/robovac/vacuum.py", line 366, in async_added_to_hass
    await self.async_forced_update()
  File "/config/custom_components/robovac/vacuum.py", line 395, in async_forced_update
    await self.async_update_vacuum()
  File "/config/custom_components/robovac/vacuum.py", line 391, in async_update_vacuum
    await self.vacuum.async_get()
  File "/config/custom_components/robovac/tuyalocalapi.py", line 763, in async_get
    response = await self.async_recieve(message)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/robovac/tuyalocalapi.py", line 923, in async_recieve
    raise ResponseTimeoutException(
custom_components.robovac.tuyalocalapi.ResponseTimeoutException: Timed out waiting for response to sequence number 384152823
2024-09-10 19:52:44.997 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Disconnected from bf176e865fc470ad656htu (192.168.1.225:6668)
2024-09-10 19:52:45.000 DEBUG (MainThread) [custom_components.robovac.vacuum] ['Quiet', 'Standard', 'Turbo', 'Max']
2024-09-10 19:52:45.002 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Processing queue. Current length: 1
2024-09-10 19:52:45.003 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Sending to bf176e865fc470ad656htu (192.168.1.225:6668): Message(0xa, {'gwId': 'bf176e865fc470ad656htu', 'devId': 'bf176e865fc470ad656htu'}, 384186211, <Device bf176e865fc470ad656htu (192.168.1.225:6668)>)
2024-09-10 19:52:45.003 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Connecting to bf176e865fc470ad656htu (192.168.1.225:6668)
2024-09-10 19:52:45.112 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Processing queue. Current length: 1
2024-09-10 19:52:45.112 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Sending to bf176e865fc470ad656htu (192.168.1.225:6668): Message(0x9, b'', 0, <Device bf176e865fc470ad656htu (192.168.1.225:6668)>)
2024-09-10 19:52:45.130 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.bf176e865fc470ad656htu] Incomplete read

If you have some spare time, could you please have a look? :)

Many thanks!

maximoei · 2024-09-16T12:43:07Z

#46 - @Casper9228 , I don't know what Incomplete read means, but I think the issue is closer to the tuya module, rather than the handling of the messages.

avidricaire · 2024-09-23T14:17:40Z

I followed the instructions and the device is detected and it can read its states (charging, cleaning, docked), but I have no controls in HA and it just says the entity is unavailable. Any ideas? When added to Alexa through HA cloud I can control it

asportnoy · 2024-09-23T17:50:05Z

I followed the instructions and the device is detected and it can read its states (charging, cleaning, docked), but I have no controls in HA and it just says the entity is unavailable. Any ideas? When added to Alexa through HA cloud I can control it

I think there is a bug where the initial state is always unavailable when you first set it up. Try using the official app to start a cleaning cycle, then see if the controls in HA start working.

avidricaire · 2024-09-23T18:48:48Z

I followed the instructions and the device is detected and it can read its states (charging, cleaning, docked), but I have no controls in HA and it just says the entity is unavailable. Any ideas? When added to Alexa through HA cloud I can control it

I think there is a bug where the initial state is always unavailable when you first set it up. Try using the official app to start a cleaning cycle, then see if the controls in HA start working.

Took a little bit but that solved it, thank you!

maximoei · 2024-09-25T08:13:52Z

I followed the instructions and the device is detected and it can read its states (charging, cleaning, docked), but I have no controls in HA and it just says the entity is unavailable. Any ideas? When added to Alexa through HA cloud I can control it

I think there is a bug where the initial state is always unavailable when you first set it up. Try using the official app to start a cleaning cycle, then see if the controls in HA start working.

Yes, this is because the vaccuum only starts reporting it's detailed state after start/stop of a cleaning cycle from the app, before that, no data is available and therefore the entity is also unavailable. After that initial use of the app the 'session' sticks, also in HA.

asportnoy · 2024-09-25T11:42:16Z

I'm not sure if that's the case. When you open the Eufy app, it knows it's connected and available right away and is able to load all that detailed information. Maybe some other API you need to implement?

Regardless, I think it might be a better UX to assume it's available when the device is set up initially. The UI controls are disabled if it's unavailable, which gives a poor experience as shown above. Especially if the user just set up the device, that would almost certainly mean it's available.

valkaholic · 2024-09-26T22:33:29Z

Got this to work for my L60, thank you!! I also have an L50 which seems nearly identical but it is not recognized. Any advice on how to port this over to the L50?

ddakotac · 2024-09-29T03:02:16Z

Amazing, thanks so much! Just go it working. Cheers maximoei!

maximoei · 2024-10-09T12:43:21Z

@valkaholic -> T2275 version of L50 is included in the branch details here

cmdrpicard · 2024-10-16T14:12:26Z

Thank you for doing this. Got my L60 SES working in HA.

mumpers68 · 2024-10-16T15:11:50Z

Second that, much appreciated for the work on this!!On Oct 16, 2024, at 10:12 AM, cmdrpicard ***@***.***> wrote: Thank you for doing this. Got my L60 SES working in HA. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

Ali229 · 2024-10-18T21:23:07Z

@maximoei Is there a way to empty the bin into the base for L60? I got the vacuum working with your fork already btw. Another vacuum I have is emptied using a script like:

target:
  device_id:
    - xyz3432432
data:
  command: setAutoEmpty
  params:
    act: start
action: vacuum.send_command

danielccm · 2024-11-14T23:17:50Z

Maximoei,

#85 (comment)

Very much not supported:

Room / Zone clean

Mopping related features

See map

Any chance Room cleaning and Map seeing could be developed? Would be a game changer with the L60 SES... Just asking.. Great work btw!

maximoei · 2024-11-19T10:53:34Z

@maximoei Is there a way to empty the bin into the base for L60? I got the vacuum working with your fork already btw. Another vacuum I have is emptied using a script like:

This works for me to empty into the bin (but not the cutting action):

action: vacuum.send_command
data: 
  entity_id: vacuum.l60
  command: 173
  params:
    value: "BBICGAE="

merkurmaniac · 2024-11-20T15:41:25Z

@maximoei , thanks so much for your hard work on this. It's much appreciated.

Sorry to be so dumb on this, but are you saying above that the L50 vacuum is now again part of this fork, and doesn't need to be treated differently than the L60 ? Just making sure I am reading this correctly.

musicscoree96 · 2024-12-06T09:42:17Z

I added all the files from the github repo using the file manager from HA to the HA installation.
Then I added the Robovac to the device and added the IP-Adres. But the first time I click "configure" it kept on spinnen showing the screen "Edit vacum". After minutes waiting I stop the recovery and click configure again. Then it kept on spinning showwing "One moment please while configuring Eufy Robovac is being in initializing". The only way to stop this if by removing the powerline from my RPI4 because clicking anywhere does not do anything.

I'm trying to add the L60. The file T2277 is available in the map.

Please help

valkaholic · 2024-12-06T21:26:28Z

@valkaholic -> T2275 version of L50 is included in the branch details here

FYI I got the L50 working using this fork and adding T2265. For some reason it was never recognized with T2275.

musicscoree96 · 2024-12-08T12:24:52Z

Thank you valkaholic. I managed to get it to work with the L60.
I missed 1 of the files in the vacuum map and thats why the add-on was not working and generated an error.
After copied ALL files to the vacuum map, the add on worked perfect.
Thank you for your reponse.

merkurmaniac · 2024-12-14T01:09:39Z

@valkaholic -> T2275 version of L50 is included in the branch details here

FYI I got the L50 working using this fork and adding T2265. For some reason it was never recognized with T2275.

Where do I find the T2265 file ? It was not in the big batch of them that I copied down.

valkaholic · 2024-12-15T16:43:53Z

@valkaholic -> T2275 version of L50 is included in the branch details here

FYI I got the L50 working using this fork and adding T2265. For some reason it was never recognized with T2275.

Where do I find the T2265 file ? It was not in the big batch of them that I copied down.

It's not in there. You can just duplicate the T2267 file and rename to T2265, and also change the reference in the code to T2265 (line 5). Add the reference to the init.py file (from .T2265 import T2265) and reboot. It should pick up the L50, but you will have to start the vacuum once from the Eufy app to get full functionality. Actually, I need to do that every time HA is reset.

merkurmaniac · 2024-12-16T04:10:10Z

Thank you @valkaholic , I appreciate you taking the time to help out with that. It was not too obvious to me.

merkurmaniac · 2025-01-02T04:50:24Z

Still cannot get it added.

I edited this file by changing line 5 to read "class T2265:"

/homeassistant/custom_components/robovac/vacuums/T2265.py

I then edited this file:
/homeassistant/custom_components/robovac/vacuums/init.py

by adding the

from .T2265 import T2265

and later down adding

"T2265": T2265,

Is there anything else I need to change ? I launch it from the Eufy app and it only shows a single entry of battery that shows unavailable.

There is also another init__.py in the directory above this one. Its here:

/homeassistant/custom_components/robovac/init.py

I have NOT edited it at all. Please advise if you see what I am doing wrong.

valkaholic · 2025-01-04T14:55:42Z

That should be everything. Before launching in the native Eufy app you configured the device in the Eufy Robovac integration?

This was referenced Jul 25, 2024

Add support for L50 SES #42

Open

Entities not populating with Eufy L60 #40

Open

Adding L60 SES support (UNTESTED) #66

Merged

Add support for Eufy X10 Pro Omni #68

Open

panagiotisTB mentioned this issue Dec 9, 2024

Issue with Plugin for Eufy Clean L60 hov3rcraft/homebridge-eufy-robovac#6

Open

Support for L60 SE #85

Support for L60 SE #85

Comments

meanandpinchy commented Jun 1, 2024

mumpers68 commented Jun 15, 2024

stoozak commented Jun 19, 2024

Harm-Veraa commented Jun 25, 2024 • edited Loading

stoozak commented Jun 25, 2024

Harm-Veraa commented Jun 25, 2024

Harm-Veraa commented Jun 25, 2024

Harm-Veraa commented Jun 25, 2024 • edited Loading

stoozak commented Jun 25, 2024 • edited Loading

Harm-Veraa commented Jun 25, 2024

Harm-Veraa commented Jun 25, 2024

stoozak commented Jun 25, 2024

Harm-Veraa commented Jun 26, 2024

stoozak commented Jun 26, 2024

Harm-Veraa commented Jun 26, 2024

stoozak commented Jun 26, 2024

JohnD76 commented Jul 8, 2024

JohnD76 commented Jul 11, 2024 • edited Loading

maximoei commented Jul 25, 2024 • edited Loading

Harm-Veraa commented Jul 25, 2024

IainPHay commented Jul 25, 2024

maximoei commented Jul 25, 2024 • edited Loading

IainPHay commented Jul 25, 2024

Harm-Veraa commented Jul 25, 2024

asportnoy commented Jul 25, 2024 • edited Loading

IainPHay commented Jul 25, 2024

jb123567 commented Jul 25, 2024

asportnoy commented Sep 3, 2024

Yorin1 commented Sep 4, 2024 • edited Loading

asportnoy commented Sep 4, 2024

Yorin1 commented Sep 5, 2024

pnm1977 commented Sep 8, 2024

Casper9228 commented Sep 10, 2024

maximoei commented Sep 16, 2024

avidricaire commented Sep 23, 2024

asportnoy commented Sep 23, 2024

avidricaire commented Sep 23, 2024

maximoei commented Sep 25, 2024

asportnoy commented Sep 25, 2024

valkaholic commented Sep 26, 2024

ddakotac commented Sep 29, 2024

maximoei commented Oct 9, 2024

cmdrpicard commented Oct 16, 2024

mumpers68 commented Oct 16, 2024 via email

Ali229 commented Oct 18, 2024 • edited Loading

danielccm commented Nov 14, 2024

maximoei commented Nov 19, 2024

merkurmaniac commented Nov 20, 2024

musicscoree96 commented Dec 6, 2024 • edited Loading

valkaholic commented Dec 6, 2024

musicscoree96 commented Dec 8, 2024

merkurmaniac commented Dec 14, 2024

valkaholic commented Dec 15, 2024

merkurmaniac commented Dec 16, 2024

merkurmaniac commented Jan 2, 2025

valkaholic commented Jan 4, 2025

Harm-Veraa commented Jun 25, 2024 •

edited

Loading

Harm-Veraa commented Jun 25, 2024 •

edited

Loading

stoozak commented Jun 25, 2024 •

edited

Loading

JohnD76 commented Jul 11, 2024 •

edited

Loading

maximoei commented Jul 25, 2024 •

edited

Loading

maximoei commented Jul 25, 2024 •

edited

Loading

asportnoy commented Jul 25, 2024 •

edited

Loading

Yorin1 commented Sep 4, 2024 •

edited

Loading

Ali229 commented Oct 18, 2024 •

edited

Loading

musicscoree96 commented Dec 6, 2024 •

edited

Loading