Démon NOK après installation version 2024-09-05 01:00:47

Plugins Protocole domotique
1

Bonjour à tous,

Je suis sur une SMART en R4.4.12
J’ai fais la mise à jour ce matin du plugin BLEA, et suite à cela les dépendances se sont lancées automatiquement. A la fin des dépendances, le démon est resté KO malgré des relances automatique ou manuelle.
Pensant que cela était lié au fait que les antennes aient besoin de mise à jour de dépendances aussi, j’ai fait « envoyer les fichiers » + « lancer les dépendances » sur les 2 antennes externes. Mais cela n’a pas réglé le problème.
Je ne sais plus quelles actions faire pour résoudre mon souci, du coup je demande votre aide.
Voici les logs quand je lance le démon :

0000|[2024-09-05 10:20:03] INFO  : Launching remotes ...
0001|[2024-09-05 10:20:03] INFO  : Lancement du démon distant
0002|[2024-09-05 10:20:03] INFO  : Arret du démon distant
0003|[2024-09-05 10:20:04] INFO  : Commande par SSH fuser -k 55008/tcp >> /dev/null 2>&1 & sur 192.168.1.23
0004|[2024-09-05 10:20:05] INFO  : Lancement démon blea : sudo /usr/bin/python3 /var/www/html/plugins/blea/resources/blead/blead.py --loglevel info --device hci0 --socketport 55008 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname local --noseeninterval 4 --scaninterval 29 --scanmode passive --pid /tmp/jeedom/blea/deamon.pid
0005|[2024-09-05 10:20:09] INFO  : Lancement du démon distant /usr/bin/python3 /home/user/blead/resources/blead/blead.py --loglevel info --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-BallonEauChaude-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 &
0006|[2024-09-05 10:20:09] INFO  : Commande par SSH /usr/bin/python3 /home/user/blead/resources/blead/blead.py --loglevel info --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-BallonEauChaude-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 & sur 192.168.1.23
0007|[2024-09-05 10:20:11] INFO  : Lancement du démon distant
0008|[2024-09-05 10:20:11] INFO  : Arret du démon distant
0009|[2024-09-05 10:20:11] INFO  : Antenna PI-BallonEauChaude-blea alive sending known devices
0010|[2024-09-05 10:20:12] INFO  : Sending ready to daemons
0011|[2024-09-05 10:20:15] INFO  : Commande par SSH fuser -k 55008/tcp >> /dev/null 2>&1 & sur 192.168.1.25
0012|[2024-09-05 10:20:22] INFO  : Lancement du démon distant /usr/bin/python3 /home/pluginblea/blead/resources/blead/blead.py --loglevel info --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-Antenne-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 &
0013|[2024-09-05 10:20:25] INFO  : Commande par SSH /usr/bin/python3 /home/pluginblea/blead/resources/blead/blead.py --loglevel info --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-Antenne-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 & sur 192.168.1.25
0014|[2024-09-05 10:20:32] INFO  : Antenna PI-Antenne-blea alive sending known devices
0015|[2024-09-05 10:20:33] INFO  : Sending ready to daemons
0016|[2024-09-05 10:20:35] ERROR  : Impossible de lancer le démon blea, vérifiez la log
[2024-09-05 10:21:06] INFO  : This is a heartbeat from antenna PI-BallonEauChaude-blea
[2024-09-05 10:21:23] INFO  : This is a heartbeat from antenna PI-Antenne-blea

Merci de vos retours.

2

Bonjour,

Il serait bien de nous montrer la page santé de Jeedom.

Le log d’installation des dépendances de BLEA copié entre balise

Mettre le niveau de log debug au démon, le démarrer et fournir le log

3

Logs Blea en mode débug :

0000|[2024-09-05 10:59:56] INFO  : Launching remotes ...
0001|[2024-09-05 10:59:56] INFO  : Lancement du démon distant
0002|[2024-09-05 10:59:56] INFO  : Arret du démon distant
0003|[2024-09-05 10:59:56] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
0004|[2024-09-05 10:59:56] INFO  : Commande par SSH fuser -k 55008/tcp >> /dev/null 2>&1 & sur 192.168.1.23
0005|[2024-09-05 10:59:57] INFO  : Lancement démon blea : sudo /usr/bin/python3 /var/www/html/plugins/blea/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname local --noseeninterval 4 --scaninterval 29 --scanmode passive --pid /tmp/jeedom/blea/deamon.pid
0006|[2024-09-05 11:00:02] INFO  : Lancement du démon distant /usr/bin/python3 /home/user/blead/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-BallonEauChaude-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 &
0007|[2024-09-05 11:00:02] INFO  : Commande par SSH /usr/bin/python3 /home/user/blead/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-BallonEauChaude-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 & sur 192.168.1.23
0008|[2024-09-05 11:00:03] INFO  : Lancement du démon distant
0009|[2024-09-05 11:00:03] INFO  : Arret du démon distant
0010|[2024-09-05 11:00:04] INFO  : Antenna PI-BallonEauChaude-blea alive sending known devices
0011|[2024-09-05 11:00:04] INFO  : Sending ready to daemons
0012|[2024-09-05 11:00:08] INFO  : Commande par SSH fuser -k 55008/tcp >> /dev/null 2>&1 & sur 192.168.1.25
0013|[2024-09-05 11:00:11] INFO  : Suppression de la log /var/www/html/plugins/blea/core/class/../../../../log/blea_PI-BallonEauChaude-blea
0014|[2024-09-05 11:00:11] INFO  : Récupération de la log distante
0015|[2024-09-05 11:00:12] INFO  : Récupération de fichier depuis 192.168.1.23
0016|[2024-09-05 11:00:13] INFO  : Commande par SSH cat /dev/null > /tmp/blea sur 192.168.1.23
0017|[2024-09-05 11:00:13] DEBUG  :  [sudo] Mot de passe de user : 
0018|[2024-09-05 11:00:14] INFO  : Suppression de la log /var/www/html/plugins/blea/core/class/../../../../log/blea_PI-Antenne-blea
0019|[2024-09-05 11:00:14] INFO  : Récupération de la log distante
0020|[2024-09-05 11:00:14] INFO  : Lancement du démon distant /usr/bin/python3 /home/pluginblea/blead/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-Antenne-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 &
0021|[2024-09-05 11:00:18] INFO  : Récupération de fichier depuis 192.168.1.25
0022|[2024-09-05 11:00:19] INFO  : Commande par SSH /usr/bin/python3 /home/pluginblea/blead/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost "" --callback http://192.168.1.29/plugins/blea/core/php/jeeBlea.php --apikey E0CfMn1d5jvRcIxqOHY2RKd1fPA7K88i --daemonname "PI-Antenne-blea" --noseeninterval 4 --scaninterval 29 --scanmode passive >> /tmp/blea 2>&1 & sur 192.168.1.25
0023|[2024-09-05 11:00:27] ERROR  : Impossible de lancer le démon blea, vérifiez la log
0024|[2024-09-05 11:00:29] INFO  : Commande par SSH cat /dev/null > /tmp/blea sur 192.168.1.25
0025|[2024-09-05 11:00:31] INFO  : Antenna PI-Antenne-blea alive sending known devices
0026|[2024-09-05 11:00:32] INFO  : Sending ready to daemons

Logs d’installation des dépendances :


Log brut  
Rechercher
 

********************************************************
*			 Installation des dépendances			 *
********************************************************
Hit:1 http://www.deb-multimedia.org buster InRelease
Hit:2 https://oph.mdrjr.net/meveric all InRelease
Hit:3 https://oph.mdrjr.net/meveric buster InRelease
Get:4 http://ftp.uk.debian.org/debian buster InRelease [122 kB]
Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [56.6 kB]
Hit:6 http://security.debian.org/debian-security buster/updates InRelease
Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 178 kB in 11s (16.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libatlas-base-dev is already the newest version (3.10.3-8).
build-essential is already the newest version (12.6).
libffi-dev is already the newest version (3.2.1-9).
libopenjp2-7 is already the newest version (2.3.0-2+deb10u2).
python3-serial is already the newest version (3.4-4).
python3-setuptools is already the newest version (40.8.0-1).
python3-dev is already the newest version (3.7.3-1).
python3-pyudev is already the newest version (0.21.0-1).
bluetooth is already the newest version (5.50-1.2~deb10u5).
libbluetooth-dev is already the newest version (5.50-1.2~deb10u5).
libssl-dev is already the newest version (1.1.1n-0+deb10u6).
python3-requests is already the newest version (2.21.0-1+deb10u1).
libtiff5 is already the newest version (4.1.0+git191117-2~deb10u9).
rfkill is already the newest version (2.33.1-0.1+deb10u1).
0 upgraded, 0 newly installed, 0 to remove and 280 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 280 not upgraded.
Need to get 0 B/1191 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 84899 files and directories currently installed.)
Preparing to unpack .../python3_3.7.3-1_arm64.deb ...
running python pre-rtupdate hooks for python3.7...
Unpacking python3 (3.7.3-1) over (3.7.3-1) ...
Preparing to unpack .../bluez_5.50-1.2~deb10u5_arm64.deb ...
Unpacking bluez (5.50-1.2~deb10u5) over (5.50-1.2~deb10u5) ...
Preparing to unpack .../python3-pip_18.1-5_all.deb ...
Unpacking python3-pip (18.1-5) over (18.1-5) ...
Setting up python3 (3.7.3-1) ...
running python rtupdate hooks for python3.7...
running python post-rtupdate hooks for python3.7...
Setting up bluez (5.50-1.2~deb10u5) ...
Setting up python3-pip (18.1-5) ...
Processing triggers for dbus (1.12.16-1) ...
Processing triggers for systemd (241-7~deb10u4) ...
Requirement already satisfied: wheel in /usr/local/lib/python3.7/dist-packages (0.38.2)
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
Requirement already satisfied: setuptools in /usr/local/lib/python3.7/dist-packages (68.0.0)
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
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u9).
libglib2.0-dev is already the newest version (2.58.3-2+deb10u6).
0 upgraded, 0 newly installed, 0 to remove and 280 not upgraded.
Requirement already satisfied: pyudev in /usr/local/lib/python3.7/dist-packages (0.24.3)
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
Requirement already satisfied: pyserial in /usr/local/lib/python3.7/dist-packages (3.5)
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
Requirement already satisfied: requests in /usr/local/lib/python3.7/dist-packages (2.31.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.7/dist-packages (from requests) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.7/dist-packages (from requests) (3.7)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests) (2.0.7)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/dist-packages (from requests) (2024.6.2)
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
Requirement already satisfied: pybluez in /usr/lib/python3/dist-packages (0.22)
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
Requirement already satisfied: pillow in /usr/local/lib/python3.7/dist-packages (9.2.0)
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
Requirement already satisfied: numpy in /usr/local/lib/python3.7/dist-packages (1.21.6)
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
Requirement already satisfied: bluepy in /usr/local/lib/python3.7/dist-packages (1.3.0)
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
Cloning into 'bluepy'...
running build
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/thingy52.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/uuids.json -> build/lib/bluepy
copying bluepy/bluez-src.tgz -> build/lib/bluepy
copying bluepy/bluepy-helper.c -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
copying bluepy/Makefile -> build/lib/bluepy
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:745: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'description-file' will not be supported in future
versions. Please use the underscore name 'description_file' instead.
This deprecation is overdue, please update your project and remove deprecated
calls to avoid build errors in the future.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
running install
running bdist_egg
running egg_info
creating bluepy.egg-info
writing bluepy.egg-info/PKG-INFO
writing dependency_links to bluepy.egg-info/dependency_links.txt
writing entry points to bluepy.egg-info/entry_points.txt
writing top-level names to bluepy.egg-info/top_level.txt
writing manifest file 'bluepy.egg-info/SOURCES.txt'
reading manifest file 'bluepy.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'bluepy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-aarch64/egg
running install_lib
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
creating build/bdist.linux-aarch64
creating build/bdist.linux-aarch64/egg
creating build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/scan_fuzz.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluez-src.tgz -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/Makefile -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/thingy52.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/btle.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/__init__.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/blescan.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/scanner.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluepy-helper.c -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/get_services.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/uuids.json -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/sensortag.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/version.h -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluepy-helper -> build/bdist.linux-aarch64/egg/bluepy
byte-compiling build/bdist.linux-aarch64/egg/bluepy/scan_fuzz.py to scan_fuzz.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/thingy52.py to thingy52.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/btle.py to btle.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/__init__.py to __init__.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/blescan.py to blescan.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/scanner.py to scanner.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/get_services.py to get_services.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/sensortag.py to sensortag.cpython-37.pyc
creating build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/PKG-INFO -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/SOURCES.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/dependency_links.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/entry_points.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/top_level.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:745: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'description-file' will not be supported in future
versions. Please use the underscore name 'description_file' instead.
This deprecation is overdue, please update your project and remove deprecated
calls to avoid build errors in the future.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
/usr/local/lib/python3.7/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
/usr/local/lib/python3.7/dist-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` and ``easy_install``.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://github.com/pypa/setuptools/issues/917 for details.
********************************************************************************
!!
self.initialize_options()
zip_safe flag not set; analyzing archive contents...
bluepy.__pycache__.btle.cpython-37: module references __file__
creating dist
creating 'dist/bluepy-1.3.0-py3.7.egg' and adding 'build/bdist.linux-aarch64/egg' to it
removing 'build/bdist.linux-aarch64/egg' (and everything under it)
Processing bluepy-1.3.0-py3.7.egg
removing '/usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg' (and everything under it)
creating /usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg
Extracting bluepy-1.3.0-py3.7.egg to /usr/lib/python3.7/site-packages
Adding bluepy 1.3.0 to easy-install.pth file
Installing blescan script to /usr/bin
Installing sensortag script to /usr/bin
Installing thingy52 script to /usr/bin
Installed /usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg
Processing dependencies for bluepy==1.3.0
Finished processing dependencies for bluepy==1.3.0
Reading package lists...
Building dependency tree...
Reading state information...
Package 'python3-cryptography' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 280 not upgraded.
Found existing installation: cryptography 2.6.1
Uninstalling cryptography-2.6.1:
Successfully uninstalled cryptography-2.6.1
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
Collecting cryptography==2.6.1
Using cached cryptography-2.6.1-cp37-cp37m-linux_aarch64.whl
Requirement already satisfied: asn1crypto>=0.21.0 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.5.1)
Requirement already satisfied: six>=1.4.1 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.16.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.7/dist-packages (from cffi!=1.11.3,>=1.8->cryptography==2.6.1) (2.21)
Installing collected packages: cryptography
Successfully installed cryptography-2.6.1
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
Requirement already satisfied: pycrypto in /usr/local/lib/python3.7/dist-packages (2.6.1)
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
********************************************************
*			 Installation terminée					*
********************************************************

Santé jeedom

Santé_Jeedom
Santé_Jeedom1881×546 84.9 KB

Santé BLEA

Santé_BLEA
Santé_BLEA1878×301 23.2 KB

Merci d’avance

4

Bonjour,

Et avez-vous un dongle bluetooth sur la smart?

si pas, aucune raison d’avoir le démon local et donc vous n’avez pas de problème (tant que les antennes distantes fonctionnent)

5

Oui, j’ai bien un dongle blea sur la SMART, ou bout d’une rallonge comme préconisé. Ma configuration hardware n’a pas changé depuis que j’ai mis BLEA en place.

6

J’ai 3 antennes : 1 local et 2 déportées

Reseau_BLEA
Reseau_BLEA1480×692 146 KB

7

Bonjour,
même initiative = même conséquence :
Mise à jour de BLEA ce matin = impossible de relancer le démon
Config SMART 16Mo sans changement matériel depuis longtemps
BLEA sur dongle Sena en local (seule antenne) et seul port USB utilisé
Rapport santé

image
image1095×462 59.9 KB

Santé BLEA
image
image1443×137 10.7 KB

Log BLEA

[2024-09-05 13:43:54] INFO  : Updating files on remotes ...
[2024-09-05 13:47:44] INFO  : Launching remotes ...
[2024-09-05 13:47:57] INFO  : Launching remotes ...
[2024-09-05 13:47:57] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-05 13:47:58] INFO  : Lancement démon blea : sudo /usr/bin/python3 /var/www/html/plugins/blea/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php --apikey mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj --daemonname local --noseeninterval 4 --scaninterval 29 --scanmode passive --pid /tmp/jeedom/blea/deamon.pid
[2024-09-05 13:48:28] ERROR  : Impossible de lancer le démon blea, vérifiez la log
[2024-09-05 13:50:04] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-05 13:50:06] INFO  : Lancement démon blea : sudo /usr/bin/python3 /var/www/html/plugins/blea/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php --apikey mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj --daemonname local --noseeninterval 4 --scaninterval 29 --scanmode passive --pid /tmp/jeedom/blea/deamon.pid
[2024-09-05 13:50:36] ERROR  : Impossible de lancer le démon blea, vérifiez la log
[2024-09-05 13:55:04] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-05 13:55:06] INFO  : Lancement démon blea : sudo /usr/bin/python3 /var/www/html/plugins/blea/resources/blead/blead.py --loglevel debug --device hci0 --socketport 55008 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php --apikey mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj --daemonname local --noseeninterval 4 --scaninterval 29 --scanmode passive --pid /tmp/jeedom/blea/deamon.pid
[2024-09-05 13:55:36] ERROR  : Impossible de lancer le démon blea, vérifiez la log

Log BLEA Update

********************************************************
*			 Installation des dépendances			 *
********************************************************
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://ftp.uk.debian.org/debian buster InRelease
Hit:3 http://ftp.uk.debian.org/debian buster-updates InRelease
Hit:4 http://www.deb-multimedia.org buster InRelease
Hit:5 https://oph.mdrjr.net/meveric all InRelease
Hit:6 https://oph.mdrjr.net/meveric buster InRelease
Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libatlas-base-dev is already the newest version (3.10.3-8).
build-essential is already the newest version (12.6).
libffi-dev is already the newest version (3.2.1-9).
libopenjp2-7 is already the newest version (2.3.0-2+deb10u2).
python3-serial is already the newest version (3.4-4).
python3-setuptools is already the newest version (40.8.0-1).
python3-dev is already the newest version (3.7.3-1).
python3-pyudev is already the newest version (0.21.0-1).
bluetooth is already the newest version (5.50-1.2~deb10u5).
libbluetooth-dev is already the newest version (5.50-1.2~deb10u5).
libssl-dev is already the newest version (1.1.1n-0+deb10u6).
python3-requests is already the newest version (2.21.0-1+deb10u1).
libtiff5 is already the newest version (4.1.0+git191117-2~deb10u9).
rfkill is already the newest version (2.33.1-0.1+deb10u1).
0 upgraded, 0 newly installed, 0 to remove and 273 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 273 not upgraded.
Need to get 0 B/1191 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 85066 files and directories currently installed.)
Preparing to unpack .../python3_3.7.3-1_arm64.deb ...
running python pre-rtupdate hooks for python3.7...
Unpacking python3 (3.7.3-1) over (3.7.3-1) ...
Preparing to unpack .../bluez_5.50-1.2~deb10u5_arm64.deb ...
Unpacking bluez (5.50-1.2~deb10u5) over (5.50-1.2~deb10u5) ...
Preparing to unpack .../python3-pip_18.1-5_all.deb ...
Unpacking python3-pip (18.1-5) over (18.1-5) ...
Setting up python3 (3.7.3-1) ...
running python rtupdate hooks for python3.7...
running python post-rtupdate hooks for python3.7...
Setting up bluez (5.50-1.2~deb10u5) ...
Setting up python3-pip (18.1-5) ...
Processing triggers for dbus (1.12.16-1) ...
Processing triggers for systemd (241-7~deb10u4) ...
Requirement already satisfied: wheel in /usr/local/lib/python3.7/dist-packages (0.40.0)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: setuptools in /usr/local/lib/python3.7/dist-packages (68.0.0)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u9).
libglib2.0-dev is already the newest version (2.58.3-2+deb10u6).
0 upgraded, 0 newly installed, 0 to remove and 273 not upgraded.
Requirement already satisfied: pyudev in /usr/local/lib/python3.7/dist-packages (0.24.1)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: pyserial in /usr/local/lib/python3.7/dist-packages (3.4)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: requests in /usr/local/lib/python3.7/dist-packages (2.31.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.7/dist-packages (from requests) (2.0.12)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.7/dist-packages (from requests) (3.4)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests) (2.0.3)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/dist-packages (from requests) (2023.5.7)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: pybluez in /usr/lib/python3/dist-packages (0.22)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: pillow in /usr/local/lib/python3.7/dist-packages (9.5.0)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: numpy in /usr/local/lib/python3.7/dist-packages (1.21.6)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: bluepy in /usr/local/lib/python3.7/dist-packages (1.3.0)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Cloning into 'bluepy'...
running build
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/thingy52.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/uuids.json -> build/lib/bluepy
copying bluepy/bluez-src.tgz -> build/lib/bluepy
copying bluepy/bluepy-helper.c -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
copying bluepy/Makefile -> build/lib/bluepy
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:745: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'description-file' will not be supported in future
versions. Please use the underscore name 'description_file' instead.
This deprecation is overdue, please update your project and remove deprecated
calls to avoid build errors in the future.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
running install
running bdist_egg
running egg_info
creating bluepy.egg-info
writing bluepy.egg-info/PKG-INFO
writing dependency_links to bluepy.egg-info/dependency_links.txt
writing entry points to bluepy.egg-info/entry_points.txt
writing top-level names to bluepy.egg-info/top_level.txt
writing manifest file 'bluepy.egg-info/SOURCES.txt'
reading manifest file 'bluepy.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'bluepy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-aarch64/egg
running install_lib
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
creating build/bdist.linux-aarch64
creating build/bdist.linux-aarch64/egg
creating build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/blescan.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluez-src.tgz -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/uuids.json -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/sensortag.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/scanner.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/get_services.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluepy-helper.c -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/scan_fuzz.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/__init__.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/thingy52.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/bluepy-helper -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/btle.py -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/Makefile -> build/bdist.linux-aarch64/egg/bluepy
copying build/lib/bluepy/version.h -> build/bdist.linux-aarch64/egg/bluepy
byte-compiling build/bdist.linux-aarch64/egg/bluepy/blescan.py to blescan.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/sensortag.py to sensortag.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/scanner.py to scanner.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/get_services.py to get_services.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/scan_fuzz.py to scan_fuzz.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/__init__.py to __init__.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/thingy52.py to thingy52.cpython-37.pyc
byte-compiling build/bdist.linux-aarch64/egg/bluepy/btle.py to btle.cpython-37.pyc
creating build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/PKG-INFO -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/SOURCES.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/dependency_links.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/entry_points.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
copying bluepy.egg-info/top_level.txt -> build/bdist.linux-aarch64/egg/EGG-INFO
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:745: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
********************************************************************************
Usage of dash-separated 'description-file' will not be supported in future
versions. Please use the underscore name 'description_file' instead.
This deprecation is overdue, please update your project and remove deprecated
calls to avoid build errors in the future.
See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
********************************************************************************
!!
opt = self.warn_dash_deprecation(opt, section)
/usr/local/lib/python3.7/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
/usr/local/lib/python3.7/dist-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` and ``easy_install``.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://github.com/pypa/setuptools/issues/917 for details.
********************************************************************************
!!
self.initialize_options()
zip_safe flag not set; analyzing archive contents...
bluepy.__pycache__.btle.cpython-37: module references __file__
creating dist
creating 'dist/bluepy-1.3.0-py3.7.egg' and adding 'build/bdist.linux-aarch64/egg' to it
removing 'build/bdist.linux-aarch64/egg' (and everything under it)
Processing bluepy-1.3.0-py3.7.egg
removing '/usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg' (and everything under it)
creating /usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg
Extracting bluepy-1.3.0-py3.7.egg to /usr/lib/python3.7/site-packages
Adding bluepy 1.3.0 to easy-install.pth file
Installing blescan script to /usr/bin
Installing sensortag script to /usr/bin
Installing thingy52 script to /usr/bin
Installed /usr/lib/python3.7/site-packages/bluepy-1.3.0-py3.7.egg
Processing dependencies for bluepy==1.3.0
Finished processing dependencies for bluepy==1.3.0
Reading package lists...
Building dependency tree...
Reading state information...
Package 'python3-cryptography' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 273 not upgraded.
Found existing installation: cryptography 2.6.1
Uninstalling cryptography-2.6.1:
Successfully uninstalled cryptography-2.6.1
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
Collecting cryptography==2.6.1
Using cached cryptography-2.6.1-cp37-cp37m-linux_aarch64.whl
Requirement already satisfied: asn1crypto>=0.21.0 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.5.1)
Requirement already satisfied: six>=1.4.1 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.16.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.7/dist-packages (from cryptography==2.6.1) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.7/dist-packages (from cffi!=1.11.3,>=1.8->cryptography==2.6.1) (2.21)
Installing collected packages: cryptography
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
mitmproxy 5.3.0 requires cryptography<3.3,>=3.2, but you have cryptography 2.6.1 which is incompatible.
pyopenssl 19.1.0 requires cryptography>=2.8, but you have cryptography 2.6.1 which is incompatible.
zigpy-zigate 0.9.2 requires pyserial>=3.5, but you have pyserial 3.4 which is incompatible.
Successfully installed cryptography-2.6.1
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
Requirement already satisfied: pycrypto in /usr/local/lib/python3.7/dist-packages (2.6.1)
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.2 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
********************************************************
*			 Installation terminée					*
********************************************************

Log BLEA Local

[2024-09-05 11:40:33] INFO  : GLOBAL------Start blead
[2024-09-05 11:40:33] INFO  : GLOBAL------Log level : debug
[2024-09-05 11:40:33] INFO  : GLOBAL------Socket port : 55008
[2024-09-05 11:40:33] INFO  : GLOBAL------Socket host : 127.0.0.1
[2024-09-05 11:40:33] INFO  : GLOBAL------Device : hci0
[2024-09-05 11:40:33] INFO  : GLOBAL------PID file : /tmp/jeedom/blea/deamon.pid
[2024-09-05 11:40:33] INFO  : GLOBAL------Apikey : mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj
[2024-09-05 11:40:33] INFO  : GLOBAL------Callback : http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php
[2024-09-05 11:40:33] INFO  : GLOBAL------Cycle : 0.3
[2024-09-05 11:40:33] INFO  : GLOBAL------Scan interval  : 29
[2024-09-05 11:40:33] INFO  : GLOBAL------Number for no seen : 4
[2024-09-05 11:40:33] INFO  : GLOBAL------Scan Mode : passive
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.amazfitgtr
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.aqualin
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.awoxmesh
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.beagle
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.beewismartdoor
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.blpnr
[2024-09-05 11:40:33] INFO  : LOADER------Import de la configuration devices.divoompixoo
[2024-09-05 11:47:59] INFO  : GLOBAL------Start blead
[2024-09-05 11:47:59] INFO  : GLOBAL------Log level : debug
[2024-09-05 11:47:59] INFO  : GLOBAL------Socket port : 55008
[2024-09-05 11:47:59] INFO  : GLOBAL------Socket host : 127.0.0.1
[2024-09-05 11:47:59] INFO  : GLOBAL------Device : hci0
[2024-09-05 11:47:59] INFO  : GLOBAL------PID file : /tmp/jeedom/blea/deamon.pid
[2024-09-05 11:47:59] INFO  : GLOBAL------Apikey : mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj
[2024-09-05 11:47:59] INFO  : GLOBAL------Callback : http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php
[2024-09-05 11:47:59] INFO  : GLOBAL------Cycle : 0.3
[2024-09-05 11:47:59] INFO  : GLOBAL------Scan interval  : 29
[2024-09-05 11:47:59] INFO  : GLOBAL------Number for no seen : 4
[2024-09-05 11:47:59] INFO  : GLOBAL------Scan Mode : passive
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.amazfitgtr
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.aqualin
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.awoxmesh
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.beagle
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.beewismartdoor
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.blpnr
[2024-09-05 11:47:59] INFO  : LOADER------Import de la configuration devices.divoompixoo
[2024-09-05 11:50:07] INFO  : GLOBAL------Start blead
[2024-09-05 11:50:07] INFO  : GLOBAL------Log level : debug
[2024-09-05 11:50:07] INFO  : GLOBAL------Socket port : 55008
[2024-09-05 11:50:07] INFO  : GLOBAL------Socket host : 127.0.0.1
[2024-09-05 11:50:07] INFO  : GLOBAL------Device : hci0
[2024-09-05 11:50:07] INFO  : GLOBAL------PID file : /tmp/jeedom/blea/deamon.pid
[2024-09-05 11:50:07] INFO  : GLOBAL------Apikey : mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj
[2024-09-05 11:50:07] INFO  : GLOBAL------Callback : http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php
[2024-09-05 11:50:07] INFO  : GLOBAL------Cycle : 0.3
[2024-09-05 11:50:07] INFO  : GLOBAL------Scan interval  : 29
[2024-09-05 11:50:07] INFO  : GLOBAL------Number for no seen : 4
[2024-09-05 11:50:07] INFO  : GLOBAL------Scan Mode : passive
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.amazfitgtr
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.aqualin
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.awoxmesh
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.beagle
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.beewismartdoor
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.blpnr
[2024-09-05 11:50:07] INFO  : LOADER------Import de la configuration devices.divoompixoo
[2024-09-05 11:55:07] INFO  : GLOBAL------Start blead
[2024-09-05 11:55:07] INFO  : GLOBAL------Log level : debug
[2024-09-05 11:55:07] INFO  : GLOBAL------Socket port : 55008
[2024-09-05 11:55:07] INFO  : GLOBAL------Socket host : 127.0.0.1
[2024-09-05 11:55:07] INFO  : GLOBAL------Device : hci0
[2024-09-05 11:55:07] INFO  : GLOBAL------PID file : /tmp/jeedom/blea/deamon.pid
[2024-09-05 11:55:07] INFO  : GLOBAL------Apikey : mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj
[2024-09-05 11:55:07] INFO  : GLOBAL------Callback : http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php
[2024-09-05 11:55:07] INFO  : GLOBAL------Cycle : 0.3
[2024-09-05 11:55:07] INFO  : GLOBAL------Scan interval  : 29
[2024-09-05 11:55:07] INFO  : GLOBAL------Number for no seen : 4
[2024-09-05 11:55:07] INFO  : GLOBAL------Scan Mode : passive
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.amazfitgtr
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.aqualin
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.awoxmesh
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.beagle
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.beewismartdoor
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.blpnr
[2024-09-05 11:55:07] INFO  : LOADER------Import de la configuration devices.divoompixoo
[2024-09-05 12:00:09] INFO  : GLOBAL------Start blead
[2024-09-05 12:00:09] INFO  : GLOBAL------Log level : debug
[2024-09-05 12:00:09] INFO  : GLOBAL------Socket port : 55008
[2024-09-05 12:00:09] INFO  : GLOBAL------Socket host : 127.0.0.1
[2024-09-05 12:00:09] INFO  : GLOBAL------Device : hci0
[2024-09-05 12:00:09] INFO  : GLOBAL------PID file : /tmp/jeedom/blea/deamon.pid
[2024-09-05 12:00:09] INFO  : GLOBAL------Apikey : mjMMY7JUJLTS3n3VUQFMwugESekgV6Hj
[2024-09-05 12:00:09] INFO  : GLOBAL------Callback : http://127.0.0.1:80/plugins/blea/core/php/jeeBlea.php
[2024-09-05 12:00:09] INFO  : GLOBAL------Cycle : 0.3
[2024-09-05 12:00:09] INFO  : GLOBAL------Scan interval  : 29
[2024-09-05 12:00:09] INFO  : GLOBAL------Number for no seen : 4
[2024-09-05 12:00:09] INFO  : GLOBAL------Scan Mode : passive
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.amazfitgtr
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.aqualin
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.awoxmesh
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.beagle
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.beewismartdoor
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.blpnr
[2024-09-05 12:00:09] INFO  : LOADER------Import de la configuration devices.divoompixoo

J’ai tenté de relancer la box : idem
J’ai retiré la Clef Sena et rebranchée : idem

Dans le Log d’update on voit une erreur et :

[notice] To update, run: python3 -m pip install --upgrade pip

Pensez vous que ce serai une bonne idée de lancer la commande « python3 -m pip install » ???
D’autres idées ou suggestions
Merci d’avance …

8

De mon côté, je ne vais pas lancer d’upgrade de python ou d’autres choses car normalement tout est fait via les releases de la SMART.

9

Je partage ce point de vue, normalement en suivant 100% des mises à jour du package standard SMART, il ne devrait pas y avoir de bidouille à lancer…

10

Oui mais Community, c’est un post = un problème
Et la cela ne ressemble pas au même souci

Après, vous êtes sur box officielle, donc le mieux c’est un ticket au support

11

Bonjour lperenna
J’ai donc fait un ticket comme vous me l’avez suggéré.
En attendant, je suis d’accord avec vous que mes log ne sont pas identiques à ceux de « lr3674 »
Pour autant, si j’avais fait un autre post dans Community, il aurait eu le même titre et la même description du problème.
Compte tenu que le Ticket officiel est très spartiate et qu’il n’est pas possible d’y répondre pour apporter des précisions (log et autre), la solution pour résoudre mon problème risque de prendre un certain temp.
Me conseillez vous en // de faire un post spécifique sur Community ?
Avec mes excuses pour mes mauvais respects des usages …
Cordialement

12

Bonjour,

Le support vient de me répondre en ce sens :
« Ok je pense avoir trouvé ca vient de la lib numpy qui a un soucis, je pense que c’est du a la version de debian (10) qui doit plus etre supporté il faudrait passer en debian 11. Si vous etes sur atlas c’est juste un recovery si vous etes sur smart il faut attendre la fin du mois (on est en train de valider la procedure). »

Wait and see.

13

J’ai installé la 4.4.15 qui indiquait ceci dans le changelog :

image
image1071×272 32.2 KB

Et depuis, les 6 plugins que j’avais en màj à faire ont disparu. Si j’avais fait la 4.4.15 avant BLEA, à mon avis la màj de BLEA aurait aussi disparu sur incompatibilité d’OS.

14

Je viens de relancer le démon BLEA et cela fonctionne :slight_smile: une amélioration de la 4.4.15?
@AlainGew67 tu peux peut être tester la 4.4.15?

15

Non la 4.4.15 n’aurait pas empêché la mise à jour car on se savait même pas que le plugin était pas compatible Debian 10. En vrai c’est même pas la mise à jour qui casse la compatibilité mais la relance des dépendances qui met à jour la lib numpy qui a un bug et ne marche plus sous debian 10

16

Je ne comprends pas car je suis toujours sous Debian10. Et la seule chose qui a changé entre hier avec mon démon BLEA KO et aujourd’hui avec mon démon BLEA KO, c’est le passage de 4.4.12 vers 4.4.15.

17

Je sais pas non plus et j’ai pas de debian 10 pour tester.

18

Hello,

J’ai plus ou moins un problème similaire. Ca semble se produire depuis la maj en 4.4.15.
Tous les soirs à minuit, le plugin semble planter, mes capteurs NUT passent activés/désactivés en boucle. Le démon du plugin ne se lance plus et la partie Port clé Bluetooth de la configure est vide.
Si je remets la config et relance le démon manuellement c’est repartie et tout fonctionne correctement jusqu’au lendemain minuit.
J’ai vu dans les changelogs un « Ajout d’un redémarrage du démon la nuit (pour limiter les soucis mémoire) » déployé le 02/09. Est-ce que ca pourrait être lié au problème qui se produit une fois par jour à minuit ?
Pour info je tourne encore en Debian 10.13 et Jeedom 4.4.15.

Sans forcément migrer en Debian 11, auriez-vous une alternative ? Peut-être désactiver le cron daily du plugin si c’est celui-ci qui pose problème à minuit ?

19

Non car debian 10 est obsolète. Il te faut changer ou ne plus toucher à ton jeedom, avec les risques que cela comporte et autrea inconvénients.

Antoine

20

C’est ce que j’avais vu aussi mais je pensais pas me lancer sur la migration tout de suite. Finalement va bien falloir…je vais chopper une autre SD pour migrer sur debian 11 tout en gardant ma SD en 10 sait-on jamais.
En attendant, ce problème apparu ces derniers jours serait-il plus lié à une incompatibilité entre debian 10 et la version 4.4.15 ou le plugin ?