My understanding is that the Sonoff units in question are based on the ESP32, not the 8266. But yes, it does have only the one sensor wired to it. I'm sure others could be added (it's still a 18b20, so still uses the Onewire interface), but that'd be kind of hacky.
I'd missed that earlier; that would indeed seem to be helpful. Pity they're so pricey.
Well I'm running that latest beta that you made for the s2 mini a couple of weeks ago when we were troubleshooting the i2c screen thing together. Is that the same as the changes that were rolled into the latest stable version? Since I switched to the D1 mini its been stable so its definitely something with the s2 mini.First - apologies for the silence from my side for the past few weeks. I’ve had a lot going on, and have had to focus my attention on non-brewing-related projects for a bit. Mostly good stuff, just all demanding loads of time.
You might be able to use the Sonoff, but the pinout is different vs my PCBs, so you would have to compile a custom version of the firmware to get it to work. As I recall, the Sonoff only has one temperature sensor wired to it as well — you would need to set something up to get it to be able to use multiple. I think it is based on the ESP8266 as well, so a Tilt isn’t an option for a second sensor.
The Tilt Pro offers temperature resolution in fractional degrees which helps for this application. It’s hard to hold a beer to a fraction of a degree Fahrenheit when you can’t see fractional degrees.
Were you running the latest firmware? The most recent release (v15c) was solid in testing — it seemed like there was some kind of issue with the Espressif framework with earlier versions that caused it to crash in strange places.
Instability in BrewPi-Script is incredibly frustrating at this point, as most of the changes I would seek have been implemented.
I’m working on a more permanent replacement, but that requires a rebuild of huge chunks of architecture. It’s coming, but it’s likely a few months away.
I honestly don't recall what was in (which) beta vs. the release. I do know that the release had been running for at least a week+ without issue while I had it hooked up to the debugging interface.
Thanks man! I'll definitely load up the S2 with the new firmware and throw it through the ringer with some water when this beer is in the keg lol I hear ya not enough memory on the D1 every time I use one in a project I cant sloppily allocate memory like I normally do for ease and convenience lolI honestly don't recall what was in (which) beta vs. the release. I do know that the release had been running for at least a week+ without issue while I had it hooked up to the debugging interface.
The D1 Mini should work fine as well. The biggest issue with it is just the frustration that I have when trying to compile for it, so there is no guarantee of future features.
...and a Kasa plug if you need to control another device. I have a couple of the Sonoff units on the way, so I'll see what I can do with them.
If you have a pinout handy, shoot me a link to it and I can see what would be required to get support.
All I have at the moment is this:
For the sake of anyone else who might want to try this:There are a couple of ways to do this that I can think of - but here is what I am envisioning:
I'm back and would like to understand what is going on here. Can you point me where to look to see what is going wrong? I'm not seeing anything in /var/log, which is where Google seems to think NGINX will put it's logs.
So the root problem seems to have been a poor choice of power supply (a 5W iPhone cube) for the Raspberry Pi. I swapped it for a 10W iPad charger and it seems to be working, although the RPI is still giving me undervoltage warnings in syslog. I probably have an official RPI PSU somewhere, but can't put my hands on it immediately.
Looks like a premature observation.
The Arduino/timer seems to reset when the Pi powers up and links but it was a one off. 5 hours stable nowView attachment 643900
Thanks! I went ahead and yolo-merged from my phone, since after thinking about it I’m pretty sure the dangerous bits I was worrying about only happen when I create a release. I hope. We’ll soon find out.Nothing but love from me @Thorrak - appreciate all that you do
The power supply is a 5v 2amp amazon fire stick usb wall adaptor. My fridge sensor first starting cutting out, then it was fridge and beer sensor and now all 3 won't read. I was able to get things working for about 24hr by plugging in a new ethernet cable, resetting the brewpi a few times and clearing everything. All 3 one wire sensors got detected, I swapped the fridge sensor with the room one. The next night it stopped reading temps again, beer and fridge which causses the fridge to stop cooling. I messed around with it again, poured a beer and came back 1 hr later. I put have somehow jammed my picnic tap open because all the beer leaked out of the keg and I could hear the co2 running. The remote sensor box was floating in beer. I cleaned everything today and all 3 sensors are no longer detected.To me, the two most likely culprits are that (at least) one of the sensors is bad, or there is an issue with the power supply to your controller. To test the power supply, if you have a different (hopefully, better) power supply available you could try swapping to that and see if that eliminates the issue. Testing the sensors is difficult given the fact pattern you describe, but here are some questions that might help to narrow it down:
- When you report that the "temp readings cut out", do all 2 (3?) temp readings cut out, or just the fridge/beer?
- When the temp readings cut out, do they stay out permanently, or do they sometimes come back without intervention?
- If they require intervention, what kind of intervention is required? Just resetting the controller, or unseating/reseating the sensors as well?
- Are you powering the sensors off 5v or 3v3? Have you tried switching the power level? (For my PCB designs, there's a jumper that selects this)
I will note that for the builds I've personally used at home, I've never had an issue with any of the sensors after the first ~day of use. If they have issues, they tend to manifest almost immediately -- what you're describing is quite strange!
The Inkbird sensor support was removed in later versions of v15, as Espressif currently has a bug that causes the bluetooth stack on ESP32 to fail after an indeterminate period of time when both Bluetooth active scanning and WiFi coexistence are enabled. I have a workaround designed for this bug, but it works by monitoring when any device hasn't been detected within a certain period of time, and assuming silence means the bluetooth stack has crashed and a device restart is required. Due to compressor protection, if this occurs frequently it can result in your beer not being properly chilled.
This bug supposedly is fixed in ESP-IDF v5.1 which comes alongside ESP32 Arduino v3. This version recently had its first alpha release, but has been under development for the past ~6 months, so my hope is that it's out soon.
The reason Tilt integration works is because it doesn't require Bluetooth active scanning.
It’s possible, but what you are describing sounds like there is an issue with the OneWire sensors.
)
Do I have to find the logs in the file system running on the frementrack or is it accessible via the web interfaces?
I clipped the fridge sensor and no change, still not reading any temps. I will open the main controller today and check the sensor voltage, when I was building the unit it only worked on 1 sensor voltage setting. Is there a way to test the temp probe I cut off with a multimeter?It’s possible, but what you are describing sounds like there is an issue with the OneWire sensors.
Are you powering the sensors with 3v3 or 5V? If you are using my PCB this is the jumper. If you are currently using 3v3, I would try switching the jumper to 5V. Additionally, how long is the Ethernet cable you are using? Shorter cables are definitely the way to go, here!
As a second step, what I would do is try to desolder (or clip) the (former) fridge sensor from the data line (if that’s the one you think might be having issues) to see if having one fewer sensor helps. Room sensors aren’t necessary for the control algorithm to work, as long as the beer and fridge sensors work you should be OK.
Thinking about it, @day_trippr - would you recommend I add provisions for decoupling capacitors on the “sensor breakout” PCB for the power lines? Think that would help something like this? (I could add a footprint for the data line too, as a test to see if people can follow directions…
Thinking about it, @day_trippr - would you recommend I add provisions for decoupling capacitors on the “sensor breakout” PCB for the power lines? Think that would help something like this? (I could add a footprint for the data line too, as a test to see if people can follow directions…
What do the device logs say?
