So was the hysteresis working, but not getting new targets? Did other elements on the interface show online or did they say offline like this?
View attachment 780823 Just trying to understand the failure mode here.
I track an interface status by looking at an individual element with the "connected" status. Seems pretty reliable so far, but if your comms were up but the board wasn't working, thats a different issue.
*edit* - I re-read and you said the wort warmed up, so I'm going to take that as the interface was completely unresponsive on both comms and function.
Yeah, the board was unresponsive and seemingly not functional. No device updated on BC, and the board wasn't showing on WiFi. I just unplugged and plugged it back in, then it worked.
My other fermenter's control board did the same last night, but my script alerted me, and I quickly resolved it. I'm trying to find patterns to see what may be causing it.
Per
@RiverCityBrewer, the "connected" property of a device element will tell the script if the interface is connected or not.
Ah, I just now see the Connected property. I printed the script section out and put it presentation book for quick access, and the Connected (true/false) is tucked at the very top of the next page from All Device Elements, hah. But at least I learned it is there now. Thanks!
Hopefully you added a resistor (10k to gnd for example) in that jumper, otherwise you are creating a direct short.
10k makes the input not receive the signal. But once I play with the Connected value, this may be moot (and better!).
How are you powering this ESP32? Usually microcontroller failures are power related (voltage dip, spike, etc). The ESP does have a realtime OS, so it is *possible* that crashed, though I think highly unlikely.
It's the ESP32R4 from Robodyn, and I'm powering it with 110v AC input (the board has 110V AC or 12-24V DC with step downs for the MCU; a jumper sets which input is used). Under the board, I daisy chained each relay's COM to the 110V hot input so that single source of 110V can be used (and tucked this thing away into a nice protected project box for safety). I'm only running a 24W glycol pump and the 12v/12w pressure release solenoid (with converter) on the relays; my house is warm enough to let the wort free climb, so no heat wrap is powered.
On my previous setup (1 ESP32 dev board for to fermenters and wired to one 8-relay board), I had the ESP32 powered by standard USB, and I had a separate USB link to power the relay board. That board sometimes dropped as well, so I hoped splitting the load and power to two different boards for both fermenters would work.
Update: The Connected property does work well for this. Thanks! If I'm traveling and have something in a tank that I want to watch/control, I use the localhost IP with different ports and Node-RED to connect to my interfaces from anywhere, so this will limit that ability since the TCP connection into Node-RED indicates a connection is made. But while home ( and thus, the only time I'm able to do anything about a dropped interface anyways), I use network IPs, so this is perfect.