Brew Bubbles: Web-Enabled Airlock

[LBussy]

@wd16261 please try flashing the binaries in /firmware from the 'origin/fix_reboot' branch and see if that fixes your reboots?

ETA: I've not been anywhere near my testbench so I have not tested this. Please test accordingly. All I did was realize I failed to publish the compiled code from the last release and did so this time. In theory, this was all tested before I released but you never know.

 

[wd16261]

Yes this looks better! I even have the temperature readings...

I will try to test it a bit more tomorrow after work. Thanks again!

 

[wd16261]

It is still failing to post data to my BrewPi Remix! Is it because I'm using the multi chamber version?
When I'm using the link (http://192.168.123.55/left/brewpi-api.php) in my browser I get the message

So I think that the url is correct?

 

[LBussy]

Halfway there.

Let me look when I get home.

 

[LBussy]

EDIT: Deleted my questions, I reproduced the issue with that.

I opened Issue #47 in BrewPi WWW.

 

[LBussy]

Minor Update: When I released 1.0.1 I failed to update the project binaries. That's been fixed in master.

 

[LBussy]

It is still failing to post data to my BrewPi Remix! Is it because I'm using the multi chamber version?
When I'm using the link (http://192.168.123.55/left/brewpi-api.php) in my browser I get the message

EDIT: Deleted my questions, I reproduced the issue with that.

I opened Issue #47 in BrewPi WWW.

So, yeah, that's exactly what it was. When I wrote the API page for BPR I failed to remember the whole multi-chamber thing. I've fixed that and pushed to master. You'll have to update to the latest BPR as shown in the latest release notes in the Mega Thread. After that, the post should work and I think that resolves all your issues (pending testing with colored water.)

I've also updated the docs to indicate the potential need for a little food coloring in the water. Another possibility is StarSan in the water. It will make the water cloudy when added to most tap water and that might be enough.

 

[day_trippr]

Star San might (likely will) foam though...

Cheers!

 

[LBussy]

Star San might (likely will) foam though...

It definitely does - although I have used it in the distant past. It seems to be popular for this. Who knows? Just another potential solution for the "water that's too clear."

 

[wd16261]

I will try this later after work. I always use StarSan in my airlocks but if I can find some food coloring I will try this also.
i'll keep you posted.

 

[wd16261]

OK I did the update of my BPR with (sudo /home/brewpi/left/utils/doUpdate.sh)
The update asked me several times if I want to override the same version 0.5.40 and I answered yes.
Then I did sudo /home/brewpi/left/utils/doPerms.sh
And then I did a reboot.
But when I checked the brewbubbles it still wasn't able to send date to my BPR see logfile.

I also have the impression that none of the files under /var/www/html/left were updated!
Did I forgot something? The Mega Thread isn't a good reference to point to as it is getting to big to find anything in it.

Further I did also the test with the coloring water but this wasn't a success either!
The only color I had was blue and none (or a few) bubbles were detected :-(
Maybe when I receive the photo interrupters from Sparkfun I can try it with those but they should be the same.
Or I can try it again with a green color but then I need to buy that first in the shop.

 

[LBussy]

Look on line 24 of brewpi-api.php. It should look like this:

$url = 'http://' . $_SERVER['SERVER_NAME'] . dirname($_SERVER['PHP_SELF']) . '/newsocketmessage.php'; // Destination

If it does not:

1. Stop the script from the web page
2. Issue the command

   sudo git pull

   from the chamber's www directory
3. Validate the above line is correct
   
4. Issue the command

   sudo ./doPerms.sh

   from your chamber's brewpi/utils directory
5. Restart the script
6. Test

I'm typing this without access to my home system, but it seems right.

As far as the food coloring goes, I would have thought blue would be close enough to block the light. When it's just sitting static, is the blue LED on or off? Any difference in the bracket? It helps shade a lot of the outside light.

 

[wd16261]

I will check it this evening after work.

 

[wd16261]

Look on line 24 of brewpi-api.php. It should look like this:

$url = 'http://' . $_SERVER['SERVER_NAME'] . dirname($_SERVER['PHP_SELF']) . '/newsocketmessage.php'; // Destination

No it still is :
$url = 'http://localhost/newsocketmessage.php'; // Destination

If it does not:

1. Stop the script from the web page
2. Issue the command

   sudo git pull

   from the chamber's www directory
3. Validate the above line is correct
4. Issue the command

   sudo ./doPerms.sh

   from your chamber's brewpi/utils directory
5. Restart the script
6. Test

I'm typing this without access to my home system, but it seems right.

Done these steps:
pi@brewpi:/var/www/html/left $ sudo git pull
Updating b6b9621..aef7e0b
Fast-forward
brewpi-api.php | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

pi@brewpi:/home/brewpi/left/utils $ sudo ./doPerms.sh
***Script doPerms.sh starting.***
Fixing file permissions for /var/www/html/left.
Fixing file permissions for /home/brewpi/left.
Allowing BrewPi python access to Bluetooth interfaces.
Checking user accounts.
***Script doPerms.sh complete.***

Then after restarting the script I power up the brewbubbles and simulated a few bubbles with my pen, but still nothing on my BPR!
this is the log from the brewbubbles:
18:32:59.416 -> ⸮Q⸮ao 2020-02-19T17:32:59ZV: ॰ₒ๐°৹
18:32:59.816 -> 2020-02-19T17:33:00ZV: ॰ₒ๐°৹
18:33:00.296 -> 2020-02-19T17:33:00ZV: ॰ₒ๐°৹
18:33:00.656 -> 2020-02-19T17:33:01ZV: ॰ₒ๐°৹
18:33:01.616 -> 2020-02-19T17:33:02ZV: ॰ₒ๐°৹
18:33:01.936 -> 2020-02-19T17:33:02ZV: ॰ₒ๐°৹
18:33:02.256 -> 2020-02-19T17:33:02ZV: ॰ₒ๐°৹
18:33:02.616 -> 2020-02-19T17:33:03ZV: ॰ₒ๐°৹
18:33:02.896 -> 2020-02-19T17:33:03ZV: ॰ₒ๐°৹
18:33:03.186 -> 2020-02-19T17:33:03ZV: ॰ₒ๐°৹
18:33:03.536 -> 2020-02-19T17:33:04ZV: ॰ₒ๐°৹
18:33:03.816 -> 2020-02-19T17:33:04ZV: ॰ₒ๐°৹
18:33:19.062 -> 2020-02-19T17:33:19ZV: Time is 2020-02-19T17:33:19Z, BPM is 11.99.
18:33:19.062 -> 2020-02-19T17:33:19ZV: Averages: BPM = 11.99 (1 in sample), Ambient = 22.19 (1 in sample), Vessel = -100.00 (1 in sample).
18:33:19.096 -> 2020-02-19T17:33:19ZV: Triggered httpPost().
18:33:19.096 -> 2020-02-19T17:33:19ZN: Posting to: http://192.168.123.55/left/brewpi-api.php
18:33:19.096 -> 2020-02-19T17:33:19ZV: Resolved host 192.168.123.55 to IP 192.168.123.55
18:33:19.135 -> 2020-02-19T17:33:19ZV: Connecting to: 192.168.123.55, 80
18:33:29.374 -> 2020-02-19T17:33:29ZW: Connection failed, Host: 192.168.123.55, Port: 80 (Err: 0)
18:33:29.408 -> 2020-02-19T17:33:29ZE: Target post failed.
18:33:29.408 -> 2020-02-19T17:33:29ZV: Handle File Read: /
18:33:29.649 -> 2020-02-19T17:33:30ZV: Handle File Read: /mstile-144x144.png
18:33:29.961 -> 2020-02-19T17:33:30ZV: Handle File Read: /favicon.ico
18:33:30.133 -> 2020-02-19T17:33:30ZV: Handle File Read: /favicon.ico

Still connection failed. But I can ping from the BPR to the brewbubble fine so I don't think that is is network related.

As far as the food coloring goes, I would have thought blue would be close enough to block the light. When it's just sitting static, is the blue LED on or off? Any difference in the bracket? It helps shade a lot of the outside light.

The blue led is on and doesn't flash when a bubble passes.

 

[LBussy]

Please check /var/log/apache2/error.log. I cannot reproduce your problem so I need more information.

On the bubbles - until you get your physical configuration to where the blue light is out (sensor blocked) when at rest, it's not going to count bubbles. I didn't have any issues with that but everyone has a different setup.

 

[wd16261]

Lee Good new! The brewbubbles finally can send his information to my BPR.

18:12:51.930 -> ⸮!⸮qj⸮j%⸮2020-02-21T17:12:53ZV: ॰ₒ๐°৹
18:12:55.690 -> 2020-02-21T17:12:56ZV: ॰ₒ๐°৹
18:12:58.270 -> 2020-02-21T17:12:59ZV: ॰ₒ๐°৹
18:13:00.480 -> 2020-02-21T17:13:01ZV: ॰ₒ๐°৹
18:13:23.220 -> 2020-02-21T17:13:24ZV: Time is 2020-02-21T17:13:24Z, BPM is 4.00.
18:13:23.220 -> 2020-02-21T17:13:24ZV: Averages: BPM = 4.00 (1 in sample), Ambient = 21.00 (1 in sample), Vessel = -100.00 (1 in sample).
18:14:01.660 -> 2020-02-21T17:14:02ZV: ॰ₒ๐°৹
18:14:03.110 -> 2020-02-21T17:14:04ZV: ॰ₒ๐°৹
18:14:05.279 -> 2020-02-21T17:14:06ZV: ॰ₒ๐°৹
18:14:23.227 -> 2020-02-21T17:14:24ZV: Time is 2020-02-21T17:14:24Z, BPM is 3.00.
18:14:23.227 -> 2020-02-21T17:14:24ZV: Averages: BPM = 3.50 (2 in sample), Ambient = 21.03 (2 in sample), Vessel = -100.00 (2 in sample).
18:14:23.227 -> 2020-02-21T17:14:24ZV: Triggered httpPost().
18:14:23.227 -> 2020-02-21T17:14:24ZN: Posting to: http://192.168.0.187/left/brewpi-api.php
18:14:23.269 -> 2020-02-21T17:14:24ZV: Resolved host 192.168.0.187 to IP 192.168.0.187
18:14:23.269 -> 2020-02-21T17:14:24ZV: Connecting to: 192.168.0.187, 80
18:14:23.349 -> 2020-02-21T17:14:24ZN: Connected to: 192.168.0.187, 80
18:14:23.349 -> 2020-02-21T17:14:24ZV: Connected to endpoint.
18:14:23.349 -> 2020-02-21T17:14:24ZV: POST /left/brewpi-api.php HTTP/1.1
18:14:23.349 -> 2020-02-21T17:14:24ZV: Host: 192.168.0.187
18:14:23.389 -> 2020-02-21T17:14:24ZV: Connection: close
18:14:23.389 -> 2020-02-21T17:14:24ZV: Content-Length: 140
18:14:23.389 -> 2020-02-21T17:14:24ZV: Content-Type: application/json
18:14:23.389 -> 2020-02-21T17:14:24ZV: X-AIO-Key:
18:14:23.389 -> 2020-02-21T17:14:24ZV: End headers.
18:14:23.389 -> 2020-02-21T17:14:24ZV: Posting JSON to target.
18:14:23.509 -> 2020-02-21T17:14:24ZV: Status: HTTP/1.1 200 OK
18:14:23.509 -> 2020-02-21T17:14:24ZV: JSON posted.
18:14:23.549 -> 2020-02-21T17:14:24ZN: Target post ok.

I didn't change anything since the last modifications except I completely shutdown everything for a few days.

Now I only need to find a solution for the bubbles that are not counting.
I found some identical problems in an very old forum (more then 10 years ago) were they encountered the same problem and someone suggested to cover up the sensor so that outside light does not interfere. At this moment I don't know how but I think that I will find a way to do this.

PS: is there a way that the airlock information is also visible in the chart? or at least the bpm?

 

[LBussy]

Lee Good new! The brewbubbles finally can send his information to my BPR.

I didn't change anything since the last modifications except I completely shutdown everything for a few days.

It was looking like a local network thing - who knows though.

Now I only need to find a solution for the bubbles that are not counting.
I found some identical problems in an very old forum (more then 10 years ago) were they encountered the same problem and someone suggested to cover up the sensor so that outside light does not interfere. At this moment I don't know how but I think that I will find a way to do this

It seems like just dropping a paper bag over the top will help. The bracket model, printed in black, is what I used for testing.

PS: is there a way that the airlock information is also visible in the chart? or at least the bpm?

Not yet. To be honest, working with dychart seems to be something only a sacred few can do without messing it up. I am fairly certain a third legend (and then the bubbles) can be added in newer versions of dychart. I have started down the road of upgrading to a current version, but then something gets in the way (like an actual bug) so it gets shelved.

It's defintely on the list though!

 

[curtis.mckay]

I recently came across your project and had a couple questions. Does this also support the brewpiless version of brewpi? I noticed it supports Brewers Friend and was wondering if there is plans to support BrewFather? I have also testing the project iSpindel-TCP-Server and think it possibly maybe something worth integrating with because it would allow the data to be forwarded to multiple locations without you needing to support it.

https://github.com/DottoreTozzi/iSpindel-TCP-Server

 

[LBussy]

Does this also support the brewpiless version of brewpi?

It's the other way around really. I will send JSON to an endpoint, that endpoint needs to do something with it. I've not had a chat with pocketmon about it, but I'm open to the possibility of collaborating. When I Have Time™ I'll drop him a note. Only half making fun of this really. I'm willing to make a couple of changes to support it.

I noticed it supports Brewers Friend and was wondering if there is plans to support BrewFather?

Yes. You would not BELIEVE the issues I've been having lately, but it all culminates in me making some really major changes to the internals to make extending that portion of it more modular. I have a dev account on Brewfather and have been in contact with Thomas about it. There's a (maybe) small bug on his side, and a large one on mine. The next release of BB should have support for Brewfather.

I have also testing the project iSpindel-TCP-Server and think it possibly maybe something worth integrating with because it would allow the data to be forwarded to multiple locations without you needing to support it.

The issue with that is you'd need to host a web server with PHP and/or Python support somewhere in order to do it. Neither the iSpindel nor Brew Bubbles (nor Brewpiless for that matter) otherwise requires that, so it's a heavy lift for someone wanting "just this." If they have a handy server (or BrewPi Remix for instance) then it's not a big deal. The better move might be to use an endpoint which already will forward, like Brewer's Friend. Not sure if Brewfather does that or not.

 

[curtis.mckay]

Thanks for the response and the work you put into this. I can imagine how challenging it is to integrate with all this different solutions that’s why I suggested you take a quick look at the ispindel-tcp-server. It is not the ispindel but a forwarding engine that runs on raspberry pi. It already works with the ispindel and emanometer. The whole point of it is to take the information from the sensor and allow users to decide on the fly where it gets sent. It currently supports mqtt, brewpiless, brewfather, craftbeerpi and a bunch more. Thought it maybe a way of simplifying things but if it doesn’t then don’t worry about it. I have been looking at it to allow me to setup my ispindels once and redirect depending on what I’m brewing. This look like a great project and just waiting on parts to start testing it.

 

[LBussy]

Yes, I'm familiar with it. The point I am making is that it requires someone to run a web server where the products which you suggest can take advantage that do not need a web server. So, it's a heavy lift unless someone already has a web server handy. If a person has no automation but just has these passive tools, running a web server may be a step too far.

 

[ChrisThomas]

I've received all the bits and built my first BrewBubble! I can confirm it counts fingers, cutters and paper extremely well, going to start some wine off in the next few days and I'll report on findings.

One question I can't easily work out from the documentation is how to configure so that I can log to Fermentrack?

Chris

 

[LBussy]

I've received all the bits and built my first BrewBubble! I can confirm it counts fingers, cutters and paper extremely well, going to start some wine off in the next few days and I'll report on findings.

Please keep in mind that this is intended to be a relative counter, and that it should show trends but is not a scientific measurement. I did discover a workflow where some bubbles might not be counted under VERY high frequency. That's going to be fixed in the next version.

One question I can't easily work out from the documentation is how to configure so that I can log to Fermentrack?

You have to continue to bother @Thorrak to add that support. (Maybe add a note or a thumbs up on the issue.) It does work on BrewPi Remix, so ditch that blocky interface and come back into the BrewPi fold.

 

[Thorrak]

You have to continue to bother @Thorrak to add that support. (Maybe add a note or a thumbs up on the issue.) It does work on BrewPi Remix, so ditch that blocky interface and come back into the BrewPi fold.

Blocky?! No comment.

I've received all the bits and built my first BrewBubble! I can confirm it counts fingers, cutters and paper extremely well, going to start some wine off in the next few days and I'll report on findings.

One question I can't easily work out from the documentation is how to configure so that I can log to Fermentrack?

Chris

I have the code half-done, but need to finish it. Soon!

 

[ChrisThomas]

I'm getting some bubbles counted but not all, OK I know this is a known "issue" with Infra Red and water, but what have other people tried to make the water more opaque to the Infra Red? I've tried a couple of store cupboard colours/dyes but nothing so far provides any consisency.

So for example, what colour and kind of dilution of food colouring do people find successful. Other than food colouring anybody tried anything else and got good results?

Chris

 

[LBussy]

There's also a condition in the code that can cause bubbles at a higher frequency to be missed - that may help. That's in the release that is pending. I really hope to be releasing it this weekend.

In my testing, I used blue food coloring. That seemed to work the best. I was far from scientific, but it was dark. A couple of times I got so much in there that I stained the plastic. Use less than that.

I also use Star San and water in my airlocks. I have a decent amount of iron in my water and that tends to make it cloudy. Maybe that helps too?

ETA: I hope you guys are using a flat-black printed bracket and hopefully covering the airlock/fermenter? Outside light will definitely impact the accuracy.

 

[wd16261]

I'm getting some bubbles counted but not all, OK I know this is a known "issue" with Infra Red and water, but what have other people tried to make the water more opaque to the Infra Red? I've tried a couple of store cupboard colours/dyes but nothing so far provides any consisency.

So for example, what colour and kind of dilution of food colouring do people find successful. Other than food colouring anybody tried anything else and got good results?

Chris

Although I don't want to put anything else then pure water in my airlock I'm also curious to know what does work because it never counted bubbles properly in my cases but I only tried it with blue food colouring.

 

[matridium]

Release Announcement: v1.0.1 - Timers and Bracket

The biggest visible change for this release is to the bracket. @matridium was instrumental in getting me going on this whole project which is something I should have put in the first post. His questions in another thread inspired me to do the project to begin with, as well as providing a good deal of information related to work he did with a similar project in an academic setting. He designed the first bracket which was offered at launch. His creation sort of "backed in" to the object file. He created the first bracket in a machine shop, and subsequently put that into a 3D model.

Thanks to @matridium for the inspiration and hard work!

This change adds a few tweaks which @gromitdj was nice enough to do. The changes were all around the hole where the airlock stem passes:

• Enlarged the hole, the original would only allow a smaller stem
• Three different ways now to secure the bracket to the airlock
  • Added a small hole for an optional M3 set screw
  • Added a collar to secure a zip-tie around the bracket and stem
  • Added "ears" which allow for a rubber-band to wrap the device

Thanks Donnie!

All changes in this release:

• Save BPM on timed reboot - The controller reboots on a timer every 24 hours. Unfortunately, I can't count on the Espressif libraries to be stable enough over time, so rebooting is the easy solution (and it takes seconds). This change saves the Bubbles per Minute value to prevent weird dips in any charting.
  
• Remove a warning on compile due to unused variable
• Updated bracket model
• Update call on firmware and spiffs OTA to remove deprecation warning (on compile only)
  
• Move mDNS timer to mdns.cpp
• Update createFirmware.py to exit on missing file (a tool only I use)
• Bumped version to 1.0.1

Thanks @LBussy for the kind words. As with all these DIY projects I find the creative think of others is inspiring. Again this project could have not happen with out the motivation and expertise of @LBussy.

I have been very busy since mid January and now with Covid I’ve had some time hay home to get back to brewing. I hurt my arm bad back in November and I’m still trying to recover.. I’m doing much better but still not 100%. I’m actually going to get another test batch of beer up and going this weekend to test out brew bubbles.
My first bracket was made in my machine shop, and if anyone finds ways to make it better please do! Any way happy bubble counting!

 

[matridium]

Although I don't want to put anything else then pure water in my airlock I'm also curious to know what does work because it never counted bubbles properly in my cases but I only tried it with blue food colouring.

When we used counters in the lab we used red food coloring and the LED we used was 635nm (maybe 633nm). Yes we did have problems with multiple and also skip counting of bubbles or frequency of bubbles were extremely high. When I did initial testing with the design @LBussy and I started working on I used blue, green, and red food coloring they all worked about the same. Again I think this is more for tracking a trend and not so much a precise scientific way to count bubbles.

 

[LBussy]

Major Version Change - 2.0.0

This is a significant update, therefore incremented as a major version change. This upgrade breaks configuration, and because of an inadvertent bug introduced in 1.0.x, the OTA upgrade via the application page does not work to apply this upgrade. I recommend you use BrewFlasher to flash your controller - I have updated it for version 2.0.0.

Remember you will need to set up the controller configuration after the upgrade.

New Functionality

• Extended target support (easier additions of new targets later)
• Enable posting to Brewfather
• Improved web server performance
• Use Async Web Server
• Update docs for BrewFlasher
• Update from Espressif 8266 2.3.3 to 2.4.0
• Enhance bubble detection
• New settings page
• Align with new config structure
• Add new generic target and class handler
• New target lib
• Create new defaults

Moved to Private Libraries

Because I've been bitten not once, not twice, not three times, but FIVE times by upstream "enhancements," I have frozen the libraries I need here:

• Move to DS18B20 library
• Use lbussy version of OneWire to elim compile warning
• Move to async web server
• Moved to my DS18B20 lib
• Move more libs to personal projects
• Move to controlled repos

Bugfixes and Minor Changes

In case you are interested in the minutia, here are most of the additional changes:

• Convert target config to String
• Move configuration to declarations in *.h
• Bring in new config type
• Get rid of deprecation warning during compile
• Change to valid resolution
• Add reset after saving credentials
• Reorder include order
• Testing new post classes
• Debug the client connect
• Begin moving posts back to semaphore/loop
• Split out functions away from helper class
• Add push semaphore and response checking
• Cleanup and fix semaphores
• Move macros to constants
• URLTarget has unique needs
• Check key and use it to turn on/off push
• Check URL and trigger push from contents
• Enable BF push, add stubs for BRF
• Change to core NTP functions
• Fix common push logic
• Rename files
• Centralize JSON config sizing
• Rename to remove name conflict
• Merge in configuration changes
• Improve ntp sync
• Improve time synch blocking loop
• Reboot on enforced portal timeout
• Change timing of time hack
• Add async thatVersion lookup
• Move to serveStatic() for SPIFFS files
• Fix heap display (view /heap/)
• Add a little delay in loop to help response
• Fix image URL
• Skip processing on 0-length key
• Raise upload baud rate
• Reduce icon size
• Remove reboot and mDNS reset
• Move bubbles to struct
• Add NTP failure mode reboot
• Move interrupts externally
• Fix reset for NTP hack
• Cleanup wifi startup
• Add license to web pages
• Change NTP loops to 10
• Add version information
• Standardize page load
• Fix null sensors
• Return bool from update
• Allow clearing keys/urls
• Correctly determine posting status
• Remove '?' in querystring when posting
• Add reset handling
• Add delay before restart()
• Reset page now reloads gracefully
• Rename 'restart' to 'reset'
• Cleanup reset logic
• Address crashing on resets (#19)

I hope some of you get some use from this.