Bonjour,
J’avais il y a fort longtemps installé sans problème le plugin beagle (Odace SFSP), avec le bluetooth interne au RPI, et avais réussi à scanner mon équipement (un interrupteur SPSP qui pilote un actionneur situé dans un cabanon).
Je n’avais jamais implémenté de scénario pour piloter tout ça et cela faisait fort longtemps que je n’avais pas été dans la page du plugin.
Je suis allé sur cette page la semaine dernière, j’y ai vu mon interrupteur, j’ai cliqué dessus, et il y avait juste deux lignes « Info », aucune ligne pour piloter les interrupteurs. Le plugin était dans un état OK, demon lancé etc. J’ai relancé l’installation des dépenances, surfé sur ce forum car j’avais des messages d’erreur. j’ai modifié le code du plugin, et relancé l’installation des dépendances.
Je n’ai plus d’erreur dans les logs « Beagle_update », mais des warnings
********************************************************
* Installation des dépendances *
********************************************************
Get:1 http://archive.raspberrypi.org/debian bullseye InRelease [39.0 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
Get:7 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [330 kB]
Hit:6 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
Get:8 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages [323 kB]
Fetched 692 kB in 2s (316 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
rfkill is already the newest version (2.36.1-8+deb11u2).
python3-setuptools is already the newest version (52.0.0-4+deb11u2).
python3-pip is already the newest version (20.3.4-4+rpt1+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.9).
libffi-dev is already the newest version (3.3-6).
python3-dev is already the newest version (3.9.2-3).
libssl-dev is already the newest version (1.1.1w-0+deb11u5).
bluetooth is already the newest version (5.55-3.1+rpt2+deb11u2).
libbluetooth-dev is already the newest version (5.55-3.1+rpt2+deb11u2).
python3-pip is already the newest version (20.3.4-4+rpt1+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (2.32.5)
Requirement already satisfied: charset_normalizer<4,>=2 in /usr/local/lib/python3.9/dist-packages (from requests) (3.4.7)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests) (3.13)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.9/dist-packages (from requests) (2.6.3)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests) (2026.4.22)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pyserial in /usr/local/lib/python3.9/dist-packages (3.5)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pyudev in /usr/local/lib/python3.9/dist-packages (0.24.3)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: wheel in /usr/local/lib/python3.9/dist-packages (0.47.0)
Requirement already satisfied: packaging>=24.0 in /usr/local/lib/python3.9/dist-packages (from wheel) (26.2)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 24: 40: No such file or directory
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: setuptools==58 in /usr/local/lib/python3.9/dist-packages (58.0.0)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
********************************************************
* Installation terminée *
********************************************************
Je me dis « bon ca va passer »…Je relance le scan, manoeuvre l’interrupteur SFSP…Ca ne marche pas, rien n’est détecté.
J’achète un dongle bluetooth 4.0, même résultat.
Je suis un peu perdu : est-ce que ce sont mes modifications qui ont mis le bazar ? Est-ce que ce sont les warnings qui indiquent ce que je dois faire…mais que dois-je alors faire sans casser quelque chose ?
Voici la page santé…
Et quand je lance le scan :
[2026-05-05 15:39:34] DEBUG Lancement démon beagle : sudo /usr/bin/python3 /var/www/html/plugins/beagle/resources/beagled/beagled.py --device hci1 --loglevel debug --socketport 55556 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/beagle/core/php/jeeBeagle.php --apikey XXX --cycle 0.1 --jeedomkey YYY
[2026-05-05 15:39:35.288] INFO : Start beagled
[2026-05-05 15:39:35.288] INFO : Log level : debug
[2026-05-05 15:39:35.288] INFO : Socket port : 55556
[2026-05-05 15:39:35.288] INFO : Socket host : 127.0.0.1
[2026-05-05 15:39:35.289] INFO : Device : hci1
[2026-05-05 15:39:35.289] INFO : PID file : /tmp/beagled.pid
[2026-05-05 15:39:35.289] INFO : Apikey : XXX
[2026-05-05 15:39:35.289] INFO : Callback : http://127.0.0.1:80/plugins/beagle/core/php/jeeBeagle.php
[2026-05-05 15:39:35.289] INFO : Cycle : 0.1
[2026-05-05 15:39:35.289] INFO : JeedomKey : YYY
[2026-05-05 15:39:35.298] DEBUG : Bluetooth Mac adress is D8:3A:DD:51:26:6E
[2026-05-05 15:39:35.298] DEBUG : Writing PID 613151 to /tmp/beagled.pid
[2026-05-05 15:39:35.300] DEBUG : Init request module v2.32.5
[2026-05-05 15:39:35.307] DEBUG : Starting new HTTP connection (1): 127.0.0.1:80
[2026-05-05 15:39:35.317] DEBUG : http://127.0.0.1:80 "GET /plugins/beagle/core/php/jeeBeagle.php?apikey=XXX HTTP/1.1" 200 0
[2026-05-05 15:39:35.320] DEBUG : Socket interface started
[2026-05-05 15:39:35.321] DEBUG : LoopNetServer Thread started
[2026-05-05 15:39:35.321] DEBUG : Read Socket Thread Launched
[2026-05-05 15:39:35.321] DEBUG : Listening on: [localhost:55556]
[2026-05-05 15:39:35.321] DEBUG : Ble Scanner Thread Launched
[2026-05-05 15:39:35.322] DEBUG : Heartbeat Thread Launched
[2026-05-05 15:39:37.672] DEBUG : Client connected to [127.0.0.1:59434]
[2026-05-05 15:39:37.673] DEBUG : Message read from socket: b'{"apikey":"XXX","cmd":"ready"}'
[2026-05-05 15:39:37.673] DEBUG : Client disconnected from [127.0.0.1:59434]
[2026-05-05 15:39:37.725] DEBUG : Message received in socket JEEDOM_SOCKET_MESSAGE
[2026-05-05 15:39:37.725] DEBUG : Received command from jeedom : ready
[2026-05-05 15:39:37.725] DEBUG : Daemon is ready
[2026-05-05 15:39:38.325] DEBUG : Ble thread started on device 1
[2026-05-05 15:39:38.325] DEBUG : 'utf-8' codec can't decode byte 0xff in position 4: invalid start byte
Merci par avance


