search

tzapu / node-red-contrib-blynk-websockets

MIT License
35 stars 12 forks source link

Get hundreds of error messges filling the syslog. What should I do? #19

Open mrohner opened 6 years ago

mrohner commented 6 years ago

Error appeared when coding first blynk write note. I obviously did a mistake defining the websocket in the node as it cannot get connected. The error close messages repeat 16 times per second filling the syslog and making node-red loosing connection too.

31 Aug 11:39:24 - [info] Node-RED version: v0.17.2 31 Aug 11:39:24 - [info] Node.js version: v6.11.2 31 Aug 11:39:24 - [info] Linux 3.4.113-sun8i arm LE 31 Aug 11:39:26 - [info] Loading palette nodes 31 Aug 11:39:38 - [info] Dashboard up and running 31 Aug 11:39:43 - [info] Dashboard version 2.4.1 started at /ui 31 Aug 11:39:45 - [warn] ------------------------------------------------------ 31 Aug 11:39:45 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 31 Aug 11:39:45 - [warn] ------------------------------------------------------ 31 Aug 11:39:45 - [info] Settings file : /home/pi/.node-red/settings.js 31 Aug 11:39:45 - [info] User directory : /home/pi/.node-red 31 Aug 11:39:45 - [info] Flows file : /home/pi/.node-red/flows_mosquitto.json 31 Aug 11:39:46 - [info] Server now running at http://127.0.0.1:1880/ 31 Aug 11:39:46 - [info] Starting flows 31 Aug 11:39:49 - [info] Started flows error close 31 Aug 11:39:49 - [info] [mqtt-broker:8e79b041.968cc] Connected to broker: mqtt://192.168.178.59:8 883 error close error close error close error close error close error close error close error close error close error close error close error close error close error close

tzapu commented 6 years ago

there are some problems with the node and i do not have time to update it currently

if anyone can provide a pull request i d be more than happy to merge it

cheers

On 1 Sep 2017, at 10:36, mrohner notifications@github.com wrote:

Error appeared when coding first blynk write note. I obviously did a mistake defining the websocket in the node as it cannot get connected. The error close messages repeat 16 times per second filling the syslog and making node-red loosing connection too.

31 Aug 11:39:24 - [info] Node-RED version: v0.17.2 31 Aug 11:39:24 - [info] Node.js version: v6.11.2 31 Aug 11:39:24 - [info] Linux 3.4.113-sun8i arm LE 31 Aug 11:39:26 - [info] Loading palette nodes 31 Aug 11:39:38 - [info] Dashboard up and running 31 Aug 11:39:43 - [info] Dashboard version 2.4.1 started at /ui 31 Aug 11:39:45 - [warn] ------------------------------------------------------ 31 Aug 11:39:45 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 31 Aug 11:39:45 - [warn] ------------------------------------------------------ 31 Aug 11:39:45 - [info] Settings file : /home/pi/.node-red/settings.js 31 Aug 11:39:45 - [info] User directory : /home/pi/.node-red 31 Aug 11:39:45 - [info] Flows file : /home/pi/.node-red/flows_mosquitto.json 31 Aug 11:39:46 - [info] Server now running at http://127.0.0.1:1880/ http://127.0.0.1:1880/ 31 Aug 11:39:46 - [info] Starting flows 31 Aug 11:39:49 - [info] Started flows error close 31 Aug 11:39:49 - [info] [mqtt-broker:8e79b041.968cc] Connected to broker: mqtt://192.168.178.59:8 883 error close error close error close error close error close error close error close error close error close error close error close error close error close error close

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tzapu/node-red-contrib-blynk-websockets/issues/19, or mute the thread https://github.com/notifications/unsubscribe-auth/AC2FkKcD3Zgo35kgmUpBzWMG5ldYyoV7ks5sd7QEgaJpZM4PJzoh.

jmikerq commented 6 years ago

@mrohner I am trying to fix this issue, but I cannot seem to reproduce this error consistently. Can you show me your setup when you see this error?