The node-red-contrib-tuya-smart-device modules/package is just about the last one supported, that was my comment intent. As for polling... after the very first interaction, the CPU load goes through the roof and stays there. This is on a Pi3B that is doing nothing else, just NR, just one flow. It does not matter if I have one IoT smart plug active or 15, once the control node connects to the device, we are off the to races. There is no way I can see, to change the polling rate. I can turn on/off the automatic connection feature, which I did, but once I connect to the device, the issue results, so the code design is in part at issue, because even when I explicitly disconnect from the IoT device, the loading does not back off, which is just odd.
I have not looked at the actual code yet, but I will when I get the chance because I need to see why this is happening of course. It may not be an issue with the specific package node source, but lower in the API stack, even back to the TUYA API its-self... which should not surprise me at this point.
I have not tried using JavaScript directly or even Python methods, but that is on plate as well to try to find the true issue. I have not used the TUYA REST API yet, but I may get to that as well.
