I’ve just added some more logging. If you run the following to update your system & bring the services back up.
brewblox-ctl update && brewblox-ctl up
Then I think you should be able to view the logs just for the Tilt service using:
docker logs brewblox_tilt_1 -f
You should now see the following if the bluetooth scanner is running and sees any devices at all:
Loop running & device found (may not be a Tilt)
And something like the following when it finds a Tilt:
Found Tilt: Black
If the loop is running and can see devices but can’t find a Tilt, then I think the problem is with the Tilt or with the Pi being able to see it. It might be worth trying the app on your phone near to where your raspberry pi is located and seeing if it can see your Tilt.
If the loop isn’t seeing anything at all (assuming there’s other bluetooth devices in the area running at higher power, i.e. not a low energy device) then that suggests a problem on my end. It could be I’ve installed something on my Raspberry Pi without releasing it and I need to figure out what that is and add it to the docs
If the service finds your Tilt but no data is getting through then I’ll have to talk to @Bob_Steers to try and figure out whats going on
Just to confirm what you should expect to happen when things work. When you create a Graph widget, you go into the settings menu, into Metrics, and you should see an entry at the top level alongside
spark-one etc called
tilt. Under this you’ll each colour of Tilt detected and the values logged from it.