You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an error in the addon log, but I am not sure it's related (I will open another issue to track that):
2023-10-09 09:23:37.483 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2023-10-09 09:23:40.306 INFO Connected to station T8030xxxxxxx on host 192.168.188.222 and port 12487
2023-10-09 09:23:42.765 INFO Push notification connection successfully established
2023-10-09 09:23:43.537 ERROR onStationDatabaseQueryLatest Error
{
error: {
message: "DeviceNotFoundError: Device doesn't exists",
stacktrace: "DeviceNotFoundError: Device doesn't exists\n" +
' at EufySecurity.getDevice (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:372:15)\n' +
' at EufySecurity.onStationDatabaseQueryLatest (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:2344:26)\n' +
' at Station.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:479:97)\n' +
' at Station.emit (node:events:525:35)\n' +
' at Station.emit (node:domain:489:12)\n' +
' at Station.onDatabaseQueryLatest (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:7377:14)\n' +
' at P2PClientProtocol.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:78:80)\n' +
' at P2PClientProtocol.emit (node:events:513:28)\n' +
' at P2PClientProtocol.emit (node:domain:489:12)\n' +
' at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1860:42)'
},
stationSN: 'T8030xxxxxxx',
returnCode: 0
}
2023-10-09 09:25:39.840 INFO Client disconnected with ip: 127.0.0.1 port: 49518 code: 1000 reason: Normal Closure
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
My eufycam S300 is not being recognized.
Using Homebase 3 (S380)
I have an error in the addon log, but I am not sure it's related (I will open another issue to track that):
The text was updated successfully, but these errors were encountered: