Possibly ; Initialization errors on machine-created flow with new home automation card in Node-RED

[anttiryt]

Possibly.

On starting to use new Home automation card, I created a tester for one input and one relay on node-red, and then asked Gemini to expand it to all 8 relays and 8 Opto ins.

While import was successful, seemed all nodes had to be modified or adjusted a bit until they started working. Adjusting was e.g. moving the input number from 4 to 0, deploy, and back. Then all started working.

sequent-tester.flows.txt

[alexburcea2877]

Hi,
I don't have a machine with Node-RED right now, but I will look at your flow later. What is the problem?
It looks like you made it work in the end.

[anttiryt]

I think this is a long term discussion item. Cards work fine, as usual.

Yesterday, instead of creating node-red nodes one by one, I pasted a ready view created by Gemini. I don't know if this was the reason, but none of the relays started working immediately. They nodes needed to be switched to different relay number and then back and then they started working.

Is there any kind of initialization done by adding a new relay to view? I wonder if this was skipped when importing a flow.

[alexburcea2877]

There is no initialization needed as far as I know.

[anttiryt]

Can you think of anything from the electronics side, i2c or between i2c and relays, why it would initially not respond to relay commands but changing the wanted relay from node-red node, e.g. 5 -> 1 -> 5 gets it working and reliable?

[alexburcea2877]

I can not suspect anything but a bug in the node itself. There is no way I2C or any low-level part of the code is related to this.
I recommend using the exec node running ioplus; some people believe it runs faster than JS accessing the I2C port, but it is definitely more controllable for us. If you find a bug, we have more resources to fix it than for the node JS code.