Hello new to Node-Red and all this stuff.
I have a Raspberry Pi running Openplotter 4.x.x
I have SignalK 2.11.0 installed through Openplotter
I have Node Red - 3.1.14 installed through SignalK
I am using Pallet iiot2k - 2.1.3 installed through Node-Red
If I deviate from these Open plotter stops working and as of right now I am just monitoring 1 switch and it is not vital so if upgrading is the answer thank you but I will not be able to solve my issue.
I have a switch hooked up to GPIO17 on the Pi. When debounce is set to 0 the switch works properly but my CPU usage maxes out. When debounce is at anything other than 0 I get a couple issues.
- it activates one time but then freezes until restarting Node-Red/SignalK -- this is 95% of the time
- it works for about 10 mins then stops working -- this is about 4.5%
- it works all the time for at least 3 hours -- I'm working on other things so I am still rebooting a bit but this has happened 3-5 times
The flow is literally 2 items the GPIO input and a SignalK output
When reviewing the flow the debug will see the initial status, see the change, but there is no additional changes after that.
The few random times it worked the Debounce was set at 25ms, I've tried adjusting this but there seems to be no change other than setting it at 0.
The other computer is a pain to get screen shots from but I will if there is possibilities for a fix, maybe instead of Edge monitoring just a check current status every 5 seconds??
The options in the palette are the following
GPIO ____ -- GPIO pin number
Mode ____ -- This is for Input resistor settings - mine is set for No-Pull
Edge _____ -- Rising/Falling - Set at Rising and Falling
Debounce ____ -- ms - set at anywhere between 5 to 500, currently 25
Send Bool _ -- check box - unchecked
Send on Start _ -- check box - checked
Name _____ -- name - called Bilge status
