[SOLVED] Blynk node red websocket error after upgrading server to 0.41.15

Cemtes · February 10, 2021, 4:57am

Node red gives a websocket error when trying to connect to blynk after updating the local blynk server.
I use the node red pallet node-red-contrib-blynk-ws (v1.0.4) with my blynk app on a local server running on a raspberry pi. Everything has been working fine for about a year until I updated the server from version 0.41.13 to 0.41.15. Since the update, node red can’t connect to blynk, I initially get the error Websocket Error: WebSocket was closed before the connection was established followed by the error Websocket Error: socket hang up every 5 seconds as node red attempts to reconnect. I tested node red with a test project in the blynk cloud and it works fine so it seems the error is only with the local server. I have tried with and without SSL enabled on the blynk server (and made the appropriate changes to the address in node red) and get the same error.

The only thing that’s changed in my setup is the server version so I’m fairly certain it’s not a network error or connection error somewhere else in the system.

Does anyone have any suggestions on correcting this issue?

Thanks

PeteKnight · February 10, 2021, 8:49am

I had a similar issue a couple of weeks ago, when I upgraded my local server from 0.41.13 to 0.41.15.

I have to say that I tried quite a lot of different things, before I overcame the issue, and I can’t remember exactly what I did and in what sequence. I do recall that, due to a discussion about the Asia server being down and websockets not working after the main issue was fixed, I changed from ws://my_local_server_IP:8080/websockets to ws://my_local_server_IP:8080/websocket (without the ‘s’ on the end) and that is what I’m successfully running now.

I think a restart of Node-Red was needed, and I did experiment with deleting and re-creating my connection setting, but I don’t think that was needed in the end.

Pete.

Cemtes · February 10, 2021, 11:04am

Amazing, thank you! I spent all day doing online searches and experimenting and couldn’t figure out what was wrong.

PeteKnight · February 10, 2021, 11:30am

So just dropping the ‘s’ fixed it?

Pete.

PeteKnight · February 10, 2021, 11:32am

@gab.lau you might want to take a look at this, and change the URL info in the Node-Red ws contrib to reflect this?

Pete.

hominidae · February 16, 2021, 6:36pm

Yes, a restart of NR was required in order for the WS library to make the change of the URL work…a simple config change in the node(s) and re-deploy would not do it.
I raised an issue regarding that aspect of the problem in the github repo, here: https://github.com/gablau/node-red-contrib-blynk-ws/issues/29

Cemtes · February 17, 2021, 3:31am

Yeah, that’s all it took. Dropped the “s” and it’s working great!

877 · February 21, 2021, 5:20pm

Same issue here this week using node red / cloud server. Fixed it seems by dropping the ‘s’.

877 · February 26, 2021, 7:36pm

Problem reared its head again today for me, I dropped the ‘s’ on all servers, restarted node red, nothing helps…

hominidae · February 26, 2021, 7:56pm

…revert blynkk the server to v0.41.14

877 · February 26, 2021, 7:57pm

Yup I was thinking that, makes sense…

Trouble is, I’m using the Cloud server

PeteKnight · February 26, 2021, 8:48pm

The majority of my Home Automation systems still use the Blynk cloud servers and Node-Red running on two separate servers in two different countries (but both using the Frankfurt server) and I’m not experiencing any issues.
As it happens, both of these servers have their Blynk connections set-up to use websockets with an ‘s’ on the end, it’s just my local server where I have to use websocket

Pete.

877 · February 28, 2021, 9:37am

Hmm strange, I am having no end of trouble with my two cloud server connections not connecting…

Tried wss, ws and combinations of the two…

PeteKnight · February 28, 2021, 9:55am

Can you post the condole output that you see when you type node-red-start (after doing a node-red-stop first of course)?

Pete.

877 · February 28, 2021, 10:39am

Here’s the log, I’m using wss connection on both cloud servers (my local server is disabled)
Cloud servers never connect…

Tests:

I switched one of the cloud servers to ws connection, both connect after re-deploy 20-30 seconds later.

Then I switch the other to ws and redeploy, connects instantly.

Now changes both servers to wss, redeploy connects instantly.

Seemingly totally random what works…


> node-red-docker@1.2.6 start /usr/src/node-red

> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"


28 Feb 10:32:00 - [info] 


Welcome to Node-RED

===================


28 Feb 10:32:00 - [info] Node-RED version: v1.2.6

28 Feb 10:32:00 - [info] Node.js  version: v10.23.0

28 Feb 10:32:00 - [info] Linux 5.4.79-v7l+ arm LE

28 Feb 10:32:00 - [info] Loading palette nodes

28 Feb 10:32:01 - [debug] Module: node-red-contrib-threshold 0.0.3

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-threshold

28 Feb 10:32:01 - [debug] Module: node-red-contrib-alexa-cakebaked 4.0.2

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-alexa-cakebaked

28 Feb 10:32:01 - [debug] Module: node-red-contrib-bigtimer 2.7.3

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-bigtimer

28 Feb 10:32:01 - [debug] Module: node-red-contrib-blynk-ws 1.0.4

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-blynk-ws

28 Feb 10:32:01 - [debug] Module: node-red-contrib-bool-gate 1.0.2

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-bool-gate

28 Feb 10:32:01 - [debug] Module: node-red-contrib-contextbrowser 0.0.4

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-contextbrowser

28 Feb 10:32:01 - [debug] Module: node-red-contrib-diode 1.0.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-diode

28 Feb 10:32:01 - [debug] Module: node-red-contrib-homekit-bridged 1.2.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-homekit-bridged

28 Feb 10:32:01 - [debug] Module: node-red-contrib-huemagic 3.0.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-huemagic

28 Feb 10:32:01 - [debug] Module: node-red-contrib-ibm-watson-iot 0.2.8

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-ibm-watson-iot

28 Feb 10:32:01 - [debug] Module: node-red-contrib-influxdb 0.5.4

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-influxdb

28 Feb 10:32:01 - [debug] Module: node-red-contrib-interval-length 0.0.4

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-interval-length

28 Feb 10:32:01 - [debug] Module: node-red-contrib-moment 4.0.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-moment

28 Feb 10:32:01 - [debug] Module: node-red-contrib-play-audio 2.5.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-play-audio

28 Feb 10:32:01 - [debug] Module: node-red-contrib-ramp-thermostat 0.8.3

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-ramp-thermostat

28 Feb 10:32:01 - [debug] Module: node-red-contrib-simple-gate 0.4.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-simple-gate

28 Feb 10:32:01 - [debug] Module: node-red-contrib-sonoff-tasmota 3.0.0

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-sonoff-tasmota

28 Feb 10:32:01 - [debug] Module: node-red-contrib-alexa-home-skill 0.1.19

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-alexa-home-skill

28 Feb 10:32:01 - [debug] Module: node-red-contrib-timeout 1.1.4

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-timeout

28 Feb 10:32:01 - [debug] Module: node-red-contrib-tplink-smarthome 0.1.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-tplink-smarthome

28 Feb 10:32:01 - [debug] Module: node-red-contrib-unifi 0.1.16

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-unifi

28 Feb 10:32:01 - [debug] Module: node-red-contrib-zigbee2mqtt 0.6.3

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-contrib-zigbee2mqtt

28 Feb 10:32:01 - [debug] Module: node-red-dashboard 2.28.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-dashboard

28 Feb 10:32:01 - [debug] Module: node-red-node-email 1.8.3

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-email

28 Feb 10:32:01 - [debug] Module: node-red-node-ledborg 0.0.22

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-ledborg

28 Feb 10:32:01 - [debug] Module: node-red-node-ping 0.2.2

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-ping

28 Feb 10:32:01 - [debug] Module: node-red-node-random 0.3.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-random

28 Feb 10:32:01 - [debug] Module: node-red-node-rbe 0.2.9

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-rbe

28 Feb 10:32:01 - [debug] Module: node-red-node-sentiment 0.1.6

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-sentiment

28 Feb 10:32:01 - [debug] Module: node-red-node-serialport 0.11.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-serialport

28 Feb 10:32:01 - [debug] Module: node-red-node-smooth 0.1.2

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-smooth

28 Feb 10:32:01 - [debug] Module: node-red-node-tail 0.1.1

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-tail

28 Feb 10:32:01 - [debug] Module: node-red-node-twitter 1.1.7

28 Feb 10:32:01 - [debug]         /data/node_modules/node-red-node-twitter

28 Feb 10:32:01 - [debug] Module: node-red-node-rbe 0.2.9 *ignored due to local copy*

28 Feb 10:32:01 - [debug]         /usr/src/node-red/node_modules/node-red-node-rbe

28 Feb 10:32:01 - [debug] Module: node-red-node-tail 0.1.1 *ignored due to local copy*

28 Feb 10:32:01 - [debug]         /usr/src/node-red/node_modules/node-red-node-tail

28 Feb 10:32:03 - [warn] ledborg : rpi-gpio.errors.libnotfound

28 Feb 10:32:05 - [info] Dashboard version 2.28.1 started at /ui

28 Feb 10:32:05 - [info] Settings file  : /data/settings.js

28 Feb 10:32:05 - [info] Context store  : 'default' [module=localfilesystem]

28 Feb 10:32:05 - [info] User directory : /data

28 Feb 10:32:05 - [warn] Projects disabled : editorTheme.projects.enabled=false

28 Feb 10:32:05 - [info] Flows file     : /data/flows.json

28 Feb 10:32:05 - [info] Server now running at http://127.0.0.1:1880/

28 Feb 10:32:06 - [debug] loaded flow revision: 9662f60b08c22de3693974bf909b16bd

28 Feb 10:32:06 - [debug] red/runtime/nodes/credentials.load : no user key present

28 Feb 10:32:06 - [debug] red/runtime/nodes/credentials.load : using default key

28 Feb 10:32:06 - [debug] red/runtime/nodes/credentials.load : keyType=system

28 Feb 10:32:06 - [warn] 


---------------------------------------------------------------------

Your flow credentials file is encrypted using a system-generated key.


If the system-generated key is lost for any reason, your credentials

file will not be recoverable, you will have to delete it and re-enter

your credentials.


You should set your own key using the 'credentialSecret' option in

your settings file. Node-RED will then re-encrypt your credentials

file using your chosen key the next time you deploy a change.

---------------------------------------------------------------------


28 Feb 10:32:06 - [info] Starting flows

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : global

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : bd52b987.d668e8

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : cc9bb259.6c984

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : be5275e8.e06c78

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 6043bdc.7576744

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : b08efd68.4f78

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : 5a9d8292.529c2c

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : cce3159f.ed5978

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : fa1345d7.0957a8

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 564b0ab8.42d084

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 2a6827d4.9b5e18

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : c351e9b7.248858

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 28b5cbf9.f29374

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : d176a11a.5c791

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : e3ce390a.5c1998

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : e82860b0.465cf

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : a6ac6110.78c0c

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : ab2be502.455278

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 738a4866.c25308

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 2776ae8.d8d2052

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : b1f887fe.970e58

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 22e4edf9.4432f2

28 Feb 10:32:06 - [debug] red/nodes/flows.start : starting flow : 73ce8bea.e89a44

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : 3c0508ca.d53c08

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : d64196b0.273b98

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : 390c5881.bc3b98

28 Feb 10:32:06 - [debug] red/nodes/flows.start : not starting disabled flow : e5f48c9e.09468

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] LOG PINS []

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://blynk-cloud.com/websockets

28 Feb 10:32:06 - [info] [blynk-ws-client:Family Blynk account] LOG PINS []

28 Feb 10:32:06 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://blynk-cloud.com/websockets

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk TEST LOCAL] LOG PINS []

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 13

28 Feb 10:32:06 - [info] [blynk-ws-client:Family Blynk account] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 4

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 7

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register LCD node pin: 70

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 0

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 104

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: style-btn pin: 104

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: app

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 106

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 108

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: style-btn pin: 106

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: style-btn pin: 108

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: app

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: app

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 97

28 Feb 10:32:06 - [info] [blynk-ws-client:Family Blynk account] Register notify node

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 62

28 Feb 10:32:06 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 3

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 18

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 105

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 116

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 117

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 102

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: style-btn pin: 102

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: app

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 100

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: style-btn pin: 100

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: app

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 103

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 109

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 111

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 110

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 50

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 49

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 10

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 101

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 254

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 61

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 62

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register input node - type: write pin: 63

28 Feb 10:32:07 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Register notify node

28 Feb 10:32:07 - [info] [blynk-ws-client:Family Blynk account] Register notify node

28 Feb 10:32:07 - [info] [blynk-ws-client:Family Blynk account] Register notify node

28 Feb 10:32:07 - [info] Started flows

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 error listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 opened listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 connected listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 closed listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 disabled listeners added. Use emitter.setMaxListeners() to increase limit

28 Feb 10:32:07 - [info] [zigbee2mqtt-server:5f73645c.dbf83c] MQTT Connected

28 Feb 10:32:07 - [info] [zigbee2mqtt-server:5f73645c.dbf83c] Refreshing devices

28 Feb 10:32:07 - [info] [mqtt-broker:5615eece.b3a81] Connected to broker: mqtt://192.168.1.95:1883

28 Feb 10:32:07 - [info] [alexa-remote-account:f24a22c6.8037c] intialising with the PROXY method and saved data...

28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: starting initialisation:


28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: Use as Login-Amazon-URL: amazon.co.uk

28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: Use as Base-URL: alexa.amazon.co.uk

28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: cookie was provided

28 Feb 10:32:07 - [debug] [alexa-remote-account:f24a22c6.8037c] Alexa-Remote: Sending Request with {"host":"alexa.amazon.co.uk","path":"/api/bootstrap?version=0","method":"GET","timeout":10000,"headers":{}}

28 Feb 10:32:07 - [error] [influxdb out:6cd8a4f8.f3b05c] Error: A 400 Bad Request error occurred: {"error":"unable to parse 'weather,topic=Xiaomi_8_weather_bathroom,make=aqara,location=bathroom,connection=zigbee,power=battery,friendlyname=Bathroom batteryPercent=100,batteryVolts=3005,humidity=62.68,linkQuality=undefined,pressure=1019.7,temperature=21.3': invalid boolean"}


28 Feb 10:32:07 - [info] [zigbee2mqtt-server:5f73645c.dbf83c] MQTT Subscribed to: "zigbee2mqtt/#

28 Feb 10:32:07 - [info] [zigbee2mqtt-server:5f73645c.dbf83c] Refreshing devices


28 Feb 10:32:08 - [info] [blynk-ws-client:Blynk TEST LOCAL] Connection disabled by configuration

2
28 Feb 10:32:09 - [warn] [blynk-ws-client:Blynk (LIVE SYSTEM)]   wss.//139.59.206.133.80/websockets

28 Feb 10:32:09 - [warn] [blynk-ws-client:Family Blynk account]   wss.//139.59.206.133.80/websockets


28 Feb 10:32:19 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:19 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:19 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:19 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:24 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:24 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:24 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:24 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:24 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:24 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:24 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:24 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:24 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:24 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:24 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:24 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:29 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:29 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:29 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:29 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:29 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:29 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:29 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:29 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:29 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:29 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:29 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:29 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:34 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:34 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:34 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:34 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:34 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:34 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:34 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:34 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:34 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:34 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:34 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:34 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope ff528803.130fc8:bd52b987.d668e8

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope f3f010b6.7a196:fa1345d7.0957a8

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope a0728fd5.03674:fa1345d7.0957a8

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 65f2e755.2825e8:e82860b0.465cf

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 9358047e.6d38f8:ab2be502.455278

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 3245d3fe.9988dc:ab2be502.455278

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 66e90019.baf01:2776ae8.d8d2052

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 7287874a.557308:b1f887fe.970e58

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 457a996d.e31138:b1f887fe.970e58

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 2f77266f.98643a:22e4edf9.4432f2

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope global

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope 8fd574e.9baab88:e82860b0.465cf

28 Feb 10:32:36 - [debug] Flushing localfilesystem context scope cad949db.837468:e82860b0.465cf

28 Feb 10:32:39 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:39 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:39 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:39 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:39 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:39 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:39 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:39 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:39 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:39 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:39 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:39 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:44 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:44 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:44 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:44 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:44 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:44 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:44 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:44 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:44 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:44 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:44 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:44 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:49 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:49 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:49 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:49 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:49 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:49 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:49 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:49 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:49 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:49 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:49 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:49 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:54 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:54 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:54 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:54 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:54 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:54 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:54 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:54 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:54 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:54 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:54 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:54 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:59 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:59 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:32:59 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:59 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:32:59 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:59 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:59 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:32:59 - [error] [blynk-ws-client:Family Blynk account] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:32:59 - [info] [blynk-ws-client:Family Blynk account] Client Error

28 Feb 10:32:59 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:32:59 - [info] [blynk-ws-client:Family Blynk account] Websocket closed: wss://139.59.206.133:80/websockets

28 Feb 10:32:59 - [info] [blynk-ws-client:Family Blynk account] Reconnect in 5 seconds...

28 Feb 10:33:04 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:33:04 - [info] [blynk-ws-client:Family Blynk account] Start secure connection: wss://139.59.206.133:80/websockets

28 Feb 10:33:04 - [error] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket Error: Client network socket disconnected before secure TLS connection was established

28 Feb 10:33:04 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Client Error

28 Feb 10:33:04 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Reconnect in 5 seconds...

28 Feb 10:33:04 - [info] [blynk-ws-client:Blynk (LIVE SYSTEM)] Websocket closed: wss://139.59.206.133:80/websockets

PeteKnight · February 28, 2021, 11:33am

877:

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 error listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 opened listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 connected listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 closed listeners added. Use emitter.setMaxListeners() to increase limit

(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 disabled listeners added. Use emitter.setMaxListeners() to increase limit

Have you noticed these error messages?

Pete.

877 · February 28, 2021, 12:58pm

Yes I have noticed them, a quick google gives mixed info. Some say it’s just a warning, ignore. Other says it’s one of the nodes causing the issue.