BLEA : non fonctionnement

Plugins
,
1

Bonjour

J’ai un soucis de fonctionnement avec ce plugin.
Je ne sais dire depuis quand, mais je suppose depuis version core en 4.4…

J’ai 2 Nut qui détectent la présence et activent des scénarios de présence et widget de présence.

Là, il n’y a plus de détection des Nut.
Lorsque je relance le demon, cela ne fait rien.
Lorsque je relance les dépendances : cela met à jour les widgets et scénarios au bon statut de présence, mais pas plus.
Si je m’absente à nouveau, il n’y a aucunes actions.
Dans les log de HTTP.error, il y a des données concernant BLEA, mais je ne sais les comprendre.
Voici une partie des log :

#0 {main}
  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://jeedomatlas.local/index.php?v=d&p=plan&plan_id=1
[Thu Jun 20 17:23:43.823232 2024] [php7:error] [pid 3432972] [client 192.168.1.11:32868] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223
Stack trace:
#0 {main}
  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://jeedomatlas.local/index.php?v=d&p=plan&plan_id=1
[Fri Jun 21 08:18:42.155287 2024] [access_compat:error] [pid 4132440] [client 142.250.32.40:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json
[Fri Jun 21 08:18:42.187581 2024] [access_compat:error] [pid 3608784] [client 66.102.9.238:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json
[Fri Jun 28 07:10:02.444776 2024] [access_compat:error] [pid 3248990] [client 142.250.32.33:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json
[Fri Jun 28 07:10:02.572059 2024] [access_compat:error] [pid 3245317] [client 66.102.9.236:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json
[Fri Jun 28 08:15:38.582237 2024] [access_compat:error] [pid 3284932] [client 142.250.32.32:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json
[Fri Jun 28 08:15:38.588954 2024] [access_compat:error] [pid 3797781] [client 142.250.32.32:0] AH01797: client denied by server configuration: /var/www/html/.well-known/assetlinks.json

[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: python3 -m pip install --upgrade pip

[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: python3 -m pip install --upgrade pip
warning: commands will be executed using /bin/sh
job 20092 at Fri Jun 28 09:48:00 2024

[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: python3 -m pip install --upgrade pip

Merci à vous.

2

Bonjour,

Pour ce problème, vu que vous êtes sur une Atlas, ouvrez un ticket auprès de Jeedom.

Merci de partager la solution qui vous sera donnée si d’autres utilisateurs rencontrent le même problème que vous.

3

OK, j’ouvre un ticket.
Merci

4

Bonjour,
Pas sur que ca corrige le soucis de fond (et j’en suis pas capable car je connais pas du tout le plugin) mais j’ai corrigé l’erreur que tu remontes, ca sera bon dans la beta de demain.

5

J’ai fait une MAJ du plugin BLEA en beta le 30/06 à 8h00 et cela n’a rien changé.
Je suis en échange avec Denis suite a demande de ticket.

6

Toujours la meme erreur dans les logs ? a mon avis c’est une autre non ?

7

voici les log de HTTP.error :

0394|[notice] A new release of pip is available: 24.0 -> 24.1.1
0395|[notice] To update, run: python3 -m pip install --upgrade pip
0396|[notice] A new release of pip is available: 24.0 -> 24.1.1
0397|[notice] To update, run: python3 -m pip install --upgrade pip
0398|[notice] A new release of pip is available: 24.0 -> 24.1.1
0399|[notice] To update, run: python3 -m pip install --upgrade pip
0400|warning: commands will be executed using /bin/sh
0401|job 21023 at Mon Jul  1 15:16:00 2024
0402|warning: commands will be executed using /bin/sh
0403|job 21059 at Mon Jul  1 18:13:00 2024
0404|[Mon Jul 01 18:51:27.983769 2024] [mpm_prefork:notice] [pid 1212] AH00170: caught SIGWINCH, shutting down gracefully
0405|[Mon Jul 01 18:52:26.456028 2024] [mpm_prefork:notice] [pid 1210] AH00163: Apache/2.4.56 (Debian) configured -- resuming normal operations
0406|[Mon Jul 01 18:52:26.458703 2024] [core:notice] [pid 1210] AH00094: Command line: '/usr/sbin/apache2'

Denis a lancé cette commande cet après midi :

sudo python3 -m pip install --upgrade pip
8

Ok donc j’ai bien corriger l’erreur que j’étais capable de corriger

9

Bonjour

J’ai également ce message d’erreur dans les log http.error concernant BLEA…
Est ce le même soucis?

0495|Stack trace:
0496|#0 /var/www/html/core/class/cmd.class.php(1314): voletPropCmd->execute()
0497|#1 /var/www/html/core/ajax/cmd.ajax.php(102): cmd->execCmd()
0498|#2 {main}
0499|thrown in /var/www/html/plugins/voletProp/core/class/voletProp.class.php on line 515
0500|warning: commands will be executed using /bin/sh
0501|job 44 at Tue Jul  2 07:00:00 2024
0502|[Tue Jul 02 07:02:20.525392 2024] [mpm_prefork:notice] [pid 2348394] AH00170: caught SIGWINCH, shutting down gracefully
0503|[Tue Jul 02 07:02:21.731052 2024] [mpm_prefork:notice] [pid 681372] AH00163: Apache/2.4.56 (Debian) configured -- resuming normal operations
0504|[Tue Jul 02 07:02:21.731277 2024] [core:notice] [pid 681372] AH00094: Command line: '/usr/sbin/apache2'
0505|[Tue Jul 02 07:25:07.812582 2024] [php7:error] [pid 694091] [client 192.168.1.55:55667] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&m=blea&p=blea
0506|[Tue Jul 02 07:25:12.833469 2024] [php7:error] [pid 694403] [client 192.168.1.55:55665] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=health
0507|[Tue Jul 02 07:25:17.812355 2024] [php7:error] [pid 691132] [client 192.168.1.55:55666] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=health
0508|[Tue Jul 02 07:25:22.811725 2024] [php7:error] [pid 692115] [client 192.168.1.55:55668] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=health
0509|[Tue Jul 02 07:25:27.830870 2024] [php7:error] [pid 694870] [client 192.168.1.55:55670] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=report
0510|[Tue Jul 02 07:25:32.812256 2024] [php7:error] [pid 694860] [client 192.168.1.55:55671] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=history
0511|[Tue Jul 02 07:25:37.812330 2024] [php7:error] [pid 691132] [client 192.168.1.55:55673] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=history
0512|[Tue Jul 02 07:25:42.825370 2024] [php7:error] [pid 686249] [client 192.168.1.55:55664] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=history
0513|[Tue Jul 02 07:25:47.819477 2024] [php7:error] [pid 693785] [client 192.168.1.55:55675] PHP Fatal error:  Uncaught Error: Call to undefined function displayExeption() in /var/www/html/plugins/blea/core/ajax/blea.ajax.php:223\nStack trace:\n#0 {main}\n  thrown in /var/www/html/plugins/blea/core/ajax/blea.ajax.php on line 223, referer: http://192.168.1.96/index.php?v=d&p=history
10

Bonjour
Ça c’est l’erreur que j’ai corrigé en beta

11

Bonjour.

Installez la version bêta du plugin et dites nous si la correction est ok

Ainsi, elle passera plus facilement en stable.

12

Je viens d’installer la version beta du plugin BLEA

1836|[notice] A new release of pip is available: 24.0 -> 24.1.1
1837|[notice] To update, run: python3 -m pip install --upgrade pip
13

Merci.

Ce message, juste une fois où en boucle ?

Il est nécessaire de passer votre installation en Debian 11.
La version 10;que vous utilisez certainement, n’a plus de support et des dépendances vont disparaitre.

Mais attention, le plugin BLEA n’est pas complètement compatible avec Debian 11. Il se remplace pour une très grosse partie de ses fonctionnalités avec les plugins :
Mqttdiscovery et Theengs Gateway (tgw).
L’installation des ces deux plugins et la mise en place des antennes est bien plus simple que BLEA. Ces deux plugins sont compatibles avec Jeedom 4.4.x et Debian 11 et 12.

14

Je suis déjà en debian 11.8
Vu que je suis passée en Beta, les images Hydrao ont disparu et je viens de les remettre

1713|job 46 at Tue Jul  2 08:34:00 2024
1714|[notice] A new release of pip is available: 24.0 -> 24.1.1
1715|[notice] To update, run: python3 -m pip install --upgrade pip
1716|[notice] A new release of pip is available: 24.0 -> 24.1.1
1717|[notice] To update, run: python3 -m pip install --upgrade pip
1718|[notice] A new release of pip is available: 24.0 -> 24.1.1
1719|[notice] To update, run: python3 -m pip install --upgrade pip
1720|[notice] A new release of pip is available: 24.0 -> 24.1.1
1721|[notice] To update, run: python3 -m pip install --upgrade pip
1722|[notice] A new release of pip is available: 24.0 -> 24.1.1
1723|[notice] To update, run: python3 -m pip install --upgrade pip
1724|[notice] A new release of pip is available: 24.0 -> 24.1.1
1725|[notice] To update, run: python3 -m pip install --upgrade pip
1726|[notice] A new release of pip is available: 24.0 -> 24.1.1
1727|[notice] To update, run: python3 -m pip install --upgrade pip
1728|[notice] A new release of pip is available: 24.0 -> 24.1.1
1729|[notice] To update, run: python3 -m pip install --upgrade pip
1730|[notice] A new release of pip is available: 24.0 -> 24.1.1
1731|[notice] To update, run: python3 -m pip install --upgrade pip
1732|[notice] A new release of pip is available: 24.0 -> 24.1.1
1733|[notice] To update, run: python3 -m pip install --upgrade pip
1734|[notice] A new release of pip is available: 24.0 -> 24.1.1
1735|[notice] To update, run: python3 -m pip install --upgrade pip
1736|[notice] A new release of pip is available: 24.0 -> 24.1.1
1737|[notice] To update, run: python3 -m pip install --upgrade pip
1738|[notice] A new release of pip is available: 24.0 -> 24.1.1
1739|[notice] To update, run: python3 -m pip install --upgrade pip
1740|[notice] A new release of pip is available: 24.0 -> 24.1.1
1741|[notice] To update, run: python3 -m pip install --upgrade pip
1742|[notice] A new release of pip is available: 24.0 -> 24.1.1
1743|[notice] To update, run: python3 -m pip install --upgrade pip
1744|[notice] A new release of pip is available: 24.0 -> 24.1.1
1745|[notice] To update, run: python3 -m pip install --upgrade pip
1746|[notice] A new release of pip is available: 24.0 -> 24.1.1
1747|[notice] To update, run: python3 -m pip install --upgrade pip
1748|[notice] A new release of pip is available: 24.0 -> 24.1.1
1749|[notice] To update, run: python3 -m pip install --upgrade pip
1750|[notice] A new release of pip is available: 24.0 -> 24.1.1
1751|[notice] To update, run: python3 -m pip install --upgrade pip
1752|[notice] A new release of pip is available: 24.0 -> 24.1.1
1753|[notice] To update, run: python3 -m pip install --upgrade pip
1754|[notice] A new release of pip is available: 24.0 -> 24.1.1
1755|[notice] To update, run: python3 -m pip install --upgrade pip
1756|[notice] A new release of pip is available: 24.0 -> 24.1.1
1757|[notice] To update, run: python3 -m pip install --upgrade pip
1758|[notice] A new release of pip is available: 24.0 -> 24.1.1
1759|[notice] To update, run: python3 -m pip install --upgrade pip
1760|[notice] A new release of pip is available: 24.0 -> 24.1.1
1761|[notice] To update, run: python3 -m pip install --upgrade pip
1762|[notice] A new release of pip is available: 24.0 -> 24.1.1
1763|[notice] To update, run: python3 -m pip install --upgrade pip
1764|[notice] A new release of pip is available: 24.0 -> 24.1.1
1765|[notice] To update, run: python3 -m pip install --upgrade pip
1766|[notice] A new release of pip is available: 24.0 -> 24.1.1
1767|[notice] To update, run: python3 -m pip install --upgrade pip
1768|[notice] A new release of pip is available: 24.0 -> 24.1.1
1769|[notice] To update, run: python3 -m pip install --upgrade pip
1770|[notice] A new release of pip is available: 24.0 -> 24.1.1
1771|[notice] To update, run: python3 -m pip install --upgrade pip
1772|[notice] A new release of pip is available: 24.0 -> 24.1.1
1773|[notice] To update, run: python3 -m pip install --upgrade pip
1774|[notice] A new release of pip is available: 24.0 -> 24.1.1
1775|[notice] To update, run: python3 -m pip install --upgrade pip
1776|[notice] A new release of pip is available: 24.0 -> 24.1.1
1777|[notice] To update, run: python3 -m pip install --upgrade pip
1778|[notice] A new release of pip is available: 24.0 -> 24.1.1
1779|[notice] To update, run: python3 -m pip install --upgrade pip
1780|[notice] A new release of pip is available: 24.0 -> 24.1.1
1781|[notice] To update, run: python3 -m pip install --upgrade pip
1782|[notice] A new release of pip is available: 24.0 -> 24.1.1
1783|[notice] To update, run: python3 -m pip install --upgrade pip
1784|[notice] A new release of pip is available: 24.0 -> 24.1.1
1785|[notice] To update, run: python3 -m pip install --upgrade pip
1786|[notice] A new release of pip is available: 24.0 -> 24.1.1
1787|[notice] To update, run: python3 -m pip install --upgrade pip
1788|[notice] A new release of pip is available: 24.0 -> 24.1.1
1789|[notice] To update, run: python3 -m pip install --upgrade pip
1790|[notice] A new release of pip is available: 24.0 -> 24.1.1
1791|[notice] To update, run: python3 -m pip install --upgrade pip
1792|[notice] A new release of pip is available: 24.0 -> 24.1.1
1793|[notice] To update, run: python3 -m pip install --upgrade pip
1794|[notice] A new release of pip is available: 24.0 -> 24.1.1
1795|[notice] To update, run: python3 -m pip install --upgrade pip
1796|[notice] A new release of pip is available: 24.0 -> 24.1.1
1797|[notice] To update, run: python3 -m pip install --upgrade pip
1798|[notice] A new release of pip is available: 24.0 -> 24.1.1
1799|[notice] To update, run: python3 -m pip install --upgrade pip
1800|[notice] A new release of pip is available: 24.0 -> 24.1.1
1801|[notice] To update, run: python3 -m pip install --upgrade pip
1802|[notice] A new release of pip is available: 24.0 -> 24.1.1
1803|[notice] To update, run: python3 -m pip install --upgrade pip
1804|[notice] A new release of pip is available: 24.0 -> 24.1.1
1805|[notice] To update, run: python3 -m pip install --upgrade pip
1806|[notice] A new release of pip is available: 24.0 -> 24.1.1
1807|[notice] To update, run: python3 -m pip install --upgrade pip
1808|[notice] A new release of pip is available: 24.0 -> 24.1.1
1809|[notice] To update, run: python3 -m pip install --upgrade pip
1810|[notice] A new release of pip is available: 24.0 -> 24.1.1
1811|[notice] To update, run: python3 -m pip install --upgrade pip
1812|[notice] A new release of pip is available: 24.0 -> 24.1.1
1813|[notice] To update, run: python3 -m pip install --upgrade pip
1814|[notice] A new release of pip is available: 24.0 -> 24.1.1
1815|[notice] To update, run: python3 -m pip install --upgrade pip
1816|[notice] A new release of pip is available: 24.0 -> 24.1.1
1817|[notice] To update, run: python3 -m pip install --upgrade pip
1818|[notice] A new release of pip is available: 24.0 -> 24.1.1
1819|[notice] To update, run: python3 -m pip install --upgrade pip
1820|[notice] A new release of pip is available: 24.0 -> 24.1.1
1821|[notice] To update, run: python3 -m pip install --upgrade pip
1822|[notice] A new release of pip is available: 24.0 -> 24.1.1
1823|[notice] To update, run: python3 -m pip install --upgrade pip
1824|[notice] A new release of pip is available: 24.0 -> 24.1.1
1825|[notice] To update, run: python3 -m pip install --upgrade pip
1826|[notice] A new release of pip is available: 24.0 -> 24.1.1
1827|[notice] To update, run: python3 -m pip install --upgrade pip
1828|[notice] A new release of pip is available: 24.0 -> 24.1.1
1829|[notice] To update, run: python3 -m pip install --upgrade pip
1830|[notice] A new release of pip is available: 24.0 -> 24.1.1
1831|[notice] To update, run: python3 -m pip install --upgrade pip
1832|[notice] A new release of pip is available: 24.0 -> 24.1.1
1833|[notice] To update, run: python3 -m pip install --upgrade pip
1834|[notice] A new release of pip is available: 24.0 -> 24.1.1
1835|[notice] To update, run: python3 -m pip install --upgrade pip
1836|[notice] A new release of pip is available: 24.0 -> 24.1.1
1837|[notice] To update, run: python3 -m pip install --upgrade pip
1838|libpng warning: Interlace handling should be turned on when using png_read_image
1839|libpng warning: Interlace handling should be turned on when using png_read_image
1840|libpng warning: Interlace handling should be turned on when using png_read_image

Je vais essayer un des autres plugin car mon antenne se déconnecte souvent

15

Bonjour

En fait:
plugin-tgw sert à installer theengsgateway. Il n’est pas indispensable si on maitrise le docker.
plugin-mqttdiscovery permet d’utiliser le.mqtt discovery de HA avec jeedom. Cela ouvre pas mal de possibilité en sus du bluetooth: zwave, zigbee, etc.

Antoine

16

Merci
Je vais regarder ça car le non fonctionnement du BLEA correspond à peu près la MAJ en 4.4…

et rien de concret en solution via la demande de ticket, les actions faites à ce jour n’ont rien donnés.

17

Je viens de regarder ces 2 plugins :
Ce ne sont pas des plugins officiels et ils dépendent de l’installation d’un autre plugin.
Donc j’évite.

Bluetooth Advertisement, est un plugin officiel :
Il n’est pas du tout envisageable qu’il soit compatible avec la version 4.4.x du Core de Jeedom ?

Merci

18

Chez moi il fonctionne (version bêta) donc ça dépend pas que de la version du core.

Peut-être lié à des versions de package os ou python (que j’ai tendance à mettre à jour régulièrement).

dsl de pas pouvoir aider plus, il faudrait sûrement comparer des trucs mais je sais pas quoi…

19

Vous êtes sous Debian 11 ?
Pas de problème de mémoire et de saturation du Swap au bout de quelques jours ?

20

Je ne sais pas quoi répondre à votre message.
Dans votre signature, il y a beaucoup de plugins non officiels et là, d’un coup, cela vous gêne.

Le plugin BLEA est abandonné depuis des années, alors que le dev des plugins Mqttdiscovery et tgw est exemplaire en terme de suivi (comme pas mal de développeurs indépendants).

Je reste sans voix