Hi i updated my node red to 0.19.4 now it won't deploy saying lost connection to server I'm a complete n00b at this so be patient with me
Hi @garywilson4 - can you share the node-red log output from the server side?
Perhaps the browser cache is still using bits from node-red 0.18.x? Try either clearing your browser's cache, or forcing a full reload using shift F5 -- maybe?
where does it store the log output? rpi running raspian i think
Welcome to Node-RED
20 Sep 14:26:19 - [info] Node-RED version: v0.19.4
20 Sep 14:26:19 - [info] Node.js version: v8.9.4
20 Sep 14:26:19 - [info] Linux 4.9.35-v7+ arm LE
20 Sep 14:26:20 - [info] Loading palette nodes
20 Sep 14:26:25 - [info] Dashboard up and running
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported part ially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <>
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported part ially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <>
20 Sep 14:26:27 - [info] Dashboard version 2.9.8 started at /ui
20 Sep 14:26:27 - [warn] nodes/core/io/lib/mqtt.js is deprecated and will be removed in a future release of Nod e-RED. Please report this usage to the Node-RED mailing list.
20 Sep 14:26:27 - [warn] nodes/core/io/lib/mqttConnectionPool.js is deprecated and will be removed in a future release of Node-RED. Please report this usage to the Node-RED mailing list.
20 Sep 14:26:27 - [info] Settings file : /home/pi/.node-red/settings.js
20 Sep 14:26:27 - [info] Context store : 'default' [module=memory]
20 Sep 14:26:27 - [info] User directory : /home/pi/.node-red
20 Sep 14:26:27 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
20 Sep 14:26:27 - [info] Flows file : /home/pi/.node-red/flows_RaspberryPi.json
20 Sep 14:26:28 - [info] Server now running at http://127.0.0.1:1880/
20 Sep 14:26:28 - [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.
20 Sep 14:26:28 - [info] Starting flows
20 Sep 14:26:29 - [info] Started flows
20 Sep 14:26:29 - [info] [mqtt-broker:523d050e.3a8a4c] Connected to broker: mqtt://192.168.0.3:1883
20 Sep 14:29:10 - [info] Stopping flows
20 Sep 14:29:10 - [info] [mqtt-broker:523d050e.3a8a4c] Disconnected from broker: mqtt://192.168.0.3:1883
20 Sep 14:29:10 - [info] Stopped flows
20 Sep 14:29:10 - [info] Starting flows
20 Sep 14:29:10 - [info] Started flows
20 Sep 14:29:10 - [red] Uncaught Exception:
20 Sep 14:29:10 - Error: dns service error: name conflict
at new Advertisement (/home/pi/.node-red/node_modules/mdns/lib/advertisement.js:56:10)
at Object.create [as createAdvertisement] (/home/pi/.node-red/node_modules/mdns/lib/advertisement.js:64:10)
at Advertiser.startAdvertising (/home/pi/.node-red/node_modules/hap-nodejs/lib/Advertiser.js:47:30)
at Accessory._onListening (/home/pi/.node-red/node_modules/hap-nodejs/lib/Accessory.js:661:20)
at emitOne (events.js:116:13)
at HAPServer.emit (events.js:211:7)
at HAPServer._onListening (/home/pi/.node-red/node_modules/hap-nodejs/lib/HAPServer.js:190:8)
at emitOne (events.js:116:13)
at EventedHTTPServer.emit (events.js:211:7)
at EventedHTTPServer. (/home/pi/.node-red/node_modules/hap-nodejs/lib/util/eventedhttp.js:65:10)
at emitNone (events.js:106:13)
at Server.emit (events.js:208:7)
at emitListeningNT (net.js:1378:10)
at _combinedTickCallback (internal/process/next_tick.js:135:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
nodered.service: main process exited, code=exited, status=1/FAILURE
Unit nodered.service entered failed state.
nodered.service holdoff time over, scheduling restart.
Stopping Node-RED graphical event wiring tool....
Starting Node-RED graphical event wiring tool....
Started Node-RED graphical event wiring tool..
20 Sep 14:29:13 - [info]
this is what comes up on the cosole screen
The key line for why it isn't starting is : Error: dns service error: name conflict
I'm guessing you use node-red-contrib-homekit?
See https://github.com/mschm/node-red-contrib-homekit/issues/48
But you might want to open a new issue given these lines:
20 Sep 14:26:27 - [warn] nodes/core/io/lib/mqtt.js is deprecated and will be removed in a future release of Nod e-RED. Please report this usage to the Node-RED mailing list.
20 Sep 14:26:27 - [warn] nodes/core/io/lib/mqttConnectionPool.js is deprecated and will be removed in a future release of Node-RED. Please report this usage to the Node-RED mailing list.
yes homekit used
thanks for help open new issue on this forum for that warning?
Well thats what the second message says to do...
I've never seen that message before!
Back on the home kit issue, that link suggests some things that might resolve the issue.
resolved this issue by removing homekit but will look further into it as i do want homekit
If it’s that node triggering that message then really the issue needs to be raised against it, as it must be quite out of date.
Then the Warn message needs amending (and not just the typo)
Yeah. Noted
The mqtt files its warning about are gone in 0.20. We've been warning they are deprecated for about 2 years now. I think that's enough time to be fair.
As an alternative have a look at: homebridge-mqtt
You can use the core mqtt in and mqtt out nodes.
