hello i am using node red in raspberry pi 400. by using mqtt protocol my devices are sending data to node red and from node red i am sending it to blynk . initially it works fine but after some time it automatically get disconnected. just after redeploying node red again reestablish connection with blynk
hardware description
1. arduino uno r4
2.Palette for blynk nodes : node-red-contrib-blynk-iot
thanks for any valuable help in advance.
If you open a PuTTY terminal session to your Pi and stop your Node-Red session (node-red-stop) then re-start it again (node-red-start) you’ll be able to monitor the events that happen (as long as you keep the terminal open).
See if you get any error or warning messages when Node-Red starts and the flows are loaded, and see what errors occur when the Blynk disconnection occurs. This should give you a clue about where the problem lies, and how to fix it.
Pete.
it happened again. i checked the log by entering ‘node-red-log’ command in terminal I got following result.
ossusbio@ossuspi:~ $ node-red-log
27 Nov 11:54:56 - [info] Starting flows
27 Nov 11:54:56 - [info] [blynk-iot-client:TB mini] LOG PINS
27 Nov 11:54:56 - [info] [blynk-iot-client:TB mini] Start TLS connection: blynk.cloud:443
27 Nov 11:54:56 - [info] Started flows
27 Nov 11:54:56 - [info] [mqtt-broker:ossus] Connected to broker:
nr@mqtt://192.168.1.101:1883
27 Nov 11:54:56 - [info] [blynk-iot-client:TB mini] Client logged
27 Nov 14:27:33 - [error] [blynk-iot-client:TB mini] Socket errorError: read ECONNRESET
27 Nov 14:27:33 - [info] [blynk-iot-client:TB mini] Client Error
27 Nov 14:27:33 - [info] [blynk-iot-client:TB mini] Reconnect in 5 seconds...
27 Nov 14:27:38 - [info] [blynk-iot-client:TB mini] Start TLS connection: blynk.cloud:443
27 Nov 14:27:38 - [info] [blynk-iot-client:TB mini] Client logged
27 Nov 18:26:33 - [error] [blynk-iot-client:TB mini] Socket errorError: read ECONNRESET
27 Nov 18:26:33 - [info] [blynk-iot-client:TB mini] Client Error
27 Nov 18:26:33 - [info] [blynk-iot-client:TB mini] Reconnect in 5 seconds...
27 Nov 18:26:38 - [info] [blynk-iot-client:TB mini] Start TLS connection: blynk.cloud:443
27 Nov 18:26:38 - [info] [blynk-iot-client:TB mini] Client logged
27 Nov 22:25:32 - [error] [blynk-iot-client:TB mini] Socket errorError: read ECONNRESET
27 Nov 22:25:32 - [info] [blynk-iot-client:TB mini] Client Error
27 Nov 22:25:32 - [info] [blynk-iot-client:TB mini] Reconnect in 5 seconds...
27 Nov 22:25:37 - [info] [blynk-iot-client:TB mini] Start TLS connection: blynk.cloud:443
27 Nov 22:25:37 - [info] [blynk-iot-client:TB mini] Client logged
28 Nov 00:16:17 - [error] [blynk-iot-client:TB mini] Socket errorError: read ETIMEDOUT
28 Nov 00:16:17 - [info] [blynk-iot-client:TB mini] Client Error
28 Nov 00:16:17 - [info] [blynk-iot-client:TB mini] Reconnect in 5 seconds...
28 Nov 00:16:22 - [info] [blynk-iot-client:TB mini] Start TLS connection: blynk.cloud:443
@sachinmc Please edit your post, using the pencil icon at the bottom, and add triple backticks at the beginning and end of your terminal output so that it displays correctly.
Triple backticks look like this:
```
Copy and paste these if you can’t find the correct symbol on your keyboard.
Are you using the same auth token in your Node-Red connection as another device (either an MCU or another Node-Red connection)?
Pete.
Pete.
done.
Pete.
NO
only nodered is connected to blynk.
all my devices are connected to nodered through MQTT
one more thing is this disconnecting is happening only around 12am everyday.
and it reconnects next day only after re deploying the nodes
You still haven’t explicitly stated that you don’t have more than one Node-Red Blynk connection.
Have you tried adding the region subdomain to your Blynk connection URL?
Pete.
yes I have only one nodered connection to blynk.
just now at IST 12:04am it again got disconnected
Seems like you don’t like answering questions. Any reason for this?
Pete.
I will try changing the url. but I have to wait 24 hours to get the results of it.
what questions?