Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Integration is not working (locked, mqtt, no devices etc) #258

Closed
bearkiter opened this issue Feb 6, 2022 · 52 comments
Closed

Integration is not working (locked, mqtt, no devices etc) #258

bearkiter opened this issue Feb 6, 2022 · 52 comments
Assignees
@fuatakgun

Comments

@bearkiter
Copy link

Everything was working perfectly for about 3 weeks, then for no reason I could see I get:

2022-02-06 14:45:11.802 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-06 14:45:15.638 ERROR MQTT Error
Error Connection refused: Not authorized
details:
{
code: 5
}
error stack:
• client.js:1386 MqttClient._handleConnack
node_modules/mqtt/lib/client.js:1386:17
• client.js:547 MqttClient._handlePacket
node_modules/mqtt/lib/client.js:547:12
• client.js:436 work
node_modules/mqtt/lib/client.js:436:12
• client.js:450 writable._write
node_modules/mqtt/lib/client.js:450:5
• _stream_writable.js:409 doWrite
node_modules/readable-stream/lib/_stream_writable.js:409:139
• _stream_writable.js:398 writeOrBuffer
node_modules/readable-stream/lib/_stream_writable.js:398:5
• _stream_writable.js:307 Writable.write
node_modules/readable-stream/lib/_stream_writable.js:307:11
• readable:754 ondata
node:internal/streams/readable:754:22
• node:events:390 emit
node:events:390:28
• readable:315 addChunk
node:internal/streams/readable:315:12
2022-02-06 14:45:15.693 INFO MQTT connection closed
2022-02-06 14:45:16.816 INFO No stations found.
2022-02-06 14:45:17.576 INFO No devices found.
2022-02-06 14:45:17.903 INFO Push notification connection successfully established
2022-02-06 14:45:30.584 INFO No stations found.
2022-02-06 14:45:31.321 INFO No devices found.

All entities offline.

Have tried reinstalling addon, repo and integration. No luck.
@fuatakgun
Copy link
Owner

Do you have any add blocker? This looks an issue a blocked network connection to eufy servers.

@bearkiter
Copy link
Author

bearkiter commented Feb 6, 2022 via email

@bearkiter
Copy link
Author

bearkiter commented Feb 6, 2022 via email

@dMopp
Copy link

dMopp commented Feb 6, 2022

Same issue here. In addition, my Account seems to be blocked:(

@bearkiter
Copy link
Author

HASSOS on RPi 4, core downgraded along with Eufy Addon (12/21 core and 0.7.0 eufy) works.

Upgrade both, addon breaks. Will try today only upgrading the addon and leaving the core on older, or upgrading the core and leaving the addon unpatched to differentiate.

@TEF2one
Copy link

TEF2one commented Feb 6, 2022

Same here everything working fine for moth and since the last update everything is now unavailable...

@san84
Copy link

san84 commented Feb 6, 2022

Same issue with core 2022.2.2 and addon 0.8.

@fuatakgun
Copy link
Owner

I am on 2022.2.0 for Home Assistant and 0.8.0 of add-on and all is working, apparently, something has changed on core but i will be able to take a look only tomorrow (EU) evening. Please rollback to earlier core version if you need this add-on.

@JimGeersinga
Copy link

Same problem here after updating to HA 2022.2.0 and Eufy 0.8.0 no station and devices found

2022-02-06 22:22:40.279 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-06 22:22:41.594 INFO MQTT connection successfully established
2022-02-06 22:22:41.794 INFO No stations found.
2022-02-06 22:22:41.891 INFO No devices found.
2022-02-06 22:22:42.198 INFO Push notification connection successfully established
2022-02-06 22:32:42.178 INFO No stations found.
2022-02-06 22:32:42.251 INFO No devices found.

@fuatakgun
Copy link
Owner

Hi all, please get latest version of add-on 0.8.1 and latest home assistant would work fine. There was no change in integration or core, it was mainly due to 0.8.0 version of add-on, should be fixed now. All is working on my local with 2022.2.2 and 0.8.1.

@fuatakgun
Copy link
Owner

Triple checked with new install, restarted addon with reloaded integration and restarted raspberry pi, all is working fine.

@bearkiter
Copy link
Author

Updated as suggested, broken again. Reverting to previous versions.

@bearkiter
Copy link
Author

Once core and addon updated, rpi rebooted.
Add on starts- no errors, but fails to discover any entities.

@fuatakgun
Copy link
Owner

if you have issues with no shared devices, can you use your main account to validate this is not a device sharing issue?

@fuatakgun fuatakgun reopened this Feb 7, 2022
@bearkiter
Copy link
Author

using main account,. creating new sharing account to re-test

@TEF2one
Copy link

TEF2one commented Feb 7, 2022

Juste updated to 8.1 an restarted, no error in logs but still no stations nor devices found

@fuatakgun
Copy link
Owner

No device issue was supposed to be fixed by 0.8.0 version. Please check here: bropat/eufy-security-ws#74

@san84
Copy link

san84 commented Feb 7, 2022

Addon is working again with 0.8.1 (thank you!), but still no stations/devices found.Country: CH

@rpartapsing
Copy link

rpartapsing commented Feb 7, 2022 •
edited

same issue here, all worked fine until today:

2022-02-07 09:04:11.074  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2022-02-07 09:04:12.334  INFO  No stations found. 
2022-02-07 09:04:12.443  INFO  No devices found. 
2022-02-07 09:04:12.698  INFO  Push notification connection successfully established 
2022-02-07 09:09:03.554  INFO  No stations found. 
2022-02-07 09:09:03.640  INFO  No devices found. 
2022-02-07 09:10:45.016  INFO  Client disconnected with ip: 192.168.178.149 port: 52756 code: 1006 reason:  
2022-02-07 09:11:03.167  INFO  No stations found. 
2022-02-07 09:11:03.258  INFO  No devices found. 
2022-02-07 09:21:03.609  INFO  No stations found. 
2022-02-07 09:21:03.711  INFO  No devices found.

Core: 2022.2.3 add-on version 0.8.1

@fuatakgun
Copy link
Owner

Please follow here: bropat/eufy-security-ws#74
or create a new one under eufy-security-ws as I dont have anyway to help here.

@san84 san84 mentioned this issue Feb 7, 2022
Closed
@Beer17HWAM
Copy link

Tried to share devices with an old Eufy app (version 2.4.0) on Android. Same results. No stations found. No devices found.
When can we expect an update??

@dMopp
Copy link

dMopp commented Feb 7, 2022 •
edited

Since my account is unlocked its working fine with latest Version. I created a second account and shared my home, working fine!

@Beer17HWAM
Copy link

Since my account is unlogged, its working fine with latest Version. I created a second account and shared my home, working fine!

I did the same but it's not working for me:

docker run -it --privileged -e USERNAME=xx@xxxx.com -e PASSWORD=xxxx -p 3300:3000 bropat/eufy-security-ws:0.8.1
2022-02-07 11:31:20.162 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-07 11:32:09.292 INFO Client disconnected with ip: 172.17.0.1 port: 60844 code: 1006 reason:
2022-02-07 11:33:41.922 INFO No stations found.
2022-02-07 11:33:42.350 INFO Push notification connection successfully established
2022-02-07 11:33:42.465 INFO No devices found.
2022-02-07 11:34:11.521 INFO No stations found.
2022-02-07 11:34:12.043 INFO No devices found.

@dMopp
Copy link

dMopp commented Feb 7, 2022

Did you logged into the app once and accepted the invitation?

@Beer17HWAM
Copy link

Beer17HWAM commented Feb 7, 2022 via email •
edited

@dMopp
Copy link

dMopp commented Feb 7, 2022

Oh okay, then i have no idea. :(

@Beer17HWAM
Copy link

How can I fill the country if I run a docker.

docker run -it --privileged -e USERNAME=xx@xxxx.com -e PASSWORD=xxxx -p 3300:3000 bropat/eufy-security-ws:0.8.1

I use local port 3300 because port 3000 is already used on my Raspberry pi4.

@fuatakgun
Copy link
Owner

Releasing a new version following bropat's release but i will not be able to test it.

@rpartapsing
Copy link

rpartapsing commented Feb 7, 2022 •
edited

no worries I can test it on my part

@fuatakgun
Copy link
Owner

Released new version, installed it, working main functionality, looks ok.

@rpartapsing
Copy link

rpartapsing commented Feb 7, 2022 •
edited

I guess it takes some time before hacs recognizes a new version is available for the Eufy Security Add-on.
So I ran the container instead:
docker run -it --privileged -e USERNAME=foo -e PASSWORD=bar -e COUNTRY=NL -p 3000:3000 bropat/eufy-security-ws:0.8.2
Retrieved this log:

Status: Downloaded newer image for bropat/eufy-security-ws:0.8.2
2022-02-07 17:57:20.093  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
Exception in PromiseRejectCallback:
/usr/src/app/node_modules/eufy-security-client/build/http/api.js:224
        return types_1.AuthResult.OK;

RangeError: Maximum call stack size exceeded
Exception in PromiseRejectCallback:
/usr/src/app/node_modules/eufy-security-client/build/http/api.js:440
            switch (await this.authenticate()) {
                               ^

RangeError: Maximum call stack size exceeded
2022-02-07 17:57:20.324  ERROR Error: 
 RangeError  Maximum call stack size exceeded
error stack:
• CallSitesHelper.ts:27 FormatStackTrace
    node_modules/tslog/src/CallSitesHelper.ts:27:16

• CallSitesHelper.ts:59 prepareStackTrace
    node_modules/tslog/src/CallSitesHelper.ts:59:31

• errors:141 maybeOverridePrepareStackTrace
    node:internal/errors:141:29

• errors:115 prepareStackTrace
    node:internal/errors:115:5

• CallSitesHelper.ts:81 getCallSites
    node_modules/tslog/src/CallSitesHelper.ts:81:15

• LoggerHelper.ts:50 getCallSites
    node_modules/tslog/src/LoggerHelper.ts:50:35

• LoggerWithoutCallSite.ts:376 _buildLogObject
    node_modules/tslog/src/LoggerWithoutCallSite.ts:376:55

• LoggerWithoutCallSite.ts:333 _handleLog
    node_modules/tslog/src/LoggerWithoutCallSite.ts:333:40

• LoggerWithoutCallSite.ts:258 debug
    node_modules/tslog/src/LoggerWithoutCallSite.ts:258:28


2022-02-07 17:57:20.328  ERROR Status return code not 200 
{
  status: undefined,
  statusText: undefined
}
2022-02-07 17:57:20.335  ERROR Error: 
 Error  `input` must not start with a slash when using `prefixUrl`
error stack:
• index.js:484 normalizeArguments
    node_modules/got/dist/source/core/index.js:484:23

• create.js:112 got
    node_modules/got/dist/source/create.js:112:39

• api.ts:492 request
    node_modules/eufy-security-client/src/http/api.ts:492:43

• api.ts:168 authenticate
    node_modules/eufy-security-client/src/http/api.ts:168:58

• task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

• api.ts:455 request
    node_modules/eufy-security-client/src/http/api.ts:455:21

• api.ts:112 getApiBaseFromCloud
    node_modules/eufy-security-client/src/http/api.ts:112:30

• api.ts:143 authenticate
    node_modules/eufy-security-client/src/http/api.ts:143:25

• api.ts:455 request
    node_modules/eufy-security-client/src/http/api.ts:455:21

• api.ts:112 getApiBaseFromCloud
    node_modules/eufy-security-client/src/http/api.ts:112:30


2022-02-07 17:57:20.338  ERROR Status return code not 200 
{
  status: undefined,
  statusText: undefined
}
2022-02-07 17:57:20.339  ERROR Token error 
{
  method: 'get',
  endpoint: '/domain/NL'
}
2022-02-07 17:57:23.683  INFO  No stations found. 
2022-02-07 17:57:23.935  INFO  No devices found. 
2022-02-07 17:57:25.232  INFO  Push notification connection successfully established

@rpartapsing
Copy link

btw this is only for cams connected to the homebase unit. (I have cams for outside and motion sensors)
I also have Eufy Ip cams, they dont have this issue.

@TEF2one
Copy link

TEF2one commented Feb 7, 2022

@rpartapsing , I would disagree I don't even have Homebase as I use only Solos and none are showing up anymore in home assistant.

@bearkiter
Copy link
Author

bearkiter commented Feb 7, 2022 via email

@kobioneil
Copy link

2022-02-07 23:00:45.824 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-07 23:00:49.783 INFO Connected to station T8010N13202418F1 on host 10.0.0.46 and port 16104
2022-02-07 23:00:49.852 INFO Connected to station T8021P1021260DBF on host 10.0.0.16 and port 18687
2022-02-07 23:00:50.027 INFO Connected to station T8410P20202205A8 on host 10.0.0.220 and port 19011
2022-02-07 23:00:50.356 INFO Connected to station T8400P2020460BE4 on host 54.219.251.168 and port 14052
2022-02-07 23:00:50.375 INFO Connected to station T8400P20204601DB on host 35.162.187.157 and port 10274
2022-02-07 23:00:50.511 INFO MQTT connection successfully established
2022-02-07 23:00:50.585 INFO Successfully registered to MQTT notifications for lock T8510Q1021260FCB
2022-02-07 23:00:56.168 ERROR Status return code not 200
{
status: 423,
statusText: 'Locked'
}
2022-02-07 23:00:56.185 INFO No stations found.

Same here, Im running on HomeAssistant Blue. Ever since upgrade, it seems to constantly get stuck right here

@san84
Copy link

san84 commented Feb 8, 2022

Thank you vry much for the new release - highly appreciated. It‘s actually the first time I can see the eufy cameras in HA.
I haven‘t managed to get RTSP/WebRTC video streams though… working on it.
Where is your KoFi link or similar?

@hunt350
Copy link

hunt350 commented Feb 8, 2022

I guess it takes some time before hacs recognizes a new version is available for the Eufy Security Add-on. So I ran the container instead: docker run -it --privileged -e USERNAME=foo -e PASSWORD=bar -e COUNTRY=NL -p 3000:3000 bropat/eufy-security-ws:0.8.2 Retrieved this log:

Status: Downloaded newer image for bropat/eufy-security-ws:0.8.2
2022-02-07 17:57:20.093  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
Exception in PromiseRejectCallback:
/usr/src/app/node_modules/eufy-security-client/build/http/api.js:224
        return types_1.AuthResult.OK;

RangeError: Maximum call stack size exceeded
Exception in PromiseRejectCallback:
/usr/src/app/node_modules/eufy-security-client/build/http/api.js:440
            switch (await this.authenticate()) {
                               ^

RangeError: Maximum call stack size exceeded
2022-02-07 17:57:20.324  ERROR Error: 
 RangeError  Maximum call stack size exceeded
error stack:
• CallSitesHelper.ts:27 FormatStackTrace
    node_modules/tslog/src/CallSitesHelper.ts:27:16

• CallSitesHelper.ts:59 prepareStackTrace
    node_modules/tslog/src/CallSitesHelper.ts:59:31

• errors:141 maybeOverridePrepareStackTrace
    node:internal/errors:141:29

• errors:115 prepareStackTrace
    node:internal/errors:115:5

• CallSitesHelper.ts:81 getCallSites
    node_modules/tslog/src/CallSitesHelper.ts:81:15

• LoggerHelper.ts:50 getCallSites
    node_modules/tslog/src/LoggerHelper.ts:50:35

• LoggerWithoutCallSite.ts:376 _buildLogObject
    node_modules/tslog/src/LoggerWithoutCallSite.ts:376:55

• LoggerWithoutCallSite.ts:333 _handleLog
    node_modules/tslog/src/LoggerWithoutCallSite.ts:333:40

• LoggerWithoutCallSite.ts:258 debug
    node_modules/tslog/src/LoggerWithoutCallSite.ts:258:28


2022-02-07 17:57:20.328  ERROR Status return code not 200 
{
  status: undefined,
  statusText: undefined
}
2022-02-07 17:57:20.335  ERROR Error: 
 Error  `input` must not start with a slash when using `prefixUrl`
error stack:
• index.js:484 normalizeArguments
    node_modules/got/dist/source/core/index.js:484:23

• create.js:112 got
    node_modules/got/dist/source/create.js:112:39

• api.ts:492 request
    node_modules/eufy-security-client/src/http/api.ts:492:43

• api.ts:168 authenticate
    node_modules/eufy-security-client/src/http/api.ts:168:58

• task_queues:96 processTicksAndRejections
    node:internal/process/task_queues:96:5

• api.ts:455 request
    node_modules/eufy-security-client/src/http/api.ts:455:21

• api.ts:112 getApiBaseFromCloud
    node_modules/eufy-security-client/src/http/api.ts:112:30

• api.ts:143 authenticate
    node_modules/eufy-security-client/src/http/api.ts:143:25

• api.ts:455 request
    node_modules/eufy-security-client/src/http/api.ts:455:21

• api.ts:112 getApiBaseFromCloud
    node_modules/eufy-security-client/src/http/api.ts:112:30


2022-02-07 17:57:20.338  ERROR Status return code not 200 
{
  status: undefined,
  statusText: undefined
}
2022-02-07 17:57:20.339  ERROR Token error 
{
  method: 'get',
  endpoint: '/domain/NL'
}
2022-02-07 17:57:23.683  INFO  No stations found. 
2022-02-07 17:57:23.935  INFO  No devices found. 
2022-02-07 17:57:25.232  INFO  Push notification connection successfully established

I have the same issue , any solution ?

@johnjoemorgan
Copy link

@hunt350 following @bearkiter 's advice I deleted the HACS and Add-On components. Restarted and reinstalled the Add-On. I got a similar error message to you. In configuration I input my secondary (guest) admin details and clicked the "reset to defaults" in the network section and saved and restarted the add-on. All errors went away and I installed the HACS part and everything's back.

@leonardpitzu
Copy link

Same issue for me. App is V.4 and i have correctly shared my "home". I am clueless as to what to do although it seems some have had more success at fixing this so it might not even be a bug but some misconfiguration...
ERROR Status return code not 200 { status: 423, statusText: 'Locked' }

@fuatakgun fuatakgun changed the title Addon broken Integration is not working (locked, mqtt, no devices etc) Feb 8, 2022
This was referenced Feb 8, 2022
Closed
Closed
Closed
@air720boarder
Copy link

Looks like this was just fixed in broplat's .84 release: bropat/ioBroker.eusec#228

@fuatakgun
Copy link
Owner

fuatakgun commented Feb 8, 2022 •
edited

I have tested new version locally, all is fine, updated the add-on version, please download latest version of add-on. (0.8.3)

@fuatakgun fuatakgun self-assigned this Feb 8, 2022
@DivanX10
Copy link

DivanX10 commented Feb 8, 2022

I have tested new version locally, all is fine, updated the add-on version, please download latest version of add-on. (0.8.3)

I tried it. I managed to pass the captcha, the integration worked

@DivanX10
Copy link

DivanX10 commented Feb 9, 2022

Strange behavior with a captcha. Updated Home Assistant to version 2022.4 and requested a captcha again. I entered everything correctly, a captcha error message appeared, but the integration itself started. It's like integration is launched bypassing the captcha

@Jo-Jo1987
Copy link

Jo-Jo1987 commented Feb 9, 2022 •
edited

I updated to 0.83 and using v 2.24.

Re-registered my device
Error changed:

2022-02-09 10:16:54.966 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-09 10:18:45.730 ERROR Response code not ok
{
code: 26015,
msg: 'This account has not been activated. Please check your inbox.'
}
2022-02-09 10:18:45.739 ERROR Token error
2022-02-09 10:20:13.988 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-09 10:20:50.315 ERROR Response code not ok
{
code: 26015,
msg: 'This account has not been activated. Please check your inbox.'
}
2022-02-09 10:20:50.325 ERROR Token erro

Tried incognito adding the right captcha, then it says,
Only one single instance is allowed

I will be awaiting the solution from bropat

Using home assistant 2022.2.5

@Jo-Jo1987
Copy link

Any breaking changes on this one?

@bearkiter
Copy link
Author

Broken again after 7.4 core update. Haven't investigated yet.

@fuatakgun
Copy link
Owner

Please get latest version of addon and try again

@Jo-Jo1987
Copy link

Jo-Jo1987 commented Feb 12, 2022 •
edited

2022-02-12 20:15:20.953 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-02-12 20:15:23.828 INFO Connected to station T8010P23214702B8 on host 192.168.1.15 and port 13072
2022-02-12 20:15:24.292 INFO Push notification connection successfully established

Excellent!

@JimGeersinga
Copy link

My app got updated to version 4.0 and after I reloaded the addon and integration it all worked again.
Thanks for your hard work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fuatakgun fuatakgun

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests