On Tue, 6 Aug 2019 20:17:42 +0100, Adrian wrote:

> I've tried unplugging the gauge, but I still get the problem, suggesting
> GPIO rather than the gauge itself.  Stopping and restarting the software
> appeared to help for a couple of days, but it has started again.
> Rebooting doesn't work either.   The Python3 code below is started at
> boot up, and can be run with nohup.  Any suggestions on where to start
> looking ?

Had any thunderstorms recently? Suspect a hardware problem, damaged
GPIO input, or the built in pull up/down resitors fried. A floating
input can produce a stream of false transitions. Either try another
GPIO for the guage or fit a 10 k or so pull up/down resistor as
required.

Then think about adding some protection to try and reduce the chances
of the Pi getting zapped again.

--
Cheers
Dave.

--- SoupGate-Win32 v1.05