Transfert d'une Atlas vers une autre : log zigbee2mqtt ROUTE_ERROR_ADDRESS_CONFLICT

Hello,
pour résoudre un problème d’Atlas qui crashe régulièrement (voir ici pour les curieux) j’en ai acheté une seconde d’occasion, je l’ai réinstallé avec la même image debian 12/jeedom 4.6.1 (celle-là) et j’ai restauré la sauvegarde de l’ancienne box vers la nouvelle.
Tout fonctionne à peu près bien, sauf le plugin-z2m .
J’ai commencé par mettre à jour le firmware vers Ember puisque sinon le démon ne démarrait pas, et aussi pour me mettre à iso-conf entre les deux box. Le démon a alors démarré :+1:.
En revanche, certains équipements n’étaient plus appairés et j’ai dû le refaire manuellement (rien de critique jusque là), par contre certains de désappairent « tout seul » au fil du temps, et surtout j’ai ce message plusieurs fois par minute dans le log z2md:

[2026-09-21 09:48:00] e[32minfoe[39m: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".

Je ne trouve pas de sujet avec ce code erreur, est-ce que quelqu’un aurait une idée ?

log z2m:

[2026-09-20 19:15:16] INFO  Démarrage du démon Z2M : ZIGBEE2MQTT_DATA=/var/www/html/plugins/z2m/core/class/../../data NODE_OPTIONS=--max_old_space_size=1536 npm start --prefix /var/www/html/plugins/z2m/resources/zigbee2mqtt
[2026-09-20 20:46:23] ERROR  Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2026-09-20 20:46:24] INFO  Arrêt du démon z2m
[2026-09-20 20:46:26] INFO  Démarrage du démon Z2M : ZIGBEE2MQTT_DATA=/var/www/html/plugins/z2m/core/class/../../data NODE_OPTIONS=--max_old_space_size=1536 npm start --prefix /var/www/html/plugins/z2m/resources/zigbee2mqtt
[2026-09-20 22:52:27] ERROR  Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2026-09-20 22:52:27] INFO  Arrêt du démon z2m
[2026-09-20 22:52:29] INFO  Démarrage du démon Z2M : ZIGBEE2MQTT_DATA=/var/www/html/plugins/z2m/core/class/../../data NODE_OPTIONS=--max_old_space_size=1536 npm start --prefix /var/www/html/plugins/z2m/resources/zigbee2mqtt

log z2mpackages:

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_z2m
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
Launch pre-install of z2m dependancy
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
chmod: cannot access '/var/www/html/core/class/../../plugins/mqtt2/.*': No such file or directory
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
PHP Warning:  Undefined array key "version" in /var/www/html/core/class/system.class.php on line 412
Plugin mqtt2 installed with success+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
unattended-upgr: 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 bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
80 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 5
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (12.0-1).
build-essential is already the newest version (12.9).
apt-utils is already the newest version (2.6.1).
git is already the newest version (1:2.39.5-0+deb12u3).
The following packages were automatically installed and are no longer required:
icu-devtools libbrotli-dev libfontconfig-dev libfontconfig1-dev
libfreetype-dev libgcrypt20-dev libgmp-dev libgmpxx4ldbl libgnutls-openssl27
libgnutls28-dev libgnutlsxx30 libgpg-error-dev libicu-dev libidn2-dev
libnspr4-dev libnss3-dev libp11-kit-dev libpng-dev libpng-tools
libpthread-stubs0-dev libtasn1-6-dev libtasn1-doc libtcl8.6 libtk8.6
libxau-dev nettle-dev uuid-dev x11proto-dev xorg-sgml-doctools
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
[Check Version NodeJS actuelle : v22.23.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Clean npm cache
npm warn using --force Recommended protections disabled.
+ echo 6
+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-yaml
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
php-yaml is already the newest version (2.2.2+2.1.0+2.0.4+1.3.2-6).
The following packages were automatically installed and are no longer required:
icu-devtools libbrotli-dev libfontconfig-dev libfontconfig1-dev
libfreetype-dev libgcrypt20-dev libgmp-dev libgmpxx4ldbl libgnutls-openssl27
libgnutls28-dev libgnutlsxx30 libgpg-error-dev libicu-dev libidn2-dev
libnspr4-dev libnss3-dev libp11-kit-dev libpng-dev libpng-tools
libpthread-stubs0-dev libtasn1-6-dev libtasn1-doc libtcl8.6 libtk8.6
libxau-dev nettle-dev uuid-dev x11proto-dev xorg-sgml-doctools
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
+ echo 7
+ sudo systemctl restart apache2
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ echo 'Launch post-install of z2m dependancy'
Launch post-install of z2m dependancy
+++ realpath /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
++ dirname /var/www/html/plugins/z2m/resources/post-install.sh
+ BASEDIR=/var/www/html/plugins/z2m/resources
+ '[' -d /var/www/html/plugins/z2m/resources/zigbee2mqtt ']'
+ rm -rf /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ mkdir /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ git clone --depth 1 https://github.com/Koenkk/zigbee2mqtt.git /var/www/html/plugins/z2m/resources/zigbee2mqtt
Cloning into '/var/www/html/plugins/z2m/resources/zigbee2mqtt'...
+ cd /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ '[' -f /var/www/html/plugins/z2m/resources/../data/wanted_z2m_version ']'
+ '[' -n '' ']'
+ npm install -g pnpm
changed 2 packages in 6s
+ pnpm i --frozen-lockfile
Lockfile is up to date, resolution step is skipped
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +227
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 227, reused 171, downloaded 0, added 0
Progress: resolved 227, reused 227, downloaded 0, added 227, done
.../node_modules/unix-dgram install$ node-gyp rebuild
.../node_modules/unix-dgram install$ node-gyp rebuild
.../node_modules/unix-dgram install: sh: line 1: node-gyp: command not found
.../node_modules/unix-dgram install: sh: line 1: node-gyp: command not found
dependencies:
+ ajv 8.20.0
+ bind-decorator 1.0.11
+ debounce 3.0.0
+ fast-deep-equal 3.1.3
+ fflate 0.8.3
+ humanize-duration 3.34.1
+ js-yaml 5.4.1
+ mqtt 5.15.2
+ semver 7.8.5
+ srvx 0.12.7
+ throttleit 3.0.0
+ winston 3.19.0
+ winston-syslog 2.7.1
+ winston-transport 4.9.0
+ ws 8.21.3
+ zigbee-herdsman 10.9.2
+ zigbee-herdsman-converters 26.105.0
+ zigbee2mqtt-frontend 0.9.21
+ zigbee2mqtt-windfront 2.15.0
optionalDependencies:
+ unix-dgram 2.0.7
devDependencies:
+ @biomejs/biome 2.5.11
+ @types/humanize-duration 3.27.4
+ @types/node 26.4.0
+ @types/readable-stream 4.0.24
+ @types/ws 8.18.1
+ @vitest/coverage-v8 3.2.7
+ tmp 0.2.7
+ typescript 7.0.2
+ vitest 3.2.7
Done in 3.6s using pnpm v10.18.3
+ pnpm run build
> zigbee2mqtt@2.14.1 build /var/www/html/plugins/z2m/resources/zigbee2mqtt
> tsc && node index.js writehash
+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
rm: invalid option -- '/'
Try 'rm --help' for more information.
+ echo 10
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************

log z2mfirmware:

[2026-09-20 19:07:41] INFO  Lancement de la mise à jour du firmware pour : /dev/ttyS2 => sudo chmod +x /var/www/html/plugins/z2m/core/class/../../resources/misc/update-firmware-elelabs.sh;sudo /var/www/html/plugins/z2m/core/class/../../resources/misc/update-firmware-elelabs.sh /dev/ttyS2 ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl
[2026-09-20 19:07:41] ALERT  sudo chmod +x /var/www/html/plugins/z2m/core/class/../../resources/misc/update-firmware-elelabs.sh;sudo /var/www/html/plugins/z2m/core/class/../../resources/misc/update-firmware-elelabs.sh /dev/ttyS2 ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl
kill: (9): No such process
Begin update of /dev/ttyS2 with firmware ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl
--2026-09-20 19:07:42--  https://github.com/Elelabs/elelabs-zigbee-ezsp-utility/archive/master.zip
Resolving github.com (github.com)... 140.82.121.3
Connecting to github.com (github.com)|140.82.121.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/Elelabs/elelabs-zigbee-ezsp-utility/zip/refs/heads/master [following]
--2026-09-20 19:07:42--  https://codeload.github.com/Elelabs/elelabs-zigbee-ezsp-utility/zip/refs/heads/master
Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1247988 (1.2M) [application/zip]
Saving to: '/tmp/elelabs.zip'
0K .......... .......... .......... .......... ..........  4% 1.18M 1s
50K .......... .......... .......... .......... ..........  8% 2.06M 1s
100K .......... .......... .......... .......... .......... 12% 2.38M 1s
150K .......... .......... .......... .......... .......... 16% 2.55M 1s
200K .......... .......... .......... .......... .......... 20% 2.49M 0s
250K .......... .......... .......... .......... .......... 24% 2.60M 0s
300K .......... .......... .......... .......... .......... 28% 2.43M 0s
350K .......... .......... .......... .......... .......... 32% 13.8M 0s
400K .......... .......... .......... .......... .......... 36% 2.93M 0s
450K .......... .......... .......... .......... .......... 41% 15.3M 0s
500K .......... .......... .......... .......... .......... 45% 2.65M 0s
550K .......... .......... .......... .......... .......... 49% 14.8M 0s
600K .......... .......... .......... .......... .......... 53% 15.9M 0s
650K .......... .......... .......... .......... .......... 57% 2.87M 0s
700K .......... .......... .......... .......... .......... 61% 9.67M 0s
750K .......... .......... .......... .......... .......... 65% 4.15M 0s
800K .......... .......... .......... .......... .......... 69% 12.2M 0s
850K .......... .......... .......... .......... .......... 73% 13.8M 0s
900K .......... .......... .......... .......... .......... 77% 3.39M 0s
950K .......... .......... .......... .......... .......... 82% 15.3M 0s
1000K .......... .......... .......... .......... .......... 86% 15.9M 0s
1050K .......... .......... .......... .......... .......... 90% 3.51M 0s
1100K .......... .......... .......... .......... .......... 94% 15.0M 0s
1150K .......... .......... .......... .......... .......... 98% 10.1M 0s
1200K .......... ........                                   100% 14.3M=0.3s
2026-09-20 19:07:43 (4.01 MB/s) - '/tmp/elelabs.zip' saved [1247988/1247988]
Archive:  elelabs.zip
7fc415497f7e2b3410e3350b359ac5c71043399e
creating: elelabs-zigbee-ezsp-utility-master/
extracting: elelabs-zigbee-ezsp-utility-master/.gitignore
inflating: elelabs-zigbee-ezsp-utility-master/CHANGELOG.md
inflating: elelabs-zigbee-ezsp-utility-master/Elelabs_EzspFwUtility.py
inflating: elelabs-zigbee-ezsp-utility-master/LICENSE
inflating: elelabs-zigbee-ezsp-utility-master/README.md
creating: elelabs-zigbee-ezsp-utility-master/data/
creating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/ELE_MG13_ot_rcp_115200_120_211116.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/ELE_MG13_ot_rcp_123_220206.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/ELE_MG13_zb_ncp_115200_610_211112.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/ELX0X3_MG13_6.0.3_ezsp_v6.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG13/ELX0X3_MG13_6.7.0_ezsp_v8.gbl
creating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG21/
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG21/ELU0141_MG21_ot_rcp_123_211204.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG21/ELU0141_MG21_zb_ncp_6103_211204.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG21/ELU0143_MG21_ot_rcp_123_211211.gbl
inflating: elelabs-zigbee-ezsp-utility-master/data/EFR32MG21/ELU0143_MG21_zb_ncp_6103_211211.gbl
creating: elelabs-zigbee-ezsp-utility-master/img/
inflating: elelabs-zigbee-ezsp-utility-master/img/ele_update_thread.png
inflating: elelabs-zigbee-ezsp-utility-master/img/ele_update_zigbee.png
inflating: elelabs-zigbee-ezsp-utility-master/img/logo.jpg
inflating: elelabs-zigbee-ezsp-utility-master/img/probe_btl.png
inflating: elelabs-zigbee-ezsp-utility-master/img/probe_thread.png
inflating: elelabs-zigbee-ezsp-utility-master/img/probe_zigbee.png
inflating: elelabs-zigbee-ezsp-utility-master/img/restart_btl.png
inflating: elelabs-zigbee-ezsp-utility-master/img/restart_nrml.png
extracting: elelabs-zigbee-ezsp-utility-master/requirements.txt
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
2026/09/20 19:07:48 Elelabs_EzspFwUtility:   Elelabs Zigbee adapter detected:
2026/09/20 19:07:48 Elelabs_EzspFwUtility:   Adapter: ELR023
2026/09/20 19:07:48 Elelabs_EzspFwUtility:   Firmware: 6.10.3-41
2026/09/20 19:07:48 Elelabs_EzspFwUtility:   EZSP v8
--2026-09-20 19:07:48--  https://github.com/darkxst/silabs-firmware-builder/raw/main/firmware_builds/elelabs-elx0x3/ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl
Resolving github.com (github.com)... 140.82.121.3
Connecting to github.com (github.com)|140.82.121.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/darkxst/silabs-firmware-builder/main/firmware_builds/elelabs-elx0x3/ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl [following]
--2026-09-20 19:07:48--  https://raw.githubusercontent.com/darkxst/silabs-firmware-builder/main/firmware_builds/elelabs-elx0x3/ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8003::154, 2606:50c0:8001::154, 2606:50c0:8002::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8003::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 237504 (232K) [application/octet-stream]
Saving to: 'ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl'
0K .......... .......... .......... .......... .......... 21% 3.73M 0s
50K .......... .......... .......... .......... .......... 43% 4.95M 0s
100K .......... .......... .......... .......... .......... 64% 17.6M 0s
150K .......... .......... .......... .......... .......... 86% 6.02M 0s
200K .......... .......... .......... .                    100% 18.3M=0.04s
2026-09-20 19:07:49 (6.37 MB/s) - 'ncp-uart-hw-v7.4.3.0-elelabs-elx0x3-115200.gbl' saved [237504/237504]
2026/09/20 19:07:50 Elelabs_EzspFwUtility:   Elelabs Zigbee adapter detected:
2026/09/20 19:07:50 Elelabs_EzspFwUtility:   Adapter: ELR023
2026/09/20 19:07:50 Elelabs_EzspFwUtility:   Firmware: 6.10.3-41
2026/09/20 19:07:50 Elelabs_EzspFwUtility:   EZSP v8
2026/09/20 19:07:50 Elelabs_EzspFwUtility:   Launch in bootloader mode
2026/09/20 19:07:59 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2026/09/20 19:07:59 Elelabs_EzspFwUtility:   Gecko Bootloader v1.A.0
2026/09/20 19:08:00 Elelabs_EzspFwUtility:   Successfully restarted into X-MODEM mode! Starting upload of the new firmware... DO NOT INTERRUPT(!)
2026/09/20 19:08:43 Elelabs_EzspFwUtility:   Firmware upload complete
2026/09/20 19:08:43 Elelabs_EzspFwUtility:   Rebooting NCP...
2026/09/20 19:08:50 Elelabs_EzspFwUtility:   Elelabs Zigbee adapter detected:
2026/09/20 19:08:50 Elelabs_EzspFwUtility:   Adapter: ELR023
2026/09/20 19:08:50 Elelabs_EzspFwUtility:   Firmware: 7.4.3-0
2026/09/20 19:08:50 Elelabs_EzspFwUtility:   EZSP v13
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
.....
..
2026/09/20 19:08:52 Elelabs_EzspFwUtility:   Elelabs Zigbee adapter detected:
2026/09/20 19:08:52 Elelabs_EzspFwUtility:   Adapter: ELR023
2026/09/20 19:08:52 Elelabs_EzspFwUtility:   Firmware: 7.4.3-0
2026/09/20 19:08:52 Elelabs_EzspFwUtility:   EZSP v13
2026/09/20 19:08:52 Elelabs_EzspFwUtility:   Allready in normal mode. No need to restart
2026/09/20 19:08:53 Elelabs_EzspFwUtility:   Elelabs Zigbee adapter detected:
2026/09/20 19:08:53 Elelabs_EzspFwUtility:   Adapter: ELR023
2026/09/20 19:08:53 Elelabs_EzspFwUtility:   Firmware: 7.4.3-0
2026/09/20 19:08:53 Elelabs_EzspFwUtility:   EZSP v13
End of update successfull
[2026-09-20 19:08:55] ALERT  Fin de la mise à jour du firmware de la clef

Informations Jeedom Atlas

Core : 4.6.1 (master)
DNS Jeedom Atlas : oui

Plugin : JeeZigbee
Version : 2026-04-13 01:01:55 (stable)
Statut Démon : Démarré - (2026-09-20 22:52:27)
Santé
🟢 Matériel : Atlas
🟢 Système à jour : OK
🟢 Cron actif : OK
🟢 Scénario actif : OK
🟢 Démarré : OK 2026-09-20 16:54:04
🟢 Date système (dernière heure enregistrée) : OK 2026-09-21 09:56:11 (2026-09-21 09:46:02)
🟢 Droits sudo : OK
🟢 Version Jeedom : 4.6.1
🟢 Version OS : debian 12.14
🟢 Version PHP : 8.2.31
🟢 Nombre de processus Apache : 11
🟢 Version OS : Linux JeedomAtlas 6.16.4-arm64 #1 SMP PREEMPT 2026-06-26 aarch64 GNU/Linux  [12.14]
🟢 Version database : 10.11.14-MariaDB-0+deb12u2
🟢 Espace disque libre : 68 %
🟢 Connexion active/max/autorisée : 12/28/151
🟢 Taille base de données : 86.09 MB
🟢 Espace disque libre tmp : 100 %
🟢 Mémoire disponible : 66 % (Total 3849 Mo)
🟢 Mémoire suffisante : 0 
🟢 Erreur I/O : 0
🟢 Swap disponible : 100 % (Total 1024 Mo)
🟢 Swappiness : 10 %
🟢 Charge : 0.9 - 0.68 - 0.51
🟢 Configuration réseau interne : OK
🟢 Configuration réseau externe : OK
🟢 Node : v22.23.1 
🟢 Python 3 : Python 3.11.2 
🟢 Persistance du cache : OK
🟢 Apache private tmp : OK

Bonjour,
Les contrôleurs zigbee étant différents, pour moi, Zigbee2Mqtt ne peut pas fonctionner correctement sans supprimer tous les équipements (pas dans Jeedom) et les réapairer.

Quand tu dis différent tu veux dire que c’est deux contrôleurs physiquement différents ? Parce que sinon c’est exactement le même hardware/firmware à la même version.

Bonjour,

donc le même jeedom sur 2 Atlas.
les 2 Atlas tournent en même temps ?

D’après log firmware, Atlas2, carte interne zigbee : Elelabs/ELR023 7.4.3

même jeedom => même configuration zigbee2mqtt :
configuration.yaml (channel, network_key, pan_id) et database.db (ieeeAddr)
=> conflit réseau zigbee potentiel.

akenad :slight_smile:

IL est possible de migrer d’un contrôleur Ember à un autre sans réappairer les équipements.
(mais pas garder les 2 en même temps en ligne avec la même configuration) :

akenad :slight_smile:

Non je n’ai pas les deux qui tournent en même temps (puisque l’autre crashe, tu le sais bien :smiley: ).
Je vais regarder tes liens dans ton deuxième message ce soir, merci !

Oui je sais qu’elle crash, tu a posté encore ce matin :

mais je ne sais pas quand tu l’allumes.

d’où ma question légitime aujourd’hui :

akenad :slight_smile:

Je n’allume plus la « défectueuse », le but est d’en avoir une suel qui tourne bien.

OK donc je comprends que tu ne feras pas les tests que je t’avais suggérés dans l’autre sujet : Box Atlas plante une fois par jour et ne répond plus suite à migration en Debian 11.11 ou 12.11

akenad :slight_smile:

Pour le moment non, ma priorité est d’avoir une Atlas qui fonctionne.

Je pense que je serai bloqué au moment de la copie de l’adresse ieee de l’ancienne box vers la nouvelle puisque l’outil xzg utilisé a besoin de tourner sur un pc sur lequel serait branché le dongle usb zigbee. Dans mon cas j’utilise la carte interne de l’atlas que je ne peux pas brancher sur un pc. Je vais devoir tout réappairer pour faire disparaitre ce qui ressemble à un « coordinateur fantome »

Un « coordinateur fantome » peut apparaitre lorsque 2 coordinateurs ont le même configuration.yaml (channel, network_key, pan_id) et database.db (ieeeAddr)
et qu’ils ont à un instant donné (même bref) tournés en même temps.

Voir :

Un « coordinateur fantome » peut apparaitre lorsque 2 coordinateurs ont le même configuration.yaml (channel, network_key, pan_id) et database.db (ieeeAddr)
et qu’ils ont à un instant donné (même bref) tournés en même temps.

oui c’est ce qui s’est passé je pense, et je pensais avoir compris que changer l’ieee du nouveau controleur pouvait résoudre ce souci, donc ça revient à la deuxième méthode de la faq zigbee2mqtt

Si tu ne peux pas changer l’ieeeAdrr de controleur2/Atlas2 (Elelabs/ELR023), tu peux mettre le Controleur1 de l’Atlas1 (Elelabs/ELR023) dans Atlas2.

akenad :slight_smile:

Oui bonne idée également. (en espérant que ce ne soit pas le contrôleur de l’atlas1 qui la faisait crasher :slight_smile: , mais ça fera un test supplémentaire justement).

C’est en effet une suggestion de test que je t’avais fais en juillet dernier mais que tu n’as pas tenté :

akenad :slight_smile:

Tout à fait, j’attendais d’avoir une solution de secours (deuxième box) puisque sans zigbee je perds 80% de ma domotique :slight_smile: