je me permet de réouvir un sujet avec le même titre qu’un sujet précédent car je ne trouve malheureusement pas de solution et l’ancien sujet date d’il y a plus d’un an.
je cherche à synchroniser des interrupteurs sans fils Schneider. j’ai donc installé le plugin odace SFSP.
je suis sur une box Luna avec un dongle USB blutooth.
j’ai le message d’erreur : Impossible de lancer le démon beagle, vérifiez le port
dans les logs j’ai cela :
[2024-03-02 15:03:27][DEBUG] : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php plugin_id=beagle function=remove callInstallFunction=1
[2024-03-02 15:04:12][INFO] : Début d'activation du plugin
[2024-03-02 15:04:13][INFO] : Info sur le démon : {"log":"beagle","state":"nok","launchable":"ok","launchable_message":"Gestion automatique d\u00e9sactiv\u00e9e","auto":"0","last_launch":"Inconnue"}
[2024-03-02 15:04:13][DEBUG] : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php plugin_id=beagle function=install callInstallFunction=1
Traceback (most recent call last):
File "/var/www/html/plugins/beagle/resources/beagled/beagled.py", line 28, in <module>
import blescan
File "/var/www/html/plugins/beagle/resources/beagled/blescan.py", line 21, in <module>
import bluetooth._bluetooth as bluez
ModuleNotFoundError: No module named 'bluetooth'
[2024-03-02 15:04:32][ERROR] : Impossible de lancer le démon beagle, vérifiez le port
0000|********************************************************
0001|* Installation des dépendances *
0002|********************************************************
0003|Hit:1 https://deb.debian.org/debian bullseye InRelease
0004|Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
0005|Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
0006|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0007|Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
0008|Reading package lists...
0009|Reading package lists...
0010|Building dependency tree...
0011|Reading state information...
0012|python3-pip is already the newest version (20.3.4-4+deb11u1).
0013|python3-setuptools is already the newest version (52.0.0-4).
0014|rfkill is already the newest version (2.36.1-8+deb11u1).
0015|0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
0016|Reading package lists...
0017|Building dependency tree...
0018|Reading state information...
0019|bluetooth is already the newest version (5.55-3.1+deb11u1).
0020|libbluetooth-dev is already the newest version (5.55-3.1+deb11u1).
0021|build-essential is already the newest version (12.9).
0022|libffi-dev is already the newest version (3.3-6).
0023|libssl-dev is already the newest version (1.1.1w-0+deb11u1).
0024|python3-pip is already the newest version (20.3.4-4+deb11u1).
0025|python3-dev is already the newest version (3.9.2-3).
0026|0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
0027|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 15: /tmp/jeedom/beagle/dependance: No such file or directory
0028|Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (2.31.0)
0029|Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.9/dist-packages (from requests) (2.0.12)
0030|Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests) (3.6)
0031|Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.9/dist-packages (from requests) (2.1.0)
0032|Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests) (2023.11.17)
0033|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
0034|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
0035|[notice] A new release of pip is available: 23.3.2 -> 24.0
0036|[notice] To update, run: python3 -m pip install --upgrade pip
0037|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 17: /tmp/jeedom/beagle/dependance: No such file or directory
0038|Requirement already satisfied: pyserial in /usr/local/lib/python3.9/dist-packages (3.5)
0039|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
0040|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
0041|[notice] A new release of pip is available: 23.3.2 -> 24.0
0042|[notice] To update, run: python3 -m pip install --upgrade pip
0043|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 19: /tmp/jeedom/beagle/dependance: No such file or directory
0044|Requirement already satisfied: pyudev in /usr/local/lib/python3.9/dist-packages (0.24.1)
0045|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
0046|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
0047|[notice] A new release of pip is available: 23.3.2 -> 24.0
0048|[notice] To update, run: python3 -m pip install --upgrade pip
0049|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 21: /tmp/jeedom/beagle/dependance: No such file or directory
0050|Requirement already satisfied: wheel in /usr/local/lib/python3.9/dist-packages (0.42.0)
0051|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
0052|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
0053|[notice] A new release of pip is available: 23.3.2 -> 24.0
0054|[notice] To update, run: python3 -m pip install --upgrade pip
0055|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 23: /tmp/jeedom/beagle/dependance: No such file or directory
0056|Requirement already satisfied: cryptography==2.6.1 in /usr/local/lib/python3.9/dist-packages (2.6.1)
0057|Requirement already satisfied: asn1crypto>=0.21.0 in /usr/local/lib/python3.9/dist-packages (from cryptography==2.6.1) (1.5.1)
0058|Requirement already satisfied: six>=1.4.1 in /usr/local/lib/python3.9/dist-packages (from cryptography==2.6.1) (1.16.0)
0059|Requirement already satisfied: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.9/dist-packages (from cryptography==2.6.1) (1.16.0)
0060|Requirement already satisfied: pycparser in /usr/local/lib/python3.9/dist-packages (from cffi!=1.11.3,>=1.8->cryptography==2.6.1) (2.21)
0061|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
0062|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
0063|[notice] A new release of pip is available: 23.3.2 -> 24.0
0064|[notice] To update, run: python3 -m pip install --upgrade pip
0065|/var/www/html/plugins/beagle/core/class/../../resources/install_apt.sh: line 25: /tmp/jeedom/beagle/dependance: No such file or directory
0066|Collecting pybluez
0067|Using cached PyBluez-0.23.tar.gz (97 kB)
0068|Preparing metadata (setup.py): started
0069|Preparing metadata (setup.py): finished with status 'error'
0070|error: subprocess-exited-with-error
0071|× python setup.py egg_info did not run successfully.
0072|│ exit code: 1
0073|╰─> [1 lines of output]
0074|error in PyBluez setup command: use_2to3 is invalid.
0075|[end of output]
0076|note: This error originates from a subprocess, and is likely not a problem with pip.
0077|error: metadata-generation-failed
0078|× Encountered error while generating package metadata.
0079|╰─> See above for output.
0080|note: This is an issue with the package mentioned above, not pip.
0081|hint: See above for details.
0082|[notice] A new release of pip is available: 23.3.2 -> 24.0
0083|[notice] To update, run: python3 -m pip install --upgrade pip
0084|********************************************************
0085|* Installation terminée *
0086|********************************************************
effectivement c’est pas logique, j’ai pas regarder cela lors de l’installation. je vois pas ou il a récupéré la 21. elle est réservé pour un autre de mes équipements.
bizare!
)
