Erreur à la synchronisation des equipements de l'alarme Ajax systeme

Bonjour à tous,
Voilà j’ai un problème depuis quelques temps, quand je veux synchroniser mes équipements avec mon compte, une erreur apparait en bas a droite en rouge:

Erreur lors de la requete à Ajax System : {« state »:« nok »,« error »:« Error on Ajax json return : [object Object] »}

Quand je relance l’installation de la dépendances j’ai des warning qui apparaisent:

0000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_ajaxSystem
0003|+ echo 1
0004|+ echo 2
0005|++ find /usr/local/lib/python2.7/dist-packages/ /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
0006|++ awk '$1 <= 4'
0007|++ cut -f 2-
0008|+ RESULTTODELETE=
0009|++ echo ''
0010|++ sed 's, ,\ ,g'
0011|+ RESULTTODELETE2=
0012|+ echo ''
0013|+ xargs rm -rf
0014|+ echo 3
0015|+ sudo pip3 cache purge
0016|Files removed: 9
0017|+ echo 4
0018|+ sudo pip3 install --upgrade pip
0019|Requirement already satisfied: pip in /usr/local/lib/python3.9/dist-packages (23.2.1)
0020|DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 23.3 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
0021|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
0022|+ echo 5
0023|+ sudo pip3 install --force-reinstall --upgrade pySIAAlarm
0024|Collecting pySIAAlarm
0025|Downloading pysiaalarm-3.1.1-py2.py3-none-any.whl (33 kB)
0026|Collecting pycryptodome (from pySIAAlarm)
0027|Obtaining dependency information for pycryptodome from https://files.pythonhosted.org/packages/40/88/89623388754162ddb82c62814ccbfdbfcc8ed9bd6d5f7412d2479bdca3a7/pycryptodome-3.18.0-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
0028|Downloading pycryptodome-3.18.0-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.4 kB)
0029|Collecting pytz (from pySIAAlarm)
0030|Downloading pytz-2023.3-py2.py3-none-any.whl (502 kB)
0031|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 502.3/502.3 kB 694.3 kB/s eta 0:00:00
0032|Downloading pycryptodome-3.18.0-cp35-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.1 MB)
0033|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 1.8 MB/s eta 0:00:00
0034|DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 23.3 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
0035|Installing collected packages: pytz, pycryptodome, pySIAAlarm
0036|Attempting uninstall: pytz
0037|Found existing installation: pytz 2023.3
0038|Uninstalling pytz-2023.3:
0039|Successfully uninstalled pytz-2023.3
0040|Attempting uninstall: pycryptodome
0041|Found existing installation: pycryptodome 3.18.0
0042|Uninstalling pycryptodome-3.18.0:
0043|Successfully uninstalled pycryptodome-3.18.0
0044|Attempting uninstall: pySIAAlarm
0045|Found existing installation: pysiaalarm 3.0.0b9
0046|Uninstalling pysiaalarm-3.0.0b9:
0047|Successfully uninstalled pysiaalarm-3.0.0b9
0048|Successfully installed pySIAAlarm-3.1.1 pycryptodome-3.18.0 pytz-2023.3
0049|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
0050|+ echo 6
0051|+ sudo chmod +x /var/www/html/core/class/../../plugins/ajaxSystem/resources/post-install.sh
0052|+ sudo /var/www/html/core/class/../../plugins/ajaxSystem/resources/post-install.sh
0053|Collecting pysiaalarm==3.0.0b9
0054|Downloading pysiaalarm-3.0.0b9-py2.py3-none-any.whl (32 kB)
0055|Requirement already satisfied: pycryptodome>=3.9.7 in /usr/local/lib/python3.9/dist-packages (from pysiaalarm==3.0.0b9) (3.18.0)
0056|Requirement already satisfied: dataclasses-json==0.5.2 in /usr/local/lib/python3.9/dist-packages (from pysiaalarm==3.0.0b9) (0.5.2)
0057|Requirement already satisfied: marshmallow<4.0.0,>=3.3.0 in /usr/local/lib/python3.9/dist-packages (from dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (3.20.1)
0058|Requirement already satisfied: marshmallow-enum<2.0.0,>=1.5.1 in /usr/local/lib/python3.9/dist-packages (from dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (1.5.1)
0059|Requirement already satisfied: typing-inspect>=0.4.0 in /usr/local/lib/python3.9/dist-packages (from dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (0.9.0)
0060|Requirement already satisfied: stringcase<2.0.0,==1.2.0 in /usr/local/lib/python3.9/dist-packages (from dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (1.2.0)
0061|Requirement already satisfied: packaging>=17.0 in /usr/local/lib/python3.9/dist-packages (from marshmallow<4.0.0,>=3.3.0->dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (23.1)
0062|Requirement already satisfied: mypy-extensions>=0.3.0 in /usr/local/lib/python3.9/dist-packages (from typing-inspect>=0.4.0->dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (1.0.0)
0063|Requirement already satisfied: typing-extensions>=3.7.4 in /usr/local/lib/python3.9/dist-packages (from typing-inspect>=0.4.0->dataclasses-json==0.5.2->pysiaalarm==3.0.0b9) (4.7.1)
0064|DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 23.3 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
0065|Installing collected packages: pysiaalarm
0066|Attempting uninstall: pysiaalarm
0067|Found existing installation: pysiaalarm 3.1.1
0068|Uninstalling pysiaalarm-3.1.1:
0069|Successfully uninstalled pysiaalarm-3.1.1
0070|Successfully installed pysiaalarm-3.0.0b9
0071|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
0072|+ echo 7
0073|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end ajaxSystem
0074|+ rm /tmp/jeedom_install_in_progress_ajaxSystem
0075|+ echo '*******************End of package installation******************'
0076|*******************End of package installation******************

Seulement quelques appareils apparaissent dans mon listing mais tout n’est pas là…
Je ne comprend pas pourquoi ces erreurs apparaissent

Je suis sous Virtual Machine Synology et j’ai installer jeedom via l’iso disponible sur le site de jeedom qui est sous debian 11

Merci de votre aide !!

1 « J'aime »

Juste au cas ou, voilà le problème qui remonte quand je synchronise les equipements en bas a droite de ma page :

Bonjour
même problème moi pour une nouvelle installation sur QNAP Docker Jeedom Ajax :slight_smile:

Bonjour
C’est un bug en cours pour l’instant je sais pas d’où il vient (peut être un changement côté Ajax) mais je suis bien dessus et la correction devrait arriver dans les semaines à venir.

Edit : en faite je viens de trouver ca devrait être bon maintenant.

1 « J'aime »

Bravo !!! Bien joué, effectivement tout fonctionne parfaitement bien !! Merci à toi @Loic

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