• Please visit and share your knowledge at our sister communities:
  • If you have not, please join our official Homebrewing Facebook Group!

    Homebrewing Facebook Group

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

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Nice work! I swear though - I need a version of the board with copper pours on both sides, just so the yellow soldermask doesn't look puke green. I realized last night I have a board in that color - it's the pour that saves it.



Awesome! Glad to hear it. I don't expect too many people to use the serial firmware, but there are some people (like yourself) for whom it's the right solution. More options are better in this case.

Seems like I would consider doing this since I loose the connection to the esp8266 once a day. Will not turn up - before I power recycle the unit.

Strange, I did switch the possible dodgy USB hub - and now use a raspberry pi powersupply.

The BrewPiLess has been running for 3 days now without loosing the connection (from the same USB hub)

Any clue why this is happening? If it where the wifi (which is strong regarding signals) it would effect the brewpiless who uses the same wifi - I presume.
 
Seems like I would consider doing this since I loose the connection to the esp8266 once a day. Will not turn up - before I power recycle the unit.

...

Any clue why this is happening?

Are you using mDNS (referring to the device as something.local) or the actual IP address of the device to connect?

If you're using the actual IP address, then yeah - that's really strange.

For mDNS, there was some work to try to enhance the strength of the wireless connection awhile back. I think that BrewPiLess and the ESP8266 firmware use the same basic code - aside from the mDNS bit.
 
Are you using mDNS (referring to the device as something.local) or the actual IP address of the device to connect?

If you're using the actual IP address, then yeah - that's really strange.

For mDNS, there was some work to try to enhance the strength of the wireless connection awhile back. I think that BrewPiLess and the ESP8266 firmware use the same basic code - aside from the mDNS bit.

In the fermtrack config, or when i connect to the fermentrack URL?
 
In the Fermentrack config for your controller.

I'd hope Fermentrack itself is staying connected/available - if that's the problem let me know because that's something entirely different.

Fermentrack is always availible. And this question became strange. I connect to my fermentrack troug hostname - and had a bit of a bad moment when I asked the question :off:

I`l update the wifi host field and see if that helps.
 
Fermentrack is always availible. And this question became strange. I connect to my fermentrack troug hostname - and had a bit of a bad moment when I asked the question :off:

I`l update the wifi host field and see if that helps.

Awesome - One last thing -- you probably have already, but if you haven't make sure that your controllers are running on the latest (v0.8) copy of the firmware. You can check this from the mdns screen of "guided setup". If you want to jump straight there, just go to:

http://raspberrypi.local/devices/guided/mdns/

...replacing raspberrypi.local with the name of your Fermentrack device. What you want to see is "Revision" set as v0.8.
 
Awesome - One last thing -- you probably have already, but if you haven't make sure that your controllers are running on the latest (v0.8) copy of the firmware. You can check this from the mdns screen of "guided setup". If you want to jump straight there, just go to:

http://raspberrypi.local/devices/guided/mdns/

...replacing raspberrypi.local with the name of your Fermentrack device. What you want to see is "Revision" set as v0.8.

Tried to switch to IP adress now. Did an update after I did this. Admin panel in django is broken in latest release.
 
Strange - I'll take a look. There's a requirement at the moment for Django-Suit v2.0 which is still in development -- I'm guessing something broke on that end.

KeyError at /admin/
'model'
Request Method: GET
Request URL: http://192.168.8.179/admin/
Django Version: 1.10.7
Exception Type: KeyError
Exception Value:
'model'
Exception Location: /home/fermentrack/venv/src/django-suit/suit/menu.py in make_child_from_native_model, line 172
Python Executable: /home/fermentrack/venv/bin/python2
Python Version: 2.7.9
Python Path:
['/home/fermentrack/venv/lib/python2.7/site-packages/git/ext/gitdb',
'/home/fermentrack/venv/bin',
'/home/fermentrack/venv/src/django-suit',
'/home/fermentrack/fermentrack/$(circus.env.HOME)/fermentrack',
'/home/fermentrack/venv/lib/python2.7/site-packages',
'/home/fermentrack/venv/lib/python2.7',
'/home/fermentrack/venv/lib/python2.7/plat-arm-linux-gnueabihf',
'/home/fermentrack/venv/lib/python2.7/lib-tk',
'/home/fermentrack/venv/lib/python2.7/lib-old',
'/home/fermentrack/venv/lib/python2.7/lib-dynload',
'/usr/lib/python2.7',
'/usr/lib/python2.7/plat-arm-linux-gnueabihf',
'/usr/lib/python2.7/lib-tk',
'/home/fermentrack/fermentrack/$(circus.env.HOME)/fermentrack',
'.',
'/home/fermentrack/venv/lib/python2.7/site-packages/gitdb/ext/smmap']
Server time: Mon, 10 Apr 2017 22:15:43 +0000
 
I'm having a problem with the brewpi script (and fermentrack).

I get the cannot receive LCD text from script/controller message

I have tried restarting the pi, the esp8266, even uninstalling and reinstalling fermentrack (did that method a few pages ago that kept the database).

What else can I check, I have this error in stderr log

Code:
Traceback (most recent call last):
  File "/home/fermentrack/fermentrack/brewpi-script/brewpi.py", line 997, in <module>
    util.save_beer_log_point(dbConfig, newRow)
  File "/home/fermentrack/fermentrack/brewpi-script/BrewPiUtil.py", line 163, in save_beer_log_point
    new_log_point = models.BeerLogPoint()
NameError: global name 'models' is not defined
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
  File "/usr/lib/python2.7/threading.py", line 763, in run
  File "/home/fermentrack/fermentrack/brewpi-script/backgroundserial.py", line 128, in __listenThread
<type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'sleep'

Thanks
Chris
 
Mine is still not possible to get into Django admin - and are still broken, even after the last update (11 april)
 
I'm having a problem with the brewpi script (and fermentrack).

I get the cannot receive LCD text from script/controller message

I have tried restarting the pi, the esp8266, even uninstalling and reinstalling fermentrack (did that method a few pages ago that kept the database).

What else can I check, I have this error in stderr log

...

So this is an interesting one. You're breaking on what is presumably a built in function for Python. Are you running this on a Raspberry Pi running a recent copy of Raspbian or another operating system?

Regardless - Try updating to the latest release of Fermentrack. There appears to be an issue with variable expansion in Circus which has been corrected and may be contributing to the issue you see.

Mine is still not possible to get into Django admin - and are still broken, even after the last update (11 april)

There's two bugs - One in Fermentrack, one (arguably) in Suit. I think a recent update to Suit caused the bug to finally pop up. I've corrected the bug in Fermentrack (and removed Suit entirely).
 
So this is an interesting one. You're breaking on what is presumably a built in function for Python. Are you running this on a Raspberry Pi running a recent copy of Raspbian or another operating system?

Regardless - Try updating to the latest release of Fermentrack. There appears to be an issue with variable expansion in Circus which has been corrected and may be contributing to the issue you see.



There's two bugs - One in Fermentrack, one (arguably) in Suit. I think a recent update to Suit caused the bug to finally pop up. I've corrected the bug in Fermentrack (and removed Suit entirely).

Django is up and running again now :) Thanks.
 
I'm stuck at this point. not sure how to add the esp8266 to my network. I can see it on the Advance IP Scanner program.

Before you go to the next step, you need to get the controller to a state where we can connect to it. If you are using WiFi finish the controller setup and connect it to your network
 
Not understanding how to marry the pi on wifi with the 8266. I can pull up my router and see both the 8266 and rpi on the "My Network" page
 
Not understanding how to marry the pi on wifi with the 8266. I can pull up my router and see both the 8266 and rpi on the "My Network" page

It sounds like you may be good, actually.

Do you have a telnet client? (For windows I suggest putty) If so, you can telnet to the IP address of the ESP and it should act like a BrewPi controller. To test it, type a single "v" and hit enter. It should give you some info.
 
It sounds like you may be good, actually.

Do you have a telnet client? (For windows I suggest putty) If so, you can telnet to the IP address of the ESP and it should act like a BrewPi controller. To test it, type a single "v" and hit enter. It should give you some info.
Network Error when I tried to connect with putty. I unplugged the 8266 to double check it's the correct one and it is
Connection Refused

putty.JPG
 
I can ping it on my router

You need to select the correct file from where you downloaded it with the "wheel" on the right side, left for the next to the 0x00000 number (it will allow you to select from a folder)
 
You need to select the correct file from where you downloaded it with the "wheel" on the right side, left for the next to the 0x00000 number (it will allow you to select from a folder)
What file do I need to flash to the 8266? I know how to load files into NODEMCU.
Seems like the Rpi and the esp8266 aren't talking to each other
 
So this is an interesting one. You're breaking on what is presumably a built in function for Python. Are you running this on a Raspberry Pi running a recent copy of Raspbian or another operating system?

Its Raspbian (jessie), was working great, then I tried changing a PID constant and it stopped working (dont think I did anything else).

Regardless - Try updating to the latest release of Fermentrack. There appears to be an issue with variable expansion in Circus which has been corrected and may be contributing to the issue you see.

Updating didn't fix it, I did an apt-get update and upgrade then a reboot of the pi, still no luck, tried reinstalling python, no luck. I reinstalled a fresh Raspbian image and am reinstalling fermentrack now
 
How do I refresh "installed devices". I'm trying to test my sensors.I had one working when the program first started.I keep hitting on the configure sensors/pins drop down under my device name. I tried f5 to reload the web page.
Edit Nevermind. I figured it out by playing around with the controls
 
Can you power off the RPI within Fermentrack?

Nope. The theoretical "ideal" model is that the Raspberry Pi and controller both are running 24/7, while you ferment batch after batch of delicious beer. Regardless, unfortunately shutting the raspberry pi down would require a sudo-ed root script that is callable from the internet, which I'm not comfortable with unfortunately. It would be easy to implement, however, if you wanted to dig into the code.


I reached out to the maker of the BrewPi Tilt integration a few weeks back, and he was incredibly forthcoming with information about his code & permission to integrate it into Fermentrack. I haven't had a chance to really delve into it yet, but I'm thinking with his generous offer it shouldn't be a hard one to build once I get time to focus on it.

Its Raspbian (jessie), was working great, then I tried changing a PID constant and it stopped working (dont think I did anything else).

Updating didn't fix it, I did an apt-get update and upgrade then a reboot of the pi, still no luck, tried reinstalling python, no luck. I reinstalled a fresh Raspbian image and am reinstalling fermentrack now

:(. I'll take a look and see if I can recreate on my end to help debug. That's a strange one. That said - I have one idea that I want to check, but I need to get remote debugging on my Raspberry Pi set up to test it.
 
Its Raspbian (jessie), was working great, then I tried changing a PID constant and it stopped working (dont think I did anything else).



Updating didn't fix it, I did an apt-get update and upgrade then a reboot of the pi, still no luck, tried reinstalling python, no luck. I reinstalled a fresh Raspbian image and am reinstalling fermentrack now

I did find one potential issue if there was an active beer being logged that is now fixed... Try updating and see if that fixes the issue.
 
esp9591654.local ESP8266 legacy 0.2.4 0.8 Set Up

This is my firware @Thorrak, This is now reflashed last night (has always been the same)
The two latest versions you have updated finds the esp devices.

I hit the "setup"

"Device Glassdoor Added. Please wait a few seconds for controller to start"

Then I get:
"Mode Off Beer --.- 20.0 °CFridge --.- 20.0 °CIdling for 2h57m32" (in LCD screen)

When I go to the Chamber and try to setup the availible devices, nothing happens when I "assign" them.

I`m totally lost in space - once again

NB! one thing I note, is this number increase when "admin/app/brewpidevice/9/change/" when you add or remove esp8266, is there a folder to "clean up" so it could start from scratch?
 
Reset eeprom - 3 times, finally solved the problem.
@ the moment I`m able to ping the host from my mack, my problem starts after some 12 hours isch, that`s when I have to power cycle the board.

I`l let it run for now, and see what happens since you have done som bug fixes.
 
Converting my last brewpiless chamber now.
Same problem, not able to save the settings when I try to Configure sensor/pins.

Flashing, first I did a Arduino upload (blink program) - then I flashed the wifi reset, then the 0.8 firmware. Once again the esp8266 just added it self to my network - which I still find kind of strange.

But anyhow, the devices responds to ping both trough mDNS name, and IP address. I found it in the wizard, hits setup - all ok that far. It`s when i try to configure pins - nothing saves.

2nd eeprom reset now, realy confused - I am :)

PS. It even says "Device definition saved for device 10" - but nothing shows up, and the sensor still remain in the list of avalible...
 
Thorrak your foray into brewpi tilt is very exciting. Can't wait until the option of changing temp based on gravity is available. [emoji106][emoji106][emoji106]
 
Nope. The theoretical "ideal" model is that the Raspberry Pi and controller both are running 24/7, while you ferment batch after batch of delicious beer. Regardless, unfortunately shutting the raspberry pi down would require a sudo-ed root script that is callable from the internet, which I'm not comfortable with unfortunately. It would be easy to implement, however, if you wanted to dig into the code.

What I'm thinking is maybe a batch or script file on a Windows PC that can be clicked to shut the BrewPi down, by automating the log-in and issue of the sudo shutdown -h now command.
 

Latest posts

Back
Top