Well if YOU don't know....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.
So BB is talking, but I'm not listening, or I'm listening to the wrong thing?2023-01-29T16:41:20Z V: Triggered URL Target push.
2023-01-29T16:41:20Z V: Host lookup: 192.168.20.197.
2023-01-29T16:41:20Z V: Resolved host 192.168.20.197 to IP 192.168.20.197.
2023-01-29T16:41:20Z N: Posting to: 192.168.20.197
2023-01-29T16:41:20Z V: Connecting to: 192.168.20.197 at 192.168.20.197 on port 80
2023-01-29T16:41:26Z W: Connection failed, Host: 192.168.20.197, Port: 80 (Err: 0)
2023-01-29T16:41:26Z E: URL Target post failed.
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: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?
That looks like whatever you have chosen as your target is not listening.When I telnet to BB I get the following at the timing specicied in the target frequency.
2023 and still no issues to fix!
... this is good, because newer versions of the libraries in Keg Kop have been giving me fits.
User HoldMyBeer has entered the chat :D
/kick HoldMyBeer
could make it stop working.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.
The path I set in BB for the URL Target is, http://IP:8123/api/webhook/brewbubbles2023-01-29T16:41:20Z V: Triggered URL Target push.
2023-01-29T16:41:20Z V: Host lookup: 192.168.20.197.
2023-01-29T16:41:20Z V: Resolved host 192.168.20.197 to IP 192.168.20.197.
2023-01-29T16:41:20Z N: Posting to: 192.168.20.197
2023-01-29T16:41:20Z V: Connecting to: 192.168.20.197 at 192.168.20.197 on port 80
2023-01-29T16:41:26Z W: Connection failed, Host: 192.168.20.197, Port: 80 (Err: 0)
2023-01-29T16:41:26Z E: URL Target post failed.
Yes.Have I at last appeared at the right tree to bark up?
Sorry! Ticket submitted.wait, let me go and check...
I was able to glean some more information about a "proper" MQTT push to HA. I'll make myself some notes and queue that up to the next effort here. I just need to actually find my Brew Bubbles board.@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)!
Well, that will all be on me. ESP32 is, in general, going to have different libs created for it depending on the ecosystem. When I am done I intend to add HAST as a feature.I can say is that the S2 mini, seems a little "odd". Not the double row of pins, but trying to get Arduino or ESPHome to talk nicely took a while to find the right post!
Well, I checked, and Brewfather removed the original API. Like, removed.Hello,
I'm a very occasional brewer that made a brewbubbles a few years ago. I'm doing a batch right now mainly to test using Brewfather (still in the 30 day premium trial). Brewbubbles is working well and I can see the data in Thingspeak, but not in Brewfather. After a few false starts, I think I have the settings in both correct, but Brewfather is still waiting for an initial logging. I did update Brewbubbles, now v2.2.3. Any idea what I'm doing wrong?
James
PATCH to https://api.brewfather.app/v1/batches/:id
PATCH to https://api.brewfather.app/v2/batches/:id
OK, thanks, no rush. I wanted to see if being able to see my brewbubbles and floaty hydrometer data in one place was worth the premium subscription cost, but I suspect it won't be.Well, I checked, and Brewfather removed the original API. Like, removed.
Old:PATCH to https://api.brewfather.app/v1/batches/:id
New:PATCH to https://api.brewfather.app/v2/batches/:id
Theoretically, I could change the URL, issue, and update, and let you test. I suspect, in practice, I will wish I had not looked. I can't say when I can look, and I know I do not have a Brewbubbles device with me, but I can give it a go and let you test it.
Logged as issue #60.
Yep, this is bigger than a breadbox, unfortunately. Not just Brewfather, but there are a lot of other lib changes that make me sad.OK, thanks, no rush. I wanted to see if being able to see my brewbubbles and floaty hydrometer data in one place was worth the premium subscription cost, but I suspect it won't be.
Looking at two different web pages or apps really isn't a big deal.
That's good to hear. I don't have a setup I can use here, so I was going the route of a simulator, and that was all sorts of messed up.For your information I did not change anything and for me it is still working fine in Brewfather (v. 2.10.5):
Enter your email address to join: