How To: BrewPi Over Bluetooth

[day_trippr]

/etc/udev/rules.d/99-arduino.rules is not used by rfcomm devices.

Cheers!

 

[EMPyre]

Perfect! Thank you! Crossing my nuts that I can get the rest hooked up and running tonight.

 

[day_trippr]

That sounds painful

 

[EMPyre]

Totally worked... 4 instances running happily on BT, and 5th hardwired to the Pi. Now onto the LCDs and stuffing it all in project boxes.

 

[day_trippr]

 

[gezzanet]

Cool. Good work

 

[stlbeer]

Totally worked... 4 instances running happily on BT, and 5th hardwired to the Pi. Now onto the LCDs and stuffing it all in project boxes.

Post some pics when you get the project boxes filled up. I'd like to see what you came up with.

 

[EMPyre]

Will do. Pretty much ripped off day_trippr package-wise, and he's right, it's a tight fit in those Hammond boxes. I just got them all cut last night. Waiting on some more jumpers for final assembly, but I might have one completed this weekend.

 

[day_trippr]

If you are using the same box as I did...



...kudos for bravery
And know that I had to crop the LCD pcb to get it to fit.



I chucked one of my belt sanders in a bench vise with the business side up and used that to give the LCD a trim...

Cheers!

 

[EMPyre]

Same dimensions, or nearly so... and yes, I'm readying a sander/dremel/polishing disc to "adjust" the LCD board.

 

[EMPyre]

As promised...
LCD First

Receptacle:

Backside:

and the Guts:

Still have a little clean up to do, and caulk the cutouts for the receptacle and LCD, but it's together and functioning. Three more will go together this week when I get some more jumpers.

Thanks to everyone whose effort on this thread, the LCD add-on, and both the 'Pints threads as well. Day_trippr, thank you a ton!

 

[wbarber69]

Not trying to be "that guy" but have you tried one of the minions out connected to a fridge yet? I see your relay board is awfully close to the lcd…

 

[EMPyre]

Hmm... I haven't. I have manually flipped the switch, but without a load. I have seen a couple of freakouts on the LCDs though, so I certainly have some power surging issues somewhere, and it seems I'm having issues getting BT to reconnect... Also I've got one box where the backlight isn't shutting off. To be fair regarding the relays though, none of these minions will be seeing a fridge compressor on the cooling circuit. They will all be used to cycle 12v ball valves for a glycol run.

 

[wbarber69]

So you have one of the rare cases where a sainsmart ssr board would actually work…

 

[EMPyre]

Good to know. If I have issues, I'll swap to ssr.

 

[user 40839]

Well, pisser.

Can't seem to get this thing to do it's duty. Ordered a couple of these: https://www.amazon.com/gp/product/B013STJSES/?tag=skimlinks_replacement-20

And have assembled the programming setup on a breadboard:

But getting nada from the serial monitor after uploading the programming sketch. Anyone see a glaring error on the breadboard, or is this flavour of HC-05 no bueno?

 

[Bigdaddyale]

Well, pisser.

Can't seem to get this thing to do it's duty. Ordered a couple of these: https://www.amazon.com/gp/product/B013STJSES/?tag=skimlinks_replacement-20

And have assembled the programming setup on a breadboard:

But getting nada from the serial monitor after uploading the programming sketch. Anyone see a glaring error on the breadboard, or is this flavour of HC-05 no bueno?

Do you have to flip the RX and TX from the HC05 to the pins on the UNO R3?

 

[day_trippr]

The Uno TX signal goes through the resistive level shifter thence on to the HC-05 RX.
The HC-05 TX goes directly to the Uno RX input.
I've never used an HC-05 or HC-06 equipped with a pushbutton, but others have, and iirc it wasn't quite as straight forward as my writeup.

Hopefully someone with experience will chime in...

Cheers!

 

[wbarber69]

Yeah look on googles for a write up on the hc-05 with push button. the sketch is actually more simple and all you have to do to enter AT mode is to hold the button as you power up.

 

[wbarber69]

Somewhere back in the beginnings of the main brewpi diy thread back when day_tripper got the bt stuff up and running, I had a short stint in it where I used the with button settup and there's plenty of info back there. I'll be going back over the old posts one day soon once I get back into finishing my system up. but until then you're more than welcome to dig through the he past 7000 posts on that forum to help you out. but Google may actually be the better place to start.


EDIT: actually some of the info you need starts on like page 4 of this thread.

https://www.homebrewtalk.com/showpost.php?p=6704139

 

[user 40839]

All nuked - I'm a gob****e.

 

[user 40839]

Aha, never mind - the internets win, as my google fu was weak. Followed the instructions here:

http://www.martyncurrey.com/arduino-with-hc-05-bluetooth-module-at-mode/

And managed to get them programmed.

Now the latest snafu is getting the PI to connect to it. Am using a Pi 3 model B, with in-built bluetooth. In pairing, the Pi will see the HC-05, entered the pin, and was then politely informed "Paired successfully, but this device has no services which can be used with Raspberry Pi" and the BrewPi web interface doesn't seem to be seeing it.

 

[day_trippr]

Unless something has changed (and it sounds like it hasn't) the desktop Bluetooth gui bundled with Jessie/LXDE is useless for anything other than headsets and microphones.

You could go back in this thread to see weeks of me trying to get an HC-05 to work on Jessie. Finally figured out that rfcomm would do it even while the gui had zero clue (and still doesn't - even when multiple HC-05's are working right under its nose).

All you need is the MAC for the HC-05 and a device nickname of your choice.
HCI-TOOL can find BT agents:

$ hcitool scan
Scanning ...
        00:02:72:32:D8:2C       OBELISK
        98:D3:31:80:25:64       BPSAT_3

Now, I can't remember if hci-tool and rfcomm are bundled with Jessie or if they are installed as part of bluez-utils or blueman. In any case, eventually rfcomm is what you need, as you can then bind the HC-05 to a channel and logical device that in turn can be connected to.


Create /etc/bluetooth/rfcomm.conf

#
# RFCOMM configuration file.
#

rfcomm0 {
# Automatically bind the device at startup
bind yes;
#
# Bluetooth address of the device
device 98:d3:31:80:25:64;
#
# RFCOMM channel for the connection
channel	1;
#
# Description of the connection
comment "BPSAT_3";
}

Then change /home/brewpi/settings/config.cfg

scriptPath = /home/brewpi
wwwPath = /var/www  [Note: or /var/www/html)
port = /dev/rfcomm0
altport = /dev/brewpi1  (<= this is the wired USB connection as an alternate port)
boardType = uno

Cheers!

 

[user 40839]

So I assume that for a multiple chamber setup, within the rfomm.conf file I'd create rfcomm0 for minion 1 and rfcomm1 for minion 2? (as opposed to differing channels)

and similarly, in the config.cfg file for each, minion1 would have

port = /dev/rfcomm0

whereas minion2 would have

port = /dev/rfcomm1

 

[wbarber69]

U gots it

 

[user 40839]

Nope, nada. No dice. Here's my situation at the moment... two minion setup which was working under USB. Both minions are using cadi's shield.

Both BT boards have been programmed via the tutorial located at http://www.martyncurrey.com/arduino-with-hc-05-bluetooth-module-at-mode/ I did use a separate Arduino to do the programming.

Both minions are currently being powered by separate 12v power supplies without a USB cable in sight.

Here are the results of the hcitool scan:

Scanning ...
	98:D3:34:90:D5:73	HC-05
	98:D3:33:80:E0:6A	HC-05

With this, here's my /etc/bluetooth/rfcomm.conf file in all it's glory:

#
# RFCOMM configuration file.
#

rfcomm0 {
# Automatically bind the device at startup
bind yes;
#
# Bluetooth address of the device
device 98:D3:34:90:D5:73;
#
# RFCOMM channel for the connection
channel 1;
#
# Description of the connection
comment "chamber1";
}

rfcomm1 {
# Automatically bind the device at startup
bind yes;
#
# Bluetooth address of the device
device 98:D3:33:80:E0:6A;
#
# RFCOMM channel for the connection
channel 1;
#
# Description of the connection
comment "chamber2";
}

The contents of /home/brewpi/chamber1/settings/config.cfg

scriptPath = /home/brewpi/chamber1/
wwwPath = /var/www/html/chamber1/
port = /dev/rfcomm0
altport = /dev/brewpi1
boardType = uno

And the contents of /home/brewpi/chamber2/settings/config.cfg

scriptPath = /home/brewpi/chamber2/
wwwPath = /var/www/html/chamber2/
port = /dev/rfcomm1
altport = /dev/brewpi2
boardType = uno

Have to say too, since I manually added that rfcomm.conf file, connectivity has gotten really sketchy. I'll try and ssh in and half the time it'll tell me that the host is down, or that the session will time out.

The script isn't running in either instance. Here's the result of trying to reprogram chamber1 via the web interface:

Jan 22 2017 17:18:02 Opening serial port
Jan 22 2017 17:18:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 17:19:03 Opening serial port
Jan 22 2017 17:19:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 17:20:02 Opening serial port
Jan 22 2017 17:20:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 17:21:03 Opening serial port
Jan 22 2017 17:21:03 Notification: Script started for beer 'My First BrewPi Run'
Jan 22 2017 17:21:13 Checking software version on controller... 
Jan 22 2017 17:21:13 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revC shield on port /dev/chamber1

Jan 22 2017 17:23:50 Opening serial port
Jan 22 2017 17:23:50 Notification: Script started for beer 'My First BrewPi Run'
Jan 22 2017 17:24:00 Checking software version on controller... 
Jan 22 2017 17:24:00 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revC shield on port /dev/chamber1

Jan 22 2017 17:35:03 Opening serial port
Jan 22 2017 17:35:03 Notification: Script started for beer 'My First BrewPi Run'
Jan 22 2017 17:35:13 Checking software version on controller... 
Jan 22 2017 17:35:13 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revC shield on port /dev/chamber1

Jan 22 2017 17:39:03 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Jan 22 2017 19:59:05 Opening serial port
Jan 22 2017 19:59:05 Notification: Script started for beer 'My First BrewPi Run'
Jan 22 2017 19:59:43 Checking software version on controller... 
Jan 22 2017 19:59:43 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revC shield on port /dev/chamber1

Jan 22 2017 20:38:05 Serial Error: [Errno 5] Input/output error)
Jan 22 2017 20:38:06 Lost serial connection. Error: [Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1')
Terminating due to fatal serial error
Jan 22 2017 20:39:02 Opening serial port
Jan 22 2017 20:39:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:40:02 Opening serial port
Jan 22 2017 20:40:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:41:02 Opening serial port
Jan 22 2017 20:41:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:42:02 Opening serial port
Jan 22 2017 20:42:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:43:03 Opening serial port
Jan 22 2017 20:43:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:44:02 Opening serial port
Jan 22 2017 20:44:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:45:02 Opening serial port
Jan 22 2017 20:45:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/chamber1: [Errno 2] No such file or directory: '/dev/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:46:03 Opening serial port
Jan 22 2017 20:46:13 Errors while opening serial port: 
[Errno 2] could not open port /rfcomm0/chamber1: [Errno 2] No such file or directory: '/rfcomm0/chamber1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:47:02 Opening serial port
Jan 22 2017 20:47:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:48:02 Opening serial port
Jan 22 2017 20:48:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:49:03 Opening serial port
Jan 22 2017 20:49:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:50:02 Opening serial port
Jan 22 2017 20:50:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:51:03 Opening serial port
Jan 22 2017 20:51:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:52:02 Opening serial port
Jan 22 2017 20:52:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:53:02 Opening serial port
Jan 22 2017 20:53:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:55:59 Opening serial port
Jan 22 2017 20:56:09 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:57:02 Opening serial port
Jan 22 2017 20:57:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:58:02 Opening serial port
Jan 22 2017 20:58:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 20:59:02 Opening serial port
Jan 22 2017 20:59:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 21:00:02 Opening serial port
Jan 22 2017 21:00:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 21:01:02 Opening serial port
Jan 22 2017 21:01:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 21:02:02 Opening serial port
Jan 22 2017 21:02:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 21:03:02 Opening serial port
Jan 22 2017 21:03:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 22 2017 21:04:02 Opening serial port
Jan 22 2017 21:04:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:05:02 Opening serial port
Jan 22 2017 21:05:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:06:02 Opening serial port
Jan 22 2017 21:06:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:07:02 Opening serial port
Jan 22 2017 21:07:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:08:02 Opening serial port
Jan 22 2017 21:08:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:09:02 Opening serial port
Jan 22 2017 21:09:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:10:02 Opening serial port
Jan 22 2017 21:10:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:11:02 Opening serial port
Jan 22 2017 21:11:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:12:02 Opening serial port
Jan 22 2017 21:12:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:13:02 Opening serial port
Jan 22 2017 21:13:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:14:02 Opening serial port
Jan 22 2017 21:14:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:15:02 Opening serial port
Jan 22 2017 21:15:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:16:02 Opening serial port
Jan 22 2017 21:16:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:17:02 Opening serial port
Jan 22 2017 21:17:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:18:02 Opening serial port
Jan 22 2017 21:18:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:19:02 Opening serial port
Jan 22 2017 21:19:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:20:02 Opening serial port
Jan 22 2017 21:20:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:21:02 Opening serial port
Jan 22 2017 21:21:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:22:03 Opening serial port
Jan 22 2017 21:22:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:23:32 Opening serial port
Jan 22 2017 21:23:42 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:24:02 Opening serial port
Jan 22 2017 21:24:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'
[Errno 2] could not open port /dev/brewpi1: [Errno 2] No such file or directory: '/dev/brewpi1'

Jan 22 2017 21:25:02 Opening serial port
Jan 22 2017 21:25:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm0: [Errno 2] No such file or directory: '/dev/rfcomm0'

The thing that's getting me is that when I try to program it, it's actually seeing that there's a BrewPi with "v0.2.10 build unknown" so... erm, help? Issue seems to be that it's not creating the rfcomm0 or rfcomm1 file in the /etc/ directory.

 

[user 40839]

This is killing me. I had visions of two minions controlling my SS Brew chronicals and the fancy pants glycol system. GAH!

So in further sniffing, it seems that bluez-utils is no longer a thing. However

sudo apt-get install -y bluetooth bluez-tools blueman

did pull down a potload of goodies onto the Pi. From there, I was actually able to pair the boards via the GUI, but as @day_trippr points out, that seems to be about as much use as a one legged man in an arse kicking competition. From a bit more sniffing, I was able to bind rfcomm0 manually

sudo rfcomm bind hci0 98:D3:34:90:D5:73 1

which did result in /dev/rfcomm0 finally being created. HOORAY!!! Alas, it doesn't survive a reboot. And brewpi wasn't seeing it anyways. Awwww. @wbarber69 was right, this thing does require many smoke breaks. It was one thing troubleshooting a dodgy PFET solder joint getting the boards up and running initially, but I'm in WAY over my head here.

Ahh screw it. Order two more boards that look a lot more like the ones everyone else is using. Maybe that'll fix it.

 

[wbarber69]

Btw my smoke breaks comment was more to do with the fact that for some reason when you go down the bt rabbit hole, sometimes things just work later. no matter how long you stare at it it won't connect until you walk away, then blamm it works forever. and you've spent 6 hours past mid night for no reason other than to incessantly click connect for no reason, when all you had to do was go enjoy a cigarette and then return to a fully functional minion.

 

[wbarber69]

And don't worry, I'll be getting better back into this stuff soon enough, and I will be starting from scratch, with Jesse and pi3 and I'll be making it happen, so hopefully we can get all this behind us, and I'll have one of you write up the new walktrough… lol

 

[user 40839]

Interesting. So having manually bound rfcomm0 (as mentioned above), the BrewPi script on the page is now giving me the "Could not receiveversion from controller Please (re)program your controller" message.

Of course, any attempts to program the controller fail miserably...

 

[user 40839]

And don't worry, I'll be getting better back into this stuff soon enough, and I will be starting from scratch, with Jesse and pi3 and I'll be making it happen, so hopefully we can get all this behind us, and I'll have one of you write up the new walktrough… lol

At this point, I think I'm throwing in the towel. Given my lack of linux knowledge, every time I delve deeper into trying things, I end up breaking my install, and have to wipe and restart. From what I've been seeing though, bluez in it's current incarnation has become extremely broken and the on-board bluetooth unit (as well as wifi it seems) on the Pi 3 is sketchy at best. Looks like I'll be sticking with USB cables at least until someone smarter than me comes along.

 

[day_trippr]

So you think this is an RPi3 problem?

fwiw, I've been running BrewPi through an HC-05 on my RPI2B Jessie test system for months.
Works fine, auto-starts on boot just like my Wheezy systems.

Did I mention adding rfcomm commands to the LXDE autostart file for user = pi?

Edit /home/pi/.config/lxsession/LXDE-pi/autostart

Add lines like this for each HC-05:

sudo rfcomm bind 0 983:31:80:25:64 1

When you reboot all BT radios should connect automagically...

Cheers!

 

[user 40839]

The Arduinos are functioning without issue, and the HC-05s seem to be fine. From my rampant googling over the past few days, I've seen thread after thread after thread of people complaining about BT functionality of late.

Anyhoo.

You beat me to it. I finally unearthed a thread on the Raspberry Pi boards. Using bluetoothctl seems to muddy the waters as then made each device show as in use when rfcomm came into play. Unpaired everything in bluetoothctl, and just opened two new terminal windows manually kicking on the HC-05s.

sudo rfcomm connect 0 98:D3:34:90:D5:73 1

Lo and behold...

Connected /dev/rfcomm0 to 98:D3:34:90:D5:73 on channel 1
Press CTRL-C for hangup

Frantically ran to my brewpi page for chamber 1 and... nothing. Goddamnit. Refresh. Nothing. Walked away to pee, came back, and... it couldn't receive version from controller. Tried reprogramming it, and was politely informed that I wasn't running the correct version of pyserial (yet when I tried upgrading, it's saying it's the newest version?) But... suddenly there it was - the data in the screen. Controller set to off, but it was now showing the beer and chamber temps!!! (Only weirdness is that now suddenly my fridge temp sensor is showing two decimal places instead of one). Connection does seem a little spotty - it will occasionally give me a "cannot receive LCD text from script" message.

Chamber 2 is still telling me to reprogram. When I tried reprogramming, it didn't seem happy:

rade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

BrewPi requires pyserial 3.0, you have version 2.6 installed.
Please upgrade pyserial via pip, by running:
sudo pip install pyserial --upgrade
If you do not have pip installed, install it with:
sudo apt-get install build-essential python-dev python-pip

Jan 24 2017 21:00:02 Opening serial port
Jan 24 2017 21:00:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:01:02 Opening serial port
Jan 24 2017 21:01:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:02:02 Opening serial port
Jan 24 2017 21:02:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:03:03 Opening serial port
Jan 24 2017 21:03:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:05:39 Opening serial port
Jan 24 2017 21:05:49 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:06:02 Opening serial port
Jan 24 2017 21:06:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:07:02 Opening serial port
Jan 24 2017 21:07:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:08:02 Opening serial port
Jan 24 2017 21:08:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:09:03 Opening serial port
Jan 24 2017 21:09:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:10:03 Opening serial port
Jan 24 2017 21:10:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:11:02 Opening serial port
Jan 24 2017 21:11:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:12:02 Opening serial port
Jan 24 2017 21:12:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:13:02 Opening serial port
Jan 24 2017 21:13:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:14:03 Opening serial port
Jan 24 2017 21:14:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:15:02 Opening serial port
Jan 24 2017 21:15:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:16:02 Opening serial port
Jan 24 2017 21:16:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:17:03 Opening serial port
Jan 24 2017 21:17:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:18:02 Opening serial port
Jan 24 2017 21:18:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:19:02 Opening serial port
Jan 24 2017 21:19:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:20:02 Opening serial port
Jan 24 2017 21:20:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:21:03 Opening serial port
Jan 24 2017 21:21:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:22:02 Opening serial port
Jan 24 2017 21:22:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:23:02 Opening serial port
Jan 24 2017 21:23:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:24:02 Opening serial port
Jan 24 2017 21:24:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:25:03 Opening serial port
Jan 24 2017 21:25:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:26:02 Opening serial port
Jan 24 2017 21:26:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:27:02 Opening serial port
Jan 24 2017 21:27:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:28:03 Opening serial port
Jan 24 2017 21:28:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:29:02 Opening serial port
Jan 24 2017 21:29:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:30:02 Opening serial port
Jan 24 2017 21:30:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:31:05 Opening serial port
Jan 24 2017 21:31:15 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:32:32 Opening serial port
Jan 24 2017 21:32:42 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:33:03 Opening serial port
Jan 24 2017 21:33:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:34:03 Opening serial port
Jan 24 2017 21:34:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:35:02 Opening serial port
Jan 24 2017 21:35:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:36:02 Opening serial port
Jan 24 2017 21:36:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:37:02 Opening serial port
Jan 24 2017 21:37:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:38:03 Opening serial port
Jan 24 2017 21:38:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:39:03 Opening serial port
Jan 24 2017 21:39:13 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:40:02 Opening serial port
Jan 24 2017 21:40:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:41:02 Opening serial port
Jan 24 2017 21:41:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:42:02 Opening serial port
Jan 24 2017 21:42:12 Errors while opening serial port: 
[Errno 2] could not open port /dev/rfcomm1: [Errno 2] No such file or directory: '/dev/rfcomm1'
Could not configure port: (25, 'Inappropriate ioctl for device')

Jan 24 2017 21:43:03 Opening serial port
Jan 24 2017 21:43:03 Notification: Script started for beer 'My First BrewPi Run'
Jan 24 2017 21:43:13 Checking software version on controller... 
Jan 24 2017 21:43:23 Warning: Cannot receive version number from controller. Your controller is either not programmed or running a very old version of BrewPi. Please upload a new version of BrewPi to your controller.
**** Arduino Program script started ****
Settings will not be restored
Devices will not be restored
Jan 24 2017 21:44:12 Opening serial port
Loading programming settings from board.txt
Checking hex file size with avr-size...
Program size: 26896 bytes out of max 32256
ERROR: could not find port in bootloader
Traceback (most recent call last):
File "/home/brewpi/chamber2/brewpi.py", line 649, in 
{'settings': restoreSettings, 'devices': restoreDevices})
File "/home/brewpi/chamber2/programController.py", line 163, in programController
return programmer.program(hexFile, system1File, system2File, useDfu, restoreWhat)
File "/home/brewpi/chamber2/programController.py", line 274, in program
if not self.flash_file(hexFile):
File "/home/brewpi/chamber2/programController.py", line 650, in flash_file
' -C ' + avrconf)
TypeError: cannot concatenate 'str' and 'NoneType' objects
Jan 24 2017 21:45:02 Opening serial port
Jan 24 2017 21:45:02 Notification: Script started for beer 'My First BrewPi Run'
Jan 24 2017 21:45:12 Checking software version on controller... 
Jan 24 2017 21:45:22 Warning: Cannot receive version number from controller. Your controller is either not programmed or running a very old version of BrewPi. Please upload a new version of BrewPi to your controller.
Jan 24 2017 21:49:25 Serial Error: [Errno 5] Input/output error)
Jan 24 2017 21:50:48 Opening serial port
Jan 24 2017 21:50:48 Notification: Script started for beer 'My First BrewPi Run'
Jan 24 2017 21:50:58 Checking software version on controller... 
Jan 24 2017 21:51:08 Warning: Cannot receive version number from controller. Your controller is either not programmed or running a very old version of BrewPi. Please upload a new version of BrewPi to your controller.
**** Arduino Program script started ****
Settings will not be restored
Devices will not be restored
Jan 24 2017 21:59:39 Opening serial port
Loading programming settings from board.txt
Checking hex file size with avr-size...
Program size: 26896 bytes out of max 32256
ERROR: could not find port in bootloader
Traceback (most recent call last):
File "/home/brewpi/chamber2/brewpi.py", line 649, in 
{'settings': restoreSettings, 'devices': restoreDevices})
File "/home/brewpi/chamber2/programController.py", line 163, in programController
return programmer.program(hexFile, system1File, system2File, useDfu, restoreWhat)
File "/home/brewpi/chamber2/programController.py", line 274, in program
if not self.flash_file(hexFile):
File "/home/brewpi/chamber2/programController.py", line 650, in flash_file
' -C ' + avrconf)
TypeError: cannot concatenate 'str' and 'NoneType' objects
Jan 24 2017 22:00:03 Opening serial port
Jan 24 2017 22:00:03 Notification: Script started for beer 'My First BrewPi Run'
Jan 24 2017 22:00:13 Checking software version on controller... 
Jan 24 2017 22:00:23 Warning: Cannot receive version number from controller. Your controller is either not programmed or running a very old version of BrewPi. Please upload a new version of BrewPi to your controller.

Think that's for another night, though. Definitely made the breakthrough!!!

Did I mention adding rfcomm commands to the LXDE autostart file for user = pi?

NO YOU DIDN'T!!! But having done it, on the latest reboot and both modules are giving me the happy double-blink every couple of seconds without manual entry. Perfecto! Two questions, though:

I did try creating the pin file, but even running as root, it's saying I don't have permission to access /var/lib/bluetooth/ - is it still necessary, or do I need to do something else?
If rfcomm0 and rfcomm1 are being assigned in the autostart file, what's the point of the rfcomm.cfg file?

 

[day_trippr]

[...]I did try creating the pin file, but even running as root, it's saying I don't have permission to access /var/lib/bluetooth/ - is it still necessary, or do I need to do something else?

"pin file"? You lost me.

If rfcomm0 and rfcomm1 are being assigned in the autostart file, what's the point of the rfcomm.cfg file?

Excellent question! On Wheezy rfcomm loads on boot without intervention and uses the rfcomm.conf file to bring BT agents on line, so I tried using the same on Jessie in those weeks chasing one issue after another (not just Bluetooth, there were LOTS of stupid problems that should never made it into the wild, and some still persist today...but I digress).

As it appears rfcomm on Jessie no longer loads on boot and requires prodding (which we do from the LXDE autostart file now) there's likely no point in editing that file as all the same values are in the commands.

But I haven't deleted mine yet

Cheers!

 

[wbarber69]

You won't ever be able to program the arduino over Bluetooth… ever, never, ever, never gonna happen. if you know the arduino is programmed then you can forget that message. you'll also see a bunch of error messages over time after you get it working about too many instances running and bs like that but it will just work. more than likely yours has been working but you've been staring at the logs and starting over every time it's thrown up an error. Once the bt is connected it can take up to 10 minutes for the system to update that it's working and then you'll be able to bring up the webui and everything should be okay. but as long as you're on bt you won't be able to program the arduino

 

[LBussy]

Connection does seem a little spotty - it will occasionally give me a "cannot receive LCD text from script" message.

This is not connectivity but a timeout on the web server. The following will help:

sudo sed -i -e 's/KeepAliveTimeout 5/KeepAliveTimeout 99/g' /etc/apache2/apache2.conf

sudo service apache2 restart

 

[user 40839]

"pin file"? You lost me.

You'd mentioned earlier in the thread (and have seen it mentioned elsewhere) that a pincodes file needed to be created in /var/lib/bluetooth/ to contain the various pins for the HC-05 (1234). But since I assume this works in tandem with the rfcomm.conf file, it's unnecessary?

You won't ever be able to program the arduino over Bluetooth… ever, never, ever, never gonna happen. if you know the arduino is programmed then you can forget that message. you'll also see a bunch of error messages over time after you get it working about too many instances running and bs like that but it will just work. more than likely yours has been working but you've been staring at the logs and starting over every time it's thrown up an error. Once the bt is connected it can take up to 10 minutes for the system to update that it's working and then you'll be able to bring up the webui and everything should be okay. but as long as you're on bt you won't be able to program the arduino

Nah, I had it running for about two hours last night, and while minion 1 seemed to work, minion 2 never progressed beyond telling me to update the script. I shut everything down before bed, and this morning minion 2 is still the same. Minion 1 has devolved back to not being seen (but both BT cards are giving the double pulse every couple of seconds to indicate they're paired). Both minions seem to be functioning normally on their own (at least in terms of the LCD panel and activity with their relay blocks) just having trouble talking to the Pi.

This is not connectivity but a timeout on the web server. The following will help:

sudo sed -i -e 's/KeepAliveTimeout 5/KeepAliveTimeout 99/g' /etc/apache2/apache2.conf

sudo service apache2 restart

Ooop, will give that a go. Cheers!

 

[day_trippr]

You'd mentioned earlier in the thread (and have seen it mentioned elsewhere) that a pincodes file needed to be created in /var/lib/bluetooth/ to contain the various pins for the HC-05 (1234). But since I assume this works in tandem with the rfcomm.conf file, it's unnecessary?[...]

Must've been someone else, I just checked the build logs from all of my RPi systems and I've never done anything in /var/lib/bluetooth.
So I'm fairly confident whatever it was, it's not needed

Cheers!

 

[user 40839]

Must've been someone else, I just checked the build logs from all of my RPi systems and I've never done anything in /var/lib/bluetooth.
So I'm fairly confident whatever it was, it's not needed

Cheers!

*cough ahem cough*

Well that was probably the easiest thing I've tried on an RPi so far.

I have a pair of HC-05s and an HC-06 connnected to my test crate right now, using rfcomm0 through rfcomm2.

I set up my PIN file in /var/lib/bluetooth/00:1A:7DA:71:0A/pincodes (<= my BT dongle MAC) and it looks like this:

98:d3:31:b4:49:ac 1234
98:d3:31:b4:4a:33 1234
30:14:09:02:06:22 1234

(Just pulling yer leg, I really really appreciate your help and all your efforts in getting homemade BrewPis back to the masses, instead of us all being shoved towards quasi-functioning sparks!)

 

[day_trippr]

sonovabeyotch!

My bad. I'm usually uber religious about updating my system logs with any changes or experiments but for whatever reason I don't have a trace of that activity.

I definitely didn't need it with Jessie, and looking at my RPi fleet I didn't need it on Wheezy, either.

Sorry 'bout that...

Cheers!