Yeelight Problem

Hardware
1

I hope someone out there can help me. I am a novice at this stuff.
I have Yeelights running on my pi and using node red.
I don not use them all the time so I disable the 2 flows that can control them.
My pi filled up the 32G mem card because of the syslog file and another log file. One was 13 Gigs and the other 15Gigs. 0 space was left on the SD card to run anything.
I have since fixed that and regained some space, but I'm afraid that will keep on happening because Node Red keeps trying to connect to the Yeelights if the flow is running or not.
I have even deleted the flows all together and Node Red keeps trying to connect.
I have posted some of the syslog info to show the messages getting logged.
I would like to know how to stop node red from trying to connect when the flows are not running.

Thanks in advance for any help.

Nov 24 21:18:17 raspberrypi Node-RED[333]:   syscall: 'connect',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   address: '192.168.0.31',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   port: 55443 }
Nov 24 21:18:17 raspberrypi Node-RED[333]: 24 Nov 21:18:17 - [info] [yeelight-compat-hue-config:Yeelight 1] Disconnected from 192.168.0.31:55443
Nov 24 21:18:17 raspberrypi Node-RED[333]: Error at 192.168.0.31:55443 { Error: connect EHOSTUNREACH 192.168.0.31:55443
Nov 24 21:18:17 raspberrypi Node-RED[333]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
Nov 24 21:18:17 raspberrypi Node-RED[333]:   errno: 'EHOSTUNREACH',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   code: 'EHOSTUNREACH',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   syscall: 'connect',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   address: '192.168.0.31',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   port: 55443 }
Nov 24 21:18:17 raspberrypi Node-RED[333]: 24 Nov 21:18:17 - [info] [yeelight-compat-hue-config:Yeelight 1] Disconnected from 192.168.0.31:55443
Nov 24 21:18:17 raspberrypi Node-RED[333]: Error at 192.168.0.33:55443 { Error: connect EHOSTUNREACH 192.168.0.33:55443
Nov 24 21:18:17 raspberrypi Node-RED[333]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
Nov 24 21:18:17 raspberrypi Node-RED[333]:   errno: 'EHOSTUNREACH',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   code: 'EHOSTUNREACH',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   syscall: 'connect',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   address: '192.168.0.33',
Nov 24 21:18:17 raspberrypi Node-RED[333]:   port: 55443 }
Nov 24 21:18:17 raspberrypi Node-RED[333]: 24 Nov 21:18:17 - [info] [yeelight-compat-hue-config:Yeelight 3] Disconnected from 192.168.0.33:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 3] Connecting to Yeelight 192.168.0.33:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 3] Connecting to Yeelight 192.168.0.33:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 3] Connecting to Yeelight 192.168.0.33:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 1] Connecting to Yeelight 192.168.0.31:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 1] Connecting to Yeelight 192.168.0.31:55443
Nov 24 21:18:19 raspberrypi Node-RED[333]: 24 Nov 21:18:19 - [info] [yeelight-compat-hue-config:Yeelight 1] Connecting to Yeelight 192.168.0.31:55443
2

Note that the error is being generated by the yeelight config node. When you deploy do you get a warning about unused config nodes? If so then click that message and delete the config node. Alternatively you can access the config nodes via the hamburger menu and delete it there.
In addition I think that it could be classed as a bug in the node that it spams syslog with messages at that rate, so it would be a good idea to submit an issue on the node's github page, assuming there is not such an issue there already.

3

Colin, Thank You for your reply. I will have to join Github and follow though as you are suggesting.
In the mean time I have made a discovery.
If I enable the Yeelight flow and let the lights connect, I can then disable the flow, turn off the Yeelights and no more of these messages are logging in the syslog file.

The problem is as soon as I change something in Node Red, in any flow and Deploy (with my Yeelights flow still disabled) the MQTT Broker tries to find the Yeelights and the logging begins again. Oh Well !

Thanks again. Off to Github I go :slight_smile:

4

I don't think that error is caused by your mqtt broker, it is the yeelight node trying to do something.