Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. Mal wieder BLE Probleme

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Mal wieder BLE Probleme

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tenor 0 @Thomas Braun last edited by

      @thomas-braun
      BTMon sieht auch gut aus:

      Bluetooth monitor ver 5.72
      btmon[9941]: = Note: Linux version 6.8.0-45-generic (x86_64)                                                                                        0.998794
      btmon[9941]: = Note: Bluetooth subsystem version 2.22                                                                                               0.998797
      = New Index: 8C:88:4B:05:62:63 (Primary,USB,hci0)                                                                                            [hci0] 0.998799
      = Open Index: 8C:88:4B:05:62:63                                                                                                              [hci0] 0.998799
      = Index Info: 8C:88:4B:05:62:63 (Realtek Semiconductor Corporation)                                                                          [hci0] 0.998800
      node[9403]: @ RAW Open: node (privileged) version 2.22                                                                              {0x0002} [hci0] 0.998801
      bluetoothd[3925]: @ MGMT Open: bluetoothd (privileged) version 1.22                                                                        {0x0001} 0.998803
      
      node[9403]: @ RAW Close: node                                                                                                      {0x0002} [hci0] 36.721193
      node[10055]: @ RAW Open: node (privileged) version 2.22                                                                            {0x0002} [hci0] 40.825724
      node[10055]: < HCI Command: Set Event Mask (0x03|0x0001) plen 8                                                                          #1 [hci0] 40.826612
              Mask: 0x3dbff807fffbffff
                Inquiry Complete
                Inquiry Result
                Connection Complete
                Connection Request
                Disconnection Complete
                Authentication Complete
                Remote Name Request Complete
                Encryption Change
                Change Connection Link Key Complete
                Link Key Type Changed
                Read Remote Supported Features Complete
                Read Remote Version Information Complete
                QoS Setup Complete
                Command Complete
                Command Status
                Hardware Error
                Flush Occurred
                Role Change
                Mode Change
                Return Link Keys
                PIN Code Request
                Link Key Request
                Link Key Notification
                Loopback Command
                Data Buffer Overflow
                Max Slots Change
                Read Clock Offset Complete
                Connection Packet Type Changed
                QoS Violation
                Page Scan Mode Change
                Page Scan Repetition Mode Change
                Flow Specification Complete
                Inquiry Result with RSSI
                Read Remote Extended Features Complete
                Synchronous Connection Complete
                Synchronous Connection Changed
                Sniff Subrating
                Extended Inquiry Result
                Encryption Key Refresh Complete
                IO Capability Request
                IO Capability Request Reply
                User Confirmation Request
                User Passkey Request
                Remote OOB Data Request
                Simple Pairing Complete
                Link Supervision Timeout Changed
                Enhanced Flush Complete
                User Passkey Notification
                Keypress Notification
                Remote Host Supported Features Notification
                LE Meta
      > HCI Event: Command Complete (0x0e) plen 4                                                                                              #2 [hci0] 40.927875
            Set Event Mask (0x03|0x0001) ncmd 2
              Status: Success (0x00)
      node[10055]: < HCI Command: LE Set Event Mask (0x08|0x0001) plen 8                                                                       #3 [hci0] 40.927956
              Mask: 0x000000000000001f
                LE Connection Complete
                LE Advertising Report
                LE Connection Update Complete
                LE Read Remote Used Features Complete
                LE Long Term Key Request
      > HCI Event: Command Complete (0x0e) plen 4                                                                                              #4 [hci0] 40.929794
            LE Set Event Mask (0x08|0x0001) ncmd 2
              Status: Success (0x00)
      node[10055]: < HCI Command: Read Local Version Information (0x04|0x0001) plen 0                                                          #5 [hci0] 40.929848
      > HCI Event: Command Complete (0x0e) plen 12                                                                                             #6 [hci0] 40.931813
            Read Local Version Information (0x04|0x0001) ncmd 2
              Status: Success (0x00)
              HCI version: Bluetooth 5.1 (0x0a) - Revision 57286 (0xdfc6)
              LMP version: Bluetooth 5.1 (0x0a) - Subversion 55586 (0xd922)
              Manufacturer: Realtek Semiconductor Corporation (93)
      node[10055]: < HCI Command: Write LE Host Supported (0x03|0x006d) plen 2                                                                 #7 [hci0] 40.931854
              Supported: 0x01
              Simultaneous: 0x00
      > HCI Event: Command Complete (0x0e) plen 4                                                                                              #8 [hci0] 40.933655
            Write LE Host Supported (0x03|0x006d) ncmd 2
              Status: Success (0x00)
      node[10055]: < HCI Command: Read LE Host Supported (0x03|0x006c) plen 0                                                                  #9 [hci0] 40.933716
      > HCI Event: Command Complete (0x0e) plen 6                                                                                             #10 [hci0] 40.935679
            Read LE Host Supported (0x03|0x006c) ncmd 2
              Status: Success (0x00)
              Supported: 0x01
              Simultaneous: 0x00
      node[10055]: < HCI Command: LE Read Buffer Size (0x08|0x0002) plen 0                                                                    #11 [hci0] 40.935729
      > HCI Event: Command Complete (0x0e) plen 7                                                                                             #12 [hci0] 40.937657
            LE Read Buffer Size (0x08|0x0002) ncmd 2
              Status: Success (0x00)
              Data packet length: 27
              Num data packets: 8
      node[10055]: < HCI Command: Read BD ADDR (0x04|0x0009) plen 0                                                                           #13 [hci0] 40.937715
      > HCI Event: Command Complete (0x0e) plen 10                                                                                            #14 [hci0] 40.939649
            Read BD ADDR (0x04|0x0009) ncmd 2
              Status: Success (0x00)
              Address: 8C:88:4B:05:62:63 (OUI 8C-88-4B)
      
      
      
      
      T 1 Reply Last reply Reply Quote 0
      • T
        Tenor 0 @Tenor 0 last edited by

        @tenor-0
        Der Neustart im Syslog

        2024-10-12T19:41:51.235429+02:00 server bluetoothd[4282]: Stopping SDP server
        2024-10-12T19:41:51.235456+02:00 server bluetoothd[4282]: Exit
        2024-10-12T19:41:51.235486+02:00 server bluealsa: bluez.c:1308: Signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved()
        2024-10-12T19:41:51.235506+02:00 server bluealsa: ba-adapter.c:144: Freeing adapter: hci0
        2024-10-12T19:41:51.236722+02:00 server systemd[1]: bluetooth.service: Deactivated successfully.
        2024-10-12T19:41:51.236949+02:00 server systemd[1]: Stopped bluetooth.service - Bluetooth service.
        2024-10-12T19:41:53.277298+02:00 server systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
        2024-10-12T19:41:53.509695+02:00 server systemd[1]: Configuration file /run/systemd/system/systemd-networkd-wait-online.service.d/10-netplan.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
        2024-10-12T19:41:53.906915+02:00 server systemd[1]: Starting bluetooth.service - Bluetooth service...
        2024-10-12T19:41:53.907273+02:00 server (uetoothd)[6107]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
        2024-10-12T19:41:53.956777+02:00 server bluetoothd[6107]: Bluetooth daemon 5.72
        2024-10-12T19:41:53.957787+02:00 server systemd[1]: Started bluetooth.service - Bluetooth service.
        2024-10-12T19:41:53.957851+02:00 server bluetoothd[6107]: Starting SDP server
        2024-10-12T19:41:53.957897+02:00 server bluetoothd[6107]: Excluding (cli) sap
        2024-10-12T19:41:53.958160+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support csip plugin
        2024-10-12T19:41:53.958198+02:00 server bluetoothd[6107]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
        2024-10-12T19:41:53.958224+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support micp plugin
        2024-10-12T19:41:53.958245+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support vcp plugin
        2024-10-12T19:41:53.958267+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support mcp plugin
        2024-10-12T19:41:53.958290+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support bass plugin
        2024-10-12T19:41:53.958312+02:00 server bluetoothd[6107]: src/plugin.c:plugin_init() System does not support bap plugin
        2024-10-12T19:41:53.958826+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
        2024-10-12T19:41:53.958997+02:00 server dbus-daemon[969]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.52' (uid=0 pid=6107 comm="/usr/libexec/bluetooth/bluetoothd --noplugin=sap" label="unconfined")
        2024-10-12T19:41:53.959038+02:00 server bluetoothd[6107]: Bluetooth management interface 1.22 initialized
        2024-10-12T19:41:53.959063+02:00 server bluetoothd[6107]: Battery Provider Manager created
        2024-10-12T19:41:53.959347+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
        2024-10-12T19:41:53.959464+02:00 server bluealsa: ba-adapter.c:53: Couldn't get HCI version: Network is down
        2024-10-12T19:41:53.959490+02:00 server bluealsa: bluez.c:783: Registering battery provider: /org/bluez/hci0/battery
        2024-10-12T19:41:53.960281+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/1
        2024-10-12T19:41:53.960311+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/1
        2024-10-12T19:41:53.960420+02:00 server bluetoothd[6107]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/source/1
        2024-10-12T19:41:53.960507+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/2
        2024-10-12T19:41:53.960529+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/2
        2024-10-12T19:41:53.960621+02:00 server bluetoothd[6107]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/source/2
        2024-10-12T19:41:53.960695+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/1
        2024-10-12T19:41:53.960716+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/1
        2024-10-12T19:41:53.960807+02:00 server bluetoothd[6107]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/sink/1
        2024-10-12T19:41:53.960876+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/2
        2024-10-12T19:41:53.960901+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/2
        2024-10-12T19:41:53.960982+02:00 server bluetoothd[6107]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/sink/2
        2024-10-12T19:41:53.961055+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
        2024-10-12T19:41:53.974784+02:00 server systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
        2024-10-12T19:41:54.051605+02:00 server dbus-daemon[969]: [system] Successfully activated service 'org.freedesktop.hostname1'
        2024-10-12T19:41:54.051794+02:00 server systemd[1]: Started systemd-hostnamed.service - Hostname Service.
        

        2 Probleme sehe ich da

        (uetoothd)[6107]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
        

        und

        2024-10-12T19:41:53.959464+02:00 server bluealsa: ba-adapter.c:53: Couldn't get HCI version: Network is down
        

        letzters scheint neu zu sein.
        Mittlerweile kommt

        matthias@server:~$ sudo hcitool lescan
        Set scan parameters failed: Broken pipe
        

        Alles was ich gemacht habe ist ein paar mal den Dienst neu gestartet zu haben

        Thomas Braun 2 Replies Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Tenor 0 last edited by

          @tenor-0

          Irgendwas haste da an den Rechten verfummelt...

          systemctl cat bluetooth.service
          

          sagt?

          T 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Tenor 0 last edited by

            @tenor-0

            CAPs gesetzt?
            Jag den

            iobroker fix
            

            über das System, ich glaube der setzt die auch. Aber NICHT als root!

            T 1 Reply Last reply Reply Quote 0
            • T
              Tenor 0 @Thomas Braun last edited by

              @thomas-braun

              # /usr/lib/systemd/system/bluetooth.service
              [Unit]
              Description=Bluetooth service
              Documentation=man:bluetoothd(8)
              ConditionPathIsDirectory=/sys/class/bluetooth
              
              [Service]
              Type=dbus
              BusName=org.bluez
              ExecStart=/usr/libexec/bluetooth/bluetoothd --noplugin=sap
              NotifyAccess=main
              #WatchdogSec=10
              Restart=on-failure
              CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
              LimitNPROC=1
              
              # Filesystem lockdown
              ProtectHome=true
              ProtectSystem=strict
              PrivateTmp=true
              ProtectKernelTunables=true
              ProtectControlGroups=true
              StateDirectory=bluetooth
              StateDirectoryMode=0700
              ConfigurationDirectory=bluetooth
              ConfigurationDirectoryMode=0555
              
              # Execute Mappings
              MemoryDenyWriteExecute=true
              
              # Privilege escalation
              NoNewPrivileges=true
              
              # Real-time
              RestrictRealtime=true
              
              [Install]
              WantedBy=bluetooth.target
              Alias=dbus-org.bluez.service
              
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Tenor 0 last edited by

                @tenor-0 sagte in Mal wieder BLE Probleme:

                ExecStart=/usr/libexec/bluetooth/bluetoothd --noplugin=sap

                Die Zeile dürfte falsch sein. Das dürfte

                ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap
                

                heißen müssen.

                T 1 Reply Last reply Reply Quote 0
                • T
                  Tenor 0 @Thomas Braun last edited by

                  @thomas-braun
                  Was meinst du mit CAPs gesetzt?
                  Den Fix habe ich erneut ausgeführt, aber kein Unterschied, der Adapter ist gelb.
                  Der Scan ging nach einem Neustart wieder.

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Tenor 0 last edited by

                    @tenor-0

                    sudo apt update
                    sudo apt install libcap2-bin
                    sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
                    
                    1 Reply Last reply Reply Quote 0
                    • T
                      Tenor 0 @Thomas Braun last edited by

                      @thomas-braun
                      Das musste ich extra rein machen, da ich sonst beim starten eine Fehlermeldung bekomme.
                      Habe die noch als Bild gespeichert:
                      b67e5a65-9284-4f30-a4d7-13fc843bac06-grafik.png

                      quelle

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Tenor 0 last edited by Thomas Braun

                        @tenor-0

                        Keine Bildchens...

                        Der Pfad /usr/libexec/bluetooth/bluetoothd dürfte falsch sein.
                        Auf meinem Debian gibt es kein /usr/libexec
                        Das sieht mir nach einem Kopierfehler aus.

                        €dit: Okay, bei ubuntu und Debian trixie gibt es den Pfad wohl. Also so lassen.

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          Tenor 0 @Thomas Braun last edited by

                          @thomas-braun said in Mal wieder BLE Probleme:

                          /usr/libexec/bluetooth/bluetoothd

                          matthias@server:~$ cd /usr/libexec/bluetooth/
                          matthias@server:/usr/libexec/bluetooth$ ls
                          bluetoothd  obexd
                          matthias@server:/usr/libexec/bluetooth$
                          
                          

                          Das existiert so und war vorher auch so drin. Ich habe nur den Parameter angehangen wie in der Quelle beschrieben.

                          Ich befürchte das der onboard adapter dazwischen funkt.
                          Der Server hat einen onboard WiFi/BT Adapter, der jedoch kein BLE kann:

                          02:00.0 Network controller: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz
                          

                          Deswegen hatte ich den deaktiviert wie aus dem ursprünglichem Thread beschrieben, dieser war immer hci0 und der USB Adapter dann HCI1
                          Seit dem ich den deaktiviert hatte, war dann der USB Adapter HCI0.
                          Bei der Fehlersuch habe ich schon 2 mal gesehen das der HCIconfig den USB Adapter als HCI1 bezeichnet hat..
                          Nach einem Reboot ist das Thema dann wieder erledigt.

                          Anleitung

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Tenor 0 last edited by Thomas Braun

                            @tenor-0

                            libcap2 installiert?
                            Kommando dazu ausgeführt?
                            Siehe oben.

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              Tenor 0 @Thomas Braun last edited by

                              @thomas-braun
                              ging wahrscheinlich wegen doppelpost unter, ja ich hatte das schon gemacht. leider kein Unterschied.
                              lescan geht, unter iobroker, kommen keinen neuen Geräte mehr dazu. (Haken in den Einstellungen ist gesetzt)

                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Tenor 0 last edited by

                                @tenor-0 sagte in Mal wieder BLE Probleme:

                                ja ich hatte das schon gemacht. l

                                Die Ausgaben dazu würde ich gerne sehen.

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  Tenor 0 @Thomas Braun last edited by

                                  @thomas-braun

                                  matthias@server:/usr/libexec/bluetooth$ sudo apt update
                                  OK:1 http://de.archive.ubuntu.com/ubuntu noble InRelease
                                  OK:2 http://security.ubuntu.com/ubuntu noble-security InRelease
                                  OK:3 http://de.archive.ubuntu.com/ubuntu noble-updates InRelease
                                  OK:4 http://de.archive.ubuntu.com/ubuntu noble-backports InRelease
                                  Paketlisten werden gelesen… Fertig
                                  Abhängigkeitsbaum wird aufgebaut… Fertig
                                  Statusinformationen werden eingelesen… Fertig
                                  Alle Pakete sind aktuell.
                                  matthias@server:/usr/libexec/bluetooth$ sudo apt install libcap2-bin
                                  Paketlisten werden gelesen… Fertig
                                  Abhängigkeitsbaum wird aufgebaut… Fertig
                                  Statusinformationen werden eingelesen… Fertig
                                  libcap2-bin ist schon die neueste Version (1:2.66-5ubuntu2).
                                  Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
                                    mailcap wmdocker
                                  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
                                  0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
                                  matthias@server:/usr/libexec/bluetooth$ sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
                                  matthias@server:/usr/libexec/bluetooth$
                                  matthias@server:/usr/libexec/bluetooth$
                                  
                                  
                                  T 1 Reply Last reply Reply Quote 0
                                  • T
                                    Tenor 0 @Tenor 0 last edited by

                                    ich stosse immer wieder auf die Meldung:
                                    bluetoothd[3674]: Failed to set privacy: Rejected (0x0b)

                                    2024-10-12T20:41:52.551245+02:00 server systemd[1]: bluetooth.service: Deactivated successfully.
                                    2024-10-12T20:41:52.551384+02:00 server systemd[1]: Stopped bluetooth.service - Bluetooth service.
                                    2024-10-12T20:41:54.589079+02:00 server systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
                                    2024-10-12T20:41:54.814941+02:00 server systemd[1]: Configuration file /run/systemd/system/systemd-networkd-wait-online.service.d/10-netplan.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
                                    2024-10-12T20:41:55.201508+02:00 server (uetoothd)[3674]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
                                    2024-10-12T20:41:55.201632+02:00 server systemd[1]: Starting bluetooth.service - Bluetooth service...
                                    2024-10-12T20:41:55.250612+02:00 server bluetoothd[3674]: Bluetooth daemon 5.72
                                    2024-10-12T20:41:55.251545+02:00 server systemd[1]: Started bluetooth.service - Bluetooth service.
                                    2024-10-12T20:41:55.251591+02:00 server bluetoothd[3674]: Starting SDP server
                                    2024-10-12T20:41:55.251620+02:00 server bluetoothd[3674]: Excluding (cli) sap
                                    2024-10-12T20:41:55.251891+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support csip plugin
                                    2024-10-12T20:41:55.251945+02:00 server bluetoothd[3674]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
                                    2024-10-12T20:41:55.251988+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support micp plugin
                                    2024-10-12T20:41:55.252020+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support vcp plugin
                                    2024-10-12T20:41:55.252045+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support mcp plugin
                                    2024-10-12T20:41:55.252070+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support bass plugin
                                    2024-10-12T20:41:55.252095+02:00 server bluetoothd[3674]: src/plugin.c:plugin_init() System does not support bap plugin
                                    2024-10-12T20:41:55.252554+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
                                    2024-10-12T20:41:55.252690+02:00 server dbus-daemon[971]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.45' (uid=0 pid=3674 comm="/usr/libexec/bluetooth/bluetoothd --noplugin=sap" label="unconfined")
                                    2024-10-12T20:41:55.252765+02:00 server bluetoothd[3674]: Bluetooth management interface 1.22 initialized
                                    2024-10-12T20:41:55.252793+02:00 server bluetoothd[3674]: Battery Provider Manager created
                                    2024-10-12T20:41:55.252889+02:00 server bluetoothd[3674]: Failed to set privacy: Rejected (0x0b)
                                    2024-10-12T20:41:55.253179+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
                                    2024-10-12T20:41:55.271225+02:00 server systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
                                    2024-10-12T20:41:55.347612+02:00 server dbus-daemon[971]: [system] Successfully activated service 'org.freedesktop.hostname1'
                                    2024-10-12T20:41:55.347704+02:00 server systemd[1]: Started systemd-hostnamed.service - Hostname Service.
                                    2024-10-12T20:41:55.356604+02:00 server bluealsa: bluez.c:783: Registering battery provider: /org/bluez/hci0/battery
                                    2024-10-12T20:41:55.357266+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/1
                                    2024-10-12T20:41:55.357317+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/1
                                    2024-10-12T20:41:55.357504+02:00 server bluetoothd[3674]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/source/1
                                    2024-10-12T20:41:55.357618+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/2
                                    2024-10-12T20:41:55.357670+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/2
                                    2024-10-12T20:41:55.357785+02:00 server bluetoothd[3674]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/source/2
                                    2024-10-12T20:41:55.357890+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/1
                                    2024-10-12T20:41:55.357930+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/1
                                    2024-10-12T20:41:55.358065+02:00 server bluetoothd[3674]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/sink/1
                                    2024-10-12T20:41:55.358135+02:00 server bluealsa: bluez.c:598: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/2
                                    2024-10-12T20:41:55.358155+02:00 server bluealsa: bluez.c:509: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/2
                                    2024-10-12T20:41:55.358215+02:00 server bluetoothd[3674]: Endpoint registered: sender=:1.11 path=/org/bluez/hci0/A2DP/SBC/sink/2
                                    2024-10-12T20:41:55.358275+02:00 server bluealsa: bluez.c:1199: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
                                    2024-10-12T20:42:25.372785+02:00 server systemd[1]: systemd-hostnamed.service: Deactivated successfully.
                                    
                                    

                                    meistens verschwindet sie nach dem Neustart des Adapters, weiß aber nicht wie relevant sie ist.

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @Tenor 0 last edited by

                                      @tenor-0

                                      rfkill
                                      

                                      sagt?

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        Tenor 0 @Thomas Braun last edited by

                                        @thomas-braun said in Mal wieder BLE Probleme:

                                        rfkill

                                        alles tuti

                                        matthias@server:~$ rfkill
                                        ID TYPE      DEVICE      SOFT      HARD
                                         0 bluetooth hci0   unblocked unblocked
                                         1 wlan      phy0   unblocked unblocked
                                        matthias@server:~$ rfkill list
                                        0: hci0: Bluetooth
                                                Soft blocked: no
                                                Hard blocked: no
                                        1: phy0: Wireless LAN
                                                Soft blocked: no
                                                Hard blocked: no
                                        
                                        
                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @Tenor 0 last edited by

                                          @tenor-0

                                          Den Haken bei 'Neue Gerät akzeptieren' im Adapter hattest du schon mal gesetzt?

                                          T 1 Reply Last reply Reply Quote 0
                                          • T
                                            Tenor 0 @Thomas Braun last edited by

                                            @thomas-braun
                                            ja diverse male

                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.1k
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            58
                                            2384
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo