Vire l’addon.
Efface le contenu de /config/zigbee2mqtt (ou /config/zigbee je ne sais plus exactement son nom)
Et recommence proprement
Pourquoi tu lui passe ta souris et ton audio? Pour le bluetooth c’est une clé ou le bluetooth interne de ta machine proxmox?
oui j’ai retiré la souris et l’audio …
je ne comprend pas trop ce que vient faire de l’audio sur un port USB ou rien n’est branché dessus …
j’ai conservé BT et combee2
je suppose qu’il faut vider le contenu de zigbee2mqtt ca peut peut etre resoudre mon probleme.
je verai demain
Merci
Dans le journal Zigbee2mqtt j’ai une erreur
spawn udevadm ENOENT
Qu’est ce que cela signifie ?
Ça ressemble bien au problème décrit dans ce topic…
Tu as effacé le contenu de ton répertoire ?
oui j’ai effacé le repertoire Zigbee2mqtt
puis reinstallé le module …
idem, je n’arrive pas a ouvrir l’interface utilisateur …
journal zigbee2mqtt
[18:00:52] INFO: Preparing to start...
[18:00:52] INFO: Socat not enabled
[18:00:53] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info 2024-01-24 18:00:54: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-24.18-00-54' filename: log.txt
Zigbee2MQTT:info 2024-01-24 18:00:54: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-24 18:00:54: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:error 2024-01-24 18:00:54: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-01-24 18:00:54: Failed to start zigbee
Zigbee2MQTT:error 2024-01-24 18:00:54: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-01-24 18:00:54: Exiting...
Zigbee2MQTT:error 2024-01-24 18:00:54: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
parametres Zigbee2mqtt
? c’est un retour à la ligne ?
j’avais créé un Utilisateur pour mqtt / user: mqtt - mot de pass : mqtt
je l’ai supprimé …
apprement ce n’est plus necessaire ?
fichier de configuration zigbee2mqtt
homeassistant: true
advanced:
network_key:
- 38
- 173
- 252
- 95
- 200
- 104
- 114
- 148
- 173
- 38
- 83
- 112
- 28
- 1
- 22
- 141
pan_id: 39497
ext_pan_id:
- 6
- 139
- 218
- 134
- 232
- 166
- 193
- 71
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password: Chiecahsiech4quiec7XaiVa3xew3san1iep6ohC8aiweepoch9XaV5uapheegh6
frontend:
port: 8099
< MQTT >
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[18:15:08] INFO: Certificates found: SSL is available
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[18:15:08] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[18:15:09] INFO: Starting mosquitto MQTT broker...
2024-01-24 18:15:09: Warning: Mosquitto should not be run as root/administrator.
2024-01-24 18:15:09: mosquitto version 2.0.18 starting
2024-01-24 18:15:09: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-01-24 18:15:09: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-01-24 18:15:09: ├── Username/password checking enabled.
2024-01-24 18:15:09: ├── TLS-PSK checking enabled.
2024-01-24 18:15:09: └── Extended authentication not enabled.
2024-01-24 18:15:09: Opening ipv4 listen socket on port 1883.
2024-01-24 18:15:09: Opening ipv6 listen socket on port 1883.
2024-01-24 18:15:09: Opening websockets listen socket on port 1884.
2024-01-24 18:15:09: Opening ipv4 listen socket on port 8883.
2024-01-24 18:15:09: Opening ipv6 listen socket on port 8883.
2024-01-24 18:15:09: Opening websockets listen socket on port 8884.
2024-01-24 18:15:09: mosquitto version 2.0.18 running
2024-01-24 18:15:09: New connection from 127.0.0.1:40792 on port 1883.
2024-01-24 18:15:09: Client <unknown> disconnected due to protocol error.
[18:15:09] INFO: Successfully send discovery information to Home Assistant.
[18:15:09] INFO: Successfully send service information to the Supervisor.
j’ai fais des redirection de ports sur mon routeur car j’ai un Heatzy Pilote qui utilise ces ports.
Config HA
## System Information
version | core-2024.1.5
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.11.6
os_name | Linux
os_version | 6.1.71-haos
arch | x86_64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4730
Installed Version | 1.32.1
Stage | running
Available Repositories | 1377
Downloaded Repositories | 8
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | 1 janvier 2018 à 01:00
relayer_connected | false
relayer_region | null
remote_enabled | false
remote_connected | false
alexa_enabled | true
google_enabled | true
remote_server | null
certificate_status | null
instance_id | a052700e65a5451a8dcd55ab9d5a89db
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 11.4
-- | --
update_channel | stable
supervisor_version | supervisor-2023.12.1
agent_version | 1.6.0
docker_version | 24.0.7
disk_total | 30.8 GB
disk_used | 12.9 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (12.2.0), File editor (5.7.0), Duck DNS (1.15.0), ESPHome (2023.12.8), Home Assistant Google Drive Backup (0.112.1), Spotify Connect (0.13.0), AdGuard Home (5.0.2), Node-RED (17.0.3), Terminal & SSH (9.8.1), InfluxDB (5.0.0), Grafana (9.1.2), Mosquitto broker (6.4.0), Zigbee2MQTT (1.35.1-1)
</details>
<details><summary>Dashboards</summary>
dashboards | 1
-- | --
resources | 6
views | 5
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 21 janvier 2024 à 18:37
-- | --
current_recorder_run | 24 janvier 2024 à 17:56
estimated_db_size | 67.99 MiB
database_engine | sqlite
database_version | 3.41.2
</details>
Oui
J’ai vu une coquille il y a serial en trop
Vire la ligne 1, vire 2 espaces de chacunes des autres lignes, ça doit ressembler à ça
merci 
toujours 502: Bad Gateway
L’important c’est les logs… bad gateway c’est juste la conséquence, pas la cause
faut que je redemarre le systeme ??
[18:32:12] INFO: Preparing to start...
[18:32:12] INFO: Socat not enabled
[18:32:12] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info 2024-01-24 18:32:14: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-24.18-32-14' filename: log.txt
Zigbee2MQTT:info 2024-01-24 18:32:14: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-24 18:32:14: Starting zigbee-herdsman (0.30.0)
Refresh pour avoir la suite des logs 
[18:32:43] INFO: Preparing to start...
[18:32:43] INFO: Socat not enabled
[18:32:44] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info 2024-01-24 18:32:45: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-24.18-32-45' filename: log.txt
Zigbee2MQTT:info 2024-01-24 18:32:45: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-24 18:32:45: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:info 2024-01-24 18:32:45: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2024-01-24 18:32:45: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:error 2024-01-24 18:32:58: Failed to start zigbee
Zigbee2MQTT:error 2024-01-24 18:32:58: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-01-24 18:32:58: Exiting...
Zigbee2MQTT:error 2024-01-24 18:32:58: Error: get network parameters Error:TIMEOUT
at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1017:35)
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:538:9)
at processTimers (node:internal/timers:512:7)
at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:360:44)
at Zigbee.start (/app/lib/zigbee.ts:120:62)
at Controller.start (/app/lib/controller.ts:98:27)
at start (/app/index.js:107:5)
c’est ok ? coté Proxmox ?
Je ne sais plus pourquoi il y a besoin des 2 fichiers … j’ai pas cette conf donc de mémoire
Mais ajoute le bloc serial à la fin
homeassistant: true
advanced:
network_key:
- 38
- 173
- 252
- 95
- 200
- 104
- 114
- 148
- 173
- 38
- 83
- 112
- 28
- 1
- 22
- 141
pan_id: 39497
ext_pan_id:
- 6
- 139
- 218
- 134
- 232
- 166
- 193
- 71
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password: Chiecahsiech4quiec7XaiVa3xew3san1iep6ohC8aiweepoch9XaV5uapheegh6
frontend:
port: 8099
serial:
port: >-
blabla
adapter: deconz
Coté proxmox c’est ok
j’ai redemarré …
c’est pareil
Donc dans la partie z2m,
Tu bascules en yaml
Tu copies/colles ça
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:
server: mqtt://core-mosquitto:1883
user: addons
password: Chiecahsiech4quiec7XaiVa3xew3san1iep6ohC8aiweepoch9XaV5uapheegh6
homeassistant: true
advanced:
network_key:
- 38
- 173
- 252
- 95
- 200
- 104
- 114
- 148
- 173
- 38
- 83
- 112
- 28
- 1
- 22
- 141
pan_id: 39497
ext_pan_id:
- 6
- 139
- 218
- 134
- 232
- 166
- 193
- 71
frontend:
port: 8099
serial:
port: blabla
adapter: deconz
Tu corriges le port avec le tien, tu sauvegarde, tu relance Z2m et tu poste les logs