[Bug]: No devices showing.

[preachrman007]

What happened?

I have installed the plugin, but no devices are showing up. I have a T8420 Floodlight, but it isn't showing up when I log in via Eufy Security.

I've checked all the common issues. Using a Family and Guests share for Eufy. Tried with 2FA on and off.

I AM in the UK. (I know that some people were having issues with other countries. I modified the json file as someone recommended. When I changed from "US" to "UK", Homebridge logs returned something about an invalid country. I changed it to "DK" as others had done and the error went away, but still no devices appeared.

I'm nowhere near an expert in Homebridge, but I'm happy to share any other logs that are needed.

Device Type

Floodlight (Supported)

Plugin Version

v1.0.x (Supported)

HomeBridge Version

other (UnSupported)

NodeJS Version

v14 (Supported)

Operating System

Mac OS X 11+ (Supported)

Relevant log output

No response

[github-actions[bot]]

Did you check this Common Issues pages ?

[preachrman007]

[viserion81]

I have the same issue that no devices are found. My Eufy Security account is registered in Germany. Editing the "country" in JSON configuration file to "DE" did not help. The log file still shows that "language" remains "en", but changing "language" to "de" didn't work. Is there a way to set the "language" in the configuration file, anyways?

However, what did work is setting up a new Eufy Security account located in the United States. Using this account, the Homebridge plugin found my Eufy devices. So, it appears to be an issue when the Eufy Security account is registered in another county other than the States.

[preachrman007]

Ok. I’ve tried creating a new Eufy account with a location of United States and then sharing to that account. Unfortunately, it looks like you can’t share between countries.

I guess I’m going to have to add my device directly to the US account, but, unless there’s a trick I’m missing, I need physical access to the camera, which means borrowing a ladder.

[schliemann]

@preachrman007 @viserion81

What do you have in the region setting of the eufy app?

I have Denmark. But can find devices if country is US as well.

[preachrman007]

United Kingdom

[viserion81]

Well, in the Eufy Security App it's "Germany" for my normal account and "United States" for the guest account that I've generated and for which I can at least see the devices in Homebridge.

[schliemann]

@preachrman007 Try GB instead of UK

[preachrman007]

@schliemann I didn't get an error message about countries, but still no devices are showing just as in my first screenshot. The country reference is just the one in /usr/local/lib/node_modules/homebridge-eufy-security/dist/platform.js, correct? No where else I need to change it?

Digging a little deeper into a closed issue, I also saw where you added a Country choice to the Beta. I tried running it as well, but still no change.

[schliemann]

Very odd. My region is DK for admin and guest account. And my country in the plugin is US. And I have never had any issues.

[preachrman007]

Just for fun, I tried the Beta version again. Setting the country there doesn't seem to change the platform.js file as the country references are still to US. I manually changed them in the file, but still no luck with devices showing up. After manually editing, Homebridge status logs show the country as "GB" .

[lenoxys]

Just for fun, I tried the Beta version again. Setting the country there doesn't seem to change the platform.js file as the country references are still to US. I manually changed them in the file, but still no luck with devices showing up. After manually editing, Homebridge status logs show the country as "GB" .

this can happened please clear your web browser cache. Does this fix your issue ?

[preachrman007]

Just for fun, I tried the Beta version again. Setting the country there doesn't seem to change the platform.js file as the country references are still to US. I manually changed them in the file, but still no luck with devices showing up. After manually editing, Homebridge status logs show the country as "GB" .

this can happened please clear your web browser cache. Does this fix your issue ?

Unfortunately, this doesn’t seem to make any difference.

[schliemann]

@preachrman007 Bropat has stated he will fix this in the next version.

https://github.com/bropat/eufy-security-client/issues/106#issuecomment-1028290035

[schliemann]

@preachrman007 The work around from bropat until next release is this:

https://github.com/bropat/eufy-security-ws/issues/74#issuecomment-1024619656

[schliemann]

@preachrman007 I can see that @lenoxys updated the package. Please re-test.

[preachrman007]

@schliemann I updated to the latest beta (I presume that’s the update you meant.) and clicked “Startover the Wizard Process”. Still not having any devices appear.

On 6 Feb 2022, at 12:43, schliemann @.***> wrote:

@preachrman007 https://github.com/preachrman007 I can see that @lenoxys https://github.com/lenoxys updated the package. Please re-test.

— Reply to this email directly, view it on GitHub https://github.com/samemory/homebridge-eufy-security/issues/343#issuecomment-1030825241, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQGR3OY5TNDREU5QU3RMKDUZZUF5ANCNFSM5NAVZRIA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.

[disappointingMrAnderson]

@preachrman007 I can see that @lenoxys updated the package. Please re-test.

Hello everyone, I signed up to Github to thank all the contributors for your work on this plugin. I can also report that I am facing the issue that is described here and that 1.1.1-beta.18 did not solve the issue for me.

Some details about my configuration:

• Homebridge running on Mac Mini
• Homebridge version: 1.4.0
• Node.js version: 16.13.2
• NPM version: 8.4.0
• homebridge-eufy-security version: 1.1.1-beta.18
• Eufy security version: 4.0.0 (sadly updated before becoming aware of this issue)
• Region (in Eufy app): Germany

I had tried to make this work (I'm relatively new to Homebridge) before 1.1.1-beta.18 was released, but with the same result as the others in this thread. After 1.1.1-beta.18 was released, I deleted the plugin entirely, checked that all configuration for the platform "EufySecurity" was gone from the config.json, reinstalled the plugin (manually choosing 1.1.1-beta.18), and started the wizard process. The result is the same as @preachrman007 describes - still, no devices appear.

I use a second Eufy account with whom I share the home/devices (I have tried both methods) and that account has admin rights.

I am happy to provide anything (e.g., logs) that might facilitate narrowing down the issue.

[lenoxys]

Could you retest on beta .19 ?

[preachrman007]

Not able to log in now. The following appears in the bottom right:

Getting the following error messages in the main Homebridge Log:

[2/8/2022, 9:35:43 PM] [Homebridge UI] [homebridge-eufy-security] [1.1.1-beta.19] ERROR: Status return code 401, invalidate token { status: 401, statusText: 'Unauthorized' } [2/8/2022, 9:35:43 PM] [Homebridge UI] [homebridge-eufy-security] [1.1.1-beta.19] ERROR: Status return code not 200 { status: 401, statusText: 'Unauthorized' }

Revd. Adam Payne Godalming United Church (A Methodist and United Reformed Congregation) Godalming, Surrey

On 8 Feb 2022, at 21:28, Aurélien @.***> wrote:



Could you retest on beta .19 ?

— Reply to this email directly, view it on GitHub https://github.com/samemory/homebridge-eufy-security/issues/343#issuecomment-1033078939, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQGR3JG5D7NJARQ4KMOEZTU2GDHDANCNFSM5NAVZRIA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.

[fullphat]

Just tried Beta 19. The plugin removed my floodlight camera so I had to add it again via the wizard and then sort out my HomeKit automations and config. First time this has happened with the betas.

Streaming seems less responsive but not able to troubleshoot right now.

[lenoxys]

Not able to log in now. The following appears in the bottom right:

Getting the following error messages in the main Homebridge Log:

[2/8/2022, 9:35:43 PM] [Homebridge UI] [homebridge-eufy-security] [1.1.1-beta.19] ERROR: Status return code 401, invalidate token { status: 401, statusText: 'Unauthorized' } [2/8/2022, 9:35:43 PM] [Homebridge UI] [homebridge-eufy-security] [1.1.1-beta.19] ERROR: Status return code not 200 { status: 401, statusText: 'Unauthorized' }

Revd. Adam Payne Godalming United Church (A Methodist and United Reformed Congregation) Godalming, Surrey

On 8 Feb 2022, at 21:28, Aurélien @.***> wrote:



Could you retest on beta .19 ?

— Reply to this email directly, view it on GitHub https://github.com/samemory/homebridge-eufy-security/issues/343#issuecomment-1033078939, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQGR3JG5D7NJARQ4KMOEZTU2GDHDANCNFSM5NAVZRIA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.

Please disable your plug-in for a day. Looks like you've been banned. I've got this issue in the past just need to wait the unban happens. Make sure to disable it for a full day and remove ur login and password and redo the wizard.

[lenoxys]

Just tried Beta 19. The plugin removed my floodlight camera so I had to add it again via the wizard and then sort out my HomeKit automations and config. First time this has happened with the betas.

Streaming seems less responsive but not able to troubleshoot right now.

First time I see that. I've just updated the bropat lib. The only thing which could imply accessories removing is a change on the serial number. We use that to generate the UUID.

[fullphat]

Just tried Beta 19. The plugin removed my floodlight camera so I had to add it again via the wizard and then sort out my HomeKit automations and config. First time this has happened with the betas.

Streaming seems less responsive but not able to troubleshoot right now.

First time I see that. I've just updated the bropat lib. The only thing which could imply accessories removing is a change on the serial number. We use that to generate the UUID.

Nothing has changed with my setup so far as I'm aware. I couldn't get the log, but I saw two entries saying "removing cached accessory...". When I ran the wizard I had to change my country to U.K. so not sure if it's related to that?

I'm still getting snapshots but now with lots of ffmpeg analysis warnings. Streaming won't work at all anymore.

[moodgorning]

I am having the same issue, not getting any devices. I noticed that I can't set the country in the plugin. It allows to choose during setup, but it will always reset to algeria. I also can't find any entry of the county in the config.json. I am located in Singapore and have selected Singapore in the Eufy App. This is on Beta 19

[karesake]

Ahh Come on! No Devices / all devices lost after Updating to 1.1.1 B19! Still nothing with downgrade to 1.0.8! Excuse me, but are the updates even checked before they are published? I do not think so! Of course, it's a free project, but it's getting on your nerves that nothing works after every update.

[njuart]

After installing beta 19, all devices also were gone from Home app. But, I had different region set in Eufy app and in config, after putting correct region in config all devices showed up again after server restart. But had to re-do all my automations.

@karesake it's BETA, no one said it will be stable straight away. That's why there are people who are willing to test beta and understand that some unexpected stuff might happen.

[moodgorning]

From the logs I cans ee that the plugin is setting my region to US: [EufySecurity-1.1.1-beta.19] INFO: Country set: US Looks like the country config is not picked up correctly or hardcoded to US at the moment

[moodgorning]

adding "country": "SG" manually to the config json seems to get the plugin to connect to the right region as I see Country set: SG in the logs at startup. However I still don't get any station or device returned. The advanced config UI also still shows Algeria no matter what I set

[karesake]

After installing beta 19, all devices also were gone from Home app. But, I had different region set in Eufy app and in config, after putting correct region in config all devices showed up again after server restart. But had to re-do all my automations.

@karesake it's BETA, no one said it will be stable straight away. That's why there are people who are willing to test beta and understand that some unexpected stuff might happen.

Yes, that's right. But what do I want to do? A normal version no longer appears and there are mass errors in 1.0.8. First and foremost, the terribly available stream of the doorbell. Then the double notifications when ringing. The previous versions always worked, hence the question of whether someone will test it at all before

[schliemann]

After installing beta 19, all devices also were gone from Home app. But, I had different region set in Eufy app and in config, after putting correct region in config all devices showed up again after server restart. But had to re-do all my automations. @karesake it's BETA, no one said it will be stable straight away. That's why there are people who are willing to test beta and understand that some unexpected stuff might happen.

Yes, that's right. But what do I want to do? A normal version no longer appears and there are mass errors in 1.0.8. First and foremost, the terribly available stream of the doorbell. Then the double notifications when ringing. The previous versions always worked, hence the question of whether someone will test it at all before

No one forced you to update? The latest version was created in order to bump the client library to the latest version which was supposed to solve an issue with no devices found.

If you want to complain because of lackluster homekit support you are welcome to drop by the eufy forums and do so.

[disappointingMrAnderson]

Could you retest on beta .19 ?

Tested again with beta .19. Deleted the plugin, reinstalled. When choosing, "Germany" as region during the wizard process, I get an error saying "undefined is not an object (evaluating 'response.result')". If I choose "United States", I am able to save. I can change the region manually in the config.json, but that doesn't lead to any devices' being found.

I hope you're not getting too frustrated because of some of the entitlement on here...

[lenoxys]

Ahh Come on! No Devices / all devices lost after Updating to 1.1.1 B19! Still nothing with downgrade to 1.0.8! Excuse me, but are the updates even checked before they are published? I do not think so! Of course, it's a free project, but it's getting on your nerves that nothing works after every update.

You can go back to .18 if it's works for you by selecting it instead of .19

[lenoxys]

From the logs I cans ee that the plugin is setting my region to US:

[EufySecurity-1.1.1-beta.19] INFO: Country set: US

Looks like the country config is not picked up correctly or hardcoded to US at the moment

Looks like browser cache issue can you clear it and test again ?

[karesake]

Again, this is not supposed to be an accusation against the developers here. Why am I updating? Because I hope that HKSV will one day be integrated and one naturally hopes that the new version will work even better than the previous one.

However, you don't think about the fact that all devices are removed and not even found anymore.

Eufy has completely lost interest in HomeKit and the new products that do not need HomeBase are not only unusable without HomeKit, but also as a security system, as they cannot issue an alarm when a door is opened.

Sorry for the tone! Shouldn't be meant as it happened to some. Downgrading to Beta 18 did not work. The version was probably not found.

[GIBBI91]

Hi together,

I´m new to all the hombridge stuff and just wanted to include my doorbell. If found this plugin and also faced the mentioned issue, there is no device listed when I login to my Eufy Account.

I´m also from Germany as previous people here in the post.

I´ve tried installing the latest Beta (26) there I can select "Germany", but when the Plugin starts searching for devices there is an "stations undefined" Error message.

Do you know how it can be fixed? :)

Of course I´m an admin with all administrative privileges to add the doorbell.

Thank you!

[lenoxys]

Hi together,

I´m new to all the hombridge stuff and just wanted to include my doorbell. If found this plugin and also faced the mentioned issue, there is no device listed when I login to my Eufy Account.

I´m also from Germany as previous people here in the post.

I´ve tried installing the latest Beta (26) there I can select "Germany", but when the Plugin starts searching for devices there is an "stations undefined" Error message.

Do you know how it can be fixed? :)

Of course I´m an admin with all administrative privileges to add the doorbell.

Thank you!

hello can you open a new issue with debug enable and log attached ?

[GIBBI91]

i

Strangely it works now after reinstalling the plugin again this morning.

Only the live feed of the doorbell doesn´t work, but if somebody rings I got notfied by homekit and I can also see a picture of the live feed, but then when homekit tries to connect to the doorbell the camea doesn´t answer and I get nothing displayed in the home app.

Generally it feels like Eufy has some problems here.