@DrGMG If you're still having issues, shoot me a PM - I've got something in the works that might help, but isn't quite 100% ready for prime-time.
PM sent.
@DrGMG If you're still having issues, shoot me a PM - I've got something in the works that might help, but isn't quite 100% ready for prime-time.
Hello, I have manually installed tiltbridge onto a Lolin D32. I can access it through my web browser and see correct readings. I have followed the cloud service setup guide to configure the fermentrack URL. I can add it as a tiltbridge in Fermentrack (it sees the mDNS, I get a message saying the tiltebridge url is configured) and can use that to add a tilt (connection type = tiltbridge). Once I have added it Fermentrack does not show any values. If I go to manage sensor the connection type is Bluetooth. If I try and add another tiltbridge it shows no unbound tiltbridges are available until I delete the current sensor.
Please let me know what other infomation I can provide.
Thanks
View attachment 662132 View attachment 662133
I'm on Dev.Are you on master or dev?
Plenty of time to get it running!Of course, my hardware shows up 12 hours before I leave town for a week! I'm be attempting this soon though!
What browser are you using?
Got mine flashed and up and running. Initial setup was pretty easy. But I have an issue accessing the web page of the device once it is on my wireless network. The d32 has an IP that it shows on startup. It sees the TILT no problem. I can see the device from my router device list, and I can ping the IP so it is on my network. But when I connect to the tiltbridge IP with http:// there is just a blank screen in my browser.
That actually sounds like the SPIFFS didn’t flash properly.
Lee- For those of us that are still challenged to get this working, can you tell us how to erase the flash? Sorry if this sounds like a fundamental question but this is very new to me! I've tried re-flashing, believing it would overwrite everything but maybe it's not that simple?Try to erase the flash, then re-flash the firmware and reconnect.
Oh how I wish that this was advanced to plug and play status! I'm mechanically savvy, but not electrically or systems-wise. I see great potential applications like this one and Raspberry Pi tools, but which have taken those who are very competent in these areas countless months and many hundreds of posts to try and get the bugs worked out, and they are still trying. Good on you, I appreciate these are still in development mode. Sadly, it is not practical for me to educate myself to the point of participating in these issues, so I must watch from the sidelines. I guess my question out of ignorance is (and it is NOT a criticism): since the general technology and tools are available, why does it take so long to sort through these matters and develop the applications? I know it's not through a lack of capability, effort and good collaboration.
can you tell us how to erase the flash?
Some configuration information, including WiFi credentials and access point information, is stored in an area of memory that is not overwritten when you re-flash. This causes confusion as you can imagine but also that area can get corrupt and will stay that way until a specific action is taken.Lee- For those of us that are still challenged to get this working, can you tell us how to erase the flash? Sorry if this sounds like a fundamental question but this is very new to me! I've tried re-flashing, believing it would overwrite everything but maybe it's not that simple?
We won't talk about the time it takes or the money we spend. My wife's divorce lawyer would find it sometime in the future and it would come back to haunt me.
Lee- For those of us that are still challenged to get this working, can you tell us how to erase the flash? Sorry if this sounds like a fundamental question but this is very new to me! I've tried re-flashing, believing it would overwrite everything but maybe it's not that simple?
Oh how I wish that this was advanced to plug and play status! I'm mechanically savvy, but not electrically or systems-wise. I see great potential applications like this one and Raspberry Pi tools, but which have taken those who are very competent in these areas countless months and many hundreds of posts to try and get the bugs worked out, and they are still trying. Good on you, I appreciate these are still in development mode. Sadly, it is not practical for me to educate myself to the point of participating in these issues, so I must watch from the sidelines. I guess my question out of ignorance is (and it is NOT a criticism): since the general technology and tools are available, why does it take so long to sort through these matters and develop the applications? I know it's not through a lack of capability, effort and good collaboration.
Seems like this *might* be that bug I keep hitting (and none of the lib devs believe it) where the AP doesn't seem to completely go into STA mode. Try to erase the flash, then re-flash the firmware and reconnect.
Well, it is running now, but I am not sure why. I sent a bit of Arduino code to the board with Arduino IDE, then reflashed the board and it came up and is working fine. Below is the code I sent, but I would think that after reflashing with the firmware (via: esptool.py --chip esp32 --before default_reset --after hard_reset write_flash 0x10000 firmware.bin 0x8000 partitions.bin 0x3D1000 spiffs.bin) that it would overwrite anything I sent to the board previously:
Here is the code:
#define SCK 15;
#define SDA 4;
void setup() {
digitalWrite(16, HIGH);
// put your setup code here, to run once:
}
void loop() {
// put your main code here, to run repeatedly:
}
After this it is working just fine.
Klaus
I'm trying to build this branch https://github.com/omgitsads/tiltbridge/tree/brewfather in platformio but I get the following error
"
Retrieving maximum program size .pio\build\lolin32_lcd_ssd1306\firmware.elf
Checking size .pio\build\lolin32_lcd_ssd1306\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
DATA: [== ] 21.6% (used 70636 bytes from 327680 bytes)
PROGRAM: [==========] 100.0% (used 1966427 bytes from 1966080 bytes)Error: The program size (1966427 bytes) is greater than maximum allowed (1966080 bytes)
*** [checkprogsize] Explicit exit, status 1
esptool.py v2.6
========================= [FAILED] Took 131.42 seconds ========================="
I also get the same error if I try to build this master https://github.com/thorrak/tiltbridge , could anyone suggest where I'm going wrong ?
Hi everyone. I flashed tiltbridge firmware to an esp32 board and it's working properly. I know the tiltbridge is working properly because I can connect directly to it via the tiltbridge's ip address and under 'available tilts' I see the gravity and temperature readout from my tilt. I can also see the gravity reading on the esp32's screen.
View attachment 664863
I've added the tilt via tiltbridge to my fermentrack installation.
Any help would be appreciated with the issues below:
Issue 1: Fermentrack says the tilt is currently 'unbound' and I'm not getting any readout from the device.
View attachment 664864
Issue 2: I'm getting the following error: "Bluetooth packages for python have not been installed. Tilt support will not work. Click here to learn how to resolve this issue." I've clicked and followed the instructions to install the additional packages, restarted linux, and I'm still receiving the error. Any suggestions? I'm running on debian and I don't recall having any issues with fermentrack installation that would have forced me into any manual or non-standard installation.
View attachment 664868
To the TiltBridge question: Can you check what connection type you have listed on the Tilt (bluetooth vs. tiltbridge)?
To the Bluetooth error question: When did you first install Fermentrack? You mentioned running on Debian - Is Debian running in a VM or on bare metal?
Hmm. When I go into the 'manage sensor' page for the Tilt it says my connection type is bluetooth. I am sure that I selected tiltbridge connection type when I initially added it because I just uninstalled the device from fermentrack and went through the process of adding it again to double check.
Debian is running in a virtual machine.
I installed fermentrack last Sept/Oct. I'm currently using the version that has commit date: June 16, 2019, 10:09 p.m.Out of curiosity, when did you first install Fermentrack? It might be worthwhile to try running the following - if you don't have the proper libraries installed that can cause the issue you're seeing:
sudo apt-get install -y bluez libcap2-bin libbluetooth3 libbluetooth-dev
(The reason I keep asking about when you installed is because of that line - the latest install script installs those packages, but they were missing up until a few months ago)
I think I'm at that point now. I don't know what to do besides maybe updating fermentrack itself. I generally go by the 'if it ain't broke don't fix it' mantra for stuff like this, so I'm hesitant to update unless you think it might help resolve the error. Otherwise maybe there's a way for me to simply adjust the 'bluetooth' option to 'tiltbridge' manually?That's your problem - If you cant get it to set/stick for some reason, let me know and I'll dive into the code
That's fine, I kind of figured as much. I'm not interested in running via bluetooth through the virtual machine. It's on a server opposite side of my house so I planned to do it with tiltbridge via wifi.That said, you can safely ignore the bluetooth warning, as I have NO idea how/if it will work in a VM. I'd imagine it depends on the hypervisor you're using.
I installed fermentrack last Sept/Oct. I'm currently using the version that has commit date: June 16, 2019, 10:09 p.m.
Yeah I did have to install those packages manually. Then after I installed pybluez in the python virtual environment for fermentrack per the link in the bluetooth error message. (also a note for others, pybluez won't install unless you install the libbluetooth-dev package which is not suggested by the help link in fermentrack)
I think I'm at that point now. I don't know what to do besides maybe updating fermentrack itself. I generally go by the 'if it ain't broke don't fix it' mantra for stuff like this, so I'm hesitant to update unless you think it might help resolve the error. Otherwise maybe there's a way for me to simply adjust the 'bluetooth' option to 'tiltbridge' manually?
WELL. About that. Updating Fermentrack will fix the bug you reported -- but only as of 30 seconds ago. There's a lot of other bugfixes in there as well, of course, but the one that you specifically noted just now (the connection type not getting saved & therefore defaulting to 'Bluetooth') was only fixed just now. Thanks for reporting this!
Although I recommend updating, if you would prefer not to update you can set the connection type manually using the Django admin. Just click the "gear" icon in the upper right, choose "Django Admin", then "Tilt Configuration" down near the bottom, and click the Tilt configuration you want to edit. You can change the connection type there.
Klaus thank you very match. According your procedure is now working. I had same issue as how you described: "After flashing tiltbridge i had black screen without wifi AP. I ,flashed by Arduino IDE your code, then reflashed tiltbridge and vuala screen is going and i can connect to AP."
ROBOL
I tried flashing my ESP32 OLED V2.0 TTGO with brewflasher, fermentrack, and esptool without success.. It supposedly completes the flash successfully each time, but I do not see the tiltbridge SSID to connect to. After the flash completes, I turn unplug and then plug it back in. The red light on the ESP32 board is on, but the OLED screen is blank. help?
Enter your email address to join: