Solved: Thingworx server initiated Websocket disconnection

ravi2 · ‎Jul 29, 2019

Hello,

I want to disconnect the Websocket connection of a connected remote thing from the Thingworx server. Is it possible? I tried using the DisableThing service, but that only disallowed the client to update the properties, not terminate the WS connection.

If it is not possible, what is the reason for it?

zyuan1 · ‎Jul 29, 2019

The SDK side or EMS side send the information to the TWX server, so in the connection, the Server side is Passive. If you disable or delete the remote thing, there is a idle connection but WS is still running, the progress in edge side is not stopped.

If you have a Power-Off service API in the edge side that can terminate the program to stop running, you can trigger it from TWX and WS will stop.

View solution in original post

zyuan1 · ‎Jul 29, 2019

The SDK side or EMS side send the information to the TWX server, so in the connection, the Server side is Passive. If you disable or delete the remote thing, there is a idle connection but WS is still running, the progress in edge side is not stopped.

If you have a Power-Off service API in the edge side that can terminate the program to stop running, you can trigger it from TWX and WS will stop.

ravi2 · ‎Jul 29, 2019

Thanks for the response!

Is the "Power-Off service API in the edge side" realised using the remote service functionality?

Can you also explain the reason for the server side being passive?

Regards,

Ravi