https://bropat.github.io/eufy-security-client/#/supported_devices
Thanks fuatakgun. I did take a look earlier - unfortunately the Garage Control Cam isnāt listed so I canāt tell whether it is supported (or not!).
I think, just setting this up and testing locally would be much more faster to find out. Even more, if it is working, you could inform @bropat to update supported devices page.
Donāt disagree - however, I have not yet purchased this. Whether this works with Home Assistant or not will be the deciding factor on whether I purchase or not. Unfortunately, as I am not in the US, returning the item in case it doesnāt work becomes much harder and cost prohibitive - otherwise I would have been happy to be the guinea pig.
Please do not make a buying decision based on home assistant support, life would be miserable.
Anytime, the integration might stop working or i might decide to move away and no one might maintain it.
1 Like
If I would make the decision now I would never buy eufy. The whole ālocalā pitch is a big scam. Still no rtsp on the doorbell, changes to the API.
Bropat and Fuatakgun made fantastic steps but ultimately we are at the whims of a crappy company.
Better to go for something fully local and set it up with frigate imho.
5 Likes
Alpha version is merged into master branch and released as version 6.
This is a breaking change and will probably require you to rework your existing automations and dashboards.
If you are happy with your current setup, there is no urgency to migrate but your integration might become inoperational in the future.
3 Likes
After starting from scratch again it all started working in the end. The only thing that stopped working is the thumnail images. But i see that thereās an update availble so Iāll see what that changes.
When you say breaking, does it also have impact on the rtsp and webrtc add-ons? Or will this just impact the naming and attributes of sensors?
Will install tonight; thanks as always!
I would say only naming of attributes. In my case after adjusting attributes it started to work again.
@alanmilinovic thanks, you are right. I am now following the naming convention of bropat from eufy-security-ws repository to keep everything under control.
Webrtc, rtsp streaming, rtsp add-on usage for p2p streaming should work as it is.
For the 6.0.0 release it lists
BREAKING CHANGES
Read below
BREAKING CHANGES: Read below
This is a breaking change and will probably require you to rework your existing automations and dashboards.
If you are happy with your current setup, there is no urgency to migrate but your integration might become inoperational in the future.
What can we expect? My main automations are arming the alarm home and away based on various other factors and automations based on contact sensors (if a window is opened the heating in that room is turned off - only for one floor, since Eufy isnāt great for this, moved to Aqara sensors for other floors). - In my case all done using Node Red, not the HA automations.
Are things renamed, does everything need to be setup again. Is there an overview of what to expect?
ps. still super happy you are putting so much work into this thing!
Main idea behind new version is making the integration manageable from technical maintainability perspective, more specifically about streaming.
But, as you might know, integration can break anytime and you might have to update it later on as i will only update it under new version. So, you either do it according to your availability while all is working. Or, you might have to do it when something is broken
1 Like
So it may also continue to work without any changes? Iām mainly asking if I should for example take time out to run past all automations to check for renames, etc. If I understand you correctly this is not the case and itās mainly a rework from a tech perspective that may cause issues.
And I know itās all based on your integration and without your hard work, no eufy integration anymore. This is one of the reasons why Iāve started moving away from Eufy for non-security things (like the contact sensors). I originally got them for the alarm system if a window or door would be opened when armed, but over time started āmisusingā them for other things like turning heating on and off, letting me know if I forgot to close a window when going to bed, etc. Announcing over the speakers that someone ran the doorbell on places to far away to hear the sound of Eufyās homebase. I am super SUPER glad this integration is here. But also realize what Iām building it on.
Ironically I never got the streaming part functional in HA.
Yes, it may, but probably not 
Take your time and migrate
And let me know if you want to work together for streaming inside HA
1 Like
Thanks!
Iāve upgraded and noticed the integration is loaded but nothing is available at the moment. I thought I may need to update the config so looked and just pressed save. It shows this error:
User input malformed: expected float for dictionary value @ data['ffmpeg_analyze_duration']
If there a way to manually update this? I donāt see any actual errors in the log files (or am just not looking right).
Edit: weird. It was a number (2) so I expected a float. But setting it to an 1.2 from the example it did accept it and the error went way. Perhaps because itās more an actual float?
You can remove and add the integration back.
I will fix this, someone reported this today
1 Like
You mean the HACS Integration and not the addons right and not the other addons it needs? If I remove and re-add it, anything I should save (for example the names al my devices). I actually never removed and readded an integration so not sure what HA will remember afterwards.
I noticed it comes up and I do see in the log for example it sets the moves, but shows as unavailable regardlessā¦
Edit: My brain still needed to wake up it seems. Luckily quickly enough to realize no donāt delete the entire HACS integration. Just remove it from integrations and add it again. Everything seems to be back to what it was and has become available again. Thank you 
Edit: My one update I needed to do in my automation was update the call to my video-doorbell ringing (have two automations triggerd by it, one to announce the ring over speakers and one to send a iOS notification). Needed to rename the entity for the ringing and those worked perfectly again also.
With the new update the Camera (EufyCam 2 Pro) I have up in the garden started working! The video-doorbell Iāve not managed to get to work (never worked before either). This maybe more due to the doorbell not supporting it perhaps?
Iām using this code in the dashboard
(basically yours but with camera.deurbel_voordeur as the name for the cam)
- theme: Backend-selected
title: test
path: test
badges: []
cards:
- type: conditional
conditions:
- entity: camera.deurbel_voordeur
state: idle
card:
show_state: true
show_name: true
type: picture-entity
entity: camera.deurbel_voordeur
camera_image: camera.deurbel_voordeur
tap_action:
action: call-service
service: camera.turn_on
data: {}
target:
entity_id: camera.deurbel_voordeur
- type: conditional
conditions:
- entity: camera.deurbel_voordeur
state: streaming
card:
type: vertical-stack
cards:
- show_name: true
show_icon: false
type: button
tap_action:
action: call-service
service: camera.turn_off
data: {}
target:
entity_id: camera.deurbel_voordeur
entity: camera.deurbel_voordeur
name: Stop
- type: custom:webrtc-camera
entity: camera.deurbel_voordeur
This results in the following:
This is a Eufy T8210 video doorbell, I have WDR Enabled under streaming. Streaming quality is Medium and Video Encoding Format is set to High
That one (T8210) is supported, I have been running it with this integration and predecessors for nearly 2 years. try to turn wdr of and switch the quality levels to low. See what happens. You will need to use P2P streaming with this one and combine with the rtsp addon [see repo readme]
2 Likes