I may be wrong, but I think that nite_man is referring to something that I've also spotted before.
With Pluto I had a simple ruby code that I put into a GSD to drive a weeder I/O. It used to work fine sending 192 (ON) and 193 (off) to several channels. Suddenly it stopped working, and this happened upon a Pluto upgrade (from .43 to .44, if I remember well).
By looking at the DCE log it was clear that command 193 was totally ignored, and the reply from Pluto staff was more or less what 1audio is saying.
After that I stopped using GSD and Weeder (so pity, but it's true) because I had no time to find out a possible workaround.
I'm following your progress with Insteon drivers (although I'm living in Europe so I unfortunately won't benefit of your work) basically to see whether this strange situation with 193 - OFF command was solved or not.
To be honest I do not understand clearly what you mean.
I used to see that when I pushed the proper scenario button to switch a light on, a 192 command was sent to GSD (no 184 to level 100%), and when pushing button to switch off a simple 192 was issued to GSD.
Ruby code in GSD was in charge to figure out which child the command was coming from and build the proper string to be sent via RS232 to Weeder board.
Simple, stupid, but working.
Moreover Weeder I/O has only digital I/O, so there's no point to set level, it's just a matter of switch channels ON/OFF
All of a sudden the command 193 was discarded. I tried several ways to do it (I think also invoking it from a shell command) but no avail.
Again, I did not investigate that much as Pluto guys seemed not interested in giving me an answer.
Did you find the same behaviour?
Thanks and regards