ChrisThomas
Well-Known Member
That's what I'm thinking, that is, ThingSpeak issue, but so far can't locate what it is. I'll keep reading...
Brew Bubbles: Web-Enabled Airlock
Help Support Homebrew Talk:
OP
OP
Well, I'm not saying "issue" but I think something changed.
Just a quick look - I don't see that the URL changed but there is a new TOU agreement. Have you logged in there lately? Maybe your account is flagged to accept that?
Just a quick look - I don't see that the URL changed but there is a new TOU agreement. Have you logged in there lately? Maybe your account is flagged to accept that?
Last edited:
ChrisThomas
Well-Known Member
Errrrmmm.... Cough... I wonder.... Didn't I tidy up that old router recently? Ah!
Some time ago (about a year) I repurposed an old router to provide better coverage in my brewing area. For simplicity I put this onto my existing network and put some port forward rules. My eventual aim was to "hide" my real network behing the IoT network. All worked well, but for reasons I can't explain the BrewBubble rule was no more! Low and behold it now works again!
Probably need to make that "temporary" test a more permanent installation, run that CAT5 cable and put my network behind my brewing network.
ARRRRGGGGG!
Some time ago (about a year) I repurposed an old router to provide better coverage in my brewing area. For simplicity I put this onto my existing network and put some port forward rules. My eventual aim was to "hide" my real network behing the IoT network. All worked well, but for reasons I can't explain the BrewBubble rule was no more! Low and behold it now works again!
Probably need to make that "temporary" test a more permanent installation, run that CAT5 cable and put my network behind my brewing network.
ARRRRGGGGG!
OP
OP
Hey, it happens - and that was a faster fix than me having to do something. My dev work is in disarray. 
ChrisThomas
Well-Known Member
Definitley NOT a BrewBubbles issue, an issue with the user... Definitely!
![Craft A Brew - Safale S-04 Dry Yeast - Fermentis - English Ale Dry Yeast - For English and American Ales and Hard Apple Ciders - Ingredients for Home Brewing - Beer Making Supplies - [1 Pack]](https://m.media-amazon.com/images/I/41fVGNh6JfL._SL500_.jpg)
OP
OP
That’s great!
I love hearing from you guys. I can see the action in GitHub, but if nothing is broken I often don’t hear anything else.
I love hearing from you guys. I can see the action in GitHub, but if nothing is broken I often don’t hear anything else.
OP
OP
Fun news:
Yes, Brew Bubbles is supported by BrewFlasher Web Edition!
ChrisThomas
Well-Known Member
Just thought I report that everything is still working. Still have to record data with Thingspeak rather than Fermentrack though
OP
OP
Working is boring, huh? I like boring.
OP
OP
2023 and still no issues to fix!
... this is good, because newer versions of the libraries in Keg Kop have been giving me fits.
... this is good, because newer versions of the libraries in Keg Kop have been giving me fits.
ChrisThomas
Well-Known Member
wait, let me go and check...
ChrisThomas
Well-Known Member
@LBussy I'm tinkering around with HomeAssistant and was thinking if I could log/use BrewBubbles. So where does the general HHTP POST from BrewBubbles come from? Is there an endpoint after the IP address, i.e. "http://IP_ADDRESS/ENDPOINT"? I've tried a few guesses but not yet been able to get HomeAssistant to actually hear anything, but that could also be me fumbling in the dark (again)!
Last edited:
OP
OP
Hell if I know! Lemme look ....
Are you talking about a "Generic HTTP Target?" That doc section shows you the payload, The target string is a full url like "http://hasst.local/brewbubbles/" (or whatever you want to call it.) It's set in "URL Target Settings." There's some additional information in that part of the doc.
(Incidentally, I found your name in the source code.)
If all that is taken care of, you might be able to see something in the serial log. There should be enough of a clue there to figure out what's going on.
Lemme look .... Are you talking about a "Generic HTTP Target?" That doc section shows you the payload, The target string is a full url like "http://hasst.local/brewbubbles/" (or whatever you want to call it.) It's set in "URL Target Settings." There's some additional information in that part of the doc.
(Incidentally, I found your name in the source code.)
If all that is taken care of, you might be able to see something in the serial log. There should be enough of a clue there to figure out what's going on.
ChrisThomas
Well-Known Member
Well if YOU don't know....Hell if I know!
Are you talking about a "Generic HTTP Target?" That doc section shows you the payload, The target string is a full url like "http://hasst.local/brewbubbles/" (or whatever you want to call it.) It's set in "URL Target Settings." There's some additional information in that part of the doc.
(Incidentally, I found your name in the source code.)
If all that is taken care of, you might be able to see something in the serial log. There should be enough of a clue there to figure out what's going on.
Yes, Generic HTTP target, but I could never find the full url of what BrewBubbles is supplying in the documentation. The information that HomeAssistant requires about the source of the POST is "http://IP_ADDRESS/ENDPOINT". I guessed several options (I think including .../brewbubbles...) but never got one to work. In BrewBubbles I think I just point to my HomeAssistant IP address, but I'm not sure if it requires anything else.
So far I've not found a combination of source and dstination that works, but I must stress I'm fumbling around with options that I'm not fully understanding!
ChrisThomas
Well-Known Member
Note to self, please see earlier note to self regarding "technical" activities AFTER alchol consumption.
OP
OP
Oh, you mean you want to PULL the information out of BB with HAST?
ChrisThomas
Well-Known Member
You'll have to excuse any terminology here, I haven't got to grips with it yet. My "task" is get information from BB into HA. So is this a POST from BB AND a GET from HA? Is this just a POST from BB, or just a GET from HA? At this point I'm unclear if HA requests the info from BB or if BB sends and HA is always listening.
More reading over a coffee or several
More reading over a coffee or several
OP
OP
Well my time with HAST ended when I moved full time into an RV ... but BB will POST to an endpoint, that means something in HAST has a RESTful API to allow that. The way HAST works most easily is to have dedicated integration or MQTT. Right now Brew Bubbles does not have MQTT but it could (I think.)
So your paths are "get Home Assistant to accept JSON POSTed by a device," add MQTT support to Brew Bubbles and send a pull request, or wait till I knock a couple projects off my list and can look at it.
One way that could work is to create an endpoint on your HAST host to receive the data and then turn around and send MQTT from there. You can look at this example in BrewPi Remix to see how to receive the POST from the device. You'd then need to code the rest to transform and send via MQTT.
So your paths are "get Home Assistant to accept JSON POSTed by a device," add MQTT support to Brew Bubbles and send a pull request, or wait till I knock a couple projects off my list and can look at it.
One way that could work is to create an endpoint on your HAST host to receive the data and then turn around and send MQTT from there. You can look at this example in BrewPi Remix to see how to receive the POST from the device. You'd then need to code the rest to transform and send via MQTT.
ChrisThomas
Well-Known Member
OP
OP
Believe it or not, I'd be in the same place. Since you guys have managed not to break Brew Bubbles, I've not been in the code for a loooong time.
ChrisThomas
Well-Known Member
So, after lots of anti-alcohol. Using RESTer on my laptop and doing a GET to the IP address of BB I get the HTML code. So I'm guessing I need to GET a different port or endpoint?
When I telnet to BB I get the following at the timing specicied in the target frequency.
When I telnet to BB I get the following at the timing specicied in the target frequency.
So BB is talking, but I'm not listening, or I'm listening to the wrong thing?
OP
OP
There is not currently an endpoint dedicated for any generic use. There is one used to supply information to the index page, however. Here's the JS in index,.htm that does the GET to Brew Bubbles:
https://github.com/lbussy/brew-bubb...350cc325c2d2a54d2020/data/index.htm#L168-L223
You can look at that and see the endpoint is /bubble/ so hit that and you will see the JSON returned. I will warn you that since this is not a "published" API, I reserve the right to change it at any time and not consider it a breaking change. Given how often I have had to make changes, you should be safe.
That looks like whatever you have chosen as your target is not listening.
ChrisThomas
Well-Known Member
OP
OP
/kick HoldMyBeer
hahaha!
ChrisThomas
Well-Known Member
So there is a small amount of illumination dawning. I can GET from HA to the BB endpoint /IP/bubble/ and I understand,
What I can't get working is the PUSH from BB to HA and am I right that the BB PUSH is always to port 80, as below?
The HA webhook set in HA is to the (default) HA port 8123 and the port is not separately configurable, in the above path I can only configure "brewbubbles".
Have I at last appeared at the right tree to bark up?
Additional: I can POST from RESTer to HA with the above path and sample BB data and it works fine.
could make it stop working.
What I can't get working is the PUSH from BB to HA and am I right that the BB PUSH is always to port 80, as below?
The path I set in BB for the URL Target is, http://IP:8123/api/webhook/brewbubbles
The HA webhook set in HA is to the (default) HA port 8123 and the port is not separately configurable, in the above path I can only configure "brewbubbles".
Have I at last appeared at the right tree to bark up?
Additional: I can POST from RESTer to HA with the above path and sample BB data and it works fine.
Last edited:
OP
OP
Yes.
It seems I might have to update the lib with which I do that work with the url and port. - the good news is that guy that owns the other lib is standing right here. The bad news is I might end up with other library issues caused by upstream stuff changing.
If you have a moment would you create an issue on GitHub so I don't forget this? I have some other stuff percolating these next days but I might be able to look at that later this week.
Similar threads
