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

    Homebrewing Facebook Group

Keg Cop: Keg Monitoring and Control

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Sorry I wasn't clear, meant the white "molex" connector that gets soldered to the breakout board.
Ohh, got it. Yeah, it’s the correct connector.

Molex part number 51090-0300 is the plug end — the receptacle end I bought is EOL, however. Here is the EOL notification I received from DigiKey:


Part Affected
ManufacturerMOLEX, LLC
DescriptionCONN HEADER VERT 3POS 2MM
Manufacturer Part Number0533240360
Digi-Key Part NumberWM8313-ND
StatusObsolete
SubstitutesPlease click here

Please please double check the substitutes they recommend for both footprint and pitch. I bought the actual Molex part — the substitutes are other manufacturers.
 
Ohh, got it. Yeah, it’s the correct connector.

Molex part number 51090-0300 is the plug end — the receptacle end I bought is EOL, however. Here is the EOL notification I received from DigiKey:


Part Affected
ManufacturerMOLEX, LLC
DescriptionCONN HEADER VERT 3POS 2MM
Manufacturer Part Number0533240360
Digi-Key Part NumberWM8313-ND
StatusObsolete
SubstitutesPlease click here

Please please double check the substitutes they recommend for both footprint and pitch. I bought the actual Molex part — the substitutes are other manufacturers.

I bought the 440054-3 connector and it doesn't fit. Got it from AliExpress and bag it came in was marked correctly but who knows if it's really the correct one.

If the actual one is EOL then I guess all that can be done is to modify the one I got. It's too small but the sides can be cut out so the connection can be made.
 
Found the original Molex 0533240360 on Arrow. Says it's discontinued but they claim to have stock and let me order. Will update with outcome.
 
Update for you all: I'm still plugging away. I did a conversion to LittleFS (the filesystem that holds the config and web pages.) Maybe it will help things, maybe it will have no impact. Still looking for a couple more debug reports before I move in that direction.
 
Which breakout board? The six-way one which I designed is intended to use JST-XH connectors. I can't speak for the three-way board.

The three way board. Reading through everything saw this post:

Post in thread 'Keg Cop: Keg Monitoring and Control' Keg Cop: Keg Monitoring and Control

Wasn't clear to me whether the JST-XH connector would work or not. Originally I ordered one of the recommended Molex substitutes from China but it was too small.

I was able to order the original EOL Molex connector from Arrow and it's supposedly shipping so we'll see if it works.
 
An update for anyone interested.

The Molex 0533240360 I received from Arrow is the proper connector for attaching the Swissflo to the "dasilychain-molex" breakout board.

https://www.arrow.com/en/products/0533240360/molex
It is considered discontinued EOL and not available on Mouser or Digikey. Only 1700 left on Arrow so grab them quick🤣

I previously ordered the 440054-3, which is a recommended replacement from Digikey. This connector is too small and will not work without cutting the sides off.
 
Last edited:
I have a new version on LittleFS but I have not had any feedback on lost data. One more corroborating point would tell me if I am in the right area.
 
Sorry Lee, since updating to Alpha .9 around a week ago I've not lost any data and getting a 404 on the flowdebuglog.txt. No news is good news I guess?
 
Sorry Lee, since updating to Alpha .9 around a week ago I've not lost any data and getting a 404 on the flowdebuglog.txt. No news is good news I guess?
Interesting. Yes, 404 is good news.

So aside from the debug file, I moved saving that file to the main loop rather than in the interrupt processing. I was never clear if a function called by an ISR was in turn operating in an ISR interrupt.

So maybe it is the thing that was killing us? Wouldn't that be funny?

Anyway, I am still going to make a backup of the two files and reload them if they get garbaged. I am 50% there.
 
Beta Release - Keg Cop 1.3.0-Beta.1

Update with BrewFlasher.

I recommend this for any users with issues related to versions > 1.1.0.

This contains all bug fixes and feature updates:

New Features​

  • New filesystem handler (also linked from "About" page)
  • Added more complete support for KegScreen TV
  • Convert docs to MyST format
  • Convert from SPIFFS to LittleFS
  • Added Telnet and Log Level as configurable items

Potentially Breaking Changes (this is a stretch)​

  • Within the documentation, converted "URL Target" to "Generic REST" to reflect its use

Bugs Fixed​

  • Moved some non-reentrant code back to the timer loop to help avoid crashes (this is the biggie)
  • Created online backups of the config files to use as a failsafe (this is also significant to users who had crashes)
  • Updated to most current Arduino and ESP Libs
  • Fixed a bug upstream where an RPints target would only connect by name to "mule.local"
  • Volume precision bug where precision greater than 0.0001 gallons caused a failed save
  • Fixed a few bugs in the context documentation links
  • Fixed calibration error
A more complete listing can be found on the Release Page.

Other items like Home Assistant Support will be coming in an upcoming release.
 
Flashed 1.3.0B2 this morning, I'll see how it goes. I never did have the problem of loss of data on 1.1.1A7 (I think that's the last version I was using), but I also set up a daily cron job to download the config files in case the data did get lost.

Is this expected to have MQTT working?
 
Is this expected to have MQTT working?
Not yet. RPints version of MQTT was working but I seem to have broken it in that version. I know that because I just fixed it.

A reasonable approximation of MQTT is forthcoming, along the lines of Home Assistant auto-discovery.
 
Hi, loving this and starting a build. Any chance you could upload the step files for the 3d printed ones? I want to make a housing for the meter breakout one and is easier from the step.
 
I’m sure I have the original files, but I don’t know what a step file is. I model in AutoCAD only.

Send me DM and we can get you sorted out, I’m sure.
A step file is a common format that allows for 3d models to be exchanged between different CAD apps. So this allows for export and sharing of the model itself rather than the generated stl file uses as a base for 3d printing.

I'm sure autocad has a possibility to save the model as an STEP file.
 
I’ll take a look tomorrow when I’m at my desk. It’s possible, but I’ve never done it.
Amazing thanks, I use fusion 360 which gives you an option under export -> STEP. This gives the used the actual most rather than the mesh which makes it easier to modify and play with.
I’m just trying to modify the design for the sensor box you created to fit the flow sensor 3x board, I am thinking it might be easier to modify the PCB to fit in the same space actually now but is good to have options!

Thanks for your help :)
 
My version of AutoCAD does not export to STEP. (I would need AutoCAD Mechanical)

I can export to .IGS or .IGES. Does either of those help you?

If so, can you also give me the name of the .STL file you are interested in so that I can make sure I get the correct file.
 
Here is an update for some of you waiting for MQTT/Home Assistant:

1687525612098.png


I need to put it through its paces a bit, but it's close to a beta.
 
Release Candidate: 1.3.0-RC1

https://web.brewflasher.com/fw/135

Release notes:

The major changes since 1.2.0 are:
  • Fixed async instability with updated core libs (finally!)
  • Added Home Assistance support (thank you @mper!)
  • Added a new filesystem editor
  • Move to LittleFS for additional file stability
  • Allow configuration for traditional debug items
    • Turn telnet on and off
    • Turn logging levels up and down
  • Attempt to reconnect WiFi if it drops
  • And, of course, bugfixes.

What's Changed​

There are changes since the 1.2.0 release:

Feature Changes:​

Bug Fixes:​

Full Changelog: 1.2.0...1.3.0-RC1

This is not yet available as an online upgrade. You must use BrewFlasher to load this code. Be sure to back up your configuration first so you can restore it after.

I did say I was going to get the keg entry by weight done first - that ended up being some significant Java Scripting so I want to look at moving to Vue first (which will be 1.4.0+).
 
Last edited:
Feature Release: 1.3.0

1689791897527.png


https://web.brewflasher.com/fw/135

Release notes:

The major changes since 1.2.0 are:
  • Fixed async instability with updated core libs (finally!)
  • Added Home Assistance support (thank you @mper!)
  • Added a new filesystem editor
  • Move to LittleFS for additional file stability
  • Allow configuration for traditional debug items
    • Turn telnet on and off
    • Turn logging levels up and down
  • Attempt to reconnect WiFi if it drops
  • And, of course, bugfixes.

What's Changed​

There are changes since the 1.2.0 release:

Feature Changes:​

Bug Fixes:​

Full Changelog: 1.2.0...1.3.0

Updating:
  • You may do an online upgrade from version 1.1+ (it will not appear if you are on < 1.1). If you do an online upgrade all settings will be retained.
  • If you are on < 1.1, you must use BrewFlasher to load this code. Be sure to back up your configuration and restore it afterward if you use BrewFlasher.
I did say I was going to get the keg entry by weight done first - that ended up being some significant Java Scripting, so I want to look at moving to Vue first (which will be 1.4.0+).
 
Last edited:
I have a lot to learn about Home Assistant, but even so I have this set up with a few minutes' effort:
1690214666478.png


I'm wondering one thing, though: the entities for the volume remaining appear to be tied to the name of the beer--when I replace the Pale Ale with something else, I'm thinking that means its card won't work any more. Or will it?
 
Back
Top