cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Thingworx server initiated Websocket disconnection

SOLVED
ravi2
12-Amethyst

Thingworx server initiated Websocket disconnection

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?

1 ACCEPTED SOLUTION

Accepted Solutions
zyuan1
18-Opal
(To:ravi2)

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

2 REPLIES 2
zyuan1
18-Opal
(To:ravi2)

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

ravi2
12-Amethyst
(To:zyuan1)

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

Announcements