Following up on this issue, because it seems to be happening more frequently to me, even with restarts. Below is my latest readings. Those sharp lines are where the gaps are. The battery in the Tilt is brand new, and I set up an old phone with the Tilt app to also log. No gaps shown in that.
thanks for the reply. I can’t select any brewpi_id and I can’t key into the field I believe. I’m not at home so I’ll have to verify tonight.
did you update the software in between? i know i did the latest updates before starting my latest brew, not sure if some pointers got mixed around between the versions - but yours at least seems to maintain the tracking. mine doesnt seem to have ever re-registered. its reporting as if it did but my gravity and temp are both way low like its locked up on a past value
Do you have any brewpi sensors, or just the iSpindel? The way the ThingSpeak support is currently set up, it is meant to push temp data from a brewpi, not gravity data from an iSpindel. If you're like me and only using the iSpindel so far, there aren't any brewpi sensors to put into that field (you'll just see the '---------' in the dropdown).
I ran an update right before brewing, but haven't run one since. Those two graphs are both from my current fermentation. It's the inconsistency that's confusing me.
HarlemBrewDoug said:
The error is on brewpi_to_push_id, which should come from the fourth option here (Brewpi to push). It looks like it wants a BrewPi device, not a gravity sensor.
View attachment 700627
As for the battery question, that's voltage. It's a nominal 3.7 volt battery, but max charge will be around 4.2 volts, and if I remember correctly it's usable down to about 3.2 (or maybe it was 3.5) before your iSpindel will stop functioning properly.
yeah I only have iSpindel. My idea was to push to ThingSpeak, then use ifttt to talk to my inkbird wireless plugs to turn on/off heater or cooling. was an idea
its funny tho, if you hover over the brewpi to push words, it says ignored if all devices selected. How do you select all devices?
If you are going directly from Tilt to Fermentrack, it's very likely because of the UART in the Pi. These can be slowed down to help prevent these missing data pieces. Have a look at this issue.
curl -L uartspeed.brewpiremix.com | sudo bashWell, I would not release it if I thought it would hurt. Still, YMMV and all that.
I don;t have any reports of bad things happening, and more than a few reports of good things happening. This is a part of the BPR install.Tilt makes a repeater. Tiltbridge is also a repeater that you can make. Both will work with Fermentrack.
pi@raspberrypi:~ $ curl -L uartspeed.brewpiremix.com | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 291 100 291 0 0 1293 0 --:--:-- --:--:-- --:--:-- 1293
100 3035 100 3035 0 0 5704 0 --:--:-- --:--:-- --:--:-- 5704
bash: line 97: main: command not found
/usr/bin/btuart backed up to /home/pi/btuart.bak.
/usr/bin/btuart updated.
Restarting bluetooth.
Bluetooth daemon restarted. Please restart any client scripts.
bash: line 102: syntax error near unexpected token `}'
bash: line 102: `}'hci0: Type: Primary Bus: UART
BD Address: DC:A6:32:1F:45:90 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:2922 acl:0 sco:0 events:154 errors:0
TX bytes:6333 acl:0 sco:0 commands:154 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'raspberrypi'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 5.0 (0x9) Revision: 0x122
LMP Version: 5.0 (0x9) Subversion: 0x6119
Manufacturer: Cypress Semiconductor Corporation (305)Well first, congratulations on being the first person for whom this has not worked.
please dont limit the high end! i just rammed through a NEIPA with a kveik in 2 days at 90F
Too much of that in 2020. This is my fun distraction!
Hope nothing serious in VA.
Glad you could help!Perfect - pretty sure that’s the Pi I have with me. Good to test with!
My pseudo-mother-in-law broke her leg the week before she was scheduled to move to a new house. Fortunate timing in that her new house is perfect for recovering from a broken leg (no stairs!) but terrible timing in that we now get to manage her move. She was suspiciously OK with going to rehab for the next week. Hmmmm...
Hmmm. Not working here. Ran the command and saw no change so I restarted the pi. Still nothing
It's working. (I had stood up my Tilt so it wasn't transmitting (smh)
Looking through the /usr/bin directory, I'm not finding the python3.7 reference. Similarly named files go up to 3.5. Not surprisingly, trying to run those commands aren't really going to work. I did just run the most recent updated dev push before checking.
maybe this depends on the pi/distro being used?
Definitely. The “fix environment” scripts should force a Python 3.7 environment, but I’m thinking @HarlemBrewDoug might not be fully updated. If that readlink command returns an earlier version that might be part of the issue.
