client disconnect returns 'Invalid client handle (not found)'

Mick W8BE

I am trying to disconnect a non gui client and it fails with a not found error message.

As you can see the non gui client handle in the discovery message. I am sending :

client disconnect 0x6EA67CEC

Which according to the wiki should disconnect a gui or non gui client

C[D]<seq_number>|client disconnect <handle>

<handle> = an optional client handle (32-bit hex value sent to client on connection)

However I am getting and error that indicates an invalid client..

request: "client disconnect 0x6EA67CEC"sequence_number: 15 status_code: "0x50000062"

From what I can tell I am sending the cmd correctly.

Thanks in advance

KD0RC

Hi Mick, I did some experiments with disconnects some time ago and could only get the non-specific (disconnects everything) one to work.

As it turns out, I didn't really need it for any of my applications.

So I wonder if you really need it or not. You might want to comment on what you are using it for.

Mick W8BE

Ken,

You saw my dashboard where I show the gui. I have it tracking the active slice in SmartSDR. When I disconnect SmartSDR the client gui is deleted but not this one. It shows up as an active client and the only way to clear it is to power the radio off. If I start SmartSDR again, then I get the message that all clients are in use.

KD0RC

Oh, I see… Try a plain client disconnect without the client ID.

Mick W8BE

I tried that Ken it does not work either. The only way I clear out the client is to disconnect the entire flow. I can do that but I was hoping for a more elegant solution.

Regards

KD0RC

Hi Mick, I just looked through my TeensyMaestro code and see that the disconnect code that Enzo, IW7DMH created in his Flex Arduino library does indeed do an Ethernet stop. So I suppose that he had the same issue getting the disconnect API command to work.

I had the same issue as you at one point, so in my power-down callback routine, I do a disconnect (actually an Ethernet stop) when powering off the TeensyMaestro. In my case, since I only connect as a GUI client under very specific conditions, this isn't as important but can be quite annoying. My normal operation is as a non-GUI client.

Mick W8BE

Thanks Ken. Maybe some one on the dev team could take a stab at describing why it works after all the effort to ship out the radios calm down.

Regards