Native ESP8266 BrewPi Firmware - WiFi BrewPi, no Arduino needed!

[alexlark]

Thanks for the updates Thorrak. It is a pleasure using Fermentrack :rockin:

I knew there was something else, before the official release you may want to remove those buttons below the chart (at the bottom of a few of the screens) they are the ones that are just duplicates, we talked about it a few pages back.

 

[Bigdaddyale]

Any plans for an RPI shut down button?

 

[Thorrak]

Any plans for an RPI shut down button?

Not at the moment. This could be done, but would require a 'sudo'-ed script (which my inner nerd cringes at the thought of from a security perspective). Is this something people would find useful?

 

[delux]

Hello. i want to say first that i love this program. I had a ink bird before this, and this just blows my mind, its so steady! But, here is my issue, i have now a beer who need step temperature profile. I have made a profile in ferm profile thats suits me well. I did this 2 days a go, and the profile goes like this. 19 degrees celcius for 4 days, and then i step it ut 0.4 degrees celcius everyday the next 10 days. Now i am on day 2, but when i look at my profile that i created, its just pushing the days for setpoint 1. It still says it 4 days before it will go over to setpoint 2. I have looked if i made a mistake and i dont run the profile i have created, but as far as what i can see, its on the right profile..

what am i doing wrong?

 

[Thorrak]

Hello. i want to say first that i love this program. I had a ink bird before this, and this just blows my mind, its so steady! But, here is my issue, i have now a beer who need step temperature profile. I have made a profile in ferm profile thats suits me well. I did this 2 days a go, and the profile goes like this. 19 degrees celcius for 4 days, and then i step it ut 0.4 degrees celcius everyday the next 10 days. Now i am on day 2, but when i look at my profile that i created, its just pushing the days for setpoint 1. It still says it 4 days before it will go over to setpoint 2. I have looked if i made a mistake and i dont run the profile i have created, but as far as what i can see, its on the right profile..

what am i doing wrong?

Everything is fine - and you don't need to worry. The profile screen for the profile you assigned shows you what would happen if you assigned the profile right that moment. Fermentrack keeps track of when you assigned the profile and will make sure that things progress as expected.

 

[alexlark]

Is this something people would find useful?

I thought I would use something like this initially but I wouldn't have any use for it now. When I was troubleshooting the WiFi connection issue I was rebooting using SSH. I actually use the fermentation fridge a lot more than what I thought. Currently summer here in South Wales, UK.

 

[gromitdj]

Forgive me if I am wrong, and perhaps @Thorrak can correct me if so. You could simplify you profile by putting in a set temp for 19°C on Day #1 and Day #5, then 23°C on Day #14 and it would ramp to 23°C over those 9 days. At least this is how it works in the original BrewPi code.

...I have made a profile in ferm profile thats suits me well. I did this 2 days a go, and the profile goes like this. 19 degrees celcius for 4 days, and then i step it ut 0.4 degrees celcius everyday the next 10 days. Now i am on day 2, but when i look at my profile that i created, its just pushing the days for setpoint 1...

 

[delux]

Forgive me if I am wrong, and perhaps @Thorrak can correct me if so. You could simplify you profile by putting in a set temp for 19°C on Day #1 and Day #5, then 23°C on Day #14 and it would ramp to 23°C over those 9 days. At least this is how it works in the original BrewPi code.

Well, it this is true, I will do this for sure. That way more easy.

 

[alexlark]

Yes you can do it that way in Fermentrack.

 

[delux]

TILT support in craftbeerpi. When does this comes to fermentrack? It would be awesome with tilt. Update on my last post, it worked like a charm, no worrys

 

[Thorrak]

TILT support in craftbeerpi. When does this comes to fermentrack? It would be awesome with tilt. Update on my last post, it worked like a charm, no worrys

Tilt support is one of the first features I plan to complete once the first official release of Fermentrack is done. I actually have a Tilt sitting on my desk that I haven't used yet as a result of missing this. Soon-ish!

 

[Thorrak]

Updates:

I just pushed a new build of Fermentrack out with the graph changes I've been talking about as well as some fixes for bugs found by @gezzanet. I'm still not 100% happy with the color choices, but hey - they're configurable in Constance (via the Django admin) so feel free to tweak the colors to your heart's content. If you find a color combination you like, ping me and I might just update the defaults!

Pretty much everything left before the first "official" release at this point is documentation. Getting close!

 

[gezzanet]

Saw the flurry of activity on GitHub so will upgrade tonight and see how it goes. Thanks Thorrak

 

[delux]

Saw the flurry of activity on GitHub so will upgrade tonight and see how it goes. Thanks Thorrak

sorry for my lak of skill in this, still pretty new in this. How do i get this update?

 

[Thorrak]

sorry for my lak of skill in this, still pretty new in this. How do i get this update?

Just wait - you'll get a message at the top of Fermentrack within 24 hours of the upgrade going live. Just click the upgrade button and everything should come through.

If you would prefer not to wait, you can also click the gear in the upper right and click the "upgrade from GitHub" button.

 

[alexlark]

Loving the update! Absolutely great. What you got planned for the buttons below the chart? Are you just scrapping them?

 

[gezzanet]

Up and running on new version, seems to be ticking over nicely. cooked a SD card earlier in the day so had to set up again but was very easy with the curl -L install.fermentrack.com | sudo bash command. works great.
buttons below the graph seem to work ok for me
thanks again

 

[alexlark]

buttons below the graph seem to work ok for me
thanks again

They work for me too but are mainly duplicate functions of the buttons on the panels above the chart.

 

[Thorrak]

They work for me too but are mainly duplicate functions of the buttons on the panels above the chart.

For now, I'm leaving them - mostly though to act as a visible line underneath the temperature graph. I haven't fully committed to the idea yet, but I'm thinking I might add a table underneath the graph that has an explanation of the beer profile that is applied to the controller and the date/time for upcoming set points. If I do that, I'll probably still keep the duplicate buttons so the temperature mode can be changed without scrolling up, but move them over to the side of the table.

I'm open to suggestion on this point though. I won't pretend that this idea is necessarily the best one!

 

[Bum Fudge]

I am running on a Wemos D1 Mini Pro. I just reinstalled everything from scratch for the 3rd time and still can't save my settings and get just one probe working. I have reset the EEPROM to factory defaults several times and I am connecting to the ESP8266 over Wifi. I just have a temp probe wired to the Wemos for now and trying to enable it for beer temp to test. I see the OneWire device and address (28FFC99863160381) and can select Assign and it seems to finish okay with a message "Device definition saved for device 1" but it does not show up as an "Installed Device"

Here is a partial excerpt from the stderr log.

What else can I try?

Jul 26 2017 13:03:51   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Jul 26 2017 13:04:53   Device updated to: {"i":0,"t":0,"c":63,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Jul 26 2017 13:04:53   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Jul 26 2017 13:04:53   Installed devices received: []
 Jul 26 2017 13:04:53   Controller debug message: ERROR 3: Device defifination update specification is invalid
 Jul 26 2017 13:04:53   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 72.16}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

 

[Thorrak]

I am running on a Wemos D1 Mini Pro. I just reinstalled everything from scratch for the 3rd time and still can't save my settings and get just one probe working. I have reset the EEPROM to factory defaults several times and I am connecting to the ESP8266 over Wifi. I just have a temp probe wired to the Wemos for now and trying to enable it for beer temp to test. I see the OneWire device and address (28FFC99863160381) and can select Assign and it seems to finish okay with a message "Device definition saved for device 1" but it does not show up as an "Installed Device"

Here is a partial excerpt from the stderr log.

What else can I try?

Jul 26 2017 13:03:51   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Jul 26 2017 13:04:53   Device updated to: {"i":0,"t":0,"c":63,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Jul 26 2017 13:04:53   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Jul 26 2017 13:04:53   Installed devices received: []
 Jul 26 2017 13:04:53   Controller debug message: ERROR 3: Device defifination update specification is invalid
 Jul 26 2017 13:04:53   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 72.16}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

My apologies - I missed this one! Not sure if you got this working, but let me dig into it and see what I can figure out. Are you using Fermentrack or brewpi-www?

 

[Thorrak]

Fermentrack Update

I just pushed an update to GitHub -- but this time the majority of the update should be transparent. The only visible change is the addition of a "Flash Controller" option directly to the device menu.

The majority of this update is to the Fermentrack documentation. Everything should now be updated - both in the markdown source as well as the mkdocs render.

There's still a few small things I want to look at, but I'm targeting the first "official" release of Fermentrack for some point within the next week. Progress!

 

[Bum Fudge]

My apologies - I missed this one! Not sure if you got this working, but let me dig into it and see what I can figure out. Are you using Fermentrack or brewpi-www?

No problem. I can appreciate how busy you have been with the update and I do appreciate all your hard work. I am running Fermentrack. I have the SMD Dupont LCD board but don't have it hooked up yet as I'm waiting for a few components. I just have a DS18B20 and resister hooked up to the Wemos GPIO Pins.

 

[alexlark]

Loving the customization of the chart colours, can't keep my hands off it!

 

[delux]

«Loving the customization of the chart colours, can't keep my hands off it!»

Where do I find this?

 

[alexlark]

Gear icon in the top right, then Django Admin Panel, Constance Config.

Look for the RGB colour codes on Google.

Tip: keep the chart open in a separate tab and refresh after each change to quickly see the changes.

 

[Thorrak]

«Loving the customization of the chart colours, can't keep my hands off it!»

Where do I find this?

Gear icon in the top right, then Django Admin Panel, Constance Config.

Look for the RGB colour codes on Google.

Tip: keep the chart open in a separate tab and refresh after each change to quickly see the changes.

If you guys find a color scheme you like, let me know.

I'm contemplating making it so that when you set up Fermentrack you can choose a "palette" from a preset list, with the option to customize if you go into the Django admin. Having different options for presets would be a nice touch!

 

[day_trippr]

Seems like folks could post screen shots here so others could steal schemes

 

[Thorrak]

Update:

I just merged a new pull request on GitHub -- but not one that really changes anything noticeable. There's now a sample placeholder profile showing what to paste on the Fermentation Profile screen, and the firmware flash routine now tells you when the firmware list was last pulled from Fermentrack.com in local time. Really thrilling stuff!

I am running on a Wemos D1 Mini Pro. I just reinstalled everything from scratch for the 3rd time and still can't save my settings and get just one probe working. I have reset the EEPROM to factory defaults several times and I am connecting to the ESP8266 over Wifi. I just have a temp probe wired to the Wemos for now and trying to enable it for beer temp to test. I see the OneWire device and address (28FFC99863160381) and can select Assign and it seems to finish okay with a message "Device definition saved for device 1" but it does not show up as an "Installed Device"

The one substantive change I did end up making was to help diagnose the issue you are describing. Previously, after an attempt to set up a pin/onewire device, you would see in the logs what the controller thought it heard to do, but not what you were attempting to tell it. Now you see both.

As an example, here is what this looks like now:

 Jul 31 2017 04:08:24   Received applyDevice request, updating to: {"a": "287B8F8A060000C9", "c": 1, "b": 0, "f": 5, "i": 0, "h": 2, "j": 0.0, "p": 12}
 Jul 31 2017 04:08:29   Device updated to: {"i":0,"t":1,"c":1,"b":0,"f":5,"h":2,"d":0,"p":12,"a":"287B8F8A060000C9","j": 0.000}

Previously, only the "Device updated to" line would be logged. Unfortunately, this probably won't solve your problem, but if you don't mind giving it another shot and pasting the newly enriched log back here I'd appreciate it!

 

[Bum Fudge]

Here is the latest log. Tx for looking..

Jul 31 2017 10:50:03   Successfully connected to controller.
 Jul 31 2017 10:50:03   Notification: Script started for beer ''
 Jul 31 2017 10:50:13   Checking software version on controller... 
 Jul 31 2017 10:50:13   Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.0.19:23

 Jul 31 2017 10:50:13   BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
 Jul 31 2017 10:50:13   Bound to TCP socket on port 2581, interface localhost 
 Jul 31 2017 10:50:14   Installed devices received: []
 Jul 31 2017 10:50:16   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 22.125}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]
 Jul 31 2017 10:50:16   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Jul 31 2017 10:52:49   Device updated to: {"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Jul 31 2017 10:52:49   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Jul 31 2017 10:52:49   Installed devices received: []
 Jul 31 2017 10:52:49   Controller debug message: ERROR 3: Device defifination update specification is invalid
 Jul 31 2017 10:52:49   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 71.486}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

 

[Thorrak]

Here is the latest log. Tx for looking..

Jul 31 2017 10:50:03   Successfully connected to controller.
 Jul 31 2017 10:50:03   Notification: Script started for beer ''
 Jul 31 2017 10:50:13   Checking software version on controller... 
 Jul 31 2017 10:50:13   Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.0.19:23

 Jul 31 2017 10:50:13   BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
 Jul 31 2017 10:50:13   Bound to TCP socket on port 2581, interface localhost 
 Jul 31 2017 10:50:14   Installed devices received: []
 Jul 31 2017 10:50:16   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 22.125}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]
 Jul 31 2017 10:50:16   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Jul 31 2017 10:52:49   Device updated to: {"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Jul 31 2017 10:52:49   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Jul 31 2017 10:52:49   Installed devices received: []
 Jul 31 2017 10:52:49   Controller debug message: ERROR 3: Device defifination update specification is invalid
 Jul 31 2017 10:52:49   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 71.486}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

Hmm. That looks like you're still running the old (pre-last-night) version. Can you click the gear icon in the upper right, click "Update from GitHub", and try again?

 

[Bum Fudge]

Sorry I clicked on Update but I needed to reboot the Pi apparently.

This is the latest Resetting the EEPROM and trying to add a Beer Temp probe.

Jul 31 2017 16:51:00   Resetting controller to factory defaults
 Jul 31 2017 16:51:05   Controller debug message: INFO MESSAGE 15: EEPROM initialized
 Jul 31 2017 16:51:05   Controller debug message: WARNING 3: EEPROM Settings not available. Starting in safe mode.
 Jul 31 2017 16:51:05   Installed devices received: []
 Jul 31 2017 16:51:05   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 24.563}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]
 Jul 31 2017 16:51:06   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Jul 31 2017 16:51:07   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMax = 90.0
 Jul 31 2017 16:51:07   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMin = 20.0
 Jul 31 2017 16:51:20   Received applyDevice request, updating to: {"a": "28FFC99863160381", "c": 1, "b": 1, "f": 9, "i": 0, "h": 2, "j": 0.0, "p": 12}
 Jul 31 2017 16:51:25   Device updated to: {"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Jul 31 2017 16:51:25   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Jul 31 2017 16:51:25   Installed devices received: []
 Jul 31 2017 16:51:25   Controller debug message: ERROR 3: Device definition update specification is invalid
 Jul 31 2017 16:51:25   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 76.211}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

 

[Thorrak]

...

Thanks for sending this across. I'll take a look tonight when I'm in front of a computer that has the firmware code on it.

At first glance, what you're requesting the firmware update to is: {"a": "28FFC99863160381", "c": 1, "b": 1, "f": 9, "i": 0, "h": 2, "j": 0.0, "p": 12}

What it's hearing though is this:
{"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}

The key thing here is "f": 9 vs. "f":-120 - and the fact that there is no "a" parameter. By comparison, here is the response from the device I got when I was playing last night:

{"i":0,"t":1,"c":1,"b":0,"f":5,"h":2,"d":0,"p":12,"a":"287B8F8A060000C9","j": 0.000}

...as you can see, f: is 5 (5 is chamber temp, 9 is beer temp if memory serves) and there is an "a" parameter which makes the firmware understand that you're sending it a device address.

The only other thing I would recommend in the mean time is reflashing your WeMos using the Fermentrack flasher. It's possible that something on the device is getting misinterpreted (or the firmware is a version that doesn't interpret things correctly).

 

[alexlark]

@Thorrak, can you take another look at the Device Logs page. My install is still showing the link URLs the wrong way around:

stderr.log takes me to
http://192.168.0.110/api/log/stdout/1/

and

stdout.log takes me to
http://192.168.0.110/api/log/stderr/1/

 

[Bum Fudge]

I reflashed from Fermentrack and also tried moving the OneWire from 3.3V to 5V but no luck yet. In a couple weeks when all my parts come in I'll solder up my board and try a different Temp Probe.

Aug 01 2017 19:58:29   Connection type WiFi selected.  Trying TCP serial (WiFi)
 Aug 01 2017 19:58:29   Connecting to BrewPi esp2691404.local (via 192.168.0.18) on port 23
 Aug 01 2017 19:58:36   Successfully connected to controller.
 Aug 01 2017 19:58:36   Notification: Script started for beer ''
 Aug 01 2017 19:58:46   Checking software version on controller... 
 Aug 01 2017 19:58:46   Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.0.18:23

 Aug 01 2017 19:58:46   BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
 Aug 01 2017 19:58:46   Bound to TCP socket on port 2070, interface localhost 
 Aug 01 2017 19:58:47   Installed devices received: []
 Aug 01 2017 19:58:48   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 26.188}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]
 Aug 01 2017 19:58:48   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Aug 01 2017 20:04:58   Received applyDevice request, updating to: {"a": "28FFC99863160381", "c": 1, "b": 1, "f": 9, "i": 0, "h": 2, "j": 0.0, "p": 12}
 Aug 01 2017 20:05:03   Device updated to: {"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Aug 01 2017 20:05:03   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Aug 01 2017 20:05:03   Installed devices received: []
 Aug 01 2017 20:05:03   Controller debug message: ERROR 3: Device definition update specification is invalid
 Aug 01 2017 20:05:03   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 79.586}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

 

[Bigdaddyale]

Did you run the sketch to check the probes?I had a few bad probes.

I reflashed from Fermentrack and also tried moving the OneWire from 3.3V to 5V but no luck yet. In a couple weeks when all my parts come in I'll solder up my board and try a different Temp Probe.

Aug 01 2017 19:58:29   Connection type WiFi selected.  Trying TCP serial (WiFi)
 Aug 01 2017 19:58:29   Connecting to BrewPi esp2691404.local (via 192.168.0.18) on port 23
 Aug 01 2017 19:58:36   Successfully connected to controller.
 Aug 01 2017 19:58:36   Notification: Script started for beer ''
 Aug 01 2017 19:58:46   Checking software version on controller... 
 Aug 01 2017 19:58:46   Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.0.18:23

 Aug 01 2017 19:58:46   BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
 Aug 01 2017 19:58:46   Bound to TCP socket on port 2070, interface localhost 
 Aug 01 2017 19:58:47   Installed devices received: []
 Aug 01 2017 19:58:48   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 26.188}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]
 Aug 01 2017 19:58:48   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 Aug 01 2017 20:04:58   Received applyDevice request, updating to: {"a": "28FFC99863160381", "c": 1, "b": 1, "f": 9, "i": 0, "h": 2, "j": 0.0, "p": 12}
 Aug 01 2017 20:05:03   Device updated to: {"i":0,"t":0,"c":39,"b":0,"f":-120,"h":1,"d":33,"p":-86,"x":41}
 Aug 01 2017 20:05:03   Controller debug message: ERROR 8: Cannot assign device type 0 to hardware 2
 Aug 01 2017 20:05:03   Installed devices received: []
 Aug 01 2017 20:05:03   Controller debug message: ERROR 3: Device definition update specification is invalid
 Aug 01 2017 20:05:03   Available devices received: [{"a": "28FFC99863160381", "c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 2, "j": 0.0, "p": 12, "t": 0, "v": 79.586}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 16, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 14, "t": 0, "x": 1}, {"c": 1, "b": 0, "d": 0, "f": 0, "i": -1, "h": 1, "p": 13, "t": 0, "x": 1}]

 

[Bigdaddyale]

https://www.homebrewtalk.com/showpost.php?p=7556259&postcount=5416

 

[Bum Fudge]

Yes it ran fine after I changed it from 18 to D6. (I also had run another temp monitor sketch before)

Parasite power is: OFF

Detected 1 devices
Device 0 is a DS18B20
Sensor 0 29.19

https://www.homebrewtalk.com/showpost.php?p=7556259&postcount=5416

tx

 

[HopRodGarage]

I'm trying to figure out how the API is working. Could someone give me some URL examples like how to:

- Set control mode for a device directly (off, beer constant, fridge constant..)
- Select a beer profile directly by name

 

[Thorrak]

I'm trying to figure out how the API is working. Could someone give me some URL examples like how to:

- Set control mode for a device directly (off, beer constant, fridge constant..)
- Select a beer profile directly by name

When you say API, are you talking about for the firmware/controller, or for Fermentrack?

If the firmware/controller, you'll need to read through the source for brewpi-script. It's not URL driven, unfortunately.

If you're talking about Fermentrack, there's not really an API for handling those functions at the moment, unfortunately. You could probably simulate it by hijacking the same methods that Fermentrack uses to speak with BrewPi script, but you'd have to dig through the various pages to see what exactly is going on.