Search results

Ah, well... my bad, copy/pasting the url from the app... fermentrack assumes it's on port 80 so it has URL http://url/tiltbridge. I'm however running on 8082 via proxy, so adjusting tiltbridge to include :8082 in the URL fixed me up. Thanks

AH, i'm on master... i did not pull dev. I switched over to dev and the postman API call directly to fermentrack works with floats now (73.0, etc). Tiltbridge still isn't updating, so I'll try to figure out what's going on there.

Side track... just got a tiltbridge to play with and it looks like the "pro" integration may have a bug. I sniffed out the payload and i'm getting "invalid literal for int() with base 10" error. If i change the payload from "73.0" to "73" for the temp then it post fine. { "mdns_id"...

Got MQTT working, my mistake for using "titlbridge/*" instead of "tiltbridge/#" for subscription. Worked on fermentrack second... the "73.0" vs "73" in payload was causing the issue. I'll go over to that thread and see if the fix is in since it just recently had an update to handle tilt pro...

disregard... I just tried running netcat listening and using URL from tiltbridge; it seems data is being sent out. I'll need to debug/check my MQTT broker, fermentrack, and brewpi-remix. Maybe the update for higher resolution temp readings is causing grief on the last two, not sure why mqtt...

Just getting into this ... using brewflasher i'm seeing 0.2.3 and a "alpha" 0.2.2. When i put 0.2.3 on i don't see any MQTT messages post or brewpi/fermtrack updates. Anyway to diagnose or t/s what the titlbridge is doing? I've tried posting directly to fermentrack/brewpi-remix API and get...

FYI for everyone else... I as well put a light greasing of keg lube thinking that would help. It did accomplish showing a leak faster (would leak at 5psi rather than 10psi). What fixed it for me was rotating the band clamp... i had it clocked such that the screw-latch ws at the 5:00 position...

Old reply.. but just FYI, at first my cf10 held pressure fine at 5 PSI but started leaking at 10 PSI. It took me a couple tries of re-seating the gasket and fidgeting with the band-clamp to get it to seal correctly. I loaded it up to 12 PSI and let it sit over 24 hours to verify no leak. 15m...

did exactly this... same issue with payments, even via bitcoin. So went looking and OSHPark ended up being the one I ordered from.

Just another thought.. since toggling ublock on my system "fixed" it then it's likely due to a caching issue. My browser likely remembered/cached part of that page from the previous non-css setup and mixed/mingled it. Try wiping/refreshing cache on any devices that are having weird headers.

I can't recall exactly.. I think I ended up with a B3-36A-20, can't recall if i got the '-20' or '-30'.. the length is what equalizes temps better though. You'd stack plates on if you're needing higher flow and less pressure drop. Pretty sure I got the '-20". I still have the stout chiller...

Found the issue... something with py3 and the changes to how ascii/encoding works and telnetlib. If I change the test_telnet() to specify "b" for ascii I get a Pass with the full reply. Otherwise the telnet.write() ends up tripping an exception and I get "None". I'm running this in a docker...

qq, what's the "Controller Response Test"? Everything seems to be working swimmingly but if I do a 'debug device connection' it fails at the Controller Response Test. I'm running the i2c arduino uno with an esp8266 bridging serial... so i'm curious if this test involves trying to reset the uno...

Hm.. disregard; i'm not sure what happened here but it's almost def a chrome issue. I toggled the ublock origin to see what happens if I block "spam", and it fixed it. I untoggled it and it's fine... i closed it all and reloaded, and it's fine now. Dbl checked the ver at the bottom and it's...

No errors.. couple "violations" if i expand to logging "verbose". CSS/JS is out of my depth so i'll paste what was logged in case it helps. dygraph-combined.js:3777 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive'...

And to confirm... looks fine in "microsoft edge", i'm using chrome which has mangled it somehow.

I may be having a personal problem... looking into it further. I do have a non-standard install kludged up into a docker container. So this may not be code issues... i'll confirm if i figure it out. But after trying the update script as well as a fresh rebuild I'm seeing crazy spacing on the...

That is perfect... exactly what I needed. Fritzing makes drawings look so nice... it's perfect.

No problem.. created Create API endpoints for posting manual gravity data · Issue #557 · thorrak/fermentrack just for an endpoint to do manual gravity readings. I'll take a look at the CSRF tokens, haven't had to do that in the past but there is a first time for everything.

Also.. some variations I took when building my box out that may help others. 1. A lot of people spend time trying to cut out receptacle style holes for mounting their 110v outlets. I instead chose to use bulkhead mounts. These are cheap, and somewhat water-proof... eg, i could spray a hose...