Perte d'une antenne - plus possible de la relancer

Bonsoir, aujourd’hui une antenne qui fonctionnait s’est arretée.
J’ai essayé de la relancer mais je n’y arrive pas
Ci joint les infos concernant cette antenne

log TGW2421

## Bluetooth adapters
Default adapter: hci0
### hci0
| Name         | Value               |
|--------------|---------------------|
| address      | 00:19:86:XX:XX:XX   |
| sw_version   | jeedom              |
| hw_version   | usb:v1D6Bp0246d0537 |
| passive_scan |                   0 |
| manufacturer | Broadcom Corp       |
| product      | BCM20702A0          |
| vendor_id    | 0a5c                |
| product_id   | 21ec                |
### hci1
| Name         | Value             |
|--------------|-------------------|
| address      | 00:00:00:XX:XX:XX |
| sw_version   | Unknown           |
Traceback (most recent call last):
File "/root/.local/bin/TheengsGateway", line 4, in 
main()
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/__init__.py", line 57, in main
run(configuration, config_path)
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/ble_gateway.py", line 591, in run
asyncio.run(diagnostics(config_path))
File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
return future.result()
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/diagnose.py", line 172, in diagnostics
await _adapters()
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/diagnose.py", line 155, in _adapters
_section(adapter, properties)  # type: ignore[arg-type]
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/diagnose.py", line 55, in _section
print(f"| {name:{max_name}} | {value:{max_value}} |")
TypeError: unsupported format string passed to NoneType.__format__

Log TGW 2421 update

[2023-12-27 21:21:42] *************************************
[2023-12-27 21:21:42] *   Launch install of dependencies  *
[2023-12-27 21:21:42] *************************************
[2023-12-27 21:21:42] Reading package lists...
[2023-12-27 21:21:42] Building dependency tree...
[2023-12-27 21:21:42] Reading state information...
[2023-12-27 21:21:42] curl is already the newest version (7.74.0-1.3+deb11u11).
[2023-12-27 21:21:42] 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     2  100     2    0     0    250      0 --:--:-- --:--:-- --:--:--   285
[2023-12-27 21:21:42] Hit:1 http://deb.debian.org/debian bullseye InRelease
[2023-12-27 21:21:42] Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
[2023-12-27 21:21:42] Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
[2023-12-27 21:21:42] Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
[2023-12-27 21:21:43] Reading package lists...
[2023-12-27 21:21:43] ***************************************
[2023-12-27 21:21:43] *  Install dependencies, venv & pipx  *
[2023-12-27 21:21:43] ***************************************
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     2  100     2    0     0    333      0 --:--:-- --:--:-- --:--:--   333
[2023-12-27 21:21:43] Reading package lists...
[2023-12-27 21:21:43] Building dependency tree...
[2023-12-27 21:21:43] Reading state information...
[2023-12-27 21:21:44] logrotate is already the newest version (3.18.0-2+deb11u2).
[2023-12-27 21:21:44] python3-pip is already the newest version (20.3.4-4+deb11u1).
[2023-12-27 21:21:44] python3 is already the newest version (3.9.2-3).
[2023-12-27 21:21:44] python3-venv is already the newest version (3.9.2-3).
[2023-12-27 21:21:44] bluez is already the newest version (5.55-3.1+deb11u1).
[2023-12-27 21:21:44] 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
[2023-12-27 21:21:44] Version debian:11
[2023-12-27 21:21:44] Install pipx via pip
[2023-12-27 21:21:44] Requirement already satisfied: pipx in /usr/local/lib/python3.9/dist-packages (1.2.1)
[2023-12-27 21:21:44] Requirement already satisfied: argcomplete>=1.9.4 in /usr/local/lib/python3.9/dist-packages (from pipx) (3.1.6)
[2023-12-27 21:21:44] Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.9/dist-packages (from pipx) (23.2)
[2023-12-27 21:21:44] Requirement already satisfied: userpath>=1.6.0 in /usr/local/lib/python3.9/dist-packages (from pipx) (1.9.1)
[2023-12-27 21:21:44] Requirement already satisfied: click in /usr/local/lib/python3.9/dist-packages (from userpath>=1.6.0->pipx) (8.1.7)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
[notice] A new release of pip is available: 23.3.1 -> 23.3.2
[notice] To update, run: python3 -m pip install --upgrade pip
[2023-12-27 21:21:44] /root/.local/bin has been been added to PATH, but you need to open a new
[2023-12-27 21:21:44] terminal or re-login for this PATH change to take effect.
[2023-12-27 21:21:44]
[2023-12-27 21:21:44] You will need to open a new terminal or re-login for the PATH changes to take
[2023-12-27 21:21:44] effect.
[2023-12-27 21:21:45]
[2023-12-27 21:21:45] Otherwise pipx is ready to go! ✨ 🌟 ✨
[2023-12-27 21:21:45] ****************************
[2023-12-27 21:21:45] *  Install TheengsGateway  *
[2023-12-27 21:21:45] ****************************
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     2  100     2    0     0    333      0 --:--:-- --:--:-- --:--:--   333
[2023-12-27 21:21:45] 'theengsgateway' already seems to be installed. Not modifying existing
[2023-12-27 21:21:45] installation in '/root/.local/pipx/venvs/theengsgateway'. Pass '--force' to
[2023-12-27 21:21:45] force installation.
[2023-12-27 21:21:45] ***************************
[2023-12-27 21:21:45] *      Install ended      *
[2023-12-27 21:21:45] ***************************
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     2  100     2    0     0      9      0 --:--:-- --:--:-- --:--:--     9

Bonjour,

Et que c’est-il passé pour que cela se produise? Car le choses n’arrivent pas seules.

Cad? Qu’avez- vous essayé ?

Vu le log j’ai l’impression que TheengsGateway a un problème avec un des adaptateurs bluetooth.

Je n’ai pas l’information sur ce qui s’est passé, en tout cas aucune intervention de ma part sur mon jeedom.
Pour la remise en route j’ai fait les choses suivantes :

  • passé de la version beta à la version stable du plugin
  • reinsatallation de l’antenne
  • relance de configurer le service et redémarrer

C’est tout.
Par contre j’ai d’autres défauts qui sont remontés dans jeedom


je ne sais pas si c’est lié ou non

Debranchez l’adaptateur bluetooth et rebranchez le.
Si ca ne suffit pas redémarrez la box.

Il y a un problème avec la clé bluetooth qui empêche theengsgateway de démarrer

J’ai débranché et rebranché la cle BT sans succès
J’ai redémarré jeedom sans succés
J’ai changé la clé BT par une autre et reinstallé tout sans succés
J’ai supprimé l’antenne et réinstallé l’antenne avec succès… avec la nouvelle clé BT
C’est tout ce que je sais pour le moment…

Bonjour,

Que donne cette commande :
sudo service bluetooth status

J’ai du mal à suivre votre infra Jeedom. Car sur de plus ancien message, vous avez aussi une antenne local sur un autre Jeedom ? Vous avez plusieurs Jeedom chez vous c’est ca ?

Car j’identifie 2 antennes locales dans vos messages, avec des ID différents

Bonjour, j’ai effectivement 2 jeedom qui communiquent entre eux. J’ai une antenne locale et 3 antennes déportées, l’une sur le second jeedom, une sur un pi zero et une sur un PI3. Sur le second jeedom j’ai eu pendant un moment le plugin tgw installée et une antenne locale.

La réponse à la commande

* bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-12-28 10:59:30 CET; 2h 1min ago
       Docs: man:bluetoothd(8)
   Main PID: 455 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 19022)
     Memory: 3.9M
        CPU: 57.690s
     CGroup: /system.slice/bluetooth.service
             `-455 /usr/libexec/bluetooth/bluetoothd

Dec 28 10:59:30 jeedom systemd[1]: Starting Bluetooth service...
Dec 28 10:59:30 jeedom bluetoothd[455]: Bluetooth daemon 5.55
Dec 28 10:59:30 jeedom systemd[1]: Started Bluetooth service.
Dec 28 10:59:30 jeedom bluetoothd[455]: Starting SDP server
Dec 28 10:59:30 jeedom bluetoothd[455]: Bluetooth management interface 1.18 initialized
Dec 28 10:59:30 jeedom bluetoothd[455]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Dec 28 10:59:30 jeedom bluetoothd[455]: sap-server: Operation not permitted (1)
Dec 28 11:27:16 jeedom bluetoothd[455]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Dec 28 11:27:16 jeedom bluetoothd[455]: sap-server: Operation not permitted (1)

Pas d’erreur sur la sortie de la commande (enfin, pas qui concerne TGW)

L’antenne fonctionne à cet instant ?

Dans le log de la nouvelle antenne j’ai

ERROR:BLEGateway:[org.bluez.Error.InProgress] Operation already in progress
Traceback (most recent call last):
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/TheengsGateway/ble_gateway.py", line 374, in ble_scan_loop
await scanner.start()
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/bleak/__init__.py", line 198, in start
await self._backend.start()
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/bleak/backends/bluezdbus/scanner.py", line 185, in start
self._stop = await manager.active_scan(
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/bleak/backends/bluezdbus/manager.py", line 416, in active_scan
assert_reply(reply)
File "/root/.local/pipx/venvs/theengsgateway/lib/python3.9/site-packages/bleak/backends/bluezdbus/utils.py", line 22, in assert_reply
raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.InProgress] Operation already in progress
ERROR:BLEGateway:BLE scan loop stopped

et toujours des erreurs

Regardez la commande :
dmesg -H
sur la machine où il y a cette erreur.

C’est visiblement des problèmes de bluetooth sur vos machines.

command not found, idem avec sudo

J’ai une rallonge de 3 metres sur le jeedom pour deporter la clé BT, est ce que cela peut influer

J’ai relancé depuis jeedom sans -H et j’ai trop de lignes, je ne peux pas les mettre dans le message

C’est bizarre, si je tape la commande il me dit ‹ command not found ›, mais si j’envoi la commande préconfigurée dans jeedom cela fonctionne, mais il n’y a pas -H

Oui, 3 mettre c’est beaucoup trop. Tout dépend de la qualité des composants de bout en bout.

Je m’étais trompé dans le nom de la commande.

C’est : dmesg -H

Le moins H permet de dater humainement. Il faut regarder vers la fin au moment où vous avez le problème.

Je vais mettre un cable plus court, mais pour l’instant je n’en ai pas…

pour le resultat de la commande

3.431644] Bluetooth: Core ver 2.22
[    3.431660] NET: Registered protocol family 31
[    3.431661] Bluetooth: HCI device and connection manager initialized
[    3.431665] Bluetooth: HCI socket layer initialized
[    3.431667] Bluetooth: L2CAP socket layer initialized
[    3.431669] Bluetooth: SCO socket layer initialized
[    3.445220] usbcore: registered new interface driver btusb
[    3.455497] Bluetooth: hci1: Bootloader revision 0.0 build 2 week 52 2014
[    3.462526] Bluetooth: hci1: Device revision is 5
[    3.462527] Bluetooth: hci1: Secure boot is enabled
[    3.462528] Bluetooth: hci1: OTP lock is enabled
[    3.462529] Bluetooth: hci1: API lock is enabled
[    3.462530] Bluetooth: hci1: Debug lock is disabled
[    3.462531] Bluetooth: hci1: Minimum firmware build 1 week 10 2014
[    3.462547] bluetooth hci1: firmware: failed to load intel/ibt-11-5.sfi (-2)
[    3.462552] bluetooth hci1: Direct firmware load for intel/ibt-11-5.sfi failed with error -2
[    3.462554] Bluetooth: hci1: Failed to load Intel firmware file (-2)
[    3.564568] Bluetooth: hci0: BCM: chip id 63
[    3.565568] Bluetooth: hci0: BCM: features 0x07
[    3.581557] Bluetooth: hci0: BCM20702A
[    3.581566] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    3.582595] bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21ec.hcd (-2)
[    3.582645] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-21ec.hcd (-2)
[    3.582657] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[    3.582666] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21ec.hcd'
[    3.582675] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21ec.hcd'
[    3.839906] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.839908] Bluetooth: BNEP filters: protocol multicast
[    3.839911] Bluetooth: BNEP socket layer initialized
[    3.854114] NET: Registered protocol family 38
[    6.449619] e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[    6.449697] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[  110.602686] tun: Universal TUN/TAP device driver, 1.6
[  122.528907] usb 1-3: USB disconnect, device number 3
[  122.839628] usb 1-3: new full-speed USB device number 7 using xhci_hcd
[  122.988635] usb 1-3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[  122.988641] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  122.990423] cdc_acm 1-3:1.0: ttyACM0: USB ACM device
[  341.165127] usb 1-4.4: USB disconnect, device number 6
[  341.504133] usb 1-4.4: new full-speed USB device number 8 using xhci_hcd
[  341.710618] usb 1-4.4: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[  341.710625] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  341.710629] usb 1-4.4: Product: ConBee II
[  341.710632] usb 1-4.4: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[  341.710635] usb 1-4.4: SerialNumber: DE2417200
[  341.719371] cdc_acm 1-4.4:1.0: ttyACM1: USB ACM device
[  345.004019] usb 1-4.4: USB disconnect, device number 8
[  345.332075] usb 1-4.4: new full-speed USB device number 9 using xhci_hcd
[  345.534753] usb 1-4.4: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[  345.534760] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  345.534764] usb 1-4.4: Product: ConBee II
[  345.534767] usb 1-4.4: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[  345.534770] usb 1-4.4: SerialNumber: DE2417200
[  345.543403] cdc_acm 1-4.4:1.0: ttyACM1: USB ACM device
[ 1667.377906] usb 1-1: USB disconnect, device number 2
[ 1669.666383] usb 1-1: new full-speed USB device number 10 using xhci_hcd
[ 1669.937436] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
[ 1669.937443] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 1669.937446] usb 1-1: Product: CSR8510 A10
[ 1669.944056] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb; LMP ver=6 subver=22bb; manufacturer=10
[ 1670.114246] Bluetooth: hci0: hardware error 0x56
[11457.281941] perf: interrupt took too long (2586 > 2500), lowering kernel.perf_event_max_sample_rate to 77250
[18904.915444] perf: interrupt took too long (3332 > 3232), lowering kernel.perf_event_max_sample_rate to 60000
[29827.759808] perf: interrupt took too long (4218 > 4165), lowering kernel.perf_event_max_sample_rate to 47250

On voit des « hardware error » sur le bluetooth.
Je ne sais pas ce que ca veut dire mais ca n’a pas l’air bon.

Sinon je ne comprends pas pq mettre une rallonge ?

Le hardware est de l’autre coté du mur et le BT ne passe pas vraiment bien, la ralonge traverse le mur

L’autre antenne présente aussi une anomalie, ci joint le log de l’antenne 2430

INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
ERROR:BLEGateway:Disconnected with return code = 16
ERROR:BLEGateway:Disconnected with return code = 16
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
ERROR:BLEGateway:Disconnected with return code = 16
ERROR:BLEGateway:Disconnected with return code = 16
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
ERROR:BLEGateway:Disconnected with return code = 7
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
ERROR:BLEGateway:Disconnected with return code = 7
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded
INFO:BLEGateway:Starting BLE scan
INFO:BLEGateway:Connected to MQTT Broker!
INFO:BLEGateway:Subscribed to home/+/BTtoMQTT/undecoded

Elle ne scanne rien …
Sur la commande dmesg, le retour des informations

[2322782.113176] usb 1-2: new full-speed USB device number 6 using xhci_hcd
[2322782.264092] usb 1-2: New USB device found, idVendor=0a5c, idProduct=21ec, bcdDevice= 1.12
[2322782.264101] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[2322782.264105] usb 1-2: Product: BCM20702A0
[2322782.264108] usb 1-2: Manufacturer: Broadcom Corp
[2322782.264110] usb 1-2: SerialNumber: 0019860009D8
[2322782.378659] Bluetooth: hci0: BCM: chip id 63
[2322782.379657] Bluetooth: hci0: BCM: features 0x07
[2322782.395777] Bluetooth: hci0: BCM20702A
[2322782.395781] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[2322782.396734] bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21ec.hcd (-2)
[2322782.396749] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-21ec.hcd (-2)
[2322782.396752] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[2322782.396754] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21ec.hcd'
[2322782.396756] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21ec.hcd'
[2367450.890162] audit: type=1400 audit(1703804401.546:59): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=689136 comm="cupsd" capability=12  capname="net_admin"
[2367451.082041] audit: type=1400 audit(1703804401.738:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=689137 comm="cups-browsed" capability=23  capname="sys_nice"