EufyHome (Anker) Plugin for Homebridge, based on node-eufy-api
This package does not work reliable for all devices due to a firmware bug, which means the device will, when receiving a message via your local network, simply close the connection.
There is no known workaround for this problem.
Device Code | Device Name | Comment |
---|---|---|
T1201 | Smart Plug | |
T1202 | Smart Plug Mini | |
T1203 | Smart WiFi Plug (UK) | |
T1211 | Smart Light Switch | Untested |
T1011 | Lumos Smart Bulb - White | |
T1012 | Lumos Smart Bulb - Tunable White | Untested |
T1013 | Lumos Smart Bulb - White & Color |
All the devices listed above should work, since they are supported in python-lakeside. Because an error might have occurred during the porting process, some are marked as untested.
If you own one of these untested devices, or any other devices that are not listed above, please consider running the node-eufy-api command-line interface and opening an issue to confirm whether or not your device works.
Device Code | Device Name |
---|---|
T1015 | Lumos Smart Bulb - Tunable White |
T1018 | Lumos Smart Bulb 2.0 Lite - White & Color |
npm install -g homebridge-eufy
Add the JSON object below to the "platforms" array in your Homebridge configuration file, usually in ~/.homebridge/config.json
.
Replace the dummy email address and password with your EufyHome/Anker account details, which are required to find and connect to your devices. The optional flag showPlugsAsSwitches
can be used to make the power plugs appear as switches in the Home app.
"platforms": [{
"platform": "eufy",
"name": "eufy",
"email": "email@example.com",
"password": "s3cr3t"
}]
At the moment, there is no automatic way to detect new devices when they are plugged in/enabled. To see newly added devices, please restart homebridge.
The device names in the Home app will not be updated when you change them in the EufyHome app. This is a HomeKit limitation. You can always rename your device in the Home app, though!
If you get odd issues or error messages, delete your cached data by running these commands:
rm -rf ~/.homebridge/accessories
rm -rf ~/.homebridge/persist
If this does not solve your problem, try other suggestions from the Homebridge documentation.