In BPR the CSV exists. I am not sure if @Thorrak kept that, but you might search for it. The bash command would be:
Bash:find {search directory path} -type f -name "*.csv"
Degree 1: 0.9417258792131212 + 0.0021541829626664727 *tilt |
Degree 2: 0.9801680596241044 + 0.0004654507643561344 *tilt + 0.000016689703718827357 *tilt*tilt |
Degree 3: 0.8380399596467517 + 0.010036603508117178 *tilt-0.0001845658017782366 *tilt*tilt + 0.0000013361011382717298 *tilt*tilt*tilt |
I just installed Fermentrack on a VirtualBox VM. A few questions:
Thanks.
- Will Fermentrack start up automatically when I start the VM? Or do I need to run a command to get Fermentrack to automatically start up?
- I currently use a Pi 4 to run Fermentrack, but wanted to free the Pi up. I see there isn't a backup/restore utility. Is there any other easy way to get the current config on the Pi over to the VM instance?
- If the Pi 4 is currently powered up and running with a couple ESP8266 controllers configured to it, do I first need to shut that down before I can see those devices and get them configured on the new VM instance of Fermentrack?
- Are there any differences I should be aware of running Fermentrack inside a VirtualBox VM instead of a Pi?
Have you checked all your wiring connections?
I used these connectors to the boards so I could pull things apart if needed. I often find I need to go in and wiggle them and press them in. My problem seems to be the temp sensor connection as that is what gets lost.
See, this worries me because I am having the same issue with the ESP8266. I thought it was because I have network security software that strobes all ports on all hosts, but if you had this happen on the Uno it makes me wonder if it's something else.I've been running the latest docker version of fermentrack. I have an Uno connected to a pair of relays to control my fermentation chamber. It has now been three times I check in on the chamber and the controller has lost all its temp sensor and pin settings stopping any cooling. I have cleared the eeprom and reflashed the controller using the guided flash process. It will work for several weeks and then just randomly stop. Any ideas?
So I need a little help from the Fermentrack family and @Thorrak. I had a working version of Fermentrack installed mid-2021 on a Raspberry Pi 3 B+ using an Arduino Uno controller built for BrewPi Remix. All was working fine for ~4 months but in late November, it no longer could read the controller script. Gave up after five days of no response, so I decided to start clean and reinstall Pi OS and Fermentrack. I have tried four different version of the Pi OS (Debian Bullseye Desktop and Lite version and legacy Buster Desktop and Lite versions). Used both a VNC and ssh to connect to Pi. All are Docker installations that seem to install ok but they all come back with "** ERROR: Unable to find an initialized, responsive instance of Fermentrack". I've reformatted the SD card each time and have used two different cards. I guess I can try a different port other than 80 but have no idea of which one to use. Any other new users having any installation issues like this? I'm stumped. The install in July went so seamless!
So I need a little help from the Fermentrack family and @Thorrak. I had a working version of Fermentrack installed mid-2021 on a Raspberry Pi 3 B+ using an Arduino Uno controller built for BrewPi Remix. All was working fine for ~4 months but in late November, it no longer could read the controller script. Gave up after five days of no response, so I decided to start clean and reinstall Pi OS and Fermentrack. I have tried four different version of the Pi OS (Debian Bullseye Desktop and Lite version and legacy Buster Desktop and Lite versions). Used both a VNC and ssh to connect to Pi. All are Docker installations that seem to install ok but they all come back with "** ERROR: Unable to find an initialized, responsive instance of Fermentrack". I've reformatted the SD card each time and have used two different cards. I guess I can try a different port other than 80 but have no idea of which one to use. Any other new users having any installation issues like this? I'm stumped. The install in July went so seamless!
Yeah @Thorrak did post how the controller handles the late start up of WiFi but its still a problem. I'm think your smart plug suggestion might be the simplest way. I have my Rpi running Fermentrack connectivity so I can use the VNC link thru remot3 to access the local network and toggle a smart plug. Any recommendation on a plug or should I DIY it?I suspect it's a timing thing - the ESP's come online faster than the router so they never connect. You could try putting smart plugs on the power supplies and restart them that way.
Do you think I'd have the same problem of them coming back up after power failure faster than the modem/router and not reconnecting to wifi?I like the Kasa plugs. You can get them in 3 and 4-packs on Amazon and they are pretty affordable. I mean, unless you need another project?
I picked up a KP-125 Kasa mini smart plug and was able to connect it to Wifi using a guest account as I don't want to rely on the cloud for remote access. I'd prefer to just be able to use my Remot3 to VNC into my Rpi that is also running my Fermentrack and use a command line direct to the Kasa smart plug to cycle the power to my ESP8266 so that it connects back into WiFi and Fermentrack can pick it up again. @happyduke had a post involving controlling a kasa smart plug but again it involves the kasa cloud which I'd rather avoid.I have been unexpectedly testing my network here recently. I have not had a single issue with the connected devices coming back up after a power failure (including Keg Cop. )
If you want to get REALLY fancy, you can script actions after a failure with Home Assistant or something like that.
Different project, actually.I *think* he might be doing something since he was just asking me about my Asynch WiFiManager port. Or maybe he's working on KegScreen. Either of which would be fine.
Different project, actually.
The Kasa smart plugs can ABSOLUTELY be controlled without the use of the Kasa cloud. I don't have code handy at the moment, but I got a proof-of-concept working on an ESP32 about a year ago. I'm sure that a python script is out there somewhere.
...
Enter your email address to join: