Bootloader mode

Bonjour,
Je suis tombé sur quelques similaires au mien mais je veux être certain de ne pas faire de bêtise et perdre tous mes noeuds zigbee !!
Suite à une maj du firmware qui ne s’est pas bien passée, il semble que ma clé POPP ( EFR32MG13) est en mode Bootloader comme l’atteste l’essai suivant que j’ai fait quand j’ai vu que le démon était HS.

Est-ce récupérable sans perdre tout mon réseau (et les X scénario que j’ai construits …) Car sinon je crois que je vais arrêter tout mon système domotique je n’aurai pas l’ambition de tout refaire !

Je suis notamment tombé sur ceci sur l’un des sujets : Mise à jour du contrôleur ZigBee ELELABS EZSP - Guillaume Kulakowski's blog

Mais est-ce une solution qui ne fera pas perdre les noeuds et surtout ces commandes il faut les entrer via l’invite de commande de jeedom ?

Merci d’avance en tout cas car toute ma domotique est paralysée …

Begin update of /dev/ttyUSB0 with firmware zigbee
--2024-05-03 19:22:43--  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]
--2024-05-03 19:22:43--  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: unspecified [application/zip]
Saving to: '/tmp/elelabs.zip'
0K .......... .......... .......... .......... .......... 1.51M
50K .......... .......... .......... .......... .......... 3.12M
100K .......... .......... .......... .......... .......... 7.86M
150K .......... .......... .......... .......... .......... 7.90M
200K .......... .......... .......... .......... .......... 5.69M
250K .......... .......... .......... .......... .......... 8.16M
300K .......... .......... .......... .......... .......... 5.41M
350K .......... .......... .......... .......... .......... 7.33M
400K .......... .......... .......... .......... .......... 11.7M
450K .......... .......... .......... .......... .......... 11.0M
500K .......... .......... .......... .......... .......... 11.4M
550K .......... .......... .......... .......... .......... 10.8M
600K .......... .......... .......... .......... .......... 19.0M
650K .......... .......... .......... .......... .......... 11.5M
700K .......... .......... .......... .......... .......... 17.2M
750K .......... .......... .......... .......... .......... 16.5M
800K .......... .......... .......... .......... .......... 16.0M
850K .......... .......... .......... .......... .......... 16.8M
900K .......... .......... .......... .......... .......... 18.3M
950K .......... .......... .......... .......... .......... 17.8M
1000K .......... .......... .......... .......... .......... 18.6M
1050K .......... .......... .......... .......... .......... 14.4M
1100K .......... .......... .......... .......... .......... 11.1M
1150K .......... .......... .......... .......... .......... 8.54M
1200K .......... ........                                    5.59M=0.2s
2024-05-03 19:22:44 (7.86 MB/s) - '/tmp/elelabs.zip' saved [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
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pyserial==3.4 in /usr/local/lib/python3.7/dist-packages (from -r requirements.txt (line 1)) (3.4)
Requirement already satisfied: xmodem==0.4.6 in /usr/local/lib/python3.7/dist-packages (from -r requirements.txt (line 2)) (0.4.6)
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
2024/05/03 19:22:53 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2024/05/03 19:22:53 Elelabs_EzspFwUtility:   Gecko Bootloader v1.12.10
2024/05/03 19:23:00 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2024/05/03 19:23:00 Elelabs_EzspFwUtility:   Gecko Bootloader v1.12.10
2024/05/03 19:23:00 Elelabs_EzspFwUtility:   The product not in the normal EZSP mode.
'restart' into normal mode or use 'flash' utility instead
2024/05/03 19:23:06 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2024/05/03 19:23:06 Elelabs_EzspFwUtility:   Gecko Bootloader v1.12.10
2024/05/03 19:23:06 Elelabs_EzspFwUtility:   Launch in normal application mode
2024/05/03 19:23:14 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2024/05/03 19:23:14 Elelabs_EzspFwUtility:   Gecko Bootloader v1.12.10
2024/05/03 19:23:20 Elelabs_EzspFwUtility:   EZSP adapter in bootloader mode detected:
2024/05/03 19:23:20 Elelabs_EzspFwUtility:   Gecko Bootloader v1.12.10
End of update successfull

Bon en lisant la FAQ jai trouve la solution, il suffisait de de sélectionner la correction du bootloader dans la mise a jour du firmware :upside_down_face: le sujet est donc résolu.

Il est possible que la clef soit bloquée en mode bootloader, pour en sortir vous pouvez aller dans la configuration du plugin puis cliquer sur “Mettre à jour le firmware”, selectionner votre type de clef (sur Smart/Atlas c’est Elelabs/Popp), dans port Zigbee selectionner votre port et dans firmware selectionner “Correction bootloader” IMPORTANT : il ne faut faire cette manipulation que les clefs de type Elelabs, box Jeedom Atlas ou Jeedom Smart. Sur tout autre clef il faut contacter le fabricant pour qu’il vous donne la procedure.

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