Fermentrack: Fermentation monitoring & BrewPi-www Replacement for Raspberry Pi

Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum

Help Support Homebrew Talk:

Joined
Jan 19, 2013
Messages
3,760
Reaction score
1,591
Location
Rural Kansas
Any suggestion for a semi-techy person or brand new install. Having problems with the tilt connection too so might just start again.
Use the Raspberry Pi Disk Imager and start over again with a clean Raspbian OS image. When you run that, hit Shift - Ctrl - X and set the options you will need like hostname, enable SSH, change the password, configure WiFi, and set locale. That way when it comes up you are ready to install your solutions.
 

Worgz01

Member
Joined
Dec 29, 2021
Messages
8
Reaction score
3
Location
Eaton, Western Australia
The only issue I've had that might be related was an intermeittent connection on one of my temperature probes. I remade all the joints and not had an issue since. My symptoms were similar but was at home when it happened and when I wiggled my connectors, temperature readings returned.

Thanks Chris.

Oddly enough (touch wood), I have not had a repeat of the issue since initial find.

I'll check all connections and monitor. Cant be to careful ;)
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
Is there a (easy) way to remove some data (consecutive) points from an running log, or for the future to pause logging?

On a few occasions I've had to move or otherwise disturb my fermenter/temp probes and it's thrown in some spurious temperature or SG readings from my iSpindel. This throws out the autoscalling.

My brewing area is also the breadmaking and laundry area and as you might guess the brewing has "to give!"


Chris
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
I suppose I could turn off the router? It's a repurposed old router, nothing is connected through it, only brewing related. Last resort though, not sure how robust everything is to rediscoving the network???
 

RocketBrewer

Well-Known Member
Lifetime Supporter
Joined
Feb 26, 2012
Messages
565
Reaction score
198
Location
Garden Valley, CA
So everything was great until I tried to assign pins/sensors....
I was able to add my ESP8266 controller without much issues, but when trying to assign sensors/pins, It keeps failing to write configuration to controller. I have reset the eprom multiple times and restarted the controller too. It see's the sensors, but won't assign them. Same goes for the heat and cool relays. I'm running a fresh install of Fermentrack on a fresh Raspbian install on a Pi 3b+. For the controllers, I'm using the Thorrak board with no sensor breakout with the Lolin D1 Mini and LCD2004 I2C LCD Display. I believe the sensors are the correct DS18b20 sensors. I know there's a script that tests them, I bookmarked it, but can't figure out how to find my bookmarked posts. I ran the "debug device connection" and everything passed. I tried changing the one-wire jumper from 5 to 3.3v too, nothing seems to make any difference. Does anyone have any other suggestions???


Here's the stderr log:

Mar 14 2022 01:16:41 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:16:41 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:17:42 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:17:42 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:18:43 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:18:43 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:19:43 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:19:43 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:20:44 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:20:44 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:21:44 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:21:44 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:22:45 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:22:45 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:23:46 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:23:46 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:24:47 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:24:47 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:25:47 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:25:47 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:26:48 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:26:48 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:27:49 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:27:49 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:28:49 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:28:49 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:29:50 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:29:50 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:30:51 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:30:51 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:31:52 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:31:52 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:32:52 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:32:52 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:33:58 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:33:58 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:33:58 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:33:58 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:34:59 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:34:59 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:35:20 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 2, "p": 12, "j": null, "a": "28E26F07000000A1"}
Mar 14 2022 01:35:22 Device updated to: {"i":0,"t":0,"c":-26,"b":30,"f":72,"h":0,"d":0,"p":3}
Mar 14 2022 01:35:22 Controller debug message: ERROR 7: Invalid config for device owner type 2 beer=0 chamber=1
Mar 14 2022 01:35:22 Installed devices received: []
Mar 14 2022 01:35:22 Controller debug message: ERROR 3: Device definition update specification is invalid
Mar 14 2022 01:35:23 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:25 Installed devices received: []
Mar 14 2022 01:35:25 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:43 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 2, "h": 1, "p": 16, "x": "1"}
Mar 14 2022 01:35:45 Device updated to: {"i":0,"t":0,"c":-26,"b":30,"f":72,"h":0,"d":0,"p":3}
Mar 14 2022 01:35:45 Controller debug message: ERROR 7: Invalid config for device owner type 2 beer=0 chamber=1
Mar 14 2022 01:35:45 Installed devices received: []
Mar 14 2022 01:35:45 Controller debug message: ERROR 3: Device definition update specification is invalid
Mar 14 2022 01:35:46 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:48 Installed devices received: []
Mar 14 2022 01:35:49 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:59 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:35:59 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:37:00 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:37:00 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:38:00 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:38:00 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:39:01 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:39:01 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:40:02 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:40:02 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:41:02 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:41:02 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:42:03 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:42:03 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:43:03 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:43:03 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:44:05 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:44:05 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:45:06 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:45:06 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:46:06 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:46:06 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:47:07 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:47:07 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:48:08 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:48:08 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:49:08 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:49:08 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:50:09 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:50:09 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:51:09 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:51:09 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:52:10 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:52:10 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:53:11 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:53:11 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:54:11 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:54:11 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:55:12 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:55:12 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:56:13 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:56:13 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:57:14 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:57:14 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
So everything was great until I tried to assign pins/sensors....
I was able to add my ESP8266 controller without much issues, but when trying to assign sensors/pins, It keeps failing to write configuration to controller. I have reset the eprom multiple times and restarted the controller too. It see's the sensors, but won't assign them. Same goes for the heat and cool relays. I'm running a fresh install of Fermentrack on a fresh Raspbian install on a Pi 3b+. For the controllers, I'm using the Thorrak board with no sensor breakout with the Lolin D1 Mini and LCD2004 I2C LCD Display. I believe the sensors are the correct DS18b20 sensors. I know there's a script that tests them, I bookmarked it, but can't figure out how to find my bookmarked posts. I ran the "debug device connection" and everything passed. I tried changing the one-wire jumper from 5 to 3.3v too, nothing seems to make any difference. Does anyone have any other suggestions???


Here's the stderr log:

Mar 14 2022 01:16:41 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:16:41 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:17:42 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:17:42 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:18:43 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:18:43 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:19:43 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:19:43 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:20:44 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:20:44 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:21:44 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:21:44 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:22:45 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:22:45 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:23:46 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:23:46 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:24:47 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:24:47 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:25:47 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:25:47 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:26:48 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:26:48 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:27:49 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:27:49 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:28:49 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:28:49 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:29:50 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:29:50 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:30:51 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:30:51 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:31:52 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:31:52 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:32:52 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:32:52 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:33:58 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:33:58 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:33:58 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:33:58 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:34:59 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:34:59 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:35:20 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 2, "p": 12, "j": null, "a": "28E26F07000000A1"}
Mar 14 2022 01:35:22 Device updated to: {"i":0,"t":0,"c":-26,"b":30,"f":72,"h":0,"d":0,"p":3}
Mar 14 2022 01:35:22 Controller debug message: ERROR 7: Invalid config for device owner type 2 beer=0 chamber=1
Mar 14 2022 01:35:22 Installed devices received: []
Mar 14 2022 01:35:22 Controller debug message: ERROR 3: Device definition update specification is invalid
Mar 14 2022 01:35:23 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:25 Installed devices received: []
Mar 14 2022 01:35:25 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:43 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 2, "h": 1, "p": 16, "x": "1"}
Mar 14 2022 01:35:45 Device updated to: {"i":0,"t":0,"c":-26,"b":30,"f":72,"h":0,"d":0,"p":3}
Mar 14 2022 01:35:45 Controller debug message: ERROR 7: Invalid config for device owner type 2 beer=0 chamber=1
Mar 14 2022 01:35:45 Installed devices received: []
Mar 14 2022 01:35:45 Controller debug message: ERROR 3: Device definition update specification is invalid
Mar 14 2022 01:35:46 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:48 Installed devices received: []
Mar 14 2022 01:35:49 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.875, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.688, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 01:35:59 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:35:59 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:37:00 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:37:00 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:38:00 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:38:00 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:39:01 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:39:01 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:40:02 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:40:02 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:41:02 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:41:02 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:42:03 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:42:03 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:43:03 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:43:03 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:44:05 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:44:05 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:45:06 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:45:06 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:46:06 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:46:06 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:47:07 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:47:07 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:48:08 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:48:08 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:49:08 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:49:08 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:50:09 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:50:09 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:51:09 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:51:09 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:52:10 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:52:10 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:53:11 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:53:11 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:54:11 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:54:11 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:55:12 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:55:12 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:56:13 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:56:13 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}
Mar 14 2022 01:57:14 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 01:57:14 Line received was: S:{"mode":"�","beerSet": 48.00,"fridgeSet": 48.00,"heatEst": 0.000,"coolEst": 0.000}

Which version of the firmware are you using?
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
I had tried that before and it still doesn't help. I don't need to be connected to the ESP board right? wifi should work I assume

Nope, everything should be able to be done over WiFi.

To add some context -- when looking at the logs you posted, it's clear that SOMETHING funky is going on. There are two issues I see:

First, the recurring log messages you get about an invalid control character imply that something weird is being sent back and forth between brewpi-script and your controller. The log itself is pretty clear as to what the strange bit of text is -- there's a "�" character being sent back from the controller as the "mode." This should be a single, human-readable letter (o, b, p, f, etc.). As this text originates from the controller, this implies that there is something funky happening inside the controller's settings. Resetting the "eeprom" SHOULD fix this - but it is indicative of there being something corrupt loaded in the controller's memory.

The second issue is revealed in these two lines from your logs:
Mar 14 2022 01:35:20 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 2, "p": 12, "j": null, "a": "28E26F07000000A1"}
Mar 14 2022 01:35:22 Device updated to: {"i":0,"t":0,"c":-26,"b":30,"f":72,"h":0,"d":0,"p":3}

The first line is what brewpi-script is telling the controller to do (assign chamber 1, beer 0, function 5, pin 12, hardware type 2, to address 28E26...) -- the second line is what the controller thinks it heard (assign type 0, chamber -26, beer 30, function 72, etc...) Clearly, what the controller thinks it heard is different from what brewpi-script is sending -- and what it thinks it heard makes no sense.

The troubling bit here to me is the fact that your chamber is showing as -26 as I actually force the chamber to be 0 in the code. The fact that it reads as -26 implies - once again - that there is something happening in the controller's memory that is corrupting things.

My thought was that maybe the '"j": null' bit was causing issues as this is the "calibration" parameter -- but if you've tried sending 0.0 as the calibration, this can be ruled out, and we're back to issues with the controller's memory.

My recommendation is to try resetting the eeprom, waiting 2-3 mins, power cycling the controller, resetting the eeprom again, waiting 2-3 more minutes, power cycling the controller one more time, then finally trying to set the pin assignments.

Separately -- are you sure that you got a genuine Lolin D1 mini (direct from Lolin, and not from Amazon/another reseller)? There are a BUNCH of knockoffs out there, and substituting cheap flash is one of the ways that competitors keep costs down.
 

RocketBrewer

Well-Known Member
Lifetime Supporter
Joined
Feb 26, 2012
Messages
565
Reaction score
198
Location
Garden Valley, CA
Tried Removing the controller from Fermentrack, re-flashed the controller, set it up again, reset eprom, power cycled, tried to set pins again and it failed again.
Here's the err log:

Mar 14 2022 04:29:00 Refreshing dbConfig
Mar 14 2022 04:29:00 Connection type WiFi selected. Trying TCP serial (WiFi)
Mar 14 2022 04:29:06 Connecting to BrewPi esp14529427.local (via 192.168.1.33) on port 23
WARNING:zeroconf:Error reading from socket -1
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/zeroconf/__init__.py", line 1408, in handle_read
data, (addr, port, *_v6) = socket_.recvfrom(_MAX_MSG_ABSOLUTE)
OSError: [Errno 9] Bad file descriptor
Mar 14 2022 04:29:09 Successfully connected to controller.
Mar 14 2022 04:29:09 Notification: Script started, with no active beer being logged
Mar 14 2022 04:29:19 Checking software version on controller...
Mar 14 2022 04:29:19 Found BrewPi v0.2.4, running commit 00000000, running on an ESP8266 ESP8266 with a DIY shield on port 192.168.1.33:23

Mar 14 2022 04:29:19 BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
Mar 14 2022 04:29:19 Bound to TCP socket on port 2453, interface localhost
Mar 14 2022 04:29:20 Installed devices received: []
Mar 14 2022 04:29:23 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.563, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.375, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:29:23 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
Mar 14 2022 04:29:26 Resetting controller to factory defaults
Mar 14 2022 04:29:26 Refreshing dbConfig
Mar 14 2022 04:29:29 JSON decode error: Invalid control character at: line 1 column 10 (char 9)
Mar 14 2022 04:29:29 Line received was: S:{"mode":"","beerSet": 54.31,"fridgeSet": 80.00,"heatEst": 44.986,"coolEst": 32.064}
Mar 14 2022 04:29:29 Controller debug message: INFO MESSAGE 15: EEPROM initialized
Mar 14 2022 04:29:29 JSON decode error: Invalid control character at: line 1 column 16 (char 15)
Mar 14 2022 04:29:29 Line received was: C:{"tempFormat":"�","tempSetMin": 48.0,"tempSetMax": 48.0,"pidMax": 1.623,"Kp": 0.000,"Ki": 0.000,"Kd": 0.000,"iMaxErr": 0.000,"idleRangeH": 44.740,"idleRangeL": 32.064,"heatTargetH":-57.670,"heatTargetL": 31.996,"coolTargetH": 0.033,"coolTargetL": 0.000,"maxHeatTimeForEst":3232,"maxCoolTimeForEst":16383,"fridgeFastFilt":199,"fridgeSlowFilt":89,"fridgeSlopeFilt":33,"beerFastFilt":64,"beerSlowFilt":128,"beerSlopeFilt":15,"lah":255,"hs":63}
Mar 14 2022 04:29:29 Installed devices received: []
Mar 14 2022 04:29:33 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.563, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.875, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:30:53 Error: controller is not responding to new data requests. Exiting.
Mar 14 2022 04:31:02 Refreshing dbConfig
Mar 14 2022 04:31:02 Connection type WiFi selected. Trying TCP serial (WiFi)
Mar 14 2022 04:31:02 Connecting to BrewPi esp14529427.local (via 192.168.1.33) on port 23
Mar 14 2022 04:31:37 Unable to connect to BrewPi 192.168.1.33 on port 23. Exiting.
Mar 14 2022 04:31:42 Refreshing dbConfig
Mar 14 2022 04:31:42 Connection type WiFi selected. Trying TCP serial (WiFi)
Mar 14 2022 04:31:47 Connecting to BrewPi esp14529427.local (via 192.168.1.33) on port 23
Mar 14 2022 04:32:21 Unable to connect to BrewPi 192.168.1.33 on port 23. Exiting.
Mar 14 2022 04:32:27 Refreshing dbConfig
Mar 14 2022 04:32:27 Connection type WiFi selected. Trying TCP serial (WiFi)
Mar 14 2022 04:32:32 Connecting to BrewPi esp14529427.local (via 192.168.1.33) on port 23
Mar 14 2022 04:32:35 Successfully connected to controller.
Mar 14 2022 04:32:35 Notification: Script started, with no active beer being logged
Mar 14 2022 04:32:45 Checking software version on controller...
Mar 14 2022 04:32:45 Found BrewPi v0.2.4, running commit 00000000, running on an ESP8266 ESP8266 with a DIY shield on port 192.168.1.33:23

Mar 14 2022 04:32:45 BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
Mar 14 2022 04:32:45 Bound to TCP socket on port 2453, interface localhost
Mar 14 2022 04:32:46 Installed devices received: []
Mar 14 2022 04:32:48 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 16.563, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 17.313, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:32:48 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
Mar 14 2022 04:34:24 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 2, "p": 12, "j": 0.0, "a": "28E26F07000000A1"}
Mar 14 2022 04:34:26 Device updated to: {"i":0,"t":1,"c":1,"b":0,"f":5,"h":2,"d":0,"p":12,"a":"28E26F07000000A1","j": 0.000}
Mar 14 2022 04:34:26 Installed devices received: []
Mar 14 2022 04:34:30 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 61.924, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 63.949, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:34:35 Installed devices received: []
Mar 14 2022 04:34:35 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 61.924, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 64.174, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:34:57 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 1, "f": 9, "h": 2, "p": 12, "j": null, "a": "28FF6401BDDF0A5B"}
Mar 14 2022 04:35:00 Device updated to: {"i":0,"t":1,"c":1,"b":1,"f":9,"h":2,"d":33,"p":12,"a":"28FF6401BDDF0A5B","j": 0.000}
Mar 14 2022 04:35:00 Installed devices received: []
Mar 14 2022 04:35:03 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 62.035, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 64.174, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Mar 14 2022 04:35:03 Installed devices received: []
Mar 14 2022 04:35:07 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 61.924, "a": "28E26F07000000A1", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 2, "d": 0, "p": 12, "v": 64.285, "a": "28FF6401BDDF0A5B", "j": 0.0}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 16, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 14, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
Despite the fact that the device isn't saving, that log actually looks much better.

Looking at these lines:

Mar 14 2022 04:34:24 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 2, "p": 12, "j": 0.0, "a": "28E26F07000000A1"}
Mar 14 2022 04:34:26 Device updated to: {"i":0,"t":1,"c":1,"b":0,"f":5,"h":2,"d":0,"p":12,"a":"28E26F07000000A1","j": 0.000}

You have a valid index (0), chamber (1), beer (0), type (1, which is a temp sensor), function (5, which is Chamber Temp), calibration (0.0), and hardware type (2, which is OneWire Temp Sensor).

I see nothing invalid about that, so it should have saved. I sent you a PM with a potential alternate solution -- If you don't want to attempt that alternative, do you now see temperatures on your LCD screen?
 

tieflyer

Well-Known Member
Joined
May 13, 2010
Messages
334
Reaction score
31
Location
reading, pa
Ok, don't shoot me, but I haven't brewed in a while(boo, i know, shame on me!) but i am itchy to get back in, so started up my raspberry pi zero w today, and charged up my ispindel all in anticipation of brewing next saturday. So i went into my web browser and entered my ip address for fermentrack and it came back as not found. Tried it from my windows pc and from my pi. So my assumption is that fermentrack is not started on my pi. So, how do i find out if it is running, how do I restart it, and how do i set it to autostart after my pi finally boots up. I know my pi is underpowered, but I cannot find an affordable replacement for it as of yet.

any and all help will be greatly appreciated.
 

tieflyer

Well-Known Member
Joined
May 13, 2010
Messages
334
Reaction score
31
Location
reading, pa
Ok, don't shoot me, but I haven't brewed in a while(boo, i know, shame on me!) but i am itchy to get back in, so started up my raspberry pi zero w today, and charged up my ispindel all in anticipation of brewing next saturday. So i went into my web browser and entered my ip address for fermentrack and it came back as not found. Tried it from my windows pc and from my pi. So my assumption is that fermentrack is not started on my pi. So, how do i find out if it is running, how do I restart it, and how do i set it to autostart after my pi finally boots up. I know my pi is underpowered, but I cannot find an affordable replacement for it as of yet.

any and all help will be greatly appreciated.
ok, I am an idiot. I searched and finally found a thread that i created with this issue long ago......Sorry for bugging you.
fermentrack is not autostarting is the post is you need it.
 

tieflyer

Well-Known Member
Joined
May 13, 2010
Messages
334
Reaction score
31
Location
reading, pa
Ok, I'm back again. turned on my Ispindel and its blinking blue on occasion and the green light is on, but when I go into Fermentrack and setup new log to run, i don't get a correct reading, its saying 37.8f which I know my bedroom isn't at. How do I reset connection to it, so i can get correct readings when I brew?

Also, running it on pi zero w, and I just picked up a pi 3b so I backed up my sd card and put it in the pi 3b. Should I upgrade/install using docker? If so, 32 or 64 bit os on pi, and how do i get my old brews from pi zero over to new install?
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
Ok, I'm back again. turned on my Ispindel and its blinking blue on occasion and the green light is on, but when I go into Fermentrack and setup new log to run, i don't get a correct reading, its saying 37.8f which I know my bedroom isn't at. How do I reset connection to it, so i can get correct readings when I brew?

I can't help you with the iSpindel, unfortunately -- Fermentrack just takes what the iSpindel reports, so you'll need to check the iSpindel's configuration to see what is going on.

Also, running it on pi zero w, and I just picked up a pi 3b so I backed up my sd card and put it in the pi 3b. Should I upgrade/install using docker?

Yes, if you're setting up a new Fermentrack install, you should absolutely upgrade/install using Docker. Either 32 or 64 bit is OK -- I compile images for both.
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
Hey all,

I've got a number of pretty big announcements coming (hopefully) later this week for both Fermentrack and BrewPi-ESP8266, but I wanted to preview two of the changes to Fermentrack specifically as I don't want anyone hitting the big "upgrade" button and then wondering what happened --

Fermentrack is converting from using Circus to using a combination of Supervisord and a custom brewpi-script process manager. Although Circus was instrumental in Fermentrack's initial release working for multiple chambers, it also has unfortunately been the culprit behind virtually all of the issues I've experienced when releasing Fermentrack updates. Between the missing version locks, reliance on ZMQ libraries that disappeared from apt, and issues with incompatible pyZMQ updates, using Circus has proven to be incredibly frustrating. More troubling, however, is the fact that there was a long stretch where Circus refused to work out-of-the-box, and the Circus team refused to merge any PRs that would have fixed it due to their CI being broken. With that in mind, it's time to bid Circus a grateful, but long overdue farewell and move on.

Unfortunately, converting from Circus to Supervisord means that the updated code will not work for non-Docker installations of Fermentrack. If your non-Docker installation of Fermentrack is working as you want it, then there is no reason to worry about this - just ignore the upgrade message as you see fit. New installations, however, should use the Docker version.

Users that currently have the Docker version of Fermentrack will be fine, but will need to update their Docker containers using the script in their (existing) fermentrack-tools folder. If you deleted your fermentrack-tools folder after installation, post here, and we can try to figure out a solution.

In order to ease the transition between legacy and updated versions of Fermentrack I have added backup and restore functionality via the command line. This functionality backs up your database and your beer logs to a tar.xz archive which can then be saved elsewhere or "restored" to a new installation of Fermentrack. Using this functionality will require some comfort with the command line and some means to transfer the tar.xz archive to the new installation. I am still trying to see if I can backport this functionality to a "non-docker friendly" version of Fermentrack -- but for those who upgrade without reading this note and break their non-docker installs, this should hopefully provide some comfort.

I'm extremely excited about the changes that are coming, and look forward to seeing how people put them to use!
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
Oooh, I was just thinking of "upgrading" my install from Pi V 1.2 to Pi V 3a. I think I'll wait... Now if it only logged BrewBubbles it would be perfect :ghostly:
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
Those the Raspberry Pi's that I currently have. I've repurposed my V3 to something that I hope will be more usefull, that is, to making more wine. On the other hand I've had to sanity check this SO MANY times (UK time) perhaps I should stop making homebrew :no:
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
Those the Raspberry Pi's that I currently have. I've repurposed my V3 to something that I hope will be more usefull, that is, to making more wine. On the other hand I've had to sanity check this SO MANY times (UK time) perhaps I should stop making homebrew :no:

Ahhhh, got it. Yeah - the latest versions of Fermentrack run better on the Pi 3, 4, and 400. They do not run at all on the Pi 1, Zero, and Zero W. I need to test it on a Zero W 2, but if I had a choice I’d avoid that one as well.

NEVER try to make sensible posts AFTER the second bottle of wine :no: No matter how good your handiwork is!
I disagree with this statement, as it would result in fewer posts!
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
I need to test it on a Zero W 2, but if I had a choice I’d avoid that one as well.
Out of curiousity I tried it, the install didn't complete. As I didn't really expect it to work I didn't pay attention to what the error(s) were. Happy to give it another go if it would be a worthwhile exercise?
 

tieflyer

Well-Known Member
Joined
May 13, 2010
Messages
334
Reaction score
31
Location
reading, pa
Well, i used docker version of fermentrack to install it for the first time on a pi 3b. I configured my iSpindel, and then i inputted the calibration points and got this " The "numpy" python package is not available which is required for calibration "
so how do i fix this?
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
Well, i used docker version of fermentrack to install it for the first time on a pi 3b. I configured my iSpindel, and then i inputted the calibration points and got this " The "numpy" python package is not available which is required for calibration "
so how do i fix this?

There's an open issue against this on GitHub with a solution in that thread.

The fix has been added to the script I use to build Docker images, but I haven't built an image since the fix went in. I'm targeting a release imminently, so if you would rather not follow the instructions in that GH issue you can wait a few days and update using the update-docker script in your fermentrack-tools directory.
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
I’ve posted an update to Fermentrack on the dev branch which I think is getting close to the last set of dockerless-compatible code I’m going to release. This code adds backup and restore functionality, including from within the Fermentrack interface.

I was planning on doing a bigger Fermentrack release tomorrow to coincide with April Fool’s Day, but ended up agreeing to go out of town last minute, and don’t want to release it and then abandon it when someone discovers the inevitable breaking issue. Instead, I’ll try to get a release out there early next week.
 
OP
OP
T

Thorrak

Supporting Member
HBT Supporter
Joined
Feb 7, 2016
Messages
3,160
Reaction score
2,081
Location
New York, NY
I just merged the Fermentrack update that was on the dev branch into master. The full changelog is here, but the two main changes are the addition of backup & restore functionality and adjustments to the various warnings for "dockerless" installations.

Of note - this is the last release that is explicitly intended to be compatible with non-containerized installations. If you are still using a non-containerized installation I recommend downloading your data using the backup functionality and - if possible - restoring to a containerized installation prior to decommissioning your non-containerized install.
 

ChrisThomas

Well-Known Member
Joined
Aug 11, 2019
Messages
175
Reaction score
43
Location
Bristol, UK
@Thorrak Ermmm, I just did the update from within Fermentrack and it's not come back up. I can connect to the Pi (VNC) and look at the install.log and I see no errors reported, I'm assuming that's where I should look? The only issue I can see is the IP address reported at the end of the log file, it's the original address where Fermentrack was originally built, 192.168.1.13 but I moved it onto a different router 192.168.2.13 some months/year back and I'm sure I've done more than one Fermentrack update since then.

Address reported on Pi and router are all 192.168.2.13. Pi is connected wirelessly. I'm assuming this is an issue with my configuration somehow, but I've no idea! So confused.

With my limited knowledge, with my laptop on the same router, I can ping ...13 and I can ping fermentrack.local. Both work but the .local drops packets sometimes. I get the same timeout/nginx from the Pi and my laptop.

Not sure if this log file is from the upgrade or original install.
 

Attachments

  • install.txt
    20.9 KB · Views: 3
Top