BrewBlox Tilt Service

j616s · June 18, 2019, 6:30am

That is definitely the Tilt.

If you ssh into the raspberry pi I think you can run bluetooth ctl to get a console for interacting with the bluetooth stack. You should then be able to run power on and scan on to start scanning and it should start outputting information. If the stack has crashed, you can sometimes run power off and then power on and scan on again to kick it back into action.

scouseboy99 · June 18, 2019, 6:56am

Thanks for the quick response. I will try that later. To try from my workplace would lead to a whole heap of pain but will give it a quick go before the internet get congested.

I have had some success, managed to ssh in and get the following info:

[bluetooth]# scan on
[NEW] Device 00:0D:44:DF:36:5C 00-0D-44-DF-36-5C
[NEW] Device E0:09:D3:FF:73:36 Tacx Vortex 23917
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[bluetooth]# scan off
Failed to stop discovery: org.bluez.Error.InProgress
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device E0:09:D3:FF:73:36 UUIDs: 00001818-0000-1000-8000-00805f9b34fb
[CHG] Device E0:09:D3:FF:73:36 UUIDs: 00001816-0000-1000-8000-00805f9b34fb
[CHG] Device E0:09:D3:FF:73:36 UUIDs: 669aa305-0c08-969e-e211-86ad5062675f
[CHG] Device E0:09:D3:FF:73:36 UUIDs: 6e40fec1-b5a3-f393-e0a9-e50e24dcca9e
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[bluetooth]#
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[bluetooth]# scan off
Failed to stop discovery: org.bluez.Error.InProgress
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12 6.
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Key: 0x0003
[CHG] Device 00:0D:44:DF:36:5C ManufacturerData Value:
00 05 30 00 00 06 94 65 2d 6f 42 c4 00 0d 44 df …0…e-oB…D.
36 5c 12

Hope that this is the information you are expecting to see

Regards

j616s · June 18, 2019, 7:00am

That’s interesting. None of those devices seem to match up with the ones found by the ibeacon app. I’m presuming the ID at the top of each entry in the ibeacon app is the device ID…

scouseboy99 · June 18, 2019, 7:07am

I am not sure, but I am inclined to agree with you. I would have thought that i would see that same MAC address appearing in the Beacon app and the data from the capture. Leave it with me and I will have another look when I get home later on and closer to the equipment.

Thanks for the assistance so far

Cheers

j616s · June 18, 2019, 7:08am

No problem. Just frustrating there’s only so much I can do remotely.

scouseboy99 · June 18, 2019, 7:10am

Far as I am concerned you are being a great help. Also I have just noticed that my smart trainer for my bike, the “Tacx Vortex” is showing up. I did not think that it was turned on. That my be swamping the signal from the Tilt. Will investigate later.

scouseboy99 · June 19, 2019, 9:11am

OK. After a couple of hours last evening, I have come to the conclusion that my best option is to rebuild the raspberry pi which is running brewblox. I built another Pi and placed it in the same location and ran the HCItool. This picked up the MAC of the tilt. Starting from base one will be the best option.

j616s · June 19, 2019, 8:52pm

Well thats both good and annoying

scouseboy99 · June 20, 2019, 8:10am

Rebuilt the Pi. Thanks to @Bob_Steers for the advice on saving the two database files. That made the process very quick indeed.
I ran the hcitool using lescan and the pi did not see the Tilt, I had my phone next to the pi and it was receiving data from the Tilt. I am coming to the conclusion the the bluetooth radio in this pi is not performing at all well. I have ordered a BLE dongle which should arrive this evening. Will give that a go over the next couple of days see if it makes any difference. I will continue to persevre with this but I have to work this weekend so may be some time before I draw any conclusions.

artemicion · July 23, 2019, 2:46am

Is there any plan for temperature control feature with the Tilt, or is this always limited for logs?

Bob_Steers · July 23, 2019, 7:57am

There are some mechanics for using remote sensors like the tilt as input for brewblox control loops, but so far there hasn’t been much demand.

j616s · July 23, 2019, 9:37pm

I’m unsure if using the Tilt (or similar) for the temp readings driving the control would be sensible. If your battery on your Tilt dies half way through a brew, you could wreck the brew or even your kit.

artemicion · July 23, 2019, 9:51pm

I agree this could be a downside, on the other hand brewers should be aware beforehand if the battery of the Tilt is running out and if it runs out as an option Brewblox could run with the default beer temperature or profile.

artemicion · July 23, 2019, 9:53pm

Not sure if a poll could be useful to see if people is interested.

j616s · July 23, 2019, 10:05pm

Sorry. Confused. Are you saying use the Tilt when you have both a Tilt and BrewPi sensor in your beer? Why would you want to use the unreliable/less accurate Tilt when you have the BrewPi sensor, if so?

There’s also an issue that you can’t really know if the Tilt’s battery is running low. It doesn’t report battery levels.

artemicion · July 23, 2019, 10:20pm

I did not explain myself clearly from the beginning, i meant use the Tilt for gravity readings and BrewPi temperature sensors and change beer temperature depending the specific gravity or attenuation.

Yes the downside is not knowing battery levels but still that’s the choice of the brewer knowing the risk beforehand.

j616s · July 23, 2019, 10:27pm

Ah! That makes more sense This is something I’d like to implement. I gather there’s some new features for people developing plugins that’ll help with this sort of thing in the near future. We’ll see.

artemicion · July 23, 2019, 10:28pm

Glad it is more clear now!, looking forward this feature too

frizzo · August 6, 2019, 8:30pm

Hmmm…
Just installed today and am also seeing the error that was fixed on 24-APR according to earlier posts
I seem to be getting tilt data despite the errors shown. Anything need to be done about it?

2019/08/06 19:Preformatted text03:24 ERROR brewblox_tilt Encountered an error: Failed to execute management command ‘scanend’ (code: 11, error: Rejected)

Full BrewBlox logs: https://termbin.com/fi48

Tilt docker log:

pi@rpi2:~/brewblox$ docker logs brewblox_tilt_1 -f
2019/08/06 19:03:24 INFO     brewblox_service.service        Creating [tilt] application
/usr/local/lib/python3.7/site-packages/aiohttp_swagger/helpers/builders.py:71: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  swagger = yaml.load(swagger_base)
/usr/local/lib/python3.7/site-packages/aiohttp_swagger/helpers/builders.py:30: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  yaml.load("\n".join(end_point_doc[end_point_swagger_start:]))
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [POST] <PlainResource  /tilt/_debug/publish>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [POST] <PlainResource  /tilt/_debug/subscribe>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [HEAD] <PlainResource  /tilt/_service/status>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [GET] <PlainResource  /tilt/_service/status>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [GET] <PlainResource  /tilt/api/doc>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [GET] <PlainResource  /tilt/api/doc/>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [GET] <PlainResource  /tilt/api/doc/swagger.json>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [GET] <StaticResource  /tilt/api/doc/swagger_static -> PosixPath('/usr/local/lib/python3.7/site-packages/aiohttp_swagger/swagger_ui')>
2019/08/06 19:03:24 INFO     brewblox_service.service        Endpoint [HEAD] <StaticResource  /tilt/api/doc/swagger_static -> PosixPath('/usr/local/lib/python3.7/site-packages/aiohttp_swagger/swagger_ui')>
2019/08/06 19:03:24 INFO     brewblox_service.service        Feature [<class 'brewblox_service.scheduler.TaskScheduler'>] <brewblox_service.scheduler.TaskScheduler object at 0x768aa9f0>
2019/08/06 19:03:24 INFO     brewblox_service.service        Feature [<class 'brewblox_service.events.EventListener'>] <EventListener for "172.17.0.1">
2019/08/06 19:03:24 INFO     brewblox_service.service        Feature [<class 'brewblox_service.events.EventPublisher'>] <EventPublisher for "172.17.0.1">
2019/08/06 19:03:24 INFO     brewblox_service.service        Feature [<class 'brewblox_tilt.tiltScanner.TiltScanner'>] <brewblox_tilt.tiltScanner.TiltScanner object at 0x74da3ef0>
2019/08/06 19:03:24 INFO     brewblox_service.events         Closing <EventListener for "172.17.0.1">
2019/08/06 19:03:24 WARNING  brewblox_tilt                   Calibration file not found: /share/SGCal.csv . Calibrated values won't be provided.
2019/08/06 19:03:24 WARNING  brewblox_tilt                   Calibration file not found: /share/tempCal.csv . Calibrated values won't be provided.
2019/08/06 19:03:24 INFO     brewblox_tilt                   Started TiltScanner
2019/08/06 19:03:24 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:25 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:26 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:27 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:28 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:29 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:30 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)
2019/08/06 19:03:31 ERROR    brewblox_tilt                   Encountered an error: Failed to execute management command 'scanend' (code: 11, error: Rejected)

j616s · August 6, 2019, 8:32pm

Will take a look when I get chance but might not have time until Sunday, unfortunately.