It wasn't the HOW to do it that is annoying to me, it was that that this rather important detail is not documented. It's sort of an important point. A lot of folks have asked very similar questions on the forum, and not one answer contained this information. I will dig up the github and put in a suggestion for documenting it better now that I have it figured out.
When you have dozens of controls that all have to have another node added to set these two values, YES I consider that tedious. I am not working on a single function "sensor" type device.
On a more serious note, is there a rationale for doing the way it is now? Logically thinking in my mind, on the devices I work with, once I connect to them, I stay connected forever, thus, if I set the node to stay connected forever, I would expect that the connect request set that state into motion. Maybe I just don't understand the use case for doing it this way.
Lastly, I also have to get WireShark cranked up to make sure that it is not tearing down and rebuilding the socket for every request that is made using this methodology. I doubt it, but I want to be sure. The application in question is largely an unattended one, meaning that the device is not readily available for hands-on tweaking and such.