Would you mind sharing your card setup? I can find the picture/snapshot on the server and can approach it through a public URL (was not aware HA publishes the www directory as public …) but unable to show it in the camera card - set it up as image but nothing happens.
The trick is to use a different entity than the camera one as that will always take presedence over the image in a picture-entity card. Can be any random entity.
2 Likes
That sounds good, but can you explain that in a bit more detail? Thank you.
If anyone is interested to test new, certainly half baked, probably broken, please update your integration using HACS to beta releases.
I installed the latest update, some options of the doorbell are working but still no stream or picture available. The error:
2022-12-27 16:21:57.038 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.deurbel] Error from stream worker: Error opening stream (ERRORTYPE_110, Operation timed out) rtsp://192.168.178.119:8554/T8200N0021060DCB
2022-12-27 16:23:48.604 INFO (MainThread) [backoff] Backing off fetch_events(…) for 0.7s (pyoverkiz.exceptions.TooManyConcurrentRequestsException: too many concurrent requests)
so, you configured RTSP add-on, enabled it and called respective service call to initiate the stream, right?
Indeed, I tried another time but no other error occurs in the log
Tried it and not much to report other then i couldn’t get it to connect at all.
In the end I created a generic camera entity. Solution of @Sp33dFr34k worked but did not refresh and continued to show the same cached image.
You can easily create a generic camera through the integration section of HA. In the config flow you can add the URL of the picture.
You’re right, there’s always that dreadful caching on the www folder sadly. I’ve tried your solution, but it’s giving me the exact same caching issues though… did you do anything specific configuring the generic camera?
Same issue here! Found any solution? Thanks
Just thought I should mention that with todays update, ring indicator is working fine, THANK YOU!
but you will probably have many new nightmares (hopefully not) 
this is an ALPHA release, so many things will be broken (probably)
Good morning. Had some issues with batteries reporting the wrong number so thought I’d just uninstall and reinstall everything. Now after adding 1.3 and setting it up I am getting the following error
2022-12-28 07:36:13.315 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-12-28 07:36:13.550 ERROR Response data is missing
{
code: 0,
msg: 'Succeed.',
data: undefined
}
Have I missed something? Worked fine previously
Nothing special, just the URL. The picture changes, did not monitor though how rapidly it updates on screen after a trigger - will check today.
I used your trigger and added person motion event. That way I can use it for notifications to the phone without delays after bell press.
Hi,
I just came around this integration, but it seems - if I read through several posts by cross-reading - that all topics for EUFY equipment are handling a live stream issue.
I have a more severe and basic issue, because it seems that sometimes (rarely) the doorbell 2K seems to loose connection to the EUFY base.
Is there any way to have a parameter/binary sensor available to trigger´doorbell lost contact` message?
As far as I understand, the doorbell is using a closed WIFI connection to the EUFY base. Is that right?
So any presence detection via ping etc is not possible.
And , since I am here …, does it make sense to try getting a live stream running with HASSOS running on a Raspberry Pi 3B+ ?
Or is it far too low performing?
Regards
Joerg
Feel free to share your device with me following readme (you can find respective EU and US accounts) and i can take a look today.
I can setup a connection sensor and check p2p streaming. It is not resource depending as you might think.
If you would share your device, please drop me an email or PM over here about your email address.
I found that adding Eufy to TRUSTED_DEVICE_NAME as pointed out here solved this issue for me. However I am still getting strange battery readings from the devices in my second property.
My main residence is fine and has the S380 HomeBase, in HA is listed as a T8030 (2K Doorbell and 2 x S300 cameras) 192.x.x.x IP address in the app.
My other property, where the battery issues are has a HomeBase 2 and is listed in HA as an T8010 (2 x eufyCam T8113-Z. IP address is listed as the WAN address in the app as I’m not in that house.
I’m starting to think this must be a limitation of having separate Homebases in separate properties. Maybe it will update when I go into the property and connect on the LAN.
I like this approach. However, just found out that the sensors never turn True so the automation never triggers. When i trigger manually I need to CTRL + F5 to have the picture entity updated. Dont know if last is possible to be forced periodically? Think the sensor will solved in next release.
I updated the addon to 2.10 and it quit working. I uninstalled everything and reinstalled to see if that fixed it.
Now, when I try to add the integration, it tells me “Host/Port is wrong.” and the addon stops.
The addon log says “INFO Authentication properties changed, invalidate saved cloud token. Killed”
The HA log says
> * eufy_security Exception in login : [Errno 104] Connection reset by peer - traceback: Traceback (most recent call last): File "/config/custom_components/eufy_security/config_flow.py", line 199, in _test_credentials await eufy_ws.connect() File "/config/custom_components/eufy_security/websocket.py", line 41, in connect self.ws: aiohttp.ClientWebSocketResponse = await self.session.ws_connect( File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 776, in _ws_connect resp = await self.request( File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 559, in _request await resp.start(conn) File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 898, in start message, payload = await protocol.read() # type: ignore[union-attr] File "/usr/local/lib/python3.10/site-packages/aiohttp/streams.py", line 616, in read await self._waiter aiohttp.client_exceptions.ClientOSError: [Errno 104] Connection reset by peer