I did notice that my AP mount stay connected in TheSkyX even after Voyager disconnect.
I investigate the TSX TCP API and found that the function Sky6RASCOMTele.disconnect() does not did the job, and the only way to proper disconnect the mount was to use a final Sky6RASCOMTele.Park().
So i push some golang code to crosscompile an exec i can call from my dragscript on the end of the session. But this force me to enable the TCP interface of TheSkyX under tools menu.
Voyager is not the owner of the connection and cannot know the reasons why you use TheSkyX and if the connection to the mount continues to serve you. If you need to close TSX you can use the dragscript block which closes the processes, there is also the one for tsx. So everything closes, or use code as you did.
The code you wrote interfer with Voyager status, if you want to park the mount just use park in Voyager … calling exactly the method you talk about.
Voyager work with TSX since 9 years … compatibility is difficult to understand in users.
Someone think if he have the last version all have last version. Someone not update if work.
The method used and for what you thank is present in the latest versions , for you info. When someone check this flag and doesnt have result in Voyager because he doesnt have the right version i will call you