"TypeError: ID and IP are missing from device."

[Barabba11]

Hi, you promised that with local dsocket it's just necessary to indicate the IP address, I've used your example flow and I got this error, NR is 4.05 I've added ID and same result, I've tried with example socket writing ID+secret and it goes to "found" (yellow) and for very short time sometime to green, but when I request:

object
payload: "request"
topic: undefined
_msgid: "3bc0dbc0f0511460"
called: true
error: "request not made as not connected Dimmer"
data: object
_event: "node:c867e2d1383cae51"
device_id: undefined

Srange it workd with direct IP, the app is driving dimmer sending UDP on my multicast LAN address, it never connect to IP of dimmer. What to do here? the app is working, the tuya profile is configured and I got the secret

[marsjupiter1]

I have pretty much given up on tuya as the local socket stuff always seems pretty flaky, so all I can really say is that the example flows do generally work. why not try using the decide id as well as the ip address?

[Barabba11]

I perfectly understand you, this system is riddle, a pain after some hours of testing. watching how it works the app the IP address isn't a way with my tuya device, only broadcast works, for sure I've already tried what you asking but no results. Maybe my device is already Tuya 3.4 and maybe this means it's already different approach

https://github.com/simeonovp/node-red-contrib-tuya-devices this module seams have a different approach, using login info to the tuya site

[marsjupiter1]

there is an inherent absurdity to both a socket approach and a API that requires external access to control a local device. Tasmota offers a simple local rest API that both makes sense and has the additional benefit of simply working. I developed these flows with the idea of disability aids, things that kind of need to be solid!

[Barabba11]

I'm thinking the same, what a dumb decision to work like that, and more.. they are changng often protocols, probably my device isn't working with your module because of that. We can just hope they let the local control much easier, probably this thing is already implemented, since the app is able to drive by WiFi with the gateway turned off, but I' not sure if the device can be registered on WiFi without gateway, no secrets then generated by Tuya, can be interesting have a try. I've sniffed the local turn on command, it's the broadcasted udp packet sent on port 7000, it's encripted 00 00 66 99 00 00 00 00 00 00 00 00 00 25 00 00 00 41 8a c2 9e de 88 55 29 fc ba b9 e1 e8 b9 49 22 b7 dd 60 ff 15 69 95 cf 22 05 9b 17 f8 02 0f 64 20 fb 98 66 8d a0 cb b7 46 c4 ec c0 ed 91 c4 bc fe a2 48 7c 73 71 d8 b9 6e 9a 76 23 2b 8c 54 05 9b 4f 00 00 99 66