Toutes les données de température se figent

Bonjour et meilleurs vœux à tous.

J’ai réinstallé Jeedom sur un RPI4 en décembre.
Avec l’aide de Mips le plugin RFXcom a fini par fonctionner :

Néanmoins j’ai toujours un problème et je ne m’en sors pas.
De temps en temps Jeedom ne reçoit plus les données de mes 8 capteurs de température. Tout se fige avec une périodicité très variable, d’une heure à ~12 heures, voire plus quelquefois. Il n’y a aucun message d’erreur quand ça se fige.
Ca repart quand je relance le demon.

Je n’ai rien trouvé de similaire sur le forum.

Précision : Je n’ai pas changé le câble entre le RPI et le boitier RFX et j’utilise ces 8 sondes depuis des années.

Dans les logs, j’ai ceci :

  1. rfxcomd : message d’erreur suivant à chaque relance des dépendances
    0006|[2025-01-07 12:14:23] ERROR : Timeout waiting status, is your rfxcom firmware up to date ?

Mon boitier est du type RFXtrx433XL.
J’ai installé la dernière version du firmware : RFXtrx433XL_ProXL1_1050.hex
Le fichier readme précise : RFXtrx433XL-ProXL1 and RFXtrx433XL-ProXL2 firmware will only operate in the RFXtrx433XL
Donc je dois être bon et j’ai la dernière version.

  1. rfxcom packages : plusieurs warnings dans les logs (générés à chaque relance des dépendances), mais je suis incapable de les interpréter.
0000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_rfxcom
0003|+ echo 1
0004|+ echo 2
0005|+ sudo chmod +x /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
0006|+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
0007|Launch pre-install of rfxcom dependancy
0008|WARNING: Skipping serial as it is not installed.
0009|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0010|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0011|Reading package lists...
0012|Building dependency tree...
0013|Reading state information...
0014|Package 'python3-serial' is not installed, so not removed
0015|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0016|+ echo 3
0017|+ sudo killall apt apt-get unattended-upgr
0018|apt: no process found
0019|apt-get: no process found
0020|unattended-upgr: no process found
0021|+ sudo rm /var/lib/apt/lists/lock
0022|+ sudo rm /var/cache/apt/archives/lock
0023|+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
0024|+ sudo sudo dpkg --configure -a --force-confdef
0025|+ sudo apt update
0026|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0027|Hit:1 http://deb.debian.org/debian bullseye InRelease
0028|Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
0029|Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
0030|Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
0031|Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
0032|Reading package lists...
0033|Building dependency tree...
0034|Reading state information...
0035|All packages are up to date.
0036|+ echo 4
0037|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3
0038|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0039|Reading package lists...
0040|Building dependency tree...
0041|Reading state information...
0042|python3 is already the newest version (3.9.2-3).
0043|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0044|+ echo 5
0045|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-pip
0046|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0047|Reading package lists...
0048|Building dependency tree...
0049|Reading state information...
0050|python3-pip is already the newest version (20.3.4-4+rpt1+deb11u1).
0051|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0052|+ echo 6
0053|+ sudo apt install -o Dpkg::Options::=--force-confdef -y build-essential
0054|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0055|Reading package lists...
0056|Building dependency tree...
0057|Reading state information...
0058|build-essential is already the newest version (12.9).
0059|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0060|+ echo 7
0061|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-pyudev
0062|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0063|Reading package lists...
0064|Building dependency tree...
0065|Reading state information...
0066|python3-pyudev is already the newest version (0.22.0-2).
0067|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0068|+ echo 8
0069|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-dev
0070|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0071|Reading package lists...
0072|Building dependency tree...
0073|Reading state information...
0074|python3-dev is already the newest version (3.9.2-3).
0075|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0076|+ echo 9
0077|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-requests
0078|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0079|Reading package lists...
0080|Building dependency tree...
0081|Reading state information...
0082|python3-requests is already the newest version (2.25.1+dfsg-2).
0083|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0084|+ echo 10
0085|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-setuptools
0086|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0087|Reading package lists...
0088|Building dependency tree...
0089|Reading state information...
0090|python3-setuptools is already the newest version (52.0.0-4+deb11u1).
0091|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0092|+ echo 11
0093|++ find /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
0094|++ awk '$1 <= 4'
0095|++ cut -f 2-
0096|+ RESULTTODELETE=
0097|++ echo ''
0098|++ sed 's, ,\ ,g'
0099|+ RESULTTODELETE2=
0100|+ echo ''
0101|+ xargs rm -rf
0102|+ echo 12
0103|+ sudo pip3 cache purge
0104|Files removed: 136
0105|+ echo 13
0106|+ sudo pip3 install --upgrade pip
0107|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0108|Requirement already satisfied: pip in /usr/local/lib/python3.9/dist-packages (24.3.1)
0109|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0110|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0111|+ echo 14
0112|+ sudo python3 -m pip install --force-reinstall --upgrade six
0113|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0114|Collecting six
0115|Downloading https://www.piwheels.org/simple/six/six-1.17.0-py2.py3-none-any.whl (11 kB)
0116|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0117|Installing collected packages: six
0118|Attempting uninstall: six
0119|Found existing installation: six 1.17.0
0120|Uninstalling six-1.17.0:
0121|Successfully uninstalled six-1.17.0
0122|Successfully installed six-1.17.0
0123|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0124|+ echo 15
0125|+ sudo python3 -m pip install --force-reinstall --upgrade requests
0126|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0127|Collecting requests
0128|Downloading https://www.piwheels.org/simple/requests/requests-2.32.3-py3-none-any.whl (64 kB)
0129|Collecting charset-normalizer<4,>=2 (from requests)
0130|Downloading charset_normalizer-3.4.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (35 kB)
0131|Collecting idna<4,>=2.5 (from requests)
0132|Downloading https://www.piwheels.org/simple/idna/idna-3.10-py3-none-any.whl (70 kB)
0133|Collecting urllib3<3,>=1.21.1 (from requests)
0134|Downloading https://www.piwheels.org/simple/urllib3/urllib3-2.3.0-py3-none-any.whl (128 kB)
0135|Collecting certifi>=2017.4.17 (from requests)
0136|Downloading https://www.piwheels.org/simple/certifi/certifi-2024.12.14-py3-none-any.whl (164 kB)
0137|Downloading charset_normalizer-3.4.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (141 kB)
0138|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0139|Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
0140|Attempting uninstall: urllib3
0141|Found existing installation: urllib3 2.3.0
0142|Uninstalling urllib3-2.3.0:
0143|Successfully uninstalled urllib3-2.3.0
0144|Attempting uninstall: idna
0145|Found existing installation: idna 3.10
0146|Uninstalling idna-3.10:
0147|Successfully uninstalled idna-3.10
0148|Attempting uninstall: charset-normalizer
0149|Found existing installation: charset-normalizer 3.4.1
0150|Uninstalling charset-normalizer-3.4.1:
0151|Successfully uninstalled charset-normalizer-3.4.1
0152|Attempting uninstall: certifi
0153|Found existing installation: certifi 2024.12.14
0154|Uninstalling certifi-2024.12.14:
0155|Successfully uninstalled certifi-2024.12.14
0156|Attempting uninstall: requests
0157|Found existing installation: requests 2.32.3
0158|Uninstalling requests-2.32.3:
0159|Successfully uninstalled requests-2.32.3
0160|Successfully installed certifi-2024.12.14 charset-normalizer-3.4.1 idna-3.10 requests-2.32.3 urllib3-2.3.0
0161|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0162|+ echo 16
0163|+ sudo python3 -m pip install --force-reinstall --upgrade setuptools
0164|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0165|Collecting setuptools
0166|Downloading https://www.piwheels.org/simple/setuptools/setuptools-75.7.0-py3-none-any.whl (1.2 MB)
0167|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 13.0 MB/s eta 0:00:00
0168|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0169|Installing collected packages: setuptools
0170|Attempting uninstall: setuptools
0171|Found existing installation: setuptools 75.7.0
0172|Uninstalling setuptools-75.7.0:
0173|Successfully uninstalled setuptools-75.7.0
0174|Successfully installed setuptools-75.7.0
0175|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0176|+ echo 17
0177|+ sudo python3 -m pip install --force-reinstall --upgrade pyudev
0178|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0179|Collecting pyudev
0180|Downloading https://www.piwheels.org/simple/pyudev/pyudev-0.24.3-py3-none-any.whl (62 kB)
0181|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0182|Installing collected packages: pyudev
0183|Attempting uninstall: pyudev
0184|Found existing installation: pyudev 0.24.3
0185|Uninstalling pyudev-0.24.3:
0186|Successfully uninstalled pyudev-0.24.3
0187|Successfully installed pyudev-0.24.3
0188|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0189|+ echo 18
0190|+ sudo python3 -m pip install --force-reinstall --upgrade pyserial
0191|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0192|Collecting pyserial
0193|Downloading https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB)
0194|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0195|Installing collected packages: pyserial
0196|Attempting uninstall: pyserial
0197|Found existing installation: pyserial 3.5
0198|Uninstalling pyserial-3.5:
0199|Successfully uninstalled pyserial-3.5
0200|Successfully installed pyserial-3.5
0201|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0202|+ echo 19
0203|+ sudo python3 -m pip install --force-reinstall --upgrade jeedomdaemon
0204|Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
0205|Collecting jeedomdaemon
0206|Downloading https://www.piwheels.org/simple/jeedomdaemon/jeedomdaemon-1.2.0-py3-none-any.whl (13 kB)
0207|Collecting aiohttp (from jeedomdaemon)
0208|Downloading aiohttp-3.11.11-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (7.7 kB)
0209|Collecting aiohappyeyeballs>=2.3.0 (from aiohttp->jeedomdaemon)
0210|Downloading https://www.piwheels.org/simple/aiohappyeyeballs/aiohappyeyeballs-2.4.4-py3-none-any.whl (14 kB)
0211|Collecting aiosignal>=1.1.2 (from aiohttp->jeedomdaemon)
0212|Downloading https://www.piwheels.org/simple/aiosignal/aiosignal-1.3.2-py2.py3-none-any.whl (7.6 kB)
0213|Collecting async-timeout<6.0,>=4.0 (from aiohttp->jeedomdaemon)
0214|Downloading https://www.piwheels.org/simple/async-timeout/async_timeout-5.0.1-py3-none-any.whl (6.2 kB)
0215|Collecting attrs>=17.3.0 (from aiohttp->jeedomdaemon)
0216|Downloading https://www.piwheels.org/simple/attrs/attrs-24.3.0-py3-none-any.whl (63 kB)
0217|Collecting frozenlist>=1.1.1 (from aiohttp->jeedomdaemon)
0218|Downloading frozenlist-1.5.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (13 kB)
0219|Collecting multidict<7.0,>=4.5 (from aiohttp->jeedomdaemon)
0220|Downloading multidict-6.1.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (5.0 kB)
0221|Collecting propcache>=0.2.0 (from aiohttp->jeedomdaemon)
0222|Downloading propcache-0.2.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (9.2 kB)
0223|Collecting yarl<2.0,>=1.17.0 (from aiohttp->jeedomdaemon)
0224|Downloading yarl-1.18.3-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (69 kB)
0225|Collecting typing-extensions>=4.1.0 (from multidict<7.0,>=4.5->aiohttp->jeedomdaemon)
0226|Downloading https://www.piwheels.org/simple/typing-extensions/typing_extensions-4.12.2-py3-none-any.whl (37 kB)
0227|Collecting idna>=2.0 (from yarl<2.0,>=1.17.0->aiohttp->jeedomdaemon)
0228|Using cached https://www.piwheels.org/simple/idna/idna-3.10-py3-none-any.whl (70 kB)
0229|Downloading aiohttp-3.11.11-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (1.6 MB)
0230|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.6/1.6 MB 18.9 MB/s eta 0:00:00
0231|Downloading frozenlist-1.5.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (241 kB)
0232|Downloading multidict-6.1.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (126 kB)
0233|Downloading propcache-0.2.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (207 kB)
0234|Downloading yarl-1.18.3-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (317 kB)
0235|WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
0236|Installing collected packages: typing-extensions, propcache, idna, frozenlist, attrs, async-timeout, aiohappyeyeballs, multidict, aiosignal, yarl, aiohttp, jeedomdaemon
0237|Attempting uninstall: typing-extensions
0238|Found existing installation: typing_extensions 4.12.2
0239|Uninstalling typing_extensions-4.12.2:
0240|Successfully uninstalled typing_extensions-4.12.2
0241|Attempting uninstall: propcache
0242|Found existing installation: propcache 0.2.1
0243|Uninstalling propcache-0.2.1:
0244|Successfully uninstalled propcache-0.2.1
0245|Attempting uninstall: idna
0246|Found existing installation: idna 3.10
0247|Uninstalling idna-3.10:
0248|Successfully uninstalled idna-3.10
0249|Attempting uninstall: frozenlist
0250|Found existing installation: frozenlist 1.5.0
0251|Uninstalling frozenlist-1.5.0:
0252|Successfully uninstalled frozenlist-1.5.0
0253|Attempting uninstall: attrs
0254|Found existing installation: attrs 24.3.0
0255|Uninstalling attrs-24.3.0:
0256|Successfully uninstalled attrs-24.3.0
0257|Attempting uninstall: async-timeout
0258|Found existing installation: async-timeout 5.0.1
0259|Uninstalling async-timeout-5.0.1:
0260|Successfully uninstalled async-timeout-5.0.1
0261|Attempting uninstall: aiohappyeyeballs
0262|Found existing installation: aiohappyeyeballs 2.4.4
0263|Uninstalling aiohappyeyeballs-2.4.4:
0264|Successfully uninstalled aiohappyeyeballs-2.4.4
0265|Attempting uninstall: multidict
0266|Found existing installation: multidict 6.1.0
0267|Uninstalling multidict-6.1.0:
0268|Successfully uninstalled multidict-6.1.0
0269|Attempting uninstall: aiosignal
0270|Found existing installation: aiosignal 1.3.2
0271|Uninstalling aiosignal-1.3.2:
0272|Successfully uninstalled aiosignal-1.3.2
0273|Attempting uninstall: yarl
0274|Found existing installation: yarl 1.18.3
0275|Uninstalling yarl-1.18.3:
0276|Successfully uninstalled yarl-1.18.3
0277|Attempting uninstall: aiohttp
0278|Found existing installation: aiohttp 3.11.11
0279|Uninstalling aiohttp-3.11.11:
0280|Successfully uninstalled aiohttp-3.11.11
0281|Attempting uninstall: jeedomdaemon
0282|Found existing installation: jeedomdaemon 1.2.0
0283|Uninstalling jeedomdaemon-1.2.0:
0284|Successfully uninstalled jeedomdaemon-1.2.0
0285|Successfully installed aiohappyeyeballs-2.4.4 aiohttp-3.11.11 aiosignal-1.3.2 async-timeout-5.0.1 attrs-24.3.0 frozenlist-1.5.0 idna-3.10 jeedomdaemon-1.2.0 multidict-6.1.0 propcache-0.2.1 typing-extensions-4.12.2 yarl-1.18.3
0286|WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
0287|+ echo 20
0288|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end rfxcom
0289|+ echo 21
0290|+ rm /tmp/jeedom_install_in_progress_rfxcom
0291|+ echo '*******************End of package installation******************'
0292|*******************End of package installation******************

Voici les infos sur mon système :

Page configuration :

Je suis bloqué, donc toute aide sera la bienvenue.
Merci d’avance.

Bonjour,

Il ne sert plus à rien de relancer les dépendances donc tu peux déjà arrêter de le faire. Le démon démarre et les infos remontent donc c’est OK coté dépendance.
Les Warning ne sont pas problématique ici.

Quand ça « plante » regarde si ton matériel voir bien toujours le RFXCom (commande lsusb en ssh).

Tu peux aussi faire un tour dans le bouton de « Gestion des protocoles RFXcom ». Est-ce qu’il sont tous utiles pour tes matériels, est-ce que tu ne pourrais pas en décocher pour éviter des conflits ? A ma connaissance ça ne devrait pas être l’origine du problème mais pour l’heure je n’ai pas d’autre idée vu que le firmware a l’air OK.

Ok, merci, je vais voir ça.

Je n’ai que 4 protocoles qui sont cochés :
4 - Lightning 4
6 - Rubicson
18 - Oregon
20 - Home Easy EU

Pourquoi ceux là ? Je dois avouer que je ne m’en souviens plus !

Déjà quand ça marche, je ne sais pas bien comment identifier le RFXcom avec la commande lsusb.
Je vois les clés Conbee et Aeotec mais pas en clair le boitier RFXcom.

Chez moi, il apparait au doux nom de « Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO) », ça doit pareil chez vous.

Tu as un hub usb non alimenté ? Des fois quand on a beaucoup d’équipements et que c’est sous alimenté, des ports peuvent sauter par manque de puissance.

Bon c’est surement pas la bonne piste alors. Il y a très peu de protocoles de cochés donc peu de chance d’avoir un conflit.

Pour le lsusb voir réponse de @defmy. Tu peux aussi « noter » ce que tu viens d’obtenir, débrancher ton RFXcom et relancer la commande. Tu verras donc la ligne qui n’est plus là et ce sera lui :slight_smile:

Merci pour vos réponses.
Pour l’instant j’ai changé le câble et je continue à surveiller le bazar !

En réponse à @defmy, j’utilise les 4 ports USB du RPI, sans hub, pour le SSD, les clés Conbee et Aeotec et le boîtier RFXcom.

Il se pourrait donc qu’il y est un sujet d’alimentation en effet. Vu que tu as changé de matériel (RPi), ce n’est pas à exclure. Si tu as l’occasion d’avoir un HUB USB qui a sa propre alimentation tu pourrais l’utiliser pour y brancher le boitier RFXCom.

Bonjour à tous,

Peut être une piste…

Pour info, j’avais le même problème de façon aléatoire.

Pour le résoudre, je downgradais " protobuf " en version 3.20.3.

Mais depuis peux (peut être suite à certaines mise à jour), je tourne avec la dernière version sans aucun problème…enfin jusqu’à maintenant.

Bonsoir,

Très mauvaise idée sur un Raspberry Pi 4. En effet, les ports USB 3 génère des parasites sur leurs entourage.
Il est préférable de ne pas utiliser ces ports, ou alors on n isolant les autres via un hub alimenté (et pas autoalimenté).
Il est aussi parfois nécessaire d’utiliser des rallonges USB pour faire disparaitre cette gêne.

Ok, je vais me procurer un hub USB avec une alimentation séparée.

Pour s’assurer de cela, laissez uniquement le SSD sur un port usb2 (pour un pi, cela ne change rien) et le RFXCOM sur l’autre port USB.

Et testez ainsi, vous aurez, probablement , un début de la réponse.

Avec le nouveau câble, pas de plantage après plus de 24h.
Je ne sais pas bien pourquoi le câble qui ne posait pas de problème sur le RPI3 en pose maintenant sur le RPI4.
Je vais quand même acheté un hub et regarder l’affectation des ports USB 2 et 3.
Je clos le sujet en vous remerciant de m’avoir aidé par vos réponses.

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.