-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HELP] Gateway disconnect and connect every some msec #1286
Comments
Hi @Tasosgi. IOTGW-80 |
Hi @Tasosgi, Usually disconnect with this reason code appears if you have already connected gateway with the same credentials, could you try to generate a new accessToken and use it? |
Hello, yes I have seen that in other cases. But in that case there isn't another gateway or device online. Anyway I will check it today. Another strange think I see in this version is that if I don't put the "type": "serial" before "master" my configuration file don't works and the gateway use the default one. According to the examples it must be under "slaves". I have attach my configuration files |
Ok, another option is rate limits, could you check your notifications on the platform - don't you have a message like "Rate limits exceeded? |
@Tasosgi I mean notification (bell icon in the top panel), there is rate limits per device on ThingsBoard level. And if you restart the gateway 3 or 4 times per minute - it may be triggered. |
I faced with this problem after enabling |
Thanks to the help of @imbeacon I found the problem. I had gave the same name to the gateway, when I created it in the platform, and the slave, in the modbus configuration file |
I can send telemetry data to platform but the gateway disconnect and connect every some msec. It seems that it tries to subscribe to attributes without success.
modbus_serial.txt
tb_gateway.json.txt
The text was updated successfully, but these errors were encountered: