You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I developing ESP32 do like TB IoT Gateway.
I follow with Mqtt Gateway Api.
I found disconnect api is not working.
I pub to topic "v1/gateway/disconnect" with payload {"device":"Device A"}
Device A is still active in TB server
How to solve it ?
The text was updated successfully, but these errors were encountered:
Could you check lastDisconnectTime on device? - it should change on receiving disconnect. Active attribute is not about that the device is connected, because it represents "activity" of the device, you can add "inactivityTimeout" to device server attributes and value in milliseconds, device will become inactive after this period of time after last activity event, like telemetry publish, attributes publish and even disconnect event. It is a logic, written in ThingsBoard and expected behaviour.
Describe the bug
I developing ESP32 do like TB IoT Gateway.
I follow with Mqtt Gateway Api.
I found disconnect api is not working.
I pub to topic "v1/gateway/disconnect" with payload {"device":"Device A"}
Device A is still active in TB server
How to solve it ?
The text was updated successfully, but these errors were encountered: