Open gohm-tech opened 2 years ago
Hi @zbeacon,
We think we don't need to send connectRequests.
Best Regards, Gohm Team
Hi @gohm-tech ,
Actually the gateway sends connect request on the very first message with telemetry/attributes from device. Connect request in your case is not required, it was developed for case when you want to create the device and process it on ThingsBoard, but the data will be sent later. In order to solve the issue with RPC we have to change the logic in ThingsBoard. Because at the moment ThingsBoard sends RPC to the gateway, that created the device, not to the latest connected gateway.
In order to send RPC to another gateway - Please try to send disconnect request to old gateway and connect to the new one, then device session will be assigned to the new gateway.
Hi @zbeacon, Thanks for your interest. If the first gateway is not working and The device connects to the second gateway, We can not send a disconnect request from the first gateway. We tried to send a disconnect request using mosquito_pub, But it is not working.
So How can we do that from another device (computer or server) as if sending the first gateway disconnect message?
Can we do that using python rest apı?
Any work on this issue? When will you solve this issue? Best Regards, Gohm Team
Hi @zbeacon,
Is there any progress to solve this problem?
Best Regards, Gohm Team
We are working on RPC capabilities.
How The second gateway can receive this incoming RPC?
Client Environment OS: Linux(Ubuntu) Browser: Chrome, Firefox Version Ubuntu Version 20.04
Connector name MQTT Connector
Configuration mqtt.txt
Versions: OS: Raspbian GNU/Linux 10 (buster) Thingsboard IoT Gateway version [e.g. 2.7] Python version 3.7.3
Best Regards, Gohm Team