Managed to get Jason's TCP centric ones to work just before bed. Brief testing was more consistent and more commands worked consecutively. Is there a pressing argument of python vs tcp based approach.?
My experience pretty much echos those of jasonfox/garryjw.
I see the commands and the threads mention the tcp connection. Can you simply have the client connection load on onload and then perhaps terminate on closure, or is leaving the connection open a big issue? (i know it seems to flood the activity log pane, which is a bit annoying but also not always?)
Or have each command create the connection, execute action, terminate connection? I found the listen, and idle , disconnect command/events a bit odd is the late hours maybe missing the rationale.
I liked the more pithy config w/ most of the commands in the PY variant being in the payload xml shrinking the LCB command tree
But it was very inconsistent and never got most commands working.
The TCP ones all worked the several I managed to try before getting to be too late and having to sleep. Command response was very good and consecutive commands no problem.
But this is pretty awesome stuff, thanks for sharing and helping all.
