Announcement

Collapse
No announcement yet.

Zwave.me RaZberry Gpio on PI3B+

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Zwave.me RaZberry Gpio on PI3B+

    I replaced my PI2 by a PI3B+ after running the PI2 succesfully many years together with HS3.
    Problem is that I don't get HS3 to initialize the old version(small) of RaZberry with the PI3B+ . Note ID is missing.
    Installed al updates, removed it from network, factory reset, tried other plugins but nothing of this seems to work.
    What do I do wrong? I want to understand what I'm missing here.
    Thanks for support


  • #2
    If your /boot/config.txt file doesn't contain the following, add it to the end

    Code:
    # disable bluetooth function and restore serial0/ttyAMA0 over GPIO 14&15
    dtoverlay=pi3-disable-bt
    If /boot/cmdline.txt contains this clause, delete the clause.
    Code:
    console=serial0,115200

    Comment


    • #3
      Thanks for your reply Zwolfpack, but this did not work. The files are as you described.
      This is what is happening. How can I find out which other "system" is trying to connect?
      On the old PI2 it still works fine.

      mrt-17 15:17:53 Z-Wave Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
      mrt-17 15:17:41 Z-Wave Z-Wave.me: Getting node information from controller...
      mrt-17 15:17:41 Z-Wave Error Z-Wave.me: The Z-Wave.me interface did not respond to the request for the controller capabilities - it may be disconnected or malfunctioning (3).

      Comment


      • #4
        There is no other system - the log message is poorly worded. What you are seeing is what happens if there is no communication at all with the Z-Wave controller. Here is what I get when I try to connect with the GPIO card not installed:

        Mar-17 13:29:19 Z-Wave Internal: ============================================================ ==========
        Mar-17 13:29:19 Z-Wave Internal: ----------------------------------------------------------------------
        Mar-17 13:29:19 Z-Wave Initializing Z-Wave interface Internal (Internal) on /dev/ttyAMA0
        Mar-17 13:29:19 Z-Wave Internal: ----------------------------------------------------------------------
        Mar-17 13:29:19 Z-Wave Internal: The Z-Wave Command Execution Thread was Started or Restarted.
        Mar-17 13:29:19 Z-Wave Internal: The Z-Wave API Execution Thread was Started or Restarted.
        Mar-17 13:29:19 Z-Wave Internal: Getting node information from controller...
        Mar-17 13:29:32 Z-Wave Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
        Mar-17 13:29:32 Z-Wave Internal: Getting node information from controller...
        Mar-17 13:29:34 Z-Wave Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.

        The previously mentioned boot file modifications are the only things I'm aware of to enable the internal interface.

        What version of the OS are you running?

        Code:
        more /etc/os-release
        I get:
        Code:
        PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
        NAME="Raspbian GNU/Linux"
        VERSION_ID="9"
        VERSION="9 (stretch)"
        ID=raspbian
        ID_LIKE=debian
        HOME_URL="http://www.raspbian.org/"
        SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
        BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
        Also run

        Code:
        udevadm info -a /dev/ttyAMA0
        I get
        Code:
        Udevadm info starts with the device specified by the devpath and then
        walks up the chain of parent devices. It prints for every device
        found, all possible attributes in the udev rules key format.
        A rule to match, can be composed by the attributes of the device
        and the attributes from one single parent device.
        
          looking at device '/devices/platform/soc/3f201000.serial/tty/ttyAMA0':
            KERNEL=="ttyAMA0"
            SUBSYSTEM=="tty"
            DRIVER==""
        
          looking at parent device '/devices/platform/soc/3f201000.serial':
            KERNELS=="3f201000.serial"
            SUBSYSTEMS=="amba"
            DRIVERS=="uart-pl011"
            ATTRS{driver_override}=="(null)"
            ATTRS{id}=="00241011"
            ATTRS{irq0}=="87"
        
          looking at parent device '/devices/platform/soc':
            KERNELS=="soc"
            SUBSYSTEMS=="platform"
            DRIVERS==""
            ATTRS{driver_override}=="(null)"
        
          looking at parent device '/devices/platform':
            KERNELS=="platform"
            SUBSYSTEMS==""
            DRIVERS==""

        Comment


        • #5
          Hi Zwolfpack
          I get

          HTML Code:
          [HTML]PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
          NAME="Raspbian GNU/Linux"
          VERSION_ID="9"
          VERSION="9 (stretch)"
          ID=raspbian
          ID_LIKE=debian
          HOME_URL="http://www.raspbian.org/"
          SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
          BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
          [/HTML]

          and
          HTML Code:
          Udevadm info starts with the device specified by the devpath and then
          walks up the chain of parent devices. It prints for every device
          found, all possible attributes in the udev rules key format.
          A rule to match, can be composed by the attributes of the device
          and the attributes from one single parent device.
          
            looking at device '/devices/platform/soc/3f201000.serial/tty/ttyAMA0':
              KERNEL=="ttyAMA0"
              SUBSYSTEM=="tty"
              DRIVER==""
          
            looking at parent device '/devices/platform/soc/3f201000.serial':
              KERNELS=="3f201000.serial"
              SUBSYSTEMS=="amba"
              DRIVERS=="uart-pl011"
              ATTRS{driver_override}=="(null)"
              ATTRS{id}=="00241011"
              ATTRS{irq0}=="87"
          
            looking at parent device '/devices/platform/soc':
              KERNELS=="soc"
              SUBSYSTEMS=="platform"
              DRIVERS==""
              ATTRS{driver_override}=="(null)"
          
            looking at parent device '/devices/platform':
              KERNELS=="platform"
              SUBSYSTEMS==""
              DRIVERS==""

          Comment


          • #6
            That all looks as it should.

            Are you running the ZeeS2 image or did you build your own?

            It's possible that the new card itself has an issue (hardware problem).

            Grasping at straws, what does this command show?

            Code:
            gpio readall

            Comment


            • #7
              This is what i get
              HTML Code:
              +-----+-----+---------+------+---+---Pi 3B+-+---+------+---------+-----+-----+
               | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
               +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
               |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
               |   2 |   8 |   SDA.1 |   IN | 1 |  3 || 4  |   |      | 5v      |     |     |
               |   3 |   9 |   SCL.1 |   IN | 1 |  5 || 6  |   |      | 0v      |     |     |
               |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT0 | TxD     | 15  | 14  |
               |     |     |      0v |      |   |  9 || 10 | 1 | ALT0 | RxD     | 16  | 15  |
               |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |
               |  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |
               |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
               |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |
               |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |
               |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
               |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |
               |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
               |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
               |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |
               |   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
               |  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
               |  19 |  24 | GPIO.24 |   IN | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
               |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | IN   | GPIO.28 | 28  | 20  |
               |     |     |      0v |      |   | 39 || 40 | 0 | IN   | GPIO.29 | 29  | 21  |
               +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
               | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
               +-----+-----+---------+------+---+---Pi 3B+-+---+------+---------+-----+-----+
              pi@raspberrypi:~ $
              Hardware problem seems not the case.
              When I place the card on my pi2 it works fine.
              I will try your make pakkage. See if HS is the cause of the issue.

              Comment


              • #8
                I installed your "make" pakkage, same issue.

                Comment


                • #9
                  Which make package? I've posted a few...

                  The gpio readall outout looks as expected.

                  When I said hardware problem, I was thinking of a problem with the new Pi, not with the Z-Wave daughter card.

                  Which product do you have - HS3-Pi or HS3 Linux ?

                  Comment


                  • #10
                    I've done a complete re-install of rasbian stretch, installed rpi-hs3.zip , updated the firmware of the Wave.me card and now it works!!
                    Thanks for the installer package and your support. I am a Happy Seer again!

                    Comment

                    Working...
                    X