Just a quick thank you note to @mitchellrj for your work on this. I don’t know if you are still active or not, but I have a 30C, and this worked great for me and I’m running it in 0.105.3 without issue.
I’m trying to get my Eufy 15C working with Home Assistant (formerly Hassio) v201 with Home Assistant Core 0.106.0. I have the local key and dev id for my vacuum. When I launch @mitchellrj 's custom component, it only prints one error:
Connection to {deviceid} (192.168.1.33:6668) failed: [Errno 104] Connection reset by peer
I suspect this may be due to me not having openssl installed. Do you know how to install openssl as a dependency when using Home Assistant Supervisor?
15C uses a different protocol and isn’t supported at the moment, sorry.
Surprisingly, I woke up this morning and the 15C <–> Home Assistant integration was working! It took a 2nd HA restart to get it to work, and I do still see “Connection reset by peer” occasionally in the logs, but the integration has been working all day so far.
FYI @mitchellrj
Word of warning to all with the 15c MAX - don’t upgrade the firmware to 1.1.3 - you may struggle to find your device id again
I tried every trick with ADB to find the key - it is no longer output to the log. Next step I decompiled the Eufyhome APK file and found that Tuya outputs the devID
The TuyaSmart app shows the device id in the menu and shows it as a string in the logcat using ReactNativeJS
03-12 22:33:04.338 14143 19939 I ReactNativeJS: Running application “TYRCTApp” with appParams: {“initialProps”:{“devInfo”:{“isShare”:false,“activeTime”:1584052353,“parentId”:null,“verSw”:“1.1.3”,“panelConfig”:{“bic”:“[{"code":"timer","selected":true},{"code":"jump_url","selected":false}]”},“devId”:“XXXXXXXXXXXXXXXXXXXX”
No sign of the LocalKey
I then re-paired the RoboVac with EufyHome
And tried python3
>>> import lakeside
>>> devices = lakeside.get_devices('EUFY_ACCOUNT_EMAIL', 'EUFY_ACCOUNT_PASSWORD')
>>> print(devices)
[{'address': '188.220.xxx.xxx', 'code': '', 'type': 'T2128', 'name': 'Buttons', 'id': 'XXXXXXXXXXXXXXXXXXXX'}]
Yes yes yes - my kids named the RoboVac … Buttons.
So I now can get my DevId from lakeside but not the localkey
Any ideas?
try the adb solution using an old version of the app. worked for me. i used version 2.3.2
That worked !
I downloaded from https://www.apkmonk.com/download-app/com.eufylife.smarthome/5_com.eufylife.smarthome_2019-09-29.apk/
- Installed on Bluestacks on my pc
- Got the Android SDK installed on my pc
- On my PC ran adb connect 127.0.0.1:5555
- Installed the Eufyhome 2.3.2 on Bluestacks
- Back on my pc I ran adb shell logcat -e 'tuya.m.my.group.device.list
- Opened EufyHome on BlueStacks
- Checked the log output
Hi Rob
did you get the 15c MAX working. I have managed to add this according to the steps. There is no error however I cant find any of my robovacs added?
eufy_vacuum:
devices:
- name: XYZ
address: 192.168.1.231
access_token: !secret token
id: !secret id
type: T2128
t seems to not complain about config error if i change the eufy_vacuum to eufy_vaccum but cant find any of my robovacs.
cheers
Hi mate
I can’t seem to get 2 of my 15c MAX to get detected. I have done everything in those links.
Also home assistant complains the eufy_vacuum component is not found. Can you share your config etc please.
Here is what I have in my config file:
eufy_vacuum:
devices:
- name: Robovac
address: !secret robovac_ip
access_token: !secret robovac_localkey
id: !secret robovac_id
type: T2118
Make sure your files are in the correct folders too:
Hi Mate thank you so much for getting back.
I figured my problem. I have named my eufy_vaccum instead of eufy_vacuum in custom components. I fixed that and everything works perfectly.
Regards
Aj
Glad it helped and yeah I recall having to rename it also
I made a step-by-step guide for, IMHO, a very simple way of adding a EUFY RoboVac.
Anyone think its helpful?
Thank you 3ATIVE. This worked for my Robovac 15C Max
The trickiest part was figuring out the local IP address because the Robovac shows up as “ESP_355E56” in my list of devices (I’m using Google Wifi) - I compared the MAC address to confirm it was the correct device.
I also had to leave the type as T2118 because changing to the ‘correct’ model number (T2128) gave me an error and said it wasn’t supported.
Thanks for creating and sharing this!
really good guide but not able to get my device IDs. It’s saying update the app for this device (assuming the X1 are too new for the old APK)
Hi,
actual integration via HACS is there. However, I sent the info to git, so I’ll include it here.
Maybe a glimmer of hope. With the new kickstarter campaign for the S1 Pro, the question of backing Matter has come up (or the competition is promising it, so why not push back a bit) and answer is official now:
Our R&D team is currently evaluating Matter integration and actively working on it. We anticipate extending support for Matter through version updates scheduled for the second half of this year.