Search results

At this point, I'm honestly thinking of ditching the addition of bluetooth. Hopefully I can get it all set up in my space in a way that USB cables can reach.

Oh, forgot to mention that I re-paired the BT module with the pi, and it is now connecting to /dev/rfcomm2. I adjusted this in Fermentrack, but the issue continues.

I originally had it wired up RX on the shield to RX on the module, same with TX, as this is what I assumed. I tried the other way around and it hasn't resolved the issue, unfortunately.

Another interesting thing I found poking around. Looked at the Stderr Log in Fermentrack and it is repeating these lines: Mar 28 2019 13:43:42 Warning: Cannot receive version number from controller. Your controller is either not programmed or running a very old version of BrewPi. Please...

There is a section in the Fermentrack Documentation for Enabling Python To Interact with Bluetooth, and says that the section needs to be re-written with full instructions. At the moment it lists code: PYTHON3_INTERPRETER="$(readlink -e $installPath/venv/bin/python)" if [ -a...

Yeah, RX to TX and vice versa.

The light on the BT module: blinks rapidly when not paired, one second long blink every other second when in AT mode, and double blink every 2 seconds when paired with the Pi. When I entered AT mode, it seemed to reflect this in the serial monitor of IDE. What should the baud rate be, and how...

Ran the first command, seemed to take ok. Ran screen /dev/rfcomm0 57600 and the terminal window becomes a blank field. I tried typing 'l' but nothing happened. Then after a minute it says [screen is terminating] and returns to pi@raspberrypi:~ $

Reboot done, now just showing one: crw-rw---- 1 root dialout 216, 0 Mar 27 21:39 /dev/rfcomm0 Deleted the device I had in Fermentrack to start over. Re-added using advanced set up, inputting /dev/rfcomm0 as the Serial Port. Still isn't communicating with the controller :(