Aucune inclusion

Bonjour à tous,
Je dois réinstaller toutes ma configuration suite à un crash de mon nas synology.
Je suis donc sous jeedom en VM.
J’ai mis à jour le rfxcom et une fois branché je le vois bien dans jeedom :

Tout semble ok dans la configuration du plugin :

J’ai laissé le port en auto mais je le vois bien dans la liste proposée :

Malgré tout lorsque je je passe en mode inclusion dans le plugin, aucun matériel ne remonte alors que je voyais bien les trames dans rfxmanager sous Windows. Le module est un RFCtrx433E.

Une idée du problème?

Bonsoir.

Et en sélectionnant le port fixé ?

Sachez que vous pouvez aussi repartir sur votre sauvegarde si vous en avez de viable.

Idemn en selectionnant le port.

Si seulement mon système de sauvegarde avait fonctionné… :confused:

Je dois repartir à 0 en oubliant certains plugins (dont openzwave) qui sont devenus obsolètes et avec DSM qui bloque le passage des ports USB vers la VM…du bonheur

Vous avez activé le protocole nécessaire à l’inclusion de vos périphériques ?

Oui, protocole par défaut et ce sont des sondes de températures oregon :

Bonsoir,
Pour mes sondes Oregon, en inclusion on attend que la led rouge signale une transmission et après je rafraichi l’écran pour que la sonde incluse apparaisse.

Bonsoir,

Oui oui j’attends bien …plusieurs minutes même.

Le boitier RFXCOM est suffisamment éloigné d’un port USB3 (générateur de parasites radio) ?

Sinon, c’est très certainement lié à l’usage de la VM et au mapage du port.

Testez aussi avec le port ttyusb1

Bonjour,

Peut-on voir les logs svp? contenu à coller dans un Texte préformaté (bouton </>), pas de fichier

J’ai essayé tous les ports disponibles…sans succés

Rfxcom_packages

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_rfxcom
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
Launch pre-install of rfxcom dependancy
WARNING: Skipping serial as it is not installed.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package 'python3-serial' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
+ echo 3
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
+ sudo sudo dpkg --configure -a --force-confdef
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 44.1 kB in 1s (51.3 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
1 package can be upgraded. Run 'apt list --upgradable' to see it.
+ echo 4
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-pyudev
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
python3-pyudev
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 37.0 kB of archives.
After this operation, 207 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 python3-pyudev all 0.22.0-2 [37.0 kB]
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:
Fetched 37.0 kB in 0s (192 kB/s)
Selecting previously unselected package python3-pyudev.
(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 ... 71917 files and directories currently installed.)
Preparing to unpack .../python3-pyudev_0.22.0-2_all.deb ...
Unpacking python3-pyudev (0.22.0-2) ...
Setting up python3-pyudev (0.22.0-2) ...
+ echo 5
++ find /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
++ cut -f 2-
++ awk '$1 <= 4'
+ RESULTTODELETE=
++ echo ''
++ sed 's, ,\ ,g'
+ RESULTTODELETE2=
+ echo ''
+ xargs rm -rf
+ echo 6
+ sudo pip3 cache purge
ERROR: No matching packages
+ echo 7
+ sudo pip3 install --upgrade pip
Requirement already satisfied: pip in /usr/lib/python3/dist-packages (20.3.4)
Collecting pip
Downloading pip-24.0-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 20.3.4
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /usr
Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-24.0
+ echo 8
+ sudo python3 -m pip install --force-reinstall --upgrade six
Collecting six
Downloading six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: six
Attempting uninstall: six
Found existing installation: six 1.16.0
Uninstalling six-1.16.0:
Successfully uninstalled six-1.16.0
Successfully installed six-1.16.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
+ echo 9
+ sudo python3 -m pip install --force-reinstall --upgrade requests
Collecting requests
Downloading requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Downloading charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting idna<4,>=2.5 (from requests)
Downloading idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Downloading urllib3-2.2.2-py3-none-any.whl.metadata (6.4 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading certifi-2024.6.2-py3-none-any.whl.metadata (2.2 kB)
Downloading requests-2.32.3-py3-none-any.whl (64 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.9/64.9 kB 1.4 MB/s eta 0:00:00
Downloading certifi-2024.6.2-py3-none-any.whl (164 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 164.4/164.4 kB 3.1 MB/s eta 0:00:00
Downloading charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (142 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 142.3/142.3 kB 5.1 MB/s eta 0:00:00
Downloading idna-3.7-py3-none-any.whl (66 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 2.1 MB/s eta 0:00:00
Downloading urllib3-2.2.2-py3-none-any.whl (121 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.4/121.4 kB 3.4 MB/s eta 0:00:00
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Attempting uninstall: urllib3
Found existing installation: urllib3 1.26.5
Uninstalling urllib3-1.26.5:
Successfully uninstalled urllib3-1.26.5
Attempting uninstall: idna
Found existing installation: idna 2.10
Uninstalling idna-2.10:
Successfully uninstalled idna-2.10
Attempting uninstall: certifi
Found existing installation: certifi 2020.6.20
Uninstalling certifi-2020.6.20:
Successfully uninstalled certifi-2020.6.20
Attempting uninstall: requests
Found existing installation: requests 2.25.1
Uninstalling requests-2.25.1:
Successfully uninstalled requests-2.25.1
Successfully installed certifi-2024.6.2 charset-normalizer-3.3.2 idna-3.7 requests-2.32.3 urllib3-2.2.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
+ echo 10
+ sudo python3 -m pip install --force-reinstall --upgrade setuptools
Collecting setuptools
Downloading setuptools-70.1.0-py3-none-any.whl.metadata (6.0 kB)
Downloading setuptools-70.1.0-py3-none-any.whl (882 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 882.6/882.6 kB 3.6 MB/s eta 0:00:00
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: setuptools
Attempting uninstall: setuptools
Found existing installation: setuptools 52.0.0
Uninstalling setuptools-52.0.0:
Successfully uninstalled setuptools-52.0.0
Successfully installed setuptools-70.1.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
+ echo 11
+ sudo python3 -m pip install --force-reinstall --upgrade pyudev
Collecting pyudev
Downloading pyudev-0.24.3-py3-none-any.whl.metadata (4.6 kB)
Downloading pyudev-0.24.3-py3-none-any.whl (62 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.7/62.7 kB 774.8 kB/s eta 0:00:00
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: pyudev
Attempting uninstall: pyudev
Found existing installation: pyudev 0.22.0
Uninstalling pyudev-0.22.0:
Successfully uninstalled pyudev-0.22.0
Successfully installed pyudev-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
+ echo 12
+ sudo python3 -m pip install --force-reinstall --upgrade pyserial
Collecting pyserial
Downloading pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)
Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 1.3 MB/s eta 0:00:00
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: pyserial
Successfully installed pyserial-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
+ echo 13
+ sudo python3 -m pip install --force-reinstall --upgrade jeedomdaemon
Collecting jeedomdaemon
Downloading jeedomdaemon-0.9.8-py3-none-any.whl.metadata (5.0 kB)
Collecting aiohttp (from jeedomdaemon)
Downloading aiohttp-3.9.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.5 kB)
Collecting aiosignal>=1.1.2 (from aiohttp->jeedomdaemon)
Downloading aiosignal-1.3.1-py3-none-any.whl.metadata (4.0 kB)
Collecting attrs>=17.3.0 (from aiohttp->jeedomdaemon)
Downloading attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting frozenlist>=1.1.1 (from aiohttp->jeedomdaemon)
Downloading frozenlist-1.4.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (12 kB)
Collecting multidict<7.0,>=4.5 (from aiohttp->jeedomdaemon)
Downloading multidict-6.0.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (4.2 kB)
Collecting yarl<2.0,>=1.0 (from aiohttp->jeedomdaemon)
Downloading yarl-1.9.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (31 kB)
Collecting async-timeout<5.0,>=4.0 (from aiohttp->jeedomdaemon)
Downloading async_timeout-4.0.3-py3-none-any.whl.metadata (4.2 kB)
Collecting idna>=2.0 (from yarl<2.0,>=1.0->aiohttp->jeedomdaemon)
Using cached idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Downloading jeedomdaemon-0.9.8-py3-none-any.whl (12 kB)
Downloading aiohttp-3.9.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 4.1 MB/s eta 0:00:00
Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Downloading async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
Downloading attrs-23.2.0-py3-none-any.whl (60 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.8/60.8 kB 679.3 kB/s eta 0:00:00
Downloading frozenlist-1.4.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (240 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 240.7/240.7 kB 2.9 MB/s eta 0:00:00
Downloading multidict-6.0.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (123 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 123.8/123.8 kB 1.6 MB/s eta 0:00:00
Downloading yarl-1.9.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (304 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 304.3/304.3 kB 3.5 MB/s eta 0:00:00
Using cached idna-3.7-py3-none-any.whl (66 kB)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 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
Installing collected packages: multidict, idna, frozenlist, attrs, async-timeout, yarl, aiosignal, aiohttp, jeedomdaemon
Attempting uninstall: idna
Found existing installation: idna 3.7
Uninstalling idna-3.7:
Successfully uninstalled idna-3.7
Successfully installed aiohttp-3.9.5 aiosignal-1.3.1 async-timeout-4.0.3 attrs-23.2.0 frozenlist-1.4.1 idna-3.7 jeedomdaemon-0.9.8 multidict-6.0.5 yarl-1.9.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
+ echo 14
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end rfxcom
+ echo 15
+ rm /tmp/jeedom_install_in_progress_rfxcom
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Rien dans le rfxcomd et rfxcom

passez en debug et relancer le démon

Rfxcom :

[2024-06-20 13:32:31] ERROR  : Erreur sur la fonction deamon_start du plugin : Vous devez attendre au moins 45 secondes entre deux lancements du démon. Dernier lancement : 2024-06-20 13:32:23
[2024-06-20 21:28:13] INFO  : Lancement démon rfxcomd : /usr/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/ttyUSB0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 12,18,20,21,22,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey xS5j2rN18cSTyqgLK9GoHi9RyZjYLkp7cMwx0dwfWyAdP87uHi1PkpsBwoIBI1uk --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
[2024-06-20 21:28:16] INFO  : Démon RFXcom lancé

J’ai retenté une inclusion et miracle…ça fonctionne…je ne comprends pas trop pourquoi mais bon !

Merci d’avoir pris le temps de chercher avec moi :smiley:

1 « J'aime »

Bonjour @mnementh, j’ai un problème qui ressemble au tiens. Tout d’abord j’avais cru à un pb d’installation des dépendances mais Mips m’a bien validé le bon fonctionnement du plugin.

J’ai ces symptômes à savoir :

  • des logs qui indiquent que tout va bien.
  • le démon qui est vert
  • des sondes Orégon qui communiquent bien (validé avec le logiciel RFXMng)
  • des valeurs qui ne remontent pas dans Jeedom
  • de temps en temps mais très rarement une sonde qui revient pour une valeur puis plus rien
  • j’ai changer les piles d’une sonde et depuis impossible de l’inclure.

Tu confirmes que ça marche bien (les sondes envoient régulièrement des infos) et tu pourrais détailler les manips que tu aurais fait pour retrouver un fonctionnement normal ? si tu t’en souviens bien sur :slight_smile: Merci

Bonjour
preneur aussi de la solution, parce que chez moi pareil : tout semble ok , mais rien ne remonte , ni valeurs, ni nouvelles inclusions …

merci

Bonjour,

Pardon de ne pas avoir répondu plus tôt. Je n’avais pas vu la notification.
J’avoue que je ne me souviens pas d’avoir fait grand chose pour que ça fonctionne; à part tester le port ttyUSB0 comme l’avois demandé @Fabrice (ce qui me semblait avoir déjà fait), et passer en mode debug.
Je ne suis pas certain de vous être d’un grand d’aide sur ce coup :confused:

Le mode débug, il faut le quitter au plus vite

Je confirme ce que le changement du port corrige le pb.
Initialement j’avais « RFXCOM RFXtrx433… » que j’ai changé pour « /dev/ttyUSB0 » et dans les minutes qui suivent j’ai retrouver mes sondes.
Ne pas oublier de sauvegarder et surtout de relancer le démon et VICTOIRE :star_struck:
Je vais surveiller cette nuit pour voir si ça tiens dans le temps.

C’est effectivement ce que j’ai fait dés que tout fonctionnait.
Merci encore.