Just to clarify, these are error logs from add-on, not integration. Have you tried to restart it? Keep in mind, latest version is 0.7.0
I finally found time to get this integration implemented. I have the following setup:
- (6) EufyCam 2C
- (3) Pan/tilt indoor cams
- (1) wired doorbell
I have the video feed working and the door press seems to get notified. What I am not getting is motion detection from any of the cameras or doorbell. The sensors in the integration are not changing from clear.
Any thoughts?
Are notifications on in the eufy app? If not, it wonât work.
Also be sure to check the right sensor, EG the global one. The others are depending on settings within eufy (either or)
You are receiving these motion notifications in your mobile app?
Odd I was not. I went ahead and reset all the devices and now all is good.
Hey
Yes these are logs from addon,
Yes i tried restart addon, restart home assistant, restart integration
everything
Iâm on 0.7.0 indeed, it broke after update of integration i think
Weird it says registration failed
I have similar issues /errors, push token is not updating. Doubt it relates to the integration, probably on eufyâs side, will flag with @bropat on his repo.
Sensor/doorbell notifications are not coming through for the doorbell, which is challenging (or relaxing depending on the pov ) as doorbell ring triggers my doorbell relay
In addition to your errors I also get the following:
2022-01-22 17:55:03.424 ERROR P2PClientProtocol.lookup(): station: T8010Nxxx - All address lookup tentatives failed.
2022-01-22 17:55:03.425 INFO Timeout connecting to station T8010Nxx
2022-01-22 17:55:23.500 INFO Connected to station T8010Nxx on host 192.168.xxxxx and port 10310
2022-01-22 17:55:23.503 WARN Station T8010Nxx - Command aged out from queue
{
commandType: 1145,
nestedCommandType: undefined,
channel: 0,
ageing: 80056,
maxAgeing: 45000
}
Will double check two things in my network, 1) I moved the station to an IoT vlan and 2) I turned adguard dns on on that vlan network. Donât think itâs related but good to rule out.
Reverting to the regular vlan (eg. same subnet as home assistant is on) caused most errors to disappear. Only one remaining (and recurring) is
2022-01-22 19:34:47.763 ERROR Status return code not 200
{
status: 204,
statusText: 'No Content'
}
@skank - did you by any chance change something in your router settings? Eg. something making it more difficult for your homebase to touch base with Eufycloud?
I have the same errors in my setup and no change was done recently other than updating addon version. Can you please share the issue link here for this error?
The no content error or the other ones? I did not raise any issue, for the other ones on my end it seems as changing vlan âsolvedâ it.
As for the no content, it appears when I give a command. There is however no debugging in the add on (to my knowledge?) so difficult to check which command causes it.
Your errors are totally different than mine.
Also i didnt change anything at router side.
It just broke after i updated integration strangly
Edit: yeah have the no content error too
2022-01-23 12:28:01.763 INFO Eufy Security server listening on port 3000
2022-01-23 12:28:02.273 ERROR Status return code not 200
{
status: 204,
statusText: âNo Contentâ
}
2022-01-23 12:28:04.348 INFO Connected to station T8010P2320280D92 on host x.x.x.X and port x
2022-01-23 12:28:04.994 ERROR Status return code not 200
{
status: 204,
statusText: âNo Contentâ
}
2022-01-23 12:28:09.973 ERROR registerFid - Error:
RequestError connect ECONNREFUSED 0.0.0.0:443
details:
{
code: âECONNREFUSEDâ,
timings: undefined
}
error stack:
⢠index.js:1183 _makeRequest
node_modules/got/dist/source/core/index.js:1183:19
⢠task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
⢠index.js:334
node_modules/got/dist/source/core/index.js:334:17
2022-01-23 12:28:09.983 ERROR registerFid - Status return code not 200
{
status: undefined,
statusText: undefined,
data: undefined
}
2022-01-23 12:28:09.998 ERROR registerFid - Generic Error:
Error FID registration failed with error: undefined
@skank @RT1080
Had the same error regarding
2022-01-22 14:03:35.779 ERROR Status return code not 200
{
status: 204,
statusText: 'No Content'
}
since this Friday. If I got the comment from @anon63427907 correctly, he also has these log messages in his setup now.
As my log didnât have these entries before it might really have something to do with a change on eufyâs sideâŚ
Anyway - I was able to get rid of the âNo Contentâ error by restoring a backup of the 0.6 version from the addon. Maybe this is worth a try for you tooâŚ
I did not include my full log, as I said, I had the same errors (token, FID etc) which disappeared when I reset the homebase IP address.
Given your error log indicates ECONNREFUSED 0.0.0.0:443
I think itâs worth a try, the add-on tries to connect but is unsuccessful. A simple reboot of the homebase might be worth to check.
ok thx for the headsup, gonna reboot now fingers crossed
Will try but donât think I have that one backedup, v0.7 however worked with prior versions of the integration.
Maybe commands are send by the integration which the add on does not recognise? difficult to check w/o debug
Reboot homebase didnt fix it:(
Iâm also getting the same error in the add-on log. but my cameras are working fine (Iâm not using streaming in HA but everything else like arm/disarm and sensors are all fine).
2022-01-23 13:19:48.081 ERROR Status return code not 200
{
status: 204,
statusText: 'No Content'
}
Oddly one of the earlier errors has returned:
P2PClientProtocol.lookup(): station: T800Nxxx - All address lookup tentatives failed.
2022-01-23 12:48:21.184 INFO Timeout connecting to station T8010xxx
Anyone else âfamiliarâ with this one?
@anon63427907 - is there a way to downgrade the add on?
Did you also downgrade the integration? inside integration, there is schema version (set to 7 as of now) and downgrading to 0.6.0 might create issues on integration side.
I will generate debug logs and create an issue under eufy-security-ws repository today.
I donât know any way of downgrading the add-on without restoring from a backup