Common Issues
We're sorry to hear that you have encountered issues with the plugin. Maybe some of these guides can help you resolve this.
If not feel free to contact uns on github or discord!
Make sure to update to the latest version of the homebridge and the plugin
Please make sure that you have the newest npm version on your system. If you have error messages realted to npm, try googling the specific error first.
Sometimes it can happen that you encounter problems after updating to a new version especially if you're testing new beta versions.
In rare cases new versions interfere with previous saved settings (e.g. saved station list).
If you have trouble updating or the device list does not update correctly after an update please try removing the stored files in the plugins storage path. You'll find the necessary steps described here.
Can you try using Incognito mode with your browser ? Does it solve the issue ?
We like to add new functionallity to the plugin. However HomeKit sometimes has a hard time dealing with Accessories that update their features after they were already added to HomeKit. So whenever you change such settings on a device, you have to expect some funny behaviour with it in HomeKit. It might be a good idea to try and remove this particular device from HomeKit and add it again. In most cases it can even be necessary to remove the whole bridge. Therefore we recommened using a child bridge for the plugin and unbridge individual devices where possible. See Bridged and Unbridged Mode.
The common process to solve these issues is:
- Remove the device from HomeKit (Sometimes removing the entire Bridge is necessary)
- Remove the device from the Homebridge Cache (see here)
- Add the Device (Bridge) again.
Sure, you can add the following section to your existing documentation:
If you encounter an error message like the one below, you are likely facing a CAPTCHA or 2FA (Two-Factor Authentication) security check from Eufy.
- CAPTCHA Required
Important Notice: CAPTCHA Required
Your account seems to have triggered a security measure that requires CAPTCHA verification for the next 24 hours...
- 2FA Requested
Attention: Two-Factor Authentication (2FA) Requested
It appears that your account is currently under a temporary 24-hour flag for security reasons...
- Disable the Eufy Security plugin
- Reboot Homebridge
-
Navigate to Eufy Security Plugin settings and click the refresh button
- You should be prompted for Captcha and 2FA
- Devices should reappear
- Click save
- Enable the plugin again
- Reboot Homebridge
For additional information on CAPTCHA and 2FA, refer to the dedicated GitHub wiki:
If you get this kind of issue:
This plugin threw an error from the characteristic 'On': Unhandled error thrown inside write handler for characteristic: No station with serial number: TXXXXXXXXXX!. See https://git.io/JtMGR for more info.
It's because you're using a guest account with guest right. This will be fixed by giving admin rights through the Eufy App.
In order to get the push notifications through the eufy cloud, you'll have to enable the push notifications for the device in the eufy app.
For motion events this would for example look like this:
Most of the time motion detection is not triggered because the security mode home/away/night/custom is configured incorrectly. You will need to enable push notification likes below :
We don't support HOOBS atm, but some people manage to make it work on the 4.0.100. HOOBS UI doesn't support the new Wizard Onboarding process, you can't use Eufy Security Account with 2FA enabled.
{
"platforms": [
{
"platform": "EufySecurity",
"username": "******@*******.****",
"password": "*******************",
"country": "US",
"enableDetailedLogging": false,
"pollingIntervalMinutes": 10,
"ignoreStations": "[]",
"ignoreDevices": "[]"
}
]
}
See Installation and Configuration for more details.
We're working mainly with battery camera. We think Eufy Security took the choice to avoid too much polling the camera to preserve their battery. That could explain you don't have the latest snapshot and or refreshed one every 10 sec.
The newest versions of the plugin have configuration settings that let you choose the snapshot behaviour in more detail.
Since naturally the most issues arise with streaming we have a dedicated article regarding Streaming Issues. Check it out!
In some cases it is possible that a device cannot be added through HomeKit. See Bridged and Unbridged Mode and problems for the cause and a solution to this problem.
This feature is experimental for now (and only available in 2.2.0-beta versions). There are many requirements to be met, to actually get this feature work properly. The most important are:
- Hardware has to be powerful enough to encode the videostream
- The stream has to meet the requested paramters of the HomeKit Controller. If this is not the case, it might be that the controller ignores the recorded stream.
For now don't expect this feature to run on low end hardware like a NAS or a RPi.
We have a dedicated wike article to cover this feature more in depth: HomeKit Secure Video