I couldn't be happier
Now that you have a working kit, when you get a chance you need to figure out what was broken and let us know. Swap in a sensor, if that doesn't break it, put the original back and swap another sensor, etc...
Cheers!
I am on it
@day_trippr . I did ohm out the resister that should read 4.59-4.6K, new, but the one I pulled out was 4.45. This is not too far out of spec.
Can anyone tell me the best way to quickly mount the micro-tipped factory DS18B20 soldered wires ? I shaved a few of them and re-soldered a longer lead tip on them to help make it easier to insert into a terminal block. Is a breadboard a better option? It would take up too much room in a work box, when I finally clean up this mess! WAGO lever nuts are great, but the super short factory tips (DS18B20), are too short to get a quick reliable connection in the lever-nuts. The copper in the wires is soooo fine, that I found it is "best" to burn the plastic/rubber off the end and then use your finger nails to clean off the burnt poison, then resolder the tip. All my hvac line stripper tools are not suitable for this fine gauge wire.
A second problem I am having with the RPR and Fermentrack, is the Pi loosing contact with the running script (2-4 times/daily). My wifi is 4/5 bars, and I do have an extender that I can extend signal of my main router with. I see Raspbian OS often searching for a better connection, jumping onto the Extender, and sometimes picking the main router that is pretty far away with usually a decent 4/5 signal in my brewery. Thanks to the Beer Gods, that the "Arduino" UNO keeps the script and relays running without any problems, ever.
I can do a - sudo systemctl restart brewpi and then a refresh. But sometimes this will not bring the script and GUI back, so I have to do a reboot.
I did assign the one working Pi a static, non-changing IP address from my rounter home. Not totally understanding what part of this program keeps the script, GUI, running on the Pi, I am not sure what to do about this. Having usually 2 (now 3) Pi's running at the same time, could well be the problem. They all have a different IP address, but I suspect that when Raspian desktop keeps occasionally searching for a stronger connection, this could be the problem. Also, not sure how important each running Pi, must have a unique "name", other then the IP address? I try to make sure each time that I burn a new SD card, I give it a different login name.
Next up - 1) Find what may have been the cause of the mis-applied sinsors, 2) Get my controls in a nice neat Job box, 3) Take a stab at getting my SG toys to work from inside the unitanks (older Tilts with bluetooth, and the Rapt Pill with both wifi and bluetooth), 4) Take a stab at
@LBussy LCD build for bench testing, and his Brewbubbles, 5) Make enough Lagers, so I do not have to buy $42 cases of beer for camping, fishing, bicycling, season soon!