I have a long automation that turns off my home theater (turning off four amps and four subwoofers, raising the screen, turning off power to the screen, turning off the projector and so on).
The JVC projector is a bit wonky on TCP/IP commands (I have seen that consistently in the well over 10 years I have had it, on two different networks, several different home automation software and even with the original app for the projector, so there’s really nothing to do about it), which means that I have to send the command several times to be sure that it actually works. I have three sends in the automation, and sometimes I still have to turn it off with the IR remote.
But that’s not the issue here, I have made peace with that projector being wonky. The problem is that when it happens and when the command times out, sometimes the automation just stops. It doesn’t obey “Continue on error” as it should. Here is the trace. It clearly says “Continue on error”, but it stops because of the “Read timeout for command”. Is that a core bug, or why is this happening?
