Mettre a jour firmware controlleur Zigbee sur Nabu Casa Yellow

Bonjour,

Mon problème

Je ne parviens pas a mettre à jour le firmware du contrôleur Zigbee de ma nouvelle Nabu Casa Yellow.

Renseigner votre problème
J’ai voulu mettre en place Zigbee2MQTT en suivant des tutos et vidéos Youtube et je bloque car apparemment mon contrôleur Zigbee n’est pas fonctionnel sous Zigbee2MQTT.
Pourtant Zigbee Home Automation détecte bien le contrôleur …
Du coup j’ai vu qu’il fallait flasher le contrôleur avec Silicon Labs Flasher, ce que j’essaye de faire sans succès.
Voici la configuration de Silicon Labs Flasher:

device: /dev/ttyAMA1
bootloader_baudrate: "115200"
flow_control: true
verbose: false

Et voici les logs après démarrage :

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[19:19:40] INFO: The selected serial port is not a USB device.
[19:19:40] WARNING: No firmware found for the selected device, assuming firmware is installed.
[19:19:40] INFO: universal-silabs-flasher-up script exited with code 0
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

J’ai aussi essayé en spécifiant une version de firmware mais rien y fait:

device: /dev/ttyAMA1
bootloader_baudrate: "115200"
flow_control: true
verbose: false
firmware: http://essayé_avec_adresse_de_plusieurs_firmware

Ma configuration


## System Information

version | core-2025.7.4
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
container_arch | aarch64
user | root
virtualenv | false
python_version | 3.13.3
os_name | Linux
os_version | 6.12.25-haos-raspi
arch | aarch64
timezone | Europe/Paris
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 5000
Installed Version | 2.0.5
Stage | running
Available Repositories | 2126
Downloaded Repositories | 21

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 16.0
-- | --
update_channel | stable
supervisor_version | supervisor-2025.07.2
agent_version | 1.7.2
docker_version | 28.3.0
disk_total | 234.7 GB
disk_used | 13.0 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
board | yellow
supervisor_api | ok
version_api | ok
installed_addons | Z-Wave JS (0.20.0), Mosquitto broker (6.5.1), Rclone Backup (3.3.4), Terminal & SSH (9.18.0), File editor (5.8.0), Studio Code Server (5.19.3), Matter Server (8.0.0), Cloudflared (5.3.5), Network UPS Tools (0.14.1), Node-RED (20.0.0), Silicon Labs Flasher (0.3.2), OpenThread Border Router (2.13.0)

</details>

<details><summary>Dashboards</summary>

dashboards | 3
-- | --
resources | 10
views | 7
mode | storage

</details>

<details><summary>Network Configuration</summary>

adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethe80a065 (disabled), veth5582e1b (disabled), veth591e023 (disabled), veth5062ece (disabled), vethcd33bd5 (disabled), vethc2911cc (disabled), veth6fc5b39 (disabled), veth894c123 (disabled), veth50a1f47 (disabled), veth0e8baaf (disabled), vethdb7eb46 (disabled), veth2fc41b5 (disabled), vethae0d451 (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.1.190/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethe80a065 (), veth5582e1b (), veth591e023 (), veth5062ece (), vethcd33bd5 (), vethc2911cc (), veth6fc5b39 (), veth894c123 (), veth50a1f47 (), veth0e8baaf (), vethdb7eb46 (), veth2fc41b5 (), vethae0d451 ()
ipv6_addresses | lo (::1/128), end0 (fdd6:2932:ea85:2de2:b72f:bcd8:e655:d9/64, fe80::181b:c230:3cb9:85f6/64), hassio (fe80::68e8:b8ff:fe37:62f/64), docker0 (fe80::5c76:3aff:fe0e:3304/64), vethe80a065 (fe80::5801:17ff:fe69:c662/64), veth5582e1b (fe80::404a:1cff:fe4c:98ec/64), veth591e023 (fe80::ba:77ff:fe2c:b396/64), veth5062ece (fe80::7069:67ff:feba:2119/64), vethcd33bd5 (fe80::b4df:c7ff:feaf:e62c/64), vethc2911cc (fe80::9414:8ff:fedf:161a/64), veth6fc5b39 (fe80::7439:58ff:fed2:4deb/64), veth894c123 (fe80::c7f:d3ff:fea3:ac08/64), veth50a1f47 (fe80::2c23:c2ff:fe22:b06b/64), veth0e8baaf (fe80::e85d:60ff:feba:9c27/64), vethdb7eb46 (fe80::a827:36ff:fec5:3b63/64), veth2fc41b5 (fe80::d0ce:68ff:febb:169a/64), vethae0d451 (fe80::b013:b5ff:fe80:bf62/64)
announce_addresses | 192.168.1.190, fdd6:2932:ea85:2de2:b72f:bcd8:e655:d9, fe80::181b:c230:3cb9:85f6

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 18 juillet 2025 à 12:11
-- | --
current_recorder_run | 1 août 2025 à 17:37
estimated_db_size | 1933.25 MiB
database_engine | sqlite
database_version | 3.48.0

</details>

Merci d’avance pour votre soutient!

Sébastien

c’est quel controleur que tu as ?

Salut,

Bonne question…
C’est celui sur la carte mère directement.

J’ai remis Nabu Casa Yellow v1.3 et la je peux voir des chose:

J’ai trouvé ceci aussi:

Cela aide?

ChatGPT me dit:

Le contrôleur du Yellow = Silicon Labs EFR32 + EZSP (EMBER)

  • Le chip intégré sur la carte mère Yellow est un EFR32MG21, de Silicon Labs.
  • Il fonctionne avec le protocole EZSP (EmberZNet Serial Protocol).
  • Ce protocole est supporté uniquement par l’intégration ZHA dans Home Assistant.

Pourtant un ami a lui aussi une Nabu Casa Yellow et cela fonctionne très bien.
Ils font plusieurs versions?

Sébastien

Bonsoir,

J ai un Yellow également avec Z2M. Ça fonctionne out of the box avec la bonne configuration. Quel adapter as tu renseigné dans la configuration Z2M ?

J ai mis à jour le firmware notamment pour passer à Ember. Pour cela j ai suivi la documentation.

La seule subtilité fût l installation de GitHub - hassio-addons/addon-ssh: Advanced SSH & Web Terminal - Home Assistant Community Add-ons afin d avoir les privilèges suffisant pour installer le flasher.

Merci,

Honnêtement je suis un peu perdu.

Voici le log quand je démarre Zigbe2MQTT:

Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-08-01 22:32:05] info: 	z2m: Logging to console, file (filename: log.log)
[2025-08-01 22:32:05] info: 	z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-01 22:32:05] info: 	z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-01 22:32:05] info: 	zh:ember: Using default stack config.
[2025-08-01 22:32:05] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-08-01 22:32:05] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-08-01 22:32:05] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-08-01 22:32:05] info: 	zh:ember:uart:ash: Serial port opened
[2025-08-01 22:32:05] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-08-01 22:32:06] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-08-01 22:32:06] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-08-01 22:32:06] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-08-01 22:32:06] error: 	z2m: Error while starting zigbee-herdsman
[2025-08-01 22:32:06] error: 	z2m: Failed to start zigbee-herdsman
[2025-08-01 22:32:06] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-08-01 22:32:06] error: 	z2m: Exiting...
[2025-08-01 22:32:06] error: 	z2m: Error: Adapter EZSP protocol version (8) is not supported by Host [13-17].
    at EmberAdapter.emberVersion (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1416:19)
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:669:9)
    at EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1547:24)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/controller/controller.ts:134:29)
    at Zigbee.start (/app/lib/zigbee.ts:67:27)
    at Controller.start (/app/lib/controller.ts:101:13)
    at start (/app/index.js:149:5)
[22:32:07] INFO: Preparing to start...
[22:32:07] INFO: Socat not enabled
[22:32:08] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/

Tu dis que tu es passé par SSH pour flasher … et le tool pour flasher est aussi Silicon Labs Flasher mais en ligne de commande.
Donc cela ne fonctionne pas avec l’interface GUI?
Et quel firrmware prendre?

OK, j’ai installe Advance SSH & Web Terminal et ensuite universal-silabs-flasher

Puis le firmware je dois prendre lequel?
Pourrais-tu juste me donner un lien et aussi la commande exacte a exécuter?

Merci,

Sebastien

Non ça ne fonctionne pas avec l IHM.

  • Le web c est pour les clés USB
  • L addon pour le FW RCP multi-pan

Il faut prendre le yellow ncp-uart. Je suis en 7.4.3 et sur un autre post du forum le 7.4.2 était utilisé. La bonne chose à faire c’est chercher si il y a des issues sur le GitHub concernant la version souhaitée. Et chercher sur Google aussi.

Dans z2m tu as du renseigner adapter dans la configuration, sûrement à ember ou ezsp.

Désole mais j’y comprends pas grand chose, j’ai le yaml de Z2M comme ceci maintenant:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt: {}
serial:
  adapter: ember

J’ai aussi téléchargé ceci :
image

Est-ce le bon firmware?
Quel ligne de commande pour démarrer le flashage?

J’ai essayé ceci:

➜  firmware universal-silabs-flasher \
    --device /dev/ttyAMA1 \
    --bootloader-reset yellow
    flash \
    --firmware ncp-uart-hw-v7.4.3.0-yellow-115200.gbl  

Usage: universal-silabs-flasher [OPTIONS] COMMAND [ARGS]...
Try 'universal-silabs-flasher --help' for help.

Error: Missing command.
zsh: command not found: flash
➜  firmware 

Et ceci:

➜  firmware universal-silabs-flasher --device /dev/ttyAMA1 --bootloader-reset yellow flash --firmware ncp-uart-hw-v7.4.3.0-yellow-115200.gbl
Error: 'ncp-uart-hw-v7.4.3.0-yellow-115200.gbl' does not appear to be a valid firmware image: ValueError('Unknown firmware image type')

Résolu : finalement ceci avec un firmware de chez Nabu Casa:


Avec ce firmware:
[https://github.com/NabuCasa/silabs-firmware-builder/releases/download/v2025.04.04-1/yellow_zigbee_ncp_7.4.4.1.gbl](https://github.com/NabuCasa/silabs-firmware-builder/releases/download/v2025.04.04-1/yellow_zigbee_ncp_7.4.4.1.gbl)

➜  firmware universal-silabs-flasher --device /dev/ttyAMA1 --bootloader-reset yellow flash --firmware yellow_zigbee_ncp_7.4.4.0.gbl
2025-08-01 23:23:07.041 a0d7b954-ssh universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version='7.4.4.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.ZIGBEE_NCP: 'zigbee_ncp'>, fw_variant=None, baudrate=115200)
2025-08-01 23:23:07.041 a0d7b954-ssh universal_silabs_flasher.flasher INFO Triggering yellow bootloader
2025-08-01 23:23:07.343 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-08-01 23:23:07.453 a0d7b954-ssh universal_silabs_flasher.flasher INFO Launched application from bootloader
2025-08-01 23:23:07.455 a0d7b954-ssh universal_silabs_flasher.flasher INFO Detected bootloader version '2.0.1'
2025-08-01 23:23:07.455 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2025-08-01 23:23:12.463 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2025-08-01 23:23:16.771 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2025-08-01 23:23:21.080 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2025-08-01 23:23:25.389 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2025-08-01 23:23:29.697 a0d7b954-ssh universal_silabs_flasher.flasher INFO Probing ApplicationType.ROUTER at 115200 baud
2025-08-01 23:23:31.701 a0d7b954-ssh universal_silabs_flasher.flasher INFO Triggering yellow bootloader
2025-08-01 23:23:32.002 a0d7b954-ssh universal_silabs_flasher.flasher WARNING Bootloader did not launch a valid application
2025-08-01 23:23:32.003 a0d7b954-ssh universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.0.1' at 115200 baudrate (bootloader baudrate 115200)
yellow_zigbee_ncp_7.4.4.0.gbl  [####################################]  100% 

TADA !

[23:38:20] INFO: Preparing to start...
[23:38:21] INFO: Socat not enabled
[23:38:21] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-08-01 23:38:22] info: 	z2m: Logging to console, file (filename: log.log)
[2025-08-01 23:38:22] info: 	z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-01 23:38:22] info: 	z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-01 23:38:22] info: 	zh:ember: Using default stack config.
[2025-08-01 23:38:22] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-08-01 23:38:22] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-08-01 23:38:22] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-08-01 23:38:22] info: 	zh:ember:uart:ash: Serial port opened
[2025-08-01 23:38:22] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-08-01 23:38:24] error: 	zh:ember:uart:ash: Received ERROR from adapter while connecting, with code=RESET_WATCHDOG.
[2025-08-01 23:38:27] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-08-01 23:38:27] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-08-01 23:38:28] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-08-01 23:38:28] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-08-01 23:38:28] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-08-01 23:38:28] info: 	zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2025-08-01 23:38:28] info: 	zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.4 [GA]","build":0,"major":7,"minor":4,"patch":4,"special":0,"type":170}
[2025-08-01 23:38:28] info: 	zh:ember: [STACK STATUS] Network up.
[2025-08-01 23:38:28] info: 	zh:ember: [INIT TC] Adapter network matches config.
[2025-08-01 23:38:28] info: 	zh:ember: [CONCENTRATOR] Started source route discovery. 1249ms until next broadcast.
[2025-08-01 23:38:28] info: 	z2m: zigbee-herdsman started (resumed)
[2025-08-01 23:38:28] info: 	z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":4,"revision":"7.4.4 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2025-08-01 23:38:28] info: 	z2m: Currently 0 devices are joined.
[2025-08-01 23:38:28] info: 	z2m: Connecting to MQTT server at mqtt://core-mosquitto
[2025-08-01 23:38:29] info: 	z2m: Connected to MQTT server
[2025-08-01 23:38:29] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2025-08-01 23:38:29] info: 	z2m: Started frontend on port 8099
[2025-08-01 23:38:29] info: 	z2m: Zigbee2MQTT started!
[2025-08-01 23:38:34] info: 	z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x60efabfffe0ac8ef/connection_state/config', payload '{"device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x60efabfffe0ac8ef"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x60efabfffe0ac8ef_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'

On est bon là ?
J’ai bien l’interface graphique qui s’ouvre.

Merci!

Sebastien

1 « J'aime »

Oui

Il manque le \ pour que ça fonctionne

Cool, je vais le mettre à jour ce week-end alors

Merci pour ton aide!

Salut,

Pour info, c’est ce firmware que j’ai pris:
https://github.com/NabuCasa/silabs-firmware-builder/releases/download/v2025.04.04-1/yellow_zigbee_ncp_7.4.4.1.gbl

Aussi, ce matin j’ai eu un message depuis HA me disant qu’il y a une mise a jour pour le contrôleur donnant référence au 7.4.4.1 … c’est apparu dans une boite disant ‹ Homa Assistant Yellow xyz › ou un truc du genre mais je n’ai pas noté …

J’ai alors arrêté Z2M et fais la mise a jour, je crois qu’il a vraiment flashé le contrôleur car il y avait une barre de progression et un statut de confirmation après le flash.

Bref, tout fonctionne et j’ai pu appairer tous mes modules zigbee !
Je ne touche plus a rien :slight_smile:

Merci encore !

Sébastien

Merci de l info

Les maj de FW il vaut mieux être prudent

Ce sujet a été automatiquement fermé après 2 jours. Aucune réponse n’est permise dorénavant.