by the way, do not forget that all commands are sent to homebase station and sometimes it just timeouts and does not process your requests and this is happening in hardware level. moreover, it can process your command but does not return a response to us, which is worse, because live stream might be running on base station but not visible to us.
maybe, you can place an automation to restart add on and reload integration, when there is no activity happening (no live stream etc), example;
If so, shouldnt we experience the same then with the app of eufy?
Cause the app of eufy is responsive here, when i click it starts , when i stop, it stops
Never had unresponsiveness there…
We are building stuff to help cause otherwise its not working…
We shouldnt be doing that
No throw at you guys…
Will see if i can see if the homebase HAS timouts?
Other problems too.
Before the last updates (from past days) i had a working script, that takes a snapshot and send the picture to my google homes.
However the script isnt working anymore, so something has changed, this is the error i’m seeing now:
Deurbel gedrukt: Choose at step 1: choice 1: Error executing script. Unexpected error for call_service at pos 3: async_camera_image() missing 2 required positional arguments: ‘width’ and ‘height’
Deurbel gedrukt: Error executing script. Unexpected error for choose at pos 1: async_camera_image() missing 2 required positional arguments: ‘width’ and ‘height’
While executing automation automation.deurbel_gedrukt
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 371, in _async_step
await getattr(self, handler)()
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 571, in _async_call_service_step
await service_task
File “/usr/src/homeassistant/homeassistant/core.py”, line 1491, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1526, in _execute_service
await handler.job.target(service_call)
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 658, in entity_service_call
future.result() # pop exception if have
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 830, in async_request_call
await coro
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 695, in _handle_entity_call
await result
File “/usr/src/homeassistant/homeassistant/components/camera/init.py”, line 752, in async_handle_snapshot_service
image = await camera.async_camera_image()
TypeError: async_camera_image() missing 2 required positional arguments: ‘width’ and ‘height’
The second thing, i’m seeing this in logs, so by this i report it too
Updating state for camera.tuin (<class custom_components.eufy_security.camera.EufySecurityCamera’>) took 0.682 seconds. Please report it to the custom component author.
question is it possible to see somewhere in the eufy security addon on which version its based form bropats eufy security client. Latest from bropat is 1.1.2, whats the eufy addon based on?
Hey, it is self explanatory, you need to update your script to include additional parameters, this is a new requirement from HA, i have adopted it. Actually, this was also asked to be fixed over here: Eufy Security Integration - #185 by tharr24
On the second one, that is a known risk i took. İn the previous versions, i had separated state and live stream initialization, but always had issues with timing. Now state change is responsible for stream initialization, not an issue but a warning for us.
Regarding to eufy-security-client, you need to check eufy-security-ws version, we are on 0.3.3, to find out exact version we are all consuming.
Any idea where i need to add width and height?
In the automation i take a camera snapshot (cant find info there that i need to add this) and then i play the media…
Any idea how tharr24 fixed that?
Ok the second is only warning
About the eufy security client, we’re on 0.3.3 you say… but i theres no bropat version with that? 0.3.0 it goes to 0.4.0
I see LOADS of fixes for cameras, you have plans to go to latest 1.1.2 version?
Why don’t you use image_url from camera and rather capture a new screenshot? image_url is coming from notification and it should be already existing while ringing notification arrived.
If i’m right, latest ws version is 0.4.2
Not sure where i can see what client version it uses, but if it’s latest, then there are a whole bunch of bug fixes since 0.3.3
But i see Fuatakgun is working on 0.4.2 which is good
To make it really stable, there has to be an open api, otherwise it’s a cat and mouse game. Eufy extends or changes the protocol and I have to reverse engineer everything again, with the possibility of misinterpretation and so on.