Ermmm... I've moved my network around and moved all brewing related gadgets onto their own network and it's gone a bit wrong! When I say wrong, I have 2 BrewPi controllers, one D1mini and on D32, the D1 mini BrewPi controller is fine, the D32 is having a serious breakdown. The D1mini hasn't had any issues at any point I should point out. So what have I done?
I tried just to move networks by connecting to the AP for each controller and attach to new network. This appeared to go without issue. However the D32 started dropping off the network, it returned to AP mode a few times. So I tried to connect to new network and again it worked for a while, but kept dropping off. I thought I'd reflash to clear things out. The network connectivity is now fine, but I cannot configure any pins or temperature sensor, I get the try resetting EEPROM message every time I hit any assign button.
I reflashed again but the symptoms remain the same. Some interesting observations: I don't think the reflash cleared the existing configuration as on first boot I was seeing a temperature reading from one (the only connected) temperature sensor and the set temperature levels were as I had set before re-flashing. When I go into Configure Sensors/Pins/Devices there were no installed devices. I've tried assiging different pin/sensor combinations but always get the try reseting EEPROM message.
There were no temperature readings but Fridge and beer were both set to 20C (as previous). If I change control mode from off to beer constant and change the temperature, I get a temperature reading from the (connected) temperature sensor and the set temperature changes accordingly. Changing back to temperature control off clears the temperature set values, but I still get a temperature reading and there are no assigned devices listed?
The good news though that this cycle of the temperature control seems to have cleared something! Now I can, and have, assigned devices and pins successfully!? Pins are correctly assigned and temperature sensors are reading. This has survived a couple of power cycles now without any further issues.
A bit rambling but does any of that make sense?
P.S. The issue with not being able to set a Not Inverted relay pin is still the same (I don't mean you haven't fixed it yet, just not affected by what I encountered above).