The thing with a two-axis graph is there are only two axes. While it *could* be put on the graph, it would be at the expense of either temp or gravity. If @Thorrak decides he wants to capture it, it would be on a separate graph or just a dashboard value.So im using Fermentrack and ispindel. Having trouble with iSpindel battery life. Did the voltage calibration. Is there a way to display Battery voltage in the graph?
Do you mean @LBussy ’s?@Thorrak have you added the 0.2.12 I2C version firmware to the flash tool yet? I looked to update my minion with the new shield at I2C support but didn't see the right firmware, only the beta firmware you said do not use.
I was flashing last night and only saw the remix version 2.11 and 2.10. then Cadibrewers RevC 2.10Do you mean @LBussy ’s?
If so, I thought I had, but if you’re not seeing it let me know and I’ll work with him to get it added.
Are there instructions on enabling bluetooth for the Tilt? I keep getting error "Connection type Bluetooth packages for python have not been installed. Tilt Hydrometers cannot be connected via Bluetooth." on my Raspberry Pi 3 and Arduino Uno R3.
10Which version of Raspbian are you using?
sudo systemctl status avahi-daemon
hosts: files mdns4_minimal [NOTFOUND=return] dns
Thanks for the reply!
...
But I do see the device on my network...simply as esp8662052 (not .local). I can ping that IP and get responses.
I ended up modifying /etc/hosts/ and pointing the ip address to esp8662052.local. I now have passing tests on everything but Controller Response Test.
Chamber temp and using Fridge Constant (so far.) Additionally, I had to make some changes to lower the min times. It's not configurable at runtime right now since I didn't want to find another way to go OOM on the Arduino.
Ohhh man. What enclosure is that? That looks fantastic!Just wanted to share a pic of my completed controller! I haven't tested in a real world scenario yet, but everything seems to be responding properly! Thanks to @Thorrak @LBussy @day_trippr and @CadiBrewer for helping me work through troubleshooting way back in this thread. Cheers!
Check the ahavi daemon
Next, see if there's a file named /etc/mdns.allow.
Then look for a file named /etc/nsswitch.conf. The line labeled hosts: should look something like this:
Code:hosts: files mdns4_minimal [NOTFOUND=return] dns
Some routers don't allow DNS multicast, so "x.local" type addresses don't work. It's generally pretty rare, but I have heard a few people running into that issue. Are you using an address similar to "raspberrypi.local" to SSH into the Pi itself?
I have Google, no issues with mDNS. You’ll have to install avahi and that should take care of the rest:I don't seem to be running ahavi daemon and there is nothing in /etc/ for it either. Same goes for mdns. It is not in /etc/ either.
apt-get install avahi-daemon avahi-discover libnss-mdns
Ohhh man. What enclosure is that? That looks fantastic!
First, I take exception to using"Windows 10" and "Server" in line with each other.
My recommendation would be a VM - and if you have not explored using VBoxVmService it's a pretty nice cohort to Oracle VirtualBox. Slap Raspberry Pi Desktop on there and Bob's your uncle. You only need to put minimal resources against a headless installation. I have many of these running on a gaming rig.
I did some work with Windows/WAMP and BrewPi a while back which may or may not help.
Honestly though - buy an RPi Zero W and be done with it.
I am attempting to update Fermentrack using the "Update from GitHub" button in the "App Settings" page.
I get this this response:
GitCommandError at /upgrade/
Cmd('git') failed due to: exit code(128)
cmdline: git fetch -v origin
stderr: 'error: object file .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f is empty
error: object file .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f is empty
fatal: loose object 0d2a49c9429043006734ae4ce17c5e026a2ff57f (stored in .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f) is corrupt
fatal: the remote end hung up unexpectedly'
Request Method: GET
Request URL: http://192.168.1.121/upgrade/
Django Version: 1.11.22
Exception Type: GitCommandError
Exception Value:
Cmd('git') failed due to: exit code(128)
cmdline: git fetch -v origin
stderr: 'error: object file .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f is empty
error: object file .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f is empty
fatal: loose object 0d2a49c9429043006734ae4ce17c5e026a2ff57f (stored in .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f) is corrupt
fatal: the remote end hung up unexpectedly'
Exception Location: /home/fermentrack/venv/lib/python3.7/site-packages/git/cmd.py in wait, line 415
Python Executable: /home/fermentrack/venv/bin/python3
Python Version: 3.7.3
Python Path:
['/home/fermentrack/venv/lib/python3.7/site-packages/git/ext/gitdb',
'/home/fermentrack/venv/bin',
'/home/fermentrack/fermentrack',
'/home/fermentrack/venv/lib/python3.7/site-packages',
'/usr/lib/python37.zip',
'/usr/lib/python3.7',
'/usr/lib/python3.7/lib-dynload',
'.',
'/home/fermentrack/venv/lib/python3.7/site-packages/gitdb/ext/smmap']
Server time: Thu, 24 Oct 2019 17:44:06 +0000
I am afraid this is a bit beyond me.
Any suggestions?
Shortly after the experiment I installed plain vanilla debian in a VM...fermentrack was super quick and easy to set up and the VM is a minimal hit to system resources. So in the end I was just making the situation more complex than it needed to be.
I'll probably be making a second one of these controllers for a friend at some point so the Zero W looks like a great suggestion, thanks.
That suggests the connection was interrupted as Git did its thing. Just wait a bit and try again later.
error: object file .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f is empty
fatal: loose object 0d2a49c9429043006734ae4ce17c5e026a2ff57f (stored in .git/objects/0d/2a49c9429043006734ae4ce17c5e026a2ff57f) is corrupt
fatal: the remote end hung up unexpectedly'
I just re-read your error, and realized I completely missed the first two lines of the above. The issue appears to be that Git got interrupted at some point, and now you have an inconsistent repo on your Pi. Thankfully, this is pretty easy to fix - but it does require manual intervention.
SSH into your Pi, and then run:
- sudo su fermentrack
- cd ~/fermentrack
- git gc --aggressive --prune=now
...then log back into Fermentrack from a web browser & try again
Enter your email address to join: