Yes it is, for the purpose of this thread (not sure how to show it in a circuit, if I could) The unit is modular and isn't connected to the actual controller when testing or experiencing this issue. So the collector and emitter aren't connected during testing, but operate in the same fashion when connected/not connected to the shutter controller.

But this is the unit that it connects too, at the red points.
If it's a process of the IoT Cloud to trigger/cycle through defined variables, then a hardware solution of changing to mosfet or low power relays would still be an issue.
I defined and set the defined pins to LOW. I've also swapped the hardware for the STOP/DOWN on one unit of 0/4 pins and still no help. I had thought it was a hardware issue.
But ultimately, if the initalization of the IoT and Arduino code that it runs through a random order of defined variables. It's always going to trigger it erroniously.
