Home Assistant : Update firmware Silicon Labs CP210x UART Bridge : KO

J’ai essayé plusieurs commandes mais sans succès :

Sur les ports USB

# lsusb 
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 002 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Chargement du fichier :

# curl -O https://github.com/darkxst/silabs-firmware-builder/raw/refs/heads/4.4.4/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl
# universal-silabs-flasher --device /dev/ttyUSB1 --ezsp-baudrate 230400 flash --firmware ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl  --allow-cross-flashing
2024-11-22 15:20:54.885 home-assistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, 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)
2024-11-22 15:20:54.886 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-11-22 15:20:56.904 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 230400 baud
2024-11-22 15:21:01.928 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-11-22 15:21:06.253 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-11-22 15:21:10.575 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-11-22 15:21:14.893 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
# universal-silabs-flasher --device /dev/ttyUSB1 --ezsp-baudrate 230400 flash --firmware ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl 
2024-11-22 15:22:12.321 home-assistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, 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)
2024-11-22 15:22:12.321 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-11-22 15:22:14.337 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 230400 baud
2024-11-22 15:22:19.361 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-11-22 15:22:23.688 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-11-22 15:22:28.015 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-11-22 15:22:32.341 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
# universal-silabs-flasher --device /dev/ttyUSB1 --ezsp-baudrate 115200 flash --firmware ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl 
2024-11-22 15:23:33.846 home-assistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, 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)
2024-11-22 15:23:33.847 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-11-22 15:23:35.864 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-11-22 15:23:40.887 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-11-22 15:23:45.211 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-11-22 15:23:49.535 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-11-22 15:23:53.861 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
# universal-silabs-flasher --device /dev/ttyUSB1 --bootloader-reset sonoff flash --firmware ncp-uart-hw-v7.4.4.0-zbdonglee-115200.gbl 
2024-11-22 15:24:42.233 home-assistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, 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)
2024-11-22 15:24:42.233 home-assistant universal_silabs_flasher.flasher INFO Triggering sonoff bootloader
2024-11-22 15:24:42.852 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-11-22 15:24:44.871 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-11-22 15:24:49.895 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-11-22 15:24:54.225 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud
2024-11-22 15:24:58.557 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud
2024-11-22 15:25:02.886 home-assistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type

Misère.

Home Assistant : zigbee2mqtt impossible de le lancer

Je vois bien mes deux modules Sonoff_Zigbee_3.0 :

# ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 19 nov.  19:58 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 10 nov.  17:35 usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 -> ../../ttyUSB0

Mon OS et docker son à jour :

# docker -v
Docker version 20.10.22, build 3a2c30b
# cat /etc/os-release  | grep "PRETTY_NAME"
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"

Test 1

J’ai fait une configuration basique :

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:
    port: >-
      /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
    adapter: ezsp

La communication semble bone :

test -w /dev/ttyUSB0 && echo success || echo failure 

Mais impossible de lancer le module.

Dans les logs :

# docker logs d5ab8e1b74d1
[22:01:02] INFO: Preparing to start...
[22:01:02] INFO: Socat not enabled
[22:01:02] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-11-19 22:01:05] info:     z2m: Logging to console, file (filename: log.log)
[2024-11-19 22:01:05] info:     z2m: Starting Zigbee2MQTT version 1.41.0 (commit #unknown)
[2024-11-19 22:01:05] info:     z2m: Starting zigbee-herdsman (2.1.7)
[2024-11-19 22:01:06] error:    z2m: Error while starting zigbee-herdsman
[2024-11-19 22:01:06] error:    z2m: Failed to start zigbee
[2024-11-19 22:01:06] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-11-19 22:01:06] error:    z2m: Exiting...
[2024-11-19 22:01:06] error:    z2m: Error: No path provided and failed to auto detect path
    at Function.create (/app/node_modules/zigbee-herdsman/src/adapter/adapter.ts:107:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:133:24)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:161:27)
    at start (/app/index.js:154:5)

J’ai essayé de changer la configuration :

Test 2 : KO

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:
    port: >-
      /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
    adapter: deconz

– Test 3 : KO

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:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
  adapter: ember
  • L’erreur semble être maintenant :
[2024-11-19 22:15:41] error:   z2m: Error while starting zigbee-herdsman
[2024-11-19 22:15:41] error:    z2m: Failed to start zigbee
[2024-11-19 22:15:41] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-11-19 22:15:41] error:    z2m: Exiting...
[2024-11-19 22:15:41] error:    z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.

Test 4 : KO

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
  base_topic: zigbee2mqtt
  user: mqtt
  password: mqtt
  server: mqtt://core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
  adapter: ember
  baudrate: 230400

Test 5 : KO

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:
  base_topic: zigbee2mqtt
  user: mqtt
  password: mqtt
  server: mqtt://core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
  adapter: zstack

Dans les logs :

# docker logs cb06c5c275d6
[22:26:26] INFO: Preparing to start...
[22:26:26] INFO: Socat not enabled
[22:26:27] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-11-19 22:26:29] info:     z2m: Logging to console, file (filename: log.log)
[2024-11-19 22:26:29] info:     z2m: Starting Zigbee2MQTT version 1.41.0 (commit #unknown)
[2024-11-19 22:26:29] info:     z2m: Starting zigbee-herdsman (2.1.7)
[2024-11-19 22:26:30] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-11-19 22:26:30] info:     zh:zstack:znp: Serialport opened
[2024-11-19 22:27:35] error:    z2m: Error while starting zigbee-herdsman
[2024-11-19 22:27:35] error:    z2m: Failed to start zigbee
[2024-11-19 22:27:35] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-11-19 22:27:35] error:    z2m: Exiting...
[2024-11-19 22:27:35] error:    z2m: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000m

Test 6 : KO

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:
  base_topic: zigbee2mqtt
  user: mqtt
  password: mqtt
  server: mqtt://core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
  adapter: zstack
advanced:
  pan_id: GENERATE
  ext_pan_id: [0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08]
  network_key: GENERATE

Test 7 : KO

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:
  base_topic: zigbee2mqtt
  user: mqtt
  password: mqtt
  server: mqtt://core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_e888a2e55f0cee11a6c834d6f49e3369-if00-port0
  adapter: zstack
advanced:
  pan_id: GENERATE
  ext_pan_id: GENERATE
  network_key: GENERATE

Test 7 : KO

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:
  base_topic: zigbee2mqtt
  user: mqtt
  password: mqtt
  server: mqtt://core-mosquitto:1883
serial:
  port: /dev/ttyUSB1
permit_join: true
advanced:
  pan_id: GENERATE
  ext_pan_id:
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
  network_key: GENERATE
  channel: 11

Home Assistant : Production solaire en octobre sur Biot

Voici le graphique de la production solaire via Home Assistant :

  • Un maximum de 24,08 kWh/j
  • Un minimum de 1,4 kWh/j
  • Total production : 401,52 kWh.

Quand il pleut il n’y a pas de production … enfin 1,4 kWh c’est 6 % de 24,08 kWh. Donc quand un commercial vous dit que l’on produit tous le temps. C’est pas faux mais la production est très très faible.

La température du toit sur Octobre :

Souvent il est indiqué que 25°C est la température limite pour le bon fonctionnement d’une installation solaire. Au-dessus, les panneaux photovoltaïques perdent jusqu’à 0,5 % de rendement par degré supplémentaire. Quand la température des cellules augmente, la tension diminue. Et plus la tension s’abaisse, plus la puissance des panneaux s’affaiblit.

Et sur Biot toujours au dessus de 25°C quand le soleil est présent.

A suivre.

Home Assistant : Installation Sauter avec Cozytouch ( Atlantic )

La création d’un compte sur Cozytouch c’est simplement l’enfer (le serveur semble pas toujours disponible) :

Mais cela finit par tomber en marche :

L’installation est détecté automatiquement par Home Assistant :

Il faut selectionner le bon serveur (Atlantic pour Sauter) :

Le reste est automatique :

On peut faire de la programmation par script et on a aussi la températeure et consommation du radiateur.

A suivre….