Open batesenergy opened 2 years ago
We have a similar issue with the same error code on the same node. With us the error happens even when there is no data injection and it happens more often than every few weeks.
Did you solve this?
Make sure you only have one telemetry node on all of your flows, multiple nodes create multiple separate connections, we expected behavior similar to an mqtt node, but not the case here.
Other than that, still waiting on a fix to check for existing cloud connection on network interruption.
On Tue, Jun 7, 2022, 5:36 AM BjornhTecnec @.***> wrote:
We have the same issue, except it happens more often than every few weeks.
Did you solve this?
— Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/node-red-contrib-google-cloud/issues/112#issuecomment-1148433654, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMCAJGLFTG4ORLV5ONE32Z3VN4JYHANCNFSM5RUZ3IQQ . You are receiving this because you authored the thread.Message ID: <GoogleCloudPlatform/node-red-contrib-google-cloud/issues/112/1148433654@ github.com>
We are using the the telemetry send successfully 90% of the time. Every once in a while (weeks) the telemetry node will start disconnecting on a data injection, although the data is successfully transmitted.
On google cloud we are seeing this in the logs on every send:
code: 6 description: "ALREADY_EXISTS" message: "SERVER: The connection was closed because there is another active connection with the same device ID."
It seems as if the node is trying to reconnect although it has a successful persistent connection? Anyone else with this issue?