search

recallfx / node-red-contrib-eufy-security

Eufy security node for Node RED
MIT License
6 stars 6 forks source link

All the fields returned as "undefined" #23

Open moryoav opened 10 months ago

moryoav commented 10 months ago

In all the events received, the fields are "undefined", see example in the image.

Capture

shane5557 commented 9 months ago

nfo] Starting flows 13 Oct 10:47:01 - [error] [function:function 1] SyntaxError: Unexpected token '}' (body:line 13) 13 Oct 10:47:01 - [error] [state-machine:4d6228e58exxxxxx] TypeError: Cannot read properties of undefined (reading 'toUpperCase') 13 Oct 10:47:01 - [info] Started flows

Ian-Nendels commented 4 months ago

is there any update about this, i have the same isue. I have 3 devices, so array of 3 is correct (i assume) but all fields are always "undefined"

image

Fleuper90 commented 2 months ago

Hello, i have the same issue. Is there any solution since the last comment?

stratacorps commented 3 weeks ago

Same here. For testing using ioBroker eusec adapter all devices supported are showing up with the correct attributes. Made sure node-red is running Node 18. ioBroker was updated a few months later so maybe its used a newer version of eufy-security-client?

EDIT: Note, ioBroker is using eufy-security-client v2.9.1. So as a test I copied the node_modules/eufy-security-client over into node-red and restarted it. I still get undefined. So this probably doesn't have much to do with the eufy-security-client as it does with how the data is handled on the return back into the node-red interface. I don't know how to troubleshoot this further.

stratacorps commented 2 weeks ago

I found a quick fix but didn't have a pull request as I'm forking this project to a new one so I can update the eufy-security-client and start adding additional commands. But here it is [https://github.com/recallfx/node-red-contrib-eufy-security/issues/30#issue-2373596999]