Ankündigung

Einklappen

Serverwartung 21.2.



Am 21.2. im Laufe des späten Abends wird eine Serverwartung durchgeführt. Das Forum ist dadurch für gut zwei Stunden nicht erreichbar.
Es wird eine Wartungsseite geschaltet.

Mehr anzeigen
Weniger anzeigen

Probleme KNXD und USB

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    Probleme KNXD und USB

    Hi,

    habe folgendes Problem mit der GIRA USB-Schnittstelle und dem KNX Deamon. Ich bekomme folgende Fehlermeldung


    root@raspberrypi:~# knxd /etc/knxd.conf
    E00000055: There is no KNX addr= in section 'main'.
    F00000000: Error setting up the KNX router.

    kann mir jedmand sagen was hier zu tun ist?

    Gruß Olli

    #2
    Erste Fehlermeldung ist wg jetzt kommt diese

    [2017-2-22 21:01:32] [homebridge-knx.KNX] DEBUG got dest=4097
    [2017-2-22 21:01:32] [homebridge-knx.KNX] [ERROR] knxwritepenTGroup: Error: request invalid

    Kommentar


      #3
      http://michlstechblog.info/blog/rasp...ter-with-knxd/

      Ein super gutes TUT, vielleicht hilft dir das weiter.

      Kommentar


        #4
        Hi, I'm having the same issue:

        pi@raspberrypi:/var/lib/homebridge$ knxd -V
        knxd 0.14.1-3:010b207
        Usage: knxd configfile [main-section]

        pi@raspberrypi:/var/lib/homebridge$ knxd /etc/knxd.conf
        [ 1:main] E00000055: There is no KNX addr= in section 'main'.
        [ 1:main] F00000000: Error setting up the KNX router.
        pi@raspberrypi:/var/lib/homebridge$


        Can someone please help.
        How can I install version 12?

        Kommentar


          #5
          migabc Sorry about that, I had a brain fart while setting up the installation of that stuff. Will be fixed tomorrow in v0.14.

          To get v0.12, check out the "stable" branch. "git checkout stable" should work; if not, do "git checkout -b stable origin/stable".
          DistKV, Home Assistant, 1wire, KNX, Python, Asterisk, SMD-Lötkolben

          Kommentar


            #6
            Great.
            Thanks a lot

            Are there many changes with v0.14?

            You say:
            • knxd is now configured with a .ini-style configuration file.

              The old way of configuring knxd via a heap of position-dependent arguments is still supported.
            Does this mean that it is still backwards compatible with /etc/knxd.conf KNXD_OPTS arguments?

            Kommentar


              #7
              Yes it's backwards compatible. Startup hasn't changed (yet). A postinst script to auto-convert the knxd.conf file is on the menu for 0.16 or so.

              See the README for the list of changes. They're somewhat intrusive, as I needed to clean up a few things.
              DistKV, Home Assistant, 1wire, KNX, Python, Asterisk, SMD-Lötkolben

              Kommentar


                #8
                Thanks for the heads up.
                I'm using:
                $ cat /etc/knxd.conf | grep ^KNXD_OPTS
                KNXD_OPTS="-e 0.0.100 -E 0.0.101:7 -D -T -R -S -b usb:2:5:1:0"

                Will I have any issues on v0.14?

                Is the new version ready?

                Kommentar


                  #9
                  Should work (with the possible exception of ETS which I haven't yet had time to test).

                  NB: "cat FOO | grep BAR" is more succinctly written as "grep BAR <FOO".
                  DistKV, Home Assistant, 1wire, KNX, Python, Asterisk, SMD-Lötkolben

                  Kommentar


                    #10
                    I see you've updated knxd with a new version:

                    pi@raspberrypi:$ knxd -V
                    knxd 0.14.1-4
                    Usage: knxd configfile [main-section]

                    I got it running with default config:

                    pi@raspberrypi:$ ps -ef | grep knxd
                    knxd 19493 1 0 11:05 ? 00:00:00 /usr/bin/knxd -e 0.0.1 -E 0.0.2:8 -u /tmp/eib -b ip:


                    But the knxd does not seem to be listening on port 6720:

                    pi@raspberrypi:/var/lib/homebridge$ knxtool groupswrite ip:localhost 0/0/3 1
                    Open failed: Connection refused

                    pi@raspberrypi:/var/lib/homebridge$ netstat -na | grep 6720
                    pi@raspberrypi:/var/lib/homebridge$

                    Still some issues with this new version or have I done something wrong?

                    Kommentar


                      #11
                      I put in the option "-i 6720" and now it's OK.

                      pi@raspberrypi:~$ ps -ef | grep knxd
                      knxd 2169 1 0 11:45 ? 00:00:00 /usr/bin/knxd -e 0.0.1 -E 0.0.2:8 -i 6720 -u /tmp/eib -b ip:

                      pi@raspberrypi:~$ knxtool groupswrite ip:localhost 0/0/3 1
                      Send request

                      I thought port 6720 was default. Not anymore?

                      Kommentar


                        #12
                        Now I added my USB interface:

                        pi@raspberrypi:~$ lsusb | grep 135e
                        Bus 001 Device 004: ID 135e:0022

                        pi@raspberrypi:~$ cat /etc/knxd.conf | grep ^KNXD_OPTS
                        KNXD_OPTS="-e 0.0.100 -E 0.0.101:7 -D -T -R -S -i 6720 -b usb:1:4:1:0"

                        But the knxd fails to start up with this error:


                        Mar 19 12:25:24 raspberrypi systemd[1]: Starting KNX Daemon...
                        Mar 19 12:25:24 raspberrypi knxd[2635]: libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/001/004: Permission denied
                        Mar 19 12:25:24 raspberrypi knxd[2635]: libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.
                        Mar 19 12:25:24 raspberrypi knxd[2635]: [10:B.usb] E00000032: B.usb: setup B.usb: failed
                        Mar 19 12:25:24 raspberrypi knxd[2635]: [ 1:main] F00000000: Error setting up the KNX router.
                        Mar 19 12:25:24 raspberrypi systemd[1]: knxd.service: main process exited, code=exited, status=1/FAILURE
                        Mar 19 12:25:24 raspberrypi systemd[1]: Failed to start KNX Daemon.
                        Mar 19 12:25:24 raspberrypi systemd[1]: Unit knxd.service entered failed state.

                        The USB interface belongs to root and knxd is running as knxd

                        pi@raspberrypi:~$ ls -l /dev/bus/usb/001/004
                        crw-rw-r-- 1 root root 189, 3 Mar 19 12:16 /dev/bus/usb/001/004

                        Any ideia on how to fix this?

                        Kommentar


                          #13
                          Hi

                          create an udev-rule to change the group for your usb-device to knxd, e.g.


                          cat /etc/udev/rules.d/90-knxusb-devices.rules

                          # Siemens KNX
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0111", ACTION=="add", GROUP="knxd", MODE="0664"
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0112", ACTION=="add", GROUP="knxd", MODE="0664"
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0681", ATTR{idProduct}=="0014", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Merlin Gerin KNX-USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0141", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Hensel KNX-USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0121", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Busch-Jaeger KNX-USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="145c", ATTR{idProduct}=="1330", ACTION=="add", GROUP="knxd", MODE="0664"
                          SUBSYSTEM=="usb", ATTR{idVendor}=="145c", ATTR{idProduct}=="1490", ACTION=="add", GROUP="knxd", MODE="0664"
                          # ABB STOTZ-KONTAKT KNX-USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="147b", ATTR{idProduct}=="5120", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Feller KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0026", ACTION=="add", GROUP="knxd", MODE="0664"
                          # JUNG KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0023", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Gira KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0022", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Berker KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0021", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Insta KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0020", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Weinzierl KNX-USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0104", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Weinzierl KNX-USB Interface (RS232)
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0103", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Weinzierl KNX-USB Interface (Flush mounted)
                          SUBSYSTEM=="usb", ATTR{idVendor}=="0e77", ATTR{idProduct}=="0102", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Tapko USB Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="16d0", ATTR{idProduct}=="0490", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Hager KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0025", ACTION=="add", GROUP="knxd", MODE="0664"
                          # preussen automation USB2KNX
                          SUBSYSTEM=="usb", ATTR{idVendor}=="16d0", ATTR{idProduct}=="0492", ACTION=="add", GROUP="knxd", MODE="0664"
                          # Merten KNX-USB Data Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="135e", ATTR{idProduct}=="0024", ACTION=="add", GROUP="knxd", MODE="0664"
                          # b+b EIBWeiche USB
                          SUBSYSTEM=="usb", ATTR{idVendor}=="04cc", ATTR{idProduct}=="0301", ACTION=="add", GROUP="knxd", MODE="0664"
                          # MDT KNX_USB_Interface
                          SUBSYSTEM=="usb", ATTR{idVendor}=="16d0", ATTR{idProduct}=="0491", ACTION=="add", GROUP="knxd", MODE="0664"
                          afterwards reload the rules (udevadm) and trigger them. Easy way to do so is to remove and plugin the device.

                          Regards
                          Gunnar

                          Kommentar


                            #14
                            Great!
                            That solved it.
                            I can now turn on/off my KNX devices :-)

                            P.S: I'm currently using this KNX USB Interface for testing purposes (borrowed it from my Gira HomeServer).
                            For this project I have ordered a new KNX USB interface which will be dedicated for the RasPI

                            TUL - TPUART USB
                            http://busware.de/tiki-index.php?page=TUL

                            I'm currently waiting on delivery for this product.

                            Is this TUL in your list above?
                            If not which attributes should should I configure?

                            P.S. Will this TUL work just the same as the GIRA USB-KNX interface?

                            Thanks.
                            Miguel

                            Kommentar


                              #15
                              TUL is OK, "-b tpuarts:/dev/ttyKNX1" (if you install the appropriate udev rule)

                              The "-i 6720" part is the default if you start with systemd and start+enable knxd.socket, this should happen automatically upon installation.

                              gklein Ist die Liste vollständig? dann installiere ich die mal mit dem knxd …
                              DistKV, Home Assistant, 1wire, KNX, Python, Asterisk, SMD-Lötkolben

                              Kommentar

                              Lädt...
                              X