Nodi-Rubrum

Here is the node-red log... `14 Sep 04:14:41 - [warn] [tuya-local:42633b64.18bd54] Error: Error from socket device: Awow 163 14 Sep 04:14:41 - [info] [tuya-local:42633b64.18bd54] error: Trying to clear a possible...

FIrmware... MCU Module 1.0.4 and update-to-date, on all 4 of the same group/publisher/bundle I purchased. The vendor ID code is also identical in the Tuya API/IoT clould API/website.

Right, I am sure I am not cross connecting the nodes. Phone offline while active in node red. I did try the tuya-cli wizard, and it matches the web site...

I am not completely sure the node is the cause, it might be the tuya API its-self, but since the phone instance for the device is functional, as well as...

I look again, that idea makes sense. I just don't think I have anything else connecting. If I did the issue should be happening to all 4 devices, since my...

Maybe use a 'gradient' scale or range? Or complimentary colors? Just ideas. I would love light blue for reads and dark blue for writes for example, just my idea.

Sounds good!

Just a foot note, you can always use 'sudo' with an exec node to avoid running Node Red under root. Are you using the official installation script for Node Red...

Is there any expectation of this being fixed? Anytime soon? True there is a work-around, but it should be fixed no?