search

homebridge-eufy-security / plugin

Homebridge plugin to control certain Eufy Security devices
Apache License 2.0
158 stars 24 forks source link

[Bug]: Plugin thinks cameras are motion sensors #448

Open Chimchimgli opened 9 months ago

Chimchimgli commented 9 months ago

What happened?

All was working fine with my setup of an S380 HomeBase and 4 S330 (EufyCam 3's), until I added one of Eufy's latest products; the eufyCam E330 (Professional). It wasn't compatible with my current version which as of right now is the latest stable version - v2.2.21, as expected. I then tried installing newer versions such as v.2.3.5 - hksv, v.2.3.1-beta.3 - beta to see if they would have any compatibility with the E330, but now all my cameras appear to be motion sensors, including my S330's, and now it only shows up as such on the Home app.

I was thinking part of the issue might be because my HB3 is itself on a beta firmware as Eufy is testing their new AI features like Multi-track or stitch... something like that.

Anyway something has rendered all my previously working cams unusable/visible, and yea kinda just bummed out by all this to be honest. I have tried multiple times in/un-stalling the plugin, but they would always end up being motion sensors. What's curious is normally they would default as motion sensors where it would then have to be manually changed to a camera, but upon installing it is already showing as a camera.

Unfortunately I didn't save any logs, but one I noticed was something along the lines of ([cam1] doesn't need battery characteristic as it is a motion sensor, adding anyway')

Device Type

Indoor Camera (Supported)

Plugin Version

v2.0.x (Supported)

HomeBridge Version

v1.6.x (Supported)

NodeJS Version

v18 (Supported)

Operating System

Raspbian 10+ (Supported)

Relevant log output

[will reinstall plugin to duplicate issue and update this post]

config

[will reinstall plugin to duplicate issue and update this post]
github-actions[bot] commented 9 months ago

Did you check this Common Issues pages ?

Sebastianwerner1985 commented 9 months ago

I have the same issue. Every device is set to camera in settings as well. All Eufy 2c cams. Same message in logs.

Chimchimgli commented 9 months ago

Just wanted to update that after reinstalling v2.2.21, after getting the same log output that the cameras are motion sensors, I just tried to toggle the option to change to motion sensor then back to camera, even though it was on camera in the first place. After saving and restarting Homebridge, for the one camera that I did those settings to, it changed to camera, but the remaining cam’s remained as motion sensors - that is until I did the same toggle for the rest of them. Oddly enough it worked.

One other thing I should note is for all the cameras I had to copy preset, with nothing else changed except the acodec which I put to copy, which perhaps coincidentally coincided with the error. I then changed it back to the default libkacc or ‘blank’ settings. And for my camera settings in the native eufy app, streaming and recording is set to 1080p. Curiously it is the recording option, especially when I set it to 4K where it ‘breaks’ the plugin, rather than the stream setting. Anyway all is good and back to normal as usual.

Sebastianwerner1985 commented 9 months ago

That worked for me too, however this seems to be all over the place right now. I would get unresponsive cameras until i activate RTSP in the plugin. I have not activated RTSP in the eufy app for any camera. With the toggle beeing switched on i can get a stream in 640px. After enableing audio transmission it stops working again all together. Not sure if it just a visual bug on the front end toggles or something else. For my setup the plugin is not useable at the moment unfortunately.