What I personally did was add a date/time helper or two for times that I can set on my dashboard when it should arm/disarm and create a fairly simply automation to switch between armed home and armed away based on those time.
Extended with things such as when the entire house goes in ‘nightmode’ or ‘vacationmode’ or when all members are away it also turns it into armed away and the schedule is ignored. (and a few NFC tags that can trigger HA toggles for the alarm also)
HA will offer a lot more freedom to create and switch between modes then the Eufy app offers
Hi.
I have a problem with this integration. I made everything said on tutorial but i don’t have stream. It works but after a some time i have an error as in the image.
If i restart the addon, camera goes up again.
At the logs everything fine, i think:
Enable debug logs for integration and share them over GitHub issue. if i am not mistaken, some users are having similar problems with webrtc, did you give it a try with native HA streaming or rtsptowebrtc/go2rtc add-on?
These sensors are used for debugging purposes only and they meant to show number of waiting frames to be forwarded to rtsp. in my cases, this value never reaches to 10-15, something is off here.
Hello,
Has anyone setup successfully the PTZ function for Eufy Indoor Cam Pan&Tilt camera?
I saw that there are some services available like eufy_security.ptz_up but I can’t figure out how to use them.
RTSP stream is also enabled and camera is streaming when I’m trying to move it via the ptz service
-EDIT 2-
I saw the logs and I’m getting these error messages:
2022-09-15 08:32:35.556 INFO Timeout connecting to station T8410...AD5
2022-09-15 08:36:59.137 ERROR P2PClientProtocol.lookup(): station: T8410...AD5 - All address lookup tentatives failed.
2022-09-15 08:36:59.141 INFO Timeout connecting to station T8410...AD5
2022-09-15 08:37:50.568 ERROR P2PClientProtocol.lookup(): station: T8410...AD5 - All address lookup tentatives failed.
2022-09-15 08:37:50.571 INFO Timeout connecting to station T8410...AD5
2022-09-15 08:38:45.182 ERROR P2PClientProtocol.lookup(): station: T8410...AD5 - All address lookup tentatives failed.
2022-09-15 08:38:45.184 INFO Timeout connecting to station T8410...AD5
Also, no other funtions like turn off LED etc is working via Home Assistant UI. I don’t know why.
I purchase the indoor camera recently , and I had already installed the integration when I pair it with the homebase2… .
Yesterday I was super excited as I finally got the Eufy Doorbell working in home assistant. Now I notice that after some time the camera stops working. I see the following error message in the logs of the eufy-security-ws container:
2022-09-20 07:04:35.443 ERROR Message error
LivestreamNotRunningError Livestream for device T8200N0020081594 could not be stopped, because it is not running
error stack:
• message_handler.ts:146 handle
src/lib/device/message_handler.ts:146:31
• task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
• server.ts:103 receiveMessage
src/lib/server.ts:103:21
After I reload the integration in Home assistant the camera will be working again. Anyone familiar with this error?
eufy_security - Exception - process_messages: 55 is not a valid DEVICE_TYPE - traceback: Traceback (most recent call last): File “/config/custom_components/eufy_security/websocket.py”, line 57, in process_messages await self.on_message(msg) File “/config/custom_components/eufy_security/websocket.py”, line 68, in on_message await self.message_callback(message) File “/config/custom_components/eufy_security/coordinator.py”, line 313, in on_message await self.process_get_device_properties_response( File “/config/custom_components/eufy_security/coordinator.py”, line 260, in process_get_device_properties_response device.set_properties(properties) File “/config/custom_components/eufy_security/const.py”, line 446, in set_properties type = DEVICE_TYPE(self.type_raw) File “/usr/local/lib/python3.10/enum.py”, line 385, in call return cls.new(cls, value) File “/usr/local/lib/python3.10/enum.py”, line 710, in new raise ve_exc ValueError: 55 is not a valid DEVICE_TYPE - message: WSMessage(type=<WSMsgType.TEXT: 1>, data=’{“type”:“result”,“success”:true,“messageId”:“get_device_properties”,“result”:{“serialNumber”:“T8530------------------”,“properties”:{“name”:“Front Door”,“model”:“T8530”,“serialNumber”:“T8530---------------”,“type”:55,“hardwareVersion”:“P1”,“softwareVersion”:“1.1.5.4”,“stationSerialNumber”:“T8021----------------”}}}’, extra=’’)
(I dashed out the serial numbers!) Hope this error log helps!