Desactivation bluetooth interne

Matériel Jeedom - Hardware Raspberry Pi ou autre carte DIY (Faire soi-même)
1

Bonjour
je sais que le sujet precedent traite du meme probleme mais il est clos. Or j’ai le meme probleme mais la solution apporté ne fonctionne pas chez moi. Lorsque j’essaye de redemarrer le service hciuart j’ai

> pi@raspberrypi:~ $ sudo systemctl stop bluetooth && sudo systemctl enable bluetooth && sudo systemctl start bluetooth && sudo systemctl stop hciuart && sudo systemctl enable hciuart && sudo systemctl start hciuart && sudo systemctl daemon-reload
> Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable bluetooth
> Job for hciuart.service failed because the control process exited with error code.
> See "systemctl status hciuart.service" and "journalctl -xe" for details.

et dans le journal j’ai

> Jan 05 10:23:04 raspberrypi sudo[3458]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl enable hciuart
> Jan 05 10:23:04 raspberrypi sudo[3458]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
> Jan 05 10:23:04 raspberrypi systemd[1]: Reloading.
> Jan 05 10:23:04 raspberrypi dbus[363]: [system] Successfully activated service 'org.freedesktop.hostname1'
> Jan 05 10:23:04 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 47min 36.528189s random time.
> Jan 05 10:23:04 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 16min 49.330058s random time.
> Jan 05 10:23:04 raspberrypi systemd[1]: Started Hostname Service.
> -- Subject: Unit systemd-hostnamed.service has finished start-up
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-hostnamed.service has finished starting up.
> -- 
> -- The start-up result is done.
> Jan 05 10:23:04 raspberrypi sudo[3458]: pam_unix(sudo:session): session closed for user root
> Jan 05 10:23:04 raspberrypi sudo[3477]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl start hciuart
> Jan 05 10:23:04 raspberrypi sudo[3477]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
> Jan 05 10:23:04 raspberrypi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
> -- Subject: Unit hciuart.service has begun start-up
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit hciuart.service has begun starting up.
> Jan 05 10:23:05 raspberrypi sudo[3373]: pam_unix(sudo:session): session closed for user root
> Jan 05 10:23:05 raspberrypi sudo[3511]: www-data : TTY=unknown ; PWD=/var/www ; USER=root ; COMMAND=/bin/ping -n -c 1 -t 255 192.168.21.35
> Jan 05 10:23:05 raspberrypi sudo[3511]: pam_unix(sudo:session): session opened for user root by (uid=0)
> Jan 05 10:23:08 raspberrypi sudo[3511]: pam_unix(sudo:session): session closed for user root
> Jan 05 10:23:08 raspberrypi sudo[3530]: www-data : TTY=unknown ; PWD=/var/www ; USER=root ; COMMAND=/bin/ping -n -c 1 -t 255 192.168.21.35
> Jan 05 10:23:08 raspberrypi sudo[3530]: pam_unix(sudo:session): session opened for user root by (uid=0)
> Jan 05 10:23:11 raspberrypi sudo[3530]: pam_unix(sudo:session): session closed for user root
> Jan 05 10:23:34 raspberrypi btuart[3484]: Initialization timed out.
> Jan 05 10:23:34 raspberrypi btuart[3484]: bcm43xx_init
> Jan 05 10:23:34 raspberrypi systemd[1]: hciuart.service: Control process exited, code=exited status=1
> Jan 05 10:23:34 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
> -- Subject: Unit hciuart.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- Unit hciuart.service has failed.
> --
> -- The result is failed.
> Jan 05 10:23:34 raspberrypi systemd[1]: hciuart.service: Unit entered failed state.
> Jan 05 10:23:34 raspberrypi systemd[1]: hciuart.service: Failed with result 'exit-code'.
> Jan 05 10:23:34 raspberrypi sudo[3477]: pam_unix(sudo:session): session closed for user root

pour info je suis sous raspbian strech, et j’ai le probleme avec jeedom v3 et jeedom RCV 4
est ce que cela parle à quelqu’un ?
un grand merci

2

Bonjour,

As-tu commencé par les préconisations de @naboleo sur le précédent sujet ? :

Le pi est à jour ? apt-get update && apt-get upgrade ??

3

Oui tout est à jour et j’ai bien désactivé les plugin openzwave et blea :o(
et petite precison, si je desintalle openzwave, BLEA refonctionne tres bien

4

Salut,

ça ressemble quand même beaucoup à la désactivation de l’uart par le plugin z-wave…
Tu peux essayer de faire les commandes (séparées par les &&) une à une ?

5

voilà mais il semblerait que j’ai le même problème :confused:

> pi@raspberrypi:~ $ sudo systemctl stop bluetooth
> pi@raspberrypi:~ $ sudo systemctl enable bluetooth
> Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable bluetooth
> pi@raspberrypi:~ $ sudo systemctl start bluetooth
> pi@raspberrypi:~ $ sudo systemctl status bluetooth
> ● bluetooth.service - Bluetooth service
>    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
>    Active: active (running) since Thu 2020-01-09 14:40:29 GMT; 6s ago
>      Docs: man:bluetoothd(8)
>  Main PID: 8591 (bluetoothd)
>    Status: "Running"
>     Tasks: 1 (limit: 4915)
>    CGroup: /system.slice/bluetooth.service
>            └─8591 /usr/lib/bluetooth/bluetoothd
> 
> Jan 09 14:40:29 raspberrypi systemd[1]: Starting Bluetooth service...
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Bluetooth daemon 5.43
> Jan 09 14:40:29 raspberrypi systemd[1]: Started Bluetooth service.
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Starting SDP server
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Bluetooth management interface 1.14 initialized
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Failed to obtain handles for "Service Changed" characteristic
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Sap driver initialization failed.
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: sap-server: Operation not permitted (1)
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Endpoint registered: sender=:1.5 path=/MediaEndpoint/A2DPSource
> Jan 09 14:40:29 raspberrypi bluetoothd[8591]: Endpoint registered: sender=:1.5 path=/MediaEndpoint/A2DPSink
> pi@raspberrypi:~ $ sudo systemctl stop hciuart
> pi@raspberrypi:~ $ sudo systemctl enable hciuart
> pi@raspberrypi:~ $ sudo systemctl start hciuart
> Job for hciuart.service failed because the control process exited with error code.
> See "systemctl status hciuart.service" and "journalctl -xe" for details.
> pi@raspberrypi:~ $ sudo systemctl status hciuart
> ● hciuart.service - Configure Bluetooth Modems connected by UART
>    Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Thu 2020-01-09 14:41:58 GMT; 12s ago
>   Process: 8951 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)
>  Main PID: 598 (code=exited, status=0/SUCCESS)
> 
> Jan 09 14:41:28 raspberrypi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
> Jan 09 14:41:58 raspberrypi btuart[8951]: Initialization timed out.
> Jan 09 14:41:58 raspberrypi btuart[8951]: bcm43xx_init
> Jan 09 14:41:58 raspberrypi systemd[1]: hciuart.service: Control process exited, code=exited status=1
> Jan 09 14:41:58 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
> Jan 09 14:41:58 raspberrypi systemd[1]: hciuart.service: Unit entered failed state.
> Jan 09 14:41:58 raspberrypi systemd[1]: hciuart.service: Failed with result 'exit-code'.
> pi@raspberrypi:~ $ sudo systemctl daemon-reload
> pi@raspberrypi:~ $

encore merci

6

Si tu veux désactiver le Bluetooth du Raspberry tu peux le faire dans le config.txt en ajoutant la commande suivante:

dtoverlay=pi3-disable-bt