[Pi IoT] - Smarter Spaces #3 - Remote Horse Feeder System

9 Jul 2016

So, I was able to get the iLumi controlled via a python script that in turn I was able to add to OpenHAB and could control the iLumi BR30 from an OpenHAB ColorPicker, however when I attempted to add the EnOcean Pi 902 to the Raspberry Pi 3 and performed the update/upgrade to support the device I lost both the Wi-Fi and the Bluetooth functionality of the Raspberry Pi 3. I was able to recover the W-Fi connection on the RasPi 3 by performing a dist-upgrade and then updating the firmware on the system to 4.4.3. This corrected the Wi-Fi issue but I am still unable to get the Bluetooth device on the RasPi 3 to enable. The system seems to think there is no bluetooth device on the board which I know there is one since it was working prior to the upbreak. I'll have to see if I can get this to come up again or just add a usb bluetooth dongle to the board to get past it.

This assisted me in getting the WiFi back up and working:

http://raspberrypi.stackexchange.com/questions/43474/how-to-enable-wi-fi-channel-12-on-raspberry-pi-3

Also, I was never able to get the RasPi to see the EnOcean Pi 902 so I was wondering if anyone knew if the device is supported with Raspberry Pi 3 and Jessie or do I need to use the RasPi B+ to connect the EnOcean Pi 902.

Top Comments

Parents

jomoenginer over 9 years ago

Still no success with getting the BLE device to enable, but I did find some more info regarding this. Apparently at kernel 4.4.9 there was a switch from ttyAMA0 to serial1; I'm currently running with 4.4.14-v7+. I've gone through a few iterations of updates and reinstall of packages and reverted the settings back to use the UART for the BLE device but the device still will not enable.

This is what I see from hciuart.service status

pi@raspberrypi:~ $ sudo systemctl -l status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
Active: failed (Result: exit-code) since Sun 2016-07-10 11:45:36 PDT; 35s ago
Process: 524 ExecStart=/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow - (code=exited, status=1/FAILURE)

Jul 10 11:45:36 raspberrypi hciattach[524]: Failed to reset chip, invalid HCI event
Jul 10 11:45:36 raspberrypi hciattach[524]: Can't initialize device: Success
Jul 10 11:45:36 raspberrypi hciattach[524]: bcm43xx_init
Jul 10 11:45:36 raspberrypi hciattach[524]: Flash firmware /lib/firmware/BCM43430A1.hcd
Jul 10 11:45:36 raspberrypi systemd[1]: hciuart.service: control process exited, code=exited status=1
Jul 10 11:45:36 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Jul 10 11:45:36 raspberrypi systemd[1]: Unit hciuart.service entered failed state.

This is the link I am following:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=148305
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel
jomoenginer over 9 years ago in reply to jomoenginer

Okay, finally a bit of success.     After searching the web and attempting many changes to the RasPi 3 config, I finally stumbled on the needed info to get the On Board BLE device working again on the RasPi 3. I am not sure what got it to the state it was in, but it is all working now.
This is what I found:
To fix the issue with the On Board BLE (hci0) not showing after an update on the RasPi 3, I followed the info in the following post, although I do not know what is being said: (NOTE: I have since found some of the info in other links but this one listed the steps more logically:
http://www.fhemwiki.de/wiki/Raspberry_Pi_3:_GPIO-Port_Module_und_Bluetooth

1. Edit /boot/config.txt and add the following:

      BLE Fix:
      sudo view /boot/config.txt

     # Additial overlays
     dtoverlay=pi3-miniuart-bt
     force_turbo=1

     # Enable UART
     enable_uart=1
     #force_turbo=1

2. Edit /boot/cmdline/txt
Add "core_freq=250" to the end of the cmdline string:
    dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait core_freq=250

3. Edit "hciuart.service" change "ttyAMA0" to "ttyS0" if not already set.
     $ sudo view /lib/systemd/system/hciuart.service

     [Unit]
     Description=Configure Bluetooth Modems connected by UART
     ConditionPathIsDirectory=/proc/device-tree/soc/gpio@7e200000/bt_pins
     Before=bluetooth.service
     After=dev-ttyS0.device

     [Service]
     Type=forking
     ExecStart=/usr/bin/hciattach /dev/ttyS0 bcm43xx 921600 noflow -

4. Add a "sleep 10" to the start section in the "fhem" init script if using FHEM.
    $ sudo view /etc/init.d/fhem

     case "$1" in
     'start')
             echo "Starting fhem..."
             perl fhem.pl fhem.cfg
             RETVAL=$?
            sleep 10
             ;;

After performing these steps and rebooting the board, the on board BLE device should show up again:
In my case I still had the USB BLE Dongle installed so both hci devices were listed in the hcitool listing from bluez:
      $ sudo hcitool dev
     Devices:
       hci1 B8:27:EB:0A:18:49 <-- On Board RasPi 3 BLE device
       hci0 5C:F3:70:6E:13:4B <-- USB BLE Dongle

      $ sudo hciconfig
     hci1: Type: BR/EDR Bus: UART
       BD Address: B8:27:EB:0A:18:49 ACL MTU: 1021:8 SCO MTU: 64:1
       UP RUNNING
       RX bytes:717 acl:0 sco:0 events:42 errors:0
       TX bytes:1560 acl:0 sco:0 commands:45 errors:0

    hci0: Type: BR/EDR Bus: USB
       BD Address: 5C:F3:70:6E:13:4B ACL MTU: 1021:8 SCO MTU: 64:1
       UP RUNNING
       RX bytes:4967 acl:44 sco:0 events:348 errors:0
       TX bytes:4942 acl:45 sco:0 commands:226 errors:0

The /dev/serial* to tty mapping is now as follows:
$ ls -lt /dev/serial*
lrwxrwxrwx 1 root root 5 Jul 16 22:59 /dev/serial1 -> ttyS0
lrwxrwxrwx 1 root root 7 Jul 16 22:59 /dev/serial0 -> ttyAMA0

Looking at the Fhem messages, we can see the EnOcean Pi is still working:

// Fhem messages
Events:
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: pressed
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 channelB: B0
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 A0,B0
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: released
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: released
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 buttons: pressed
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 channelB: BI
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 AI,BI

NOTE: I found if Fhem init script was up and running, the EnOcean script would not display any events from the Pi device, thus I shut down the Fhem process prior to running the EnOcean script or before running the OpenHab start script.

pi@raspberrypi:~ $ sudo /etc/init.d/fhem status
fhem is running
pi@raspberrypi:~ $ sudo /etc/init.d/fhem stop
Stopping fhem...
pi@raspberrypi:~ $ cd EnOceanSpy/
pi@raspberrypi:~/EnOceanSpy $ sudo ./EnOceanSpy /dev/ttyAMA0
Starting EnOceanSpy...
2016-07-16 10:05:14 55 00 07 07 01 7A F6 70 00 2B A8 20 B0 01 FF FF FF FF 30 00 E5
2016-07-16 10:05:15 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 33 00 97 55 00 07 07 01 7A F6 10 00 2B A8 20 B0 01 FF FF FF FF 36 00 9E
2016-07-16 10:05:16 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 34 00 FC 55 00 07 07 01 7A F6 37 00 2B A8 20 B0 01 FF FF FF FF 45 00 18 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 42 00 20

If needed, Change the OpenHAB serial port setting to ttyAMA0:
$ view configurations/openhab.cfg

     # EnOcean USB adapter serial port
     enocean:serialPort=/dev/ttyAMA0

Initially, after doing all of this and seeing both the On Board BLE device working as well as the EnOcean device working, when I started OpenHAB, the PTM 210 U events were not being reported by OpenHAB. However, I did find a blogpost posting by Kai Kreuzer (The Creator of OpenHAB) regarding this issue.
http://kaikreuzer.blogspot.com/2014/08/forget-me-not-with-openhab-and-enocean.html

He states:
“… Unfortunately, the RXTX library that is used by openHAB for connecting to serial ports does not consider /dev/ttyAMA0 to be a standard port and thus simply does not recognise it. You therefore have to explicitly declare it through the JVM parameter "-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0" in the start(_debug).sh launch script.”

I added the following heading:
echo Launching the openHAB runtime...
java \

    -Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0 \

After this, I was able to see the events from the EnOcean Pi via OpenHAB again when pressing the PTM 210u switch..

Messages from openhab.log:
2016-07-17 01:33:23.303 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:23.315 [INFO ] [g.openhab.io.net.exec.ExecUtil] - executed commandLine 'sudo /usr/bin/python /opt/openhab/configurations/scripts/test2.py iLumi1 255 255 255'
2016-07-17 01:33:23.317 [INFO ] [penhab.model.script.EnOcean On] - Send on
2016-07-17 01:33:23.499 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:27.107 [INFO ] [penhab.model.script.EnOcean On] - Trying to run python script
2016-07-17 01:33:27.118 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:27.126 [INFO ] [g.openhab.io.net.exec.ExecUtil] - executed commandLine 'sudo /usr/bin/python /opt/openhab/configurations/scripts/test2.py iLumi1 0 0 0'
2016-07-17 01:33:27.128 [INFO ] [penhab.model.script.EnOcean On] - Send off
2016-07-17 01:33:27.337 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script

Now, the only thing left is to get the EnOcean Pi to recognize other EnOcean sensors. Thus, far I have not been successful with this, but that is something for a later time.

I’ll create another post to outline how I am controlling the ilimi BR30 with the EnOcean PTM 210U via OpenhHAB.
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel

Comment

jomoenginer over 9 years ago in reply to jomoenginer

Okay, finally a bit of success.     After searching the web and attempting many changes to the RasPi 3 config, I finally stumbled on the needed info to get the On Board BLE device working again on the RasPi 3. I am not sure what got it to the state it was in, but it is all working now.
This is what I found:
To fix the issue with the On Board BLE (hci0) not showing after an update on the RasPi 3, I followed the info in the following post, although I do not know what is being said: (NOTE: I have since found some of the info in other links but this one listed the steps more logically:
http://www.fhemwiki.de/wiki/Raspberry_Pi_3:_GPIO-Port_Module_und_Bluetooth

1. Edit /boot/config.txt and add the following:

      BLE Fix:
      sudo view /boot/config.txt

     # Additial overlays
     dtoverlay=pi3-miniuart-bt
     force_turbo=1

     # Enable UART
     enable_uart=1
     #force_turbo=1

2. Edit /boot/cmdline/txt
Add "core_freq=250" to the end of the cmdline string:
    dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait core_freq=250

3. Edit "hciuart.service" change "ttyAMA0" to "ttyS0" if not already set.
     $ sudo view /lib/systemd/system/hciuart.service

     [Unit]
     Description=Configure Bluetooth Modems connected by UART
     ConditionPathIsDirectory=/proc/device-tree/soc/gpio@7e200000/bt_pins
     Before=bluetooth.service
     After=dev-ttyS0.device

     [Service]
     Type=forking
     ExecStart=/usr/bin/hciattach /dev/ttyS0 bcm43xx 921600 noflow -

4. Add a "sleep 10" to the start section in the "fhem" init script if using FHEM.
    $ sudo view /etc/init.d/fhem

     case "$1" in
     'start')
             echo "Starting fhem..."
             perl fhem.pl fhem.cfg
             RETVAL=$?
            sleep 10
             ;;

After performing these steps and rebooting the board, the on board BLE device should show up again:
In my case I still had the USB BLE Dongle installed so both hci devices were listed in the hcitool listing from bluez:
      $ sudo hcitool dev
     Devices:
       hci1 B8:27:EB:0A:18:49 <-- On Board RasPi 3 BLE device
       hci0 5C:F3:70:6E:13:4B <-- USB BLE Dongle

      $ sudo hciconfig
     hci1: Type: BR/EDR Bus: UART
       BD Address: B8:27:EB:0A:18:49 ACL MTU: 1021:8 SCO MTU: 64:1
       UP RUNNING
       RX bytes:717 acl:0 sco:0 events:42 errors:0
       TX bytes:1560 acl:0 sco:0 commands:45 errors:0

    hci0: Type: BR/EDR Bus: USB
       BD Address: 5C:F3:70:6E:13:4B ACL MTU: 1021:8 SCO MTU: 64:1
       UP RUNNING
       RX bytes:4967 acl:44 sco:0 events:348 errors:0
       TX bytes:4942 acl:45 sco:0 commands:226 errors:0

The /dev/serial* to tty mapping is now as follows:
$ ls -lt /dev/serial*
lrwxrwxrwx 1 root root 5 Jul 16 22:59 /dev/serial1 -> ttyS0
lrwxrwxrwx 1 root root 7 Jul 16 22:59 /dev/serial0 -> ttyAMA0

Looking at the Fhem messages, we can see the EnOcean Pi is still working:

// Fhem messages
Events:
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: pressed
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 channelB: B0
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 A0,B0
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: released
2016-07-16 09:56:31 EnOcean EnO_switch_002BA820 buttons: released
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 buttons: pressed
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 channelB: BI
2016-07-16 09:56:33 EnOcean EnO_switch_002BA820 AI,BI

NOTE: I found if Fhem init script was up and running, the EnOcean script would not display any events from the Pi device, thus I shut down the Fhem process prior to running the EnOcean script or before running the OpenHab start script.

pi@raspberrypi:~ $ sudo /etc/init.d/fhem status
fhem is running
pi@raspberrypi:~ $ sudo /etc/init.d/fhem stop
Stopping fhem...
pi@raspberrypi:~ $ cd EnOceanSpy/
pi@raspberrypi:~/EnOceanSpy $ sudo ./EnOceanSpy /dev/ttyAMA0
Starting EnOceanSpy...
2016-07-16 10:05:14 55 00 07 07 01 7A F6 70 00 2B A8 20 B0 01 FF FF FF FF 30 00 E5
2016-07-16 10:05:15 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 33 00 97 55 00 07 07 01 7A F6 10 00 2B A8 20 B0 01 FF FF FF FF 36 00 9E
2016-07-16 10:05:16 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 34 00 FC 55 00 07 07 01 7A F6 37 00 2B A8 20 B0 01 FF FF FF FF 45 00 18 55 00 07 07 01 7A F6 00 00 2B A8 20 A0 01 FF FF FF FF 42 00 20

If needed, Change the OpenHAB serial port setting to ttyAMA0:
$ view configurations/openhab.cfg

     # EnOcean USB adapter serial port
     enocean:serialPort=/dev/ttyAMA0

Initially, after doing all of this and seeing both the On Board BLE device working as well as the EnOcean device working, when I started OpenHAB, the PTM 210 U events were not being reported by OpenHAB. However, I did find a blogpost posting by Kai Kreuzer (The Creator of OpenHAB) regarding this issue.
http://kaikreuzer.blogspot.com/2014/08/forget-me-not-with-openhab-and-enocean.html

He states:
“… Unfortunately, the RXTX library that is used by openHAB for connecting to serial ports does not consider /dev/ttyAMA0 to be a standard port and thus simply does not recognise it. You therefore have to explicitly declare it through the JVM parameter "-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0" in the start(_debug).sh launch script.”

I added the following heading:
echo Launching the openHAB runtime...
java \

    -Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0 \

After this, I was able to see the events from the EnOcean Pi via OpenHAB again when pressing the PTM 210u switch..

Messages from openhab.log:
2016-07-17 01:33:23.303 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:23.315 [INFO ] [g.openhab.io.net.exec.ExecUtil] - executed commandLine 'sudo /usr/bin/python /opt/openhab/configurations/scripts/test2.py iLumi1 255 255 255'
2016-07-17 01:33:23.317 [INFO ] [penhab.model.script.EnOcean On] - Send on
2016-07-17 01:33:23.499 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:27.107 [INFO ] [penhab.model.script.EnOcean On] - Trying to run python script
2016-07-17 01:33:27.118 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script
2016-07-17 01:33:27.126 [INFO ] [g.openhab.io.net.exec.ExecUtil] - executed commandLine 'sudo /usr/bin/python /opt/openhab/configurations/scripts/test2.py iLumi1 0 0 0'
2016-07-17 01:33:27.128 [INFO ] [penhab.model.script.EnOcean On] - Send off
2016-07-17 01:33:27.337 [INFO ] [enhab.model.script.EnOcean Off] - Trying to run python script

Now, the only thing left is to get the EnOcean Pi to recognize other EnOcean sensors. Thus, far I have not been successful with this, but that is something for a later time.

I’ll create another post to outline how I am controlling the ilimi BR30 with the EnOcean PTM 210U via OpenhHAB.
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel

Children

No Data