Sorry for being so slow on this. Getting things working has taken a little tweaking and I haven’t had much time recently.
I’ve just pushed a new version that uses the bluez library for bluetooth. It seems more reliable. You should be able to update in the usual way. Worth noting there’s a bug in brewblox atm that makes first load of the web page very slow. So people might want to wait until that’s sorted in the next brewblox release.
EDIT: Also worth noting, you’ll likely see some errors about publishing data on start up of the service. This seems to be while another service comes up and settles down after a short while.
Tilt values are no longer being grabbed for either one of my Tilts (currently just in water in the fridge). It looks like it was around an hour after my post.
Odd. There’s nothing in there at all. Not even the default brewblox service info. Unfortunately, my tilt’s battery seems to have gone so I can’t test on my end atm.
Is there any specific testing you owuld like me to try? I am happy to test what I can. I have just put a beer in the chamber, so as long as I do not mess with the profile I can do whatever testing is required.
Gives similar output to last time, with repeated lines like:
2019/10/06 11:26:35 ERROR brewblox_tilt Error when publishing data AmqpClosedConnection()
2019/10/06 11:26:36 WARNING aioamqp.protocol only PLAIN login_method is supported, falling back to AMQPLAIN
2019/10/06 11:26:36 WARNING aioamqp.protocol only PLAIN login_method is supported, falling back to AMQPLAIN
2019/10/06 11:26:36 ERROR brewblox_tilt Error when publishing data AmqpClosedConnection()
2019/10/06 11:26:40 WARNING aioamqp.protocol only PLAIN login_method is supported, falling back to AMQPLAIN
Ah. Think your links are missing something. The first link (and the one you posted last time) only has a message for what the escape key combination is.
The kernal logs might be useful. Would indicate problems in the stack on the host rather than in the docker container, though. Which might be harder to fix. Given restarting the container fixes things, I might look into weather I can add some sort of heartbeat to the container.
The links in the comment about kern.log do work for me, can you recheck them please? The first is from the start of the log, the second is the tail (as the output exceeds termbin’s maximum size).
All looking good now. I’ll try and put some time to this soon. Like I say, think the best approach is going to be some kind of heartbeat/healthcheck on the container.
@jerryp if you run brewblox-ctl log, it will automatically include a full log dump for containers (not sys or kernel logs).
@j616s the service is likely already running with a restart: always flag. Feel free to raise a SystemExit to force a service restart.
Those amqp errors seem off - normally it only logs errors about failing to connect, and then a single warning about the fallback to plain. I’ll run other services tomorrow without muting repeated errors, see how that looks like.
Finally bottled my belgian. Been trying the exit approach but testing has been hampered by the battery life being zilch atm. Anyone else had issues with battery life on the old Tilts or is it probably just my stash of batteries not storing well?
@j616s I have found the older tilt batteries to be dire, In the past I had put a new battery in at the beginning of fermentation and have it not working by the end. Like you I was not sure if it was fake batteries on Ebay that was the problem.
Upgraded to V2 Tilit and that has had the same battery now for over 3 months.
I am trying to install the brewblox-tilt service. The instructions on Github are not completely clear to me. I am stuck at deploying the tilt docker image. In the instructions it only says to deploy with ‘rpi-latest for the arm architecture (when deploying on a RaspberryPi)’
Can anyone help me out?
tilt_installer.py is a script in the github repository. The simplest way to create and run it on your Pi is to run the following commands in the brewblox directory:
