Eufy Security Integration

The data exists but the picture url isnt accesible
It was accesible before and i didnt change anything except updating the addon :wink:

Should i try to remove the camera and re-add it? If so, whats the best method for this?

I have exactly the same issue and i can share the camera if you can tell me how (= point me to the how-to).

Apparently there is no fix available :frowning: Camera 2C has no image · Issue #48 · bropat/eufy-security-ws · GitHub or there is nothing to fix. @bropat has the correct point of contact for the issue

Why dont we use http 1.0/1.1 then?
Anyone also seeing issues with webrtc now with latest HA update?

I don’t have any dependency or preference over http2.0 vs http1.1, not sure if this is an issue of the client (browser or home assistant http client) or is it coming from eufy-security-ws. So, not sure what is exact problem.

If anyone is having issues about webrtc installation, please check here: Webrtc stopped working after update core to version core-2021.12.0

1 Like

Hi all, integration has been updated recently with long waited switches, users can use switches to enable and disable features on devices.

4 Likes

Thanks a lot for the developments @anon63427907
I take it the minimum version for this intetgration is 2021.12?
I get the following after upgrading to the latest version of the integration on 2021.11.5:

Error while setting up eufy_security platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/eufy_security/binary_sensor.py", line 40, in async_setup_entry
    ("battery_low", "Battery Low", "state.batteryLow", None, DEVICE_CLASS_BATTERY),
NameError: name 'DEVICE_CLASS_BATTERY' is not defined

please get latest version again, it should be fixed today.

1 Like

Thanks, fixed indeed

Platform eufy_security does not generate unique IDs. ID eufy_security_T8200[redacted]08EC_audio_recording_switch already exists - ignoring switch.doorbell_audio_recording
Is this also related to the latest update?

1 Like

yes yes yes :slight_smile: fixed now, apparently i was rushing too much and did not test enough

1 Like

Lol just saw the update notification, restarting after applying. Thanks for the speed of light updates

image
Yeah ! :slight_smile:

Brilliant! Works like a charm. Now that the basics work I look forward to explore these new features.

On the doorbell I had to reduce quality but the delay is now less than 3 seconds with webrtc. Thanks!

1 Like

Hi fuatakgun,

I am getting this still.

2021-12-15 05:06:37.931 ERROR Status return code not 200
{
status: 423,
statusText: ‘Locked’
}
2021-12-15 05:06:38.754 ERROR Status return code 401, invalidate token
{
status: 401,
statusText: ‘Unauthorized’
}
2021-12-15 05:06:38.757 ERROR Status return code not 200
{
status: 401,
statusText: ‘Unauthorized’
}
2021-12-15 05:06:38.839 ERROR Status return code not 200
{
status: 423,
statusText: ‘Locked’

Please create a github issue to track this and double check if your account has 2 factor authentication enabled, integration does not support it

And now, we have supports for multi selection options.

5 Likes

Nice work.
Also good move on the versioning, I was going to ask :+1:
Minor bug: the icon of the binary_sensor.doorbell_status_led_enabled appears to be set to mdi: led-on (with a space in between)
I’ve just submitted a PR

1 Like

Ur going as fast as lightning! Thx !

1 Like

Thanks for the PR, merged

1 Like