ENOTFOUND

[ahartman]

At every poll I see an error ENOTFOUND as in image below. The device works fine, why the error? I use latest versions of module and of Shelly 1 firmware.

[windkh]

Hm strange, what did you enter? An IP Adress or a hostname? What node is it?

[ahartman]

Dear Karl-Heinz,

I entered an IP address, since hostnames are not working for me. I tried hostnames f3d414 and f3d414.local and neither works.

I just looked again and the particular switch is now stable after it has shown that error for several hours.

Again, during the occurrence of the error, I could control the switch from Node-Red without any issuers.

Kind regards, ahartman, belgium

Op 14 sep. 2021, om 13:17 heeft Karl-Heinz Wind @.***> het volgende geschreven:

Hm strange, what did you enter? An IP Adress or a hostname? What node is it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/windkh/node-red-contrib-shelly/issues/30#issuecomment-919055597, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIBPCKWL273CB3WGBVCILUB4VOFANCNFSM5D7S5PMQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[windkh]

Sorry for delay, I was on vacation.

On what device do you run node-red? Can you call nslookup with the address from the command line? Please do this on the device you are running node-red.

[mmierke]

Hi, same issue here:

Node red running standalone in a docker container on my synology NAS. Roller Shutter is identified by ip address

Br Martin

[windkh]

@mmierke can I send you a flow for testing?

[mmierke]

The node claims ENOTFOUND http. The object states, that HTTP is the source of the object.

My Shellies are not exposed to the cloud

[mmierke]

I have disabled the flow now, but the issue still appears in the disabled flow.

[mmierke]

I have restarted the container and the node looks stable now.

[windkh]

@mmierke can you try to use this flow and see if a plain httprequest works for your device? Please change the IP address if the http request node so that it contains the IP of your shelly device

[{"id":"4c4a5e34726a98e3","type":"http request","z":"74b2240c4c1d35f8","name":"","method":"GET","ret":"txt","paytoqs":"ignore","url":"http://192.168.178.189/status","tls":"","persist":false,"proxy":"","authType":"","x":280,"y":220,"wires":[["2f7bc52f09f7d521"]]},{"id":"acb1ab1159468ede","type":"inject","z":"74b2240c4c1d35f8","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":130,"y":220,"wires":[["4c4a5e34726a98e3"]]},{"id":"2f7bc52f09f7d521","type":"debug","z":"74b2240c4c1d35f8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":480,"y":220,"wires":[]}]

[ahartman]

I have now found that I need to address a Shelly 1 node as: shelly1-F3991B.local and a Shelly2.5 as shellyswitch25-76CA13.local, where F39991B and 76CA13 are the Shelly device IDs. The naming is not very consistent and should be documented more clearly.

My Shelly switches have now been stable for several weeks.

Regards, ahartman, belgium

[windkh]

ok then I will close the issue.