Sounds like you may have an Arduino that’s not reporting as a valid Arduino or one without a serial? Does it work when you only use single chamber mode?
You should be able to freely switch the modes, so I'm guessing something may be borked.
I would go into "Maintenance panel - View logs", click on "Enable auto-refresh", and see if there's any hints shown in stderr or stdout.
If you don't find anything, you could power-cycle the Arduino and see what happens...
Cheers!
Jun 29 2024 23:22:58 Notification: Temperature control disabled
Jun 29 2024 23:22:58 controller debug message: INFO MESSAGE 12: Received new setting: mode = o
Jun 29 2024 23:25:03 Notification: Beer temperature set to 36.0 degrees in web interface
Jun 29 2024 23:25:03 controller debug message: INFO MESSAGE 12: Received new setting: mode = b
Jun 29 2024 23:25:03 controller debug message: INFO MESSAGE 12: Received new setting: beerSet = 36.0
Sometimes, the EEPROM likes to act up. Offhand, I cannot remember if the modes are in EEPROM. You could always try it (you will have to set up your sensors again) and see how that works:Thanks for your advice, I really appreciate it.
I get similar messages, but the tab continues to say off.
Thanks for your advice, I really appreciate it.
I get similar messages, but the tab continues to say off.
Do you ever see an "INFO MESSAGE 12: Received new setting: mode = b" in stderr?
Thanks LBussy.Sometimes, the EEPROM likes to act up. Offhand, I cannot remember if the modes are in EEPROM. You could always try it (you will have to set up your sensors again) and see how that works:
Maintenance Panel - Advanced Settings, then scroll the Control Constants pane to the bottom, and click on the "Reset controller to factory defaults" button
That 30 was when it went to defaults in centigrade and I started raising it.. I quickly changed it back to 68.0 degrees F. I was aiming for. Unfortunately I really messed up.. When I thought it was borked I hooked up my old ST-1000 and was using that. But when I figured the Brewpi might be working, I swapped out the temp probe back to the Brewpi. Unfortunately, I left the heater plugged into the ST-1000.Something's definitely hinky, probably with the web gui. The Arduino reported all kinds of good things happening, like these lines that show the controller being put into Beer Constant at 30° (btw, might want to make sure you have the set point and temperature scale you actually want lest you cook or stun your yeast)
Jun 30 2024 08:18:17 Arduino debug message: INFO MESSAGE 12: Received new setting: mode = b
Jun 30 2024 08:18:17 Arduino debug message: INFO MESSAGE 12: Received new setting: beerSet = 30.0
So I agree the controller seems to be working and only the gui seems to have an issue. Try flushing the browser cache?
Cheers!
By "power only," he means the one connecting the Arduino. You would be amazed how many power only cables people seem to have squirreled away.Thanks for the intel. I don't have backup Pi's or Arduino's, so I'll have to focus on the SD card and power supply. I was using a power-only USB cable that came with the PI. And I guess I'll look into getting spare PI and Arduino so I can get this beer cooling (thankfully I haven't put the yeast in yet).
Ok, I've picked up a new Arduino, it lights up when plugged into the PI, once I start attaching low voltage wires to it, it dies. I added GRD, unplugged and tested, A4 repeat, 5V repeat. It was when I added the 5V wire that no lights on the board came on. I then tested it again by disconnecting the 5V low voltage wire to the relay board. Same issue, no lights on Arduino.The errors indicate that the system is not communicating with the Arduino. If you have a different Arduino, try that. If you have a different Pi, try that, then combinations.
While not specifically indicated here, the most common errors are bad SD cards and flakey power supplies.
One of my splices for the probe was bad, corrected and now my Arduino has lights when all is connected! I went ahead and reinstalled BrewPi and flashed the Arduino with the defaults. It came back that it was successful, and got the happy brewing splash screen. Sadly, when I load the page, I am still presented with the 'Couldn't write to socket: [111] Connection refused Is the script running?' when applying a beer profile, and am unable to start the script. I noticed on my putty connection, I'm showing the build as 0.8.1, but on brewpi.local it says 0.8.0. Is that a bug, or should I format my SD card, and reinstall?The smart bet is the probes. The cheapest and most direct bet is both. Resisters are a few cents.
You could disconnect all but one probe, test, lather rinse and repeat.
I've been using a Pi2 vB. I'll uninstall and do w/o tilt with fingers crossed.It's quicker (for me of course) to suggest you try it again without the tilt. The log messages suggest that this may be where the issue is.
What model of Pi?
Dongles have always been a special sort of hell ... let me think about that a bit. You may have used an older version previously that was not as "Smart" as the current version, but now has fallen afoul of some other vagary I forgot to check for.I have a Bluetooth dongle on my PI to connect to the Tilt. Its worked before.
They are set both to inverted. I have it running right now and its running when it should be off. I've tried the other 2 devices it found with similar results.Be sure to set the Cool and Heat gpios to "inverted"...
It's time for the multimeter. Check the voltage (disconnect the relays) and see if that is correct. If it is, your wiring is suspect.They are set both to inverted. I have it running right now and its running when it should be off. I've tried the other 2 devices it found with similar results.
Ok, will do. Just to confirm, I'll disconnect the wires to the relay and check the Dupont wires from the Arduino to the relay for 5V. Anything else?It's time for the multimeter. Check the voltage (disconnect the relays) and see if that is correct. If it is, your wiring is suspect.