I’m not sure if this will work, since not all variables can work with service: eufy_security.send_message. If it doesn’t work with a variable, then don’t use variables and specify a specific number.
For example, I slightly rewrote the code taken from here
that works, but i want to integrate it in the webrtc built in Ptz control.
thats my problem.i must use a script for it.
i get the value from my button to the script, BUT the value for example : 1 is than a Number, and the integration accepts no number, it must be a string.
my code, the script that accepts the values, here only the 2
service: eufy_security.send_message
data:
message: |-
{
"messageId": "cmd Pan And Tilt Down",
"command": "device.pan_and_tilt",
"serialNumber": "XXX",
"direction":
{% if direction == "left" %} 2
{% endif %}
}
and my webrtc card
- type: custom:webrtc-camera
entity: camera.kinderzimmer
ui: true
webrtc: true
ptz:
service: script.ptz_kinderzimmer
data_left:
direction: left
data_right:
direction: right
data_up:
direction: up
data_down:
direction: down
when i now click he says the data must be a string.
when i add the if condition in the script the STRING turns into a NUMBER. and that not works
Why do you need webrtc integration? Pay attention to AgentDVR, it has a built-in webrtc and a video stream without delays. There is a video output card for AgentDVR. Create a video card + PTZ buttons
the problem is not the webrtc the problem is the eufy integration, why acctepts the direction no number values??
its a Number, 0-4 , NO String.
i spent hours for a problem, that’s just incredible, “direction” has to accept a number as a value. This is simply a mistake in integration
Can i ask something here?
I have an eufycam 2 (model T8114)
Sometimes theres a heron in my garden, and i want to see it on my cam, but it doesnt record it.
Is that normal? Camera is set to “all motions”.
Secondly, theres a dog outside my house, that does his day job… i also want to record that, so i know which dog/human it is.
Will another eufycam 2 record it? The dog?
Should i jump on this?
@anon63427907, you still have plans for official integration?
Can you please assist me I have followed all guides and still having the same issue.
I can get a live feed working for my camera (Eufy Floodlight Pro 2, model T8423) this works for 3 minutes and then cuts off. I can see this is normal but unsure how to keep a constant live feed showing? This is with using WebRTC.
When using Eufy Security addon i can get all types on things working such as turning the flood lights on. But still not the live feed.
Is this going to be the case with these cameras or is there a work around? I can’t see the point of using these cameras If I can’t get a live feed.
So I have got this installed and it’s working pretty good. I guess my only question would be the little preview thumbnails like emotion and stuff outside they’re really old is there anyway to get them to update to be current?
Return Status Code Not 200 - Receiving Status Code 423
New Setup, system connects to devices, then received Status return code not 200. and continues this way, until a restart of the add-on in HAOS. (Receiving Status Code 423). So something is causing it to lock the account?
Please see attachment. At a loss as to what is the cause here. I have 16 Eufy Cameras, created a separate account for HA, etc. API request limit on Eufy API servers??
after some tweaking…and last event not showing as they have been, noticed that the Floodlight last evet is no longer available and not entirely sure why…nothing has changed and all other camera last event show just fine
Did you use someone’s write-up, or just piece it together? I’ve been struggling with this for a few days, and although I know the device’s IP, I can’t make any progress on the connection. If you have a source you used to figure it out, could you link it? I’m fairly new to both the device and HA, so although I have eufy_security installed I’m still handicapped in even finding the device through HA and configuring it. Any tutorial that does some hand-holding would be appreciated.
Add-on version: 1.24.0
You are running the latest version of this add-on.
System: Home Assistant OS 8.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.8.5
Home Assistant Supervisor: 2022.08.3
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:03:11] INFO: Exporting log level for nodejs: info
[08:03:12] INFO: Symlinking data dir
[08:03:12] INFO: Running ‘eval’ commands
[08:03:12] INFO: Generating config.yml from options.json
[08:03:12] INFO: Image build with version 0.2.24
[08:03:12] INFO: starting original stuff…
[email protected] start /app
NODE_ENV=production node --unhandled-rejections=strict index.js
(node:352) UnhandledPromiseRejectionWarning: TypeError: devices is not iterable
at EufyHttp.refreshStoredDevices (/app/eufy/http.js:45:24)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async EufyClient.init (/app/eufy/client.js:17:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:352) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v21.6.2 Documentation). (rejection id: 1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: NODE_ENV=production node --unhandled-rejections=strict index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-08-16T06_03_17_994Z-debug.log
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
