node-red-contrib-flic-buttons
node-red-contrib-flic-buttons copied to clipboard
hardillb
Node does not reconnect to flicd
If flicd crashes the node does not attempt to reconnect to it once it's been restarted.
@Roaders any reason for this? It means that you have to restart Node-RED if there is an issue which is a pain as if I set up flicd to auto restart I have no way to know I have to kick Node-RED (which I shouldn't need to do really)
No particular reason. I am not sure that flicd has ever crashed for me. I did get into a few situations where I had to power up my 2 pis in the right order as one pi connected to daemons on both pis. I was considering implementing a retry feature for this which would probably solve both issues.
flicd has crashed twice on me now in the space of a couple of hours so sounds like it would be useful
So what do you think? Try to connect to the daemon every 60 seconds or something?
60 seconds is as good as anything.
I think I've just found when you last looked at this https://github.com/50ButtonsEach/fliclib-linux-hci/issues/19 as I'm about to raise a bug about flicd crashing all the time
For anyone interested in a fix for this, see my fork: https://github.com/hufftheweevil/node-red-contrib-flic-buttons
I've modified the underlying library a bit to ensure the client stays connected to the server after the server restarts. Additionally, all connection channels are kept in tact to ensure events continue without having to restart the nodes.
I also added a feature that allows for more than one event to output on a particular node, if you so choose.
Since neither myself or @Roaders use this node any more (I just don't use the flic's and Roaders is using the Flic hub hardware) would you be interested in taking it over? I can close this repo and add you to the npm package?
OK, let me know what your npm username and I'll sort it out tomorrow evening.