I had two tilts all integrated and working last week. This weekend, I added the files for calibrating their Sg and temp readings. And when I brought the system back up, it says the Tilts cannot be found. If I use the Tilt app, I can see that they are working.
I’m fairly sure I made no other changes. Probably forgetting something simple.
Try;
Move calibration files out of their proper location to disable and restart the stack. Does everything work again?
If so, Then check your calibration files for hidden control characters, especially if you copy/pasted from the docs directly. Some browsers are fussy that way. also double-check your line endings… Linux vs windows… etc…
Barring that, can’t imagine what else would cause those files to break the service.
I’m having the same issue. My tilt was working just find but I had to mess with it and try and add the calibration files and now it not showing up. I removed the calibration files and restarted the stack, the pi and I even re-ran the setup on Brewblox. When I look at the logs for the tilt service it’s not complaining about anything and says the service is up. I’m in the middle of a brew so rebuilding the pi from the ground up will have to wait.But I feel like this should be fixable.
I reset hci0 and then forced the restart of the tilt service with no luck. I even removed the tilt service and then re-ran the install_tilt.py. Still nothing. I do a show services and it’s in there but not on the UI.
The UI picks it up as service once it publishes data.
To manually scan for devices, you could tinker with bluetoothctl:
sudo bluetoothctl
this changes the prompt. In there, use
scan on
I’m not entirely sure what the mac address of your tilt would be, but should be a decent test to see whether it can see anything.
You could turn on bluetooth on your phone to have a test device.
It’s not my phone. I’m using a vpn to hit my home network right now. So if my pi is seeing the tilt, why isn’t the service/readings showing up in the UI?
In older versions (brewpi) there was a script that you could run and it would list the output of the tilt messages in the terminal. If I remember correctly it was part of some “tilt tools” that used to come with the tilt package.