zigbee2mqtt / hassio-zigbee2mqtt Goto Github PK

View Code? Open in Web Editor NEW

974.0 29.0 348.0 459 KB

Official Zigbee2MQTT Home Assistant add-on

Home Page: https://www.zigbee2mqtt.io

License: Apache License 2.0

Shell 46.30% Dockerfile 29.32% Groovy 24.38%

zigbee zigbee2mqtt home-assistant hassio hassio-addons hassio-repository

hassio-zigbee2mqtt's Introduction

Official Zigbee2MQTT Home Assistant addon

Installation

If you don't have an MQTT broker yet; in Home Assistant go to Settings → Add-ons → Add-on store and install the Mosquitto broker addon, then start it.
Go back to the Add-on store, click ⋮ → Repositories, fill in
https://github.com/zigbee2mqtt/hassio-zigbee2mqtt and click Add → Close or click the Add repository button below, click Add → Close (You might need to enter the internal IP address of your Home Assistant instance first).
The repository includes two add-ons:
- Zigbee2MQTT is the stable release that tracks the released versions of Zigbee2MQTT. (recommended for most users)
- Zigbee2MQTT Edge tracks the dev branch of Zigbee2MQTT such that you can install the edge version if there are features or fixes in the Zigbee2MQTT dev branch that are not yet released.
Click on the addon and press Install and wait till the addon is installed.
Click on Configuration
- If you are not using the Mosquitto broker addon fill in your MQTT details (leave empty when using the Mosquitto broker addon). Format can be found here, but skip the initial mqtt: indent. e.g.:
```
server: mqtt://localhost:1883
user: my_user
password: "my_password"
```
  Note: If the password includes certain special characters (reserved by yaml specification), the enclosing quotes are required. So it is recommended to always quote it when in doubt.
- Fill in the serial details (e.g. port of your USB coordinator). Format can be found here, but skip the initial serial: indent. e.g.:
```
port: /dev/ttyUSB0
```
- If you don't know the port and you have just one USB device connected to your machine try /dev/ttyUSB0. Else use the Home Assistant CLI and execute ha hardware info to find out.
- Click Save
- Tip: it is possible to refer to variables in the Home Assistant secrets.yaml file (not the Zigbee2MQTT one!) by using e.g. password: '!secret mqtt_pass'
Start the addon by going to Info and click Start
Wait till Zigbee2MQTT starts and press OPEN WEB UI to verify Zigbee2MQTT started correctly.
- If it shows 502: Bad Gateway wait a bit more and refresh the page.
- If this takes too long (e.g. 2 minutes +) check the Log tab to see what went wrong.

For more information see the documentation.

Restoring data from a standalone installation

Ensure that both environments are running the same version
Backup your standalone environment data folder (possibly leaving out the logs/ folder)
Configure your serial port using the HA addon configuration UI
Restore your data folder contents into /usr/share/hassio/homeassistant/zigbee2mqtt
Edit the /usr/share/hassio/homeassistant/zigbee2mqtt/configuration.yaml file:
- Ensure that the serial port section matches the one configured with the UI
- Remove any irrelevant sections from the config (e.g. mqtt, advanced/log_syslog, frontend)
Start the add-on

Changelog

The format is based on Keep a Changelog.

All notable changes to this project will be documented in the CHANGELOG.md file.

Version for releases is based on Zigbee2MQTT format: X.Y.Z.

Any changes on the addon that do not require a new version of Zigbee2MQTT will use the format: X.Y.Z-A where X.Y.Z is fixed on the Zigbee2MQTT release version and A is related to the addon.

Edge version will not maintain a CHANGELOG and doesn't have a version.

Issues

If you find any issues with the add-on, please check the issue tracker for similar issues before creating one. If your issue is regarding specific devices or, more generally, an issue that arises after Zigbee2MQTT has successfully started, it should likely be reported in the Zigbee2MQTT issue tracker.

Feel free to create a PR for fixes and enhancements.

Testing changes locally

If you're submitting a PR and wish to test it locally:

Gain root access to your Home Assistant installation
In the Add-on Settings, Ensure "Watchdog" is turned off so the container isn't automatically restarted when it's stopped via the CLI

Enter the zigbee2mqtt container interactively.

docker exec -it $(docker ps | grep zigbee2mqtt | cut -d" " -f 1) /bin/sh

Edit the file you'd like to test & save.

vi node_modules/zigbee-herdsman-converters/converters/toZigbee.js

Back on the Home Assistant installation, restart the zigbee2mqtt container

docker restart $(docker ps | grep zigbee2mqtt | cut -d" " -f 1)

Refresh the web UI and perform your testing.

Credits

hassio-zigbee2mqtt's People

Contributors

Stargazers

Watchers

Forkers

ciotlosm rstein ostenh johanleirnes wilmsr grbasta 9840380 hnhkj wtk andreypolyak ewoutdenheijer david-sawatzke 11protos11 maksir zesani dinhchinh82 gz315200 liquidblacknl hungpr0 lukasvotypka gwdg86 gawronnek jgronowski quantumlemur srgadget orinocoz davyroswinkel codefinder2 aurynofmordor casp3rvpn dementeb gleepwurp smartmaker-pl jqk91 ozadr1an cym9007 swiftpaws kaynguyen0502 emilhetty badersik ant-ds beosro yuriibut srchun hdemel homesmart0 sts0mrg0 biasf apakann poeka stefanfr nbogojevic pascalschwientek leocal quadportnick koterak donnie-darko liviob74 kloknibor mlachowski-stx szym1991 mansic2 justanygithubuser andreiradchenko bingofang www005531 krconv djansen1987 xdvorakv sterni18 shved89 pyromanv teameh sebas86 vmarkovsky suifeng009 bacyapetkin blaathor maxpassukhin szulck scaredmushroom danyafilatov fsfikke ikke-zelf pakkardkaw merdely miroslavb drberthol acekjys powercolorsky nnkostov tomaszkob89 rlagerweij ireneuo pacdesaintes vvv279 fschaeck ahmedsamer zuz666 trave3x

hassio-zigbee2mqtt's Issues

1.16.2 WARNING (MainThread) [supervisor.addons.validate] Unknown options restartdelay

zigbee2mqtt add-on version (if edge, please report commit hash):
1.16.2
Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:
Error in logs when start or restart addon

Your logs from Home Assistant

20-12-03 16:34:59 WARNING (MainThread) [supervisor.addons.validate] Unknown options restartdelay
20-12-03 16:34:59 WARNING (MainThread) [supervisor.addons.validate] Unknown options initialdelay

CC2652P dont start on 1.18.0-1 release

Description of problem:

Stick CC2652P (CC1352P2_CC2652P_coordinator_20210120.zip firmware inside stick) dont start.
This error was detected at first time on zegbee2mqtt edge in release upper than 2021.02.21 (zigbee-herdsman relise upper 0.13.60)

// Make sure your problem is related to the add-on, not to core Zigbee2mqtt functionality, like problems with specific devices - for such issues use https://github.com/Koenkk/zigbee2mqtt/issues

Zigbee2mqtt add-on version (if edge, please report commit hash):

zigbee2mqtt@ 1.18.0-1 master

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: mqtt
  password: mqtt
  version: 5
serial:
  port: /dev/ttyUSB0
advanced:
  log_level: debug
  pan_id: 6754
  channel: 25
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
  last_seen: ISO_8601_local
  homeassistant_legacy_triggers: true
  availability_timeout: 1800
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
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
zigbee_shepherd_devices: true
zigbee_herdsman_debug: true
ota: {}

Running platform (details from Suypervisor > System)

Pi4b
core-2021.2.3
supervisor-2021.02.11
Home Assistant OS 5.12

Your logs from Home Assistant Supervisor

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[00:03:58] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[00:03:59] INFO: MQTT available, fetching server detail ...
[00:03:59] INFO: Previous config file found, checking backup
[00:03:59] INFO: Creating backup config in '/share/zigbee2mqtt/.configuration.yaml.bk'
[00:03:59] WARNING: No devices.js file found in data path, starting with default devices.js
[00:03:59] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[00:04:00] INFO: Zigbee Herdsman debug logging enabled
[00:04:00] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:debug 2021-03-02 00:04:04: Loaded state from file /share/zigbee2mqtt/state.json
Zigbee2MQTT:info  2021-03-02 00:04:04: Logging to console and directory: '/share/zigbee2mqtt/log/2021-03-02.00-04-03' filename: log.txt
Zigbee2MQTT:debug 2021-03-02 00:04:04: Removing old log directory '/share/zigbee2mqtt/log/2021-03-01.23-58-43'
Zigbee2MQTT:info  2021-03-02 00:04:05: Starting Zigbee2MQTT version 1.18.0 (commit #1.18.0)
Zigbee2MQTT:info  2021-03-02 00:04:05: Starting zigbee-herdsman (0.13.72)
Zigbee2MQTT:debug 2021-03-02 00:04:05: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null},"backupPath":"/share/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","databasePath":"/share/zigbee2mqtt/database.db","network":{"channelList":[25],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyUSB0"}}'
2021-03-01T21:04:05.276Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2021-03-01T21:04:05.280Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[25]},"serialPort":{"path":"/dev/ttyUSB0"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","adapter":{"concurrent":null,"delay":null}}'
2021-03-01T21:04:05.282Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyUSB0 and {"baudRate":115200,"rtscts":false,"autoOpen":false}
2021-03-01T21:04:05.302Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened
2021-03-01T21:04:05.762Z zigbee-herdsman:adapter:zStack:znp:log Writing skip bootloader payload
2021-03-01T21:04:05.763Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2021-03-01T21:04:06.771Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-01T21:04:06.775Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2021-03-01T21:04:12.784Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-01T21:04:12.785Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2021-03-01T21:04:18.793Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-01T21:04:18.794Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
Zigbee2MQTT:error 2021-03-02 00:04:24: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-02 00:04:24: Failed to start zigbee
Zigbee2MQTT:error 2021-03-02 00:04:24: Exiting...
Zigbee2MQTT:error 2021-03-02 00:04:24: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-01T21_04_24_880Z-debug.log

My Home Assistant is not showing new version available, even though there are

Description of problem:
Hello,

I'm running version 1.16.1 and dev version (edge) is 1.16.2 but I've just browsed the repository and there I saw that version 1.18 is out. Why is that the case? How do I force an upgrade making sure I don't break anything. I have like 30 devices running just fine.

Zigbee2mqtt add-on version (if edge, please report commit hash):

"permit_join":false,"version":"1.16.1"}'

Running platform (details from Suypervisor > System)

  OS Version:               Debian GNU/Linux 10 (buster)
  Home Assistant Core:      2021.2.1

deprecated add-on option

zigbee2mqtt add-on version (if edge, please report commit hash): 0.17.0

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant): Debian 10 Supervised

Description of problem:
New Supervisor (2021.2.5) prints error in Supervisor's log:

21-02-10 06:19:14 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'auto_uart' is deprecated, use 'uart'. Please report this to the maintainer of Zigbee2mqtt
21-02-10 06:19:14 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'auto_uart' is deprecated, use 'uart'. Please report this to the maintainer of Zigbee2mqtt Edge

Your entire configuration from the frontend (with sensitive fields redacted):

n/a

Your logs from Home Assistant
n/a

Dev branch can't load my configuration (string error) - stable works fine

Description of problem:
The dev branch can't load up my configuration suddenly. The error lies with devices.yaml and says it needs to be a string. The exact configuration works fine with stable branch (and has always worked with both dev and stable). This is how devices.yaml is setup (and what works under stable and previous dev).

Just to clarify: I switch between stable and dev now and then when I propose a change for dev. I ran dev for a while. Switched to stable and then switched to a dev (newer build than before) and that one doesn’t work. Stable works fine.

'0x90fd9ffffe67aa7b':
  friendly_name: Keuken Lamp Plafond 1
  transition: 0.4

Zigbee2mqtt add-on version (if edge, please report commit hash):

[email protected] /app

Configuration:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user:  [REDACTED]
  password:  [REDACTED]
serial:
  adapter: deconz
  disable_led: false
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2133075-if00
advanced:
  log_level: debug
  last_seen: ISO_8601_local
  log_directory: /share/zigbee2mqtt/log/
  log_file: log.txt
  report: true
  pan_id: 62369
  channel: 25
  network_key: [REDACTED]
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false```

Running platform (details from Suypervisor > System)

Core: core-2021.3.3
Supervisor: supervisor-2021.03.4
Operating System: Home Assistant OS 5.12

Your logs from Home Assistant Supervisor

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[13:12:52] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[13:12:53] INFO: MQTT available, fetching server detail ...
[13:12:53] INFO: Previous config file found, checking backup
[13:12:53] INFO: Creating backup config in '/share/zigbee2mqtt/.configuration.yaml.bk'
[13:12:53] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:12:55] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:
- devices['0xd0cf5efffed82e95']['transition'] should be string
- devices['0x90fd9ffffe67aa7b']['transition'] should be string
- devices['0x000b57fffed96377']['transition'] should be string
- devices['0x000b57fffeeaff88']['transition'] should be string
- devices['0x90fd9ffffe6dfed5']['transition'] should be string
- devices['0x90fd9ffffe6fc60e']['transition'] should be string
- devices['0x00158d00012f5559']['transition'] should be string
- devices['0x00158d00013bcd7b']['transition'] should be string
- devices['0x00158d00013bcde0']['transition'] should be string
- devices['0x00158d00012ec354']['transition'] should be string
- devices['0xccccccfffecba5ce']['transition'] should be string
- devices['0xccccccfffe36abbf']['transition'] should be string
- devices['0xccccccfffe36009f']['transition'] should be string
- devices['0xccccccfffe31f456']['transition'] should be string
- devices['0x14b457fffe744c51']['transition'] should be string
- devices['0x00158d00012f558f']['transition'] should be string
- devices['0x00158d000126faf1']['transition'] should be string
- devices['0x00158d000126fb1f']['transition'] should be string
- devices['0x00158d00012ee7ae']['transition'] should be string
- devices['0x7cb03eaa0a074f90']['transition'] should be string
- devices['0x7cb03eaa00b03420']['transition'] should be string
- devices['0x00158d0001271b2b']['transition'] should be string
- devices['0x5c0272fffebe23d3']['reverse_direction'] should be string
- devices['0x7cb03eaa0a0749ed']['transition'] should be string
- devices['0x14b457fffe6be2fe']['legacy'] should be string
- devices['0x00158d00012ee461']['transition'] should be string
- devices['0x00158d00012f41a4']['transition'] should be string
- devices['0x847127fffe1b72fc']['reverse_direction'] should be string
- devices['0x00158d00012f40c1']['transition'] should be string
- devices['0xbc33acfffe8acbb3']['legacy'] should be string
- devices['0xbc33acfffec040dc']['transition'] should be string
- devices['0x7cb03eaa00b02f2f']['transition'] should be string
If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-13T12_12_57_341Z-debug.log
[13:12:57] INFO: Handing over control to Zigbee2mqtt Core ...

How to switch to the new repository without losing all my configs and devices?

I am stuck with release 1.17.1-4. So I've read that I need the new repository link. However, when I add the new repository, It does not update the existing zigbee2mqtt, it creates a new one, therefore all me settings and devices are "lost".
Is there a way to update to the latest release without losing all my setting, configs and devices?
Thanks a lot.

zigbee2mqtt add-on version 1.17.1-4

Current repository:
Home Assistant Add-on: Zigbee2mqtt
Daniel Welch [email protected]
https://www.zigbee2mqtt.io

Core: core-2021.3.1
Supervisor: supervisor-2021.03.4
Operating System: HassOS 5.12

[1.17.1-1] transit_power option removed from settings ...

Nothing has changed regarding this option from the z2m perspective. Likely something in the addon so create an issue her: https://github.com/danielwelch/hassio-zigbee2mqtt/issues

Originally posted by @Koenkk in Koenkk/zigbee2mqtt#6251 (comment)

Description of problem:
transmit_power was removed from experimental settings - this functionality didn't change and is still implemented in zigbee2mqtt itself in the same place.

This currently results in the transit_power setting not working at all in the addon itself (it did with 1.17.1).

Zigbee2mqtt add-on version (if edge, please report commit hash):

 > [email protected]

Running platform (details from Suypervisor > System)

Core: core-2021.2.1
Supervisor: supervisor-2021.02.6
Operating System: HassOS 5.10

Make measurement_poll_interval available via GUI

Description of problem:
I didn't found a way to specify a measurement_poll_interval for certain devices in the UI. The config file is split, so I can only access the main config file of the add-on. The devices section is managed by the add-on and not available to the user via the GUI in the supervisor section.

Zigbee2mqtt add-on version:

1.17.1-4

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto:1883'
  user: 
  password: 
serial:
  port: /dev/ttyUSB0
advanced:
  log_level: error
  pan_id: 6754
  channel: 11
  network_key:
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

Running platform

Core: core-2021.2.3
Supervisor: supervisor-2021.02.11
Operating System: HassOS 5.11

RFI: How to migrate from separate Docker Z2M to HASSIO integrated Z2M add-on?

Hi,
After a long death struggle, I gave up. I wanted to migrate my HA from my slow/small RasPi 3B to a decent RasPi 4 (4GB),
Initially I was going to use again a supervised HA install, as I have on my RasPi 3B for a good year now but after so many issues over a long time (which I could all fix, learned a lot along the way) today I had enough.

I just decided I'm going to the dark (but hopefully more stable working) side of a 64 bit HASSIO, running on the RasPi 4.
I'm currently have a decent size (about 90 devices) network of which 60+ Zigbee.
So I would like to move my coordinator and move the Z2M relevant files (incl. device names, settings etc) to the Add-on install of Z2M.

How would I best to go about it?

I can see probably the following files need to be transferred but how to do it easiest?

configuration.yaml
database.db
state.json
coordinator_backup.json

Thanks.

I'll have to figure the same out for my influxdb db files :)

Unknown device - control via MQTT

Good day,
I have a device (_TZE200_zion52ef) and in "external_devices.js" I have everything I need to get information. Now I would like to control this device via MQTT, but only errors are displayed via the "toZigbee" file and the thermostat does not respond (for example child_lock). Can you show me how and what to add to "external_devices.js". Thanks

external_devices.js

const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const constants = require('zigbee-herdsman-converters/lib/constants');
const {repInterval, defaultBindGroup, OneJanuary2000} = require('zigbee-herdsman-converters/lib/constants');
const reporting = require('zigbee-herdsman-converters/lib/reporting');

const e = exposes.presets;
const ea = exposes.access;


const LocaldataPoints = {
    moesHold: 2,
    moesTempManualMode: 16,
    moesLocalTemp: 24,
    moesChildLock: 30,
    moesBattery: 34,
    moesComfortPresetTemp: 101,
    moesEnergyPresetTemp: 102,
    moesTempOffset: 104,
    moesTempAutoMode: 105,
    moesScheduleMonday: 109,
    moesScheduleTuesday: 110,
    moesScheduleWednesday: 111,
    moesScheduleThursday: 112,
    moesScheduleFriday: 113,
    moesScheduleSaturday: 114,
    moesScheduleSunDay: 115,
    moesOpenWindowTemp: 116,
    moesOpenWindowTime: 117,
    moesRapidModeCountdownTimer: 118,
};

function DTT(Numbero) { //DataToTime
    Hod = Math.floor((Numbero*15)/60);
    Min = ((((Numbero*15)/60)-Hod)*60);
    if (Min == "0") { Min ="00"}
    return Hod + ':' + Min;
}

function Schedule(Pole) {
    TTX = '00:00';
    for (i = 1; i < 18; i++) {
        switch (i) {
            case 1: case 3: case 5: case 7: case 9: case 11: case 13: case 15: case 17:
                TTX = TTX + ' - ' + Pole[i]/2;
                break;
            case 2: case 4: case 6: case 8: case 10: case 12: case 14: case 16:
                TTX = TTX + ' - ' + DTT(Pole[i]);
                break;
        }
 if (Pole[i] === 96) { break; }
        
    }
    return TTX;
}


const fzLocal = {
        moes_thermostat: {
        cluster: 'manuSpecificTuya',
        type: ['commandGetData', 'commandSetDataResponse'],
        convert: (model, msg, publish, options, meta) => {
            const dp = msg.data.dp;
            const value = tuya.getDataValue(msg.data.datatype, msg.data.data);
            switch (dp) {
            case LocaldataPoints.moesHold:
                return {preset_mode: value ? 'manu' : 'auto', preset: value ? 'manu' : 'auto'};
            case LocaldataPoints.moesChildLock:
                return {child_lock: value ? 'LOCK' : 'UNLOCK'};
            case LocaldataPoints.moesLocalTemp:
                return {local_temperature: parseFloat((value / 10).toFixed(1))};
            case LocaldataPoints.moesTempAutoMode: //DP 105 teplota v AUTO
                return {current_heating_setpoint: parseFloat((value / 2).toFixed(1))};
            case LocaldataPoints.moesTempManualMode: //DP 16 teplota v MANU
                return {current_heating_setpoint: parseFloat((value / 2).toFixed(1))};
            case LocaldataPoints.moesBattery:
                return {battery: value};
            case LocaldataPoints.moesScheduleMonday:
                return { '1-Monday': Schedule(value) };
            case LocaldataPoints.moesScheduleTuesday:
                return { '2-Tuesday': Schedule(value) };
            case LocaldataPoints.moesScheduleWednesday:
                return { '3-Wednesday': Schedule(value) };
            case LocaldataPoints.moesScheduleThursday:
                return { '4-Thursday': Schedule(value) };
            case LocaldataPoints.moesScheduleFriday:
                return { '5-Friday': Schedule(value) };
            case LocaldataPoints.moesScheduleSaturday:
                return { '6-Saturday': Schedule(value) };
            case LocaldataPoints.moesScheduleSunDay:
                return { '7-Sunday': Schedule(value) };
            case LocaldataPoints.moesOpenWindowTemp:
                return {open_window_temperature: parseFloat((value / 2).toFixed(1))};
            case LocaldataPoints.moesOpenWindowTime:
                return {open_window_time: value};
            case LocaldataPoints.moesRapidModeCountdownTimer:
                return {rapid_mode_countdown: value};
            default:
                meta.logger.warn(`###################: NEZNAME DP #${dp} data ${JSON.stringify(msg.data)}`);
            }
        },
    },

}

const device = 
    {
        zigbeeModel: ['wdxldoj'],
        fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_zion52ef'}],
        model: 'TS0601_thermostat',
        vendor: 'TuYa',
        description: 'Radiator valve with thermostat',
        onEvent: tuya.onEventSetLocalTime,
        fromZigbee: [
            fz.ignore_basic_report,
            fzLocal.moes_thermostat,
            fz.ignore_tuya_set_time
        ],
        toZigbee: [
            tz.tuya_data_point_test, //pridano
            tz.moes_thermostat_child_lock, //not working
        ],
               exposes: [
            e.child_lock(),
            ],
    };

module.exports = device;

Failed to start zigbee

Description of problem:
I am running this plugin on my Home Assistant. After I rebooted the system everything failed to start, due to an update from Supervisor. So I downgraden supervisor, restored a snapshot, but then zigbee2mqtt was gone.. I was using danielwelch/hassio-zigbee2mqtt which migrated to here I saw.
So I installed this version 1.17.1-4, updated the config to what I had before:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto
  user: my_user
  password: my_pass
serial:
  port: /dev/ttyACM0
advanced:
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
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

When starting I get errors:

Zigbee2MQTT:error 2021-02-15 21:57:22: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-02-15 21:57:22: Failed to start zigbee
Zigbee2MQTT:error 2021-02-15 21:57:22: Exiting...
Zigbee2MQTT:error 2021-02-15 21:57:22: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Running platform (details from Suypervisor > System)

Core: core-2021.2.1
Supervisor: supervisor-2021.01.7
Operating System: Docker version 18.09.8

My Supervisor System Hardware shows:

serial:
  - /dev/ttyACM0
  - >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014DA4C0E-if00
  - /dev/ttyS0
  - /dev/ttyS1
  - /dev/ttyS2
  - /dev/ttyS3
input:
  - Sleep Button
  - Video Bus
  - Power Button
disk: []
gpio:
  - gpiochip0
usb:
  - /dev/bus/usb/001/001
  - '/dev/1-0:1.0'
  - /dev/bus/usb/001/003
  - '/dev/1-10:1.0'
  - '/dev/1-10:1.1'
  - /dev/bus/usb/001/002
  - '/dev/1-9:1.0'
  - /dev/bus/usb/002/001
  - '/dev/2-0:1.0'
audio: {}

So the device is available.

Your logs from Home Assistant Supervisor

21-02-15 20:05:49 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.17.1-4

21-02-15 20:08:22 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_core_mosquitto application
21-02-15 20:08:22 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_core_mosquitto application
21-02-15 20:08:31 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_7ad98f9c_zigbee2mqtt application
21-02-15 20:08:32 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_7ad98f9c_zigbee2mqtt application
21-02-15 20:09:06 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mosquitto with version 5.1
21-02-15 20:09:07 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
21-02-15 20:10:00 INFO (SyncWorker_3) [supervisor.docker.interface] Removing image zigbee2mqtt/zigbee2mqtt-amd64 with latest and 1.17.1-4
21-02-15 20:10:01 INFO (MainThread) [supervisor.addons.addon] Removing add-on data folder /data/addons/data/7ad98f9c_zigbee2mqtt
21-02-15 20:10:01 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-02-15 20:10:01 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for 7ad98f9c_zigbee2mqtt
21-02-15 20:10:01 INFO (MainThread) [supervisor.addons] Add-on '7ad98f9c_zigbee2mqtt' successfully removed
21-02-15 20:12:33 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_core_mosquitto application
21-02-15 20:12:34 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_core_mosquitto application



21-02-15 20:23:37 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-02-15 20:23:37 INFO (MainThread) [supervisor.resolution.check] System checks complete

21-02-15 20:28:57 INFO (SyncWorker_0) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant
21-02-15 20:29:07 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-02-15 20:29:42 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-02-15 20:31:49 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant
21-02-15 20:31:57 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-02-15 20:32:32 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance

21-02-15 20:35:40 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mosquitto with version 5.1
21-02-15 20:35:41 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
21-02-15 20:36:26 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-nginx_proxy with version 3.0.1
21-02-15 20:37:46 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-rpc_shutdown with version 2.2
21-02-15 20:37:54 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/aircast/amd64 with version 3.0.0

21-02-15 20:41:16 INFO (MainThread) [supervisor.store.git] Removing custom add-on repository https://github.com/danielwelch/hassio-zigbee2mqtt
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/deconz/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/homematic/config.json: does not match regular expression for dictionary value @ data['schema']['hmip'][0]['device']. Got 'device(subsystem=tty)'
does not match regular expression for dictionary value @ data['schema']['rf'][0]['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/zwave/config.json: does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/zwave_js/config.json: does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/node-red/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/ssh/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/wireguard/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/net/tun'
21-02-15 20:41:16 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/zerotier/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/net/tun'
21-02-15 20:41:16 INFO (MainThread) [supervisor.store] Loading add-ons from store: 57 all - 0 new - 2 remove
21-02-15 20:41:46 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/deconz/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/homematic/config.json: does not match regular expression for dictionary value @ data['schema']['hmip'][0]['device']. Got 'device(subsystem=tty)'
does not match regular expression for dictionary value @ data['schema']['rf'][0]['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/zwave/config.json: does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/core/zwave_js/config.json: does not match regular expression for dictionary value @ data['schema']['device']. Got 'device(subsystem=tty)'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/node-red/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/ssh/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/mem'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/wireguard/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/net/tun'
21-02-15 20:41:47 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/a0d7b954/zerotier/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/net/tun'
21-02-15 20:41:47 INFO (MainThread) [supervisor.store] Loading add-ons from store: 59 all - 2 new - 0 remove

21-02-15 20:44:43 CRITICAL (MainThread) [supervisor.jobs] The following job conditions are ignored and will make the system unstable when they occur: {<JobCondition.HEALTHY: 'healthy'>}
21-02-15 20:44:43 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/45df7312_zigbee2mqtt
21-02-15 20:44:43 INFO (SyncWorker_4) [supervisor.docker.interface] Downloading docker image zigbee2mqtt/zigbee2mqtt-amd64 with tag 1.17.1-4.
21-02-15 20:44:54 INFO (MainThread) [supervisor.addons] Add-on '45df7312_zigbee2mqtt' successfully installed
21-02-15 20:47:46 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-02-15 20:47:46 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for 45df7312_zigbee2mqtt

21-02-15 20:48:21 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.17.1-4

Update icons not shown anymore in GUI

After updating from 1.17 to latest (1.17.1-4) the update icons in the GUI.

This is shown now:

For this device with this state:

So now it is now possible to update from GUI.

AddonManager.install blocked from execution, system is not health

I am trying to install the addon but I am unable to do so, I am receiving the following error:

20-12-04 22:41:37 WARNING (MainThread) [supervisor.jobs] 'AddonManager.install' blocked from execution, system is not healthy

Failed to connect to Adapter after Update

Description of problem:
I updated to the new version 1.18.0-1 and the addon was not able to start: "missing OTA in root". so i added

ota:
  update_check_interval: 10
  disable_automatic_update_check: false

to the config. now i get another error log:

[20:10:04] INFO: Previous config file found, checking backup
[20:10:04] INFO: Creating backup config in '/share/zigbee2mqtt/.configuration.yaml.bk'
[20:10:04] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[20:10:05] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:info  2021-03-01 20:10:08: Logging to console and directory: '/share/zigbee2mqtt/log/2021-03-01.20-10-07' filename: log.txt
Zigbee2MQTT:info  2021-03-01 20:10:08: Starting Zigbee2MQTT version 1.18.0 (commit #1.18.0)
Zigbee2MQTT:info  2021-03-01 20:10:08: Starting zigbee-herdsman (0.13.72)
Zigbee2MQTT:error 2021-03-01 20:10:28: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-01 20:10:28: Failed to start zigbee
Zigbee2MQTT:error 2021-03-01 20:10:28: Exiting...
Zigbee2MQTT:error 2021-03-01 20:10:28: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: **********
  password: *********
serial:
  port: >-
    /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CB_FD_8A-if00-port0
advanced:
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  ikea_ota_use_test_url: true
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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
ota:
  update_check_interval: 10
  disable_automatic_update_check: false

Running platform (details from Suypervisor > System)

Core: core-2021.2.3
Supervisor: supervisor-2021.02.11
Operating System: Debian

Request - add EZSP adapter support to edge

No issue. Request to add the new testing adapter for EZSP for supervisor users.

Still 1.18.1.1 version in Hassio with Hassos

Description of problem:
The version of add on is 1.18.1.1 I've tried to reload the add on repository, reboot the host, restart of server but non updating of add on the version 1.18.1.2 is not available

**Zigbee2mqtt add-on version and platform

// 
// > [email protected]
// Supervisor 2021.03.6
// Core 2021.03.4
// HassOS 5.12

Set the speed of the roller shutter using Home Assistant

Description of problem:
I can only control the position of my roller shutter [https://www.zigbee2mqtt.io/devices/TS0601_cover.html], which I have connected to Home Assistant via zigbee, but it is also possible to set the speed and the status (open, close) in Zigbee2Mqtt.
However, these values only appear as attributes in Home Assistant and cannot be changed. Above all, the speed that the roller shutter needs to be closed is at a speed of "1" 3 minutes and at a speed of "255" 20 seconds, which incidentally also makes a large difference in volume of the motor. (e.g. important in the morning and in the evening)

Zigbee2mqtt add-on version (if edge, please report commit hash):

current version: 1.17.1-4

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.178.128:1883'
  user: pi
  password: smarthome2020
serial:
  disable_led: true
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E334C7-if00
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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

Running platform (details from Suypervisor > System)

// Example
Core: core-2021.3.4
Supervisor: supervisor-2021.03.6
Operating System: Home Assistant OS 5.12

Failed to start zigbee: RaspBee/Conbee with homeassistant OS (Supervised) on Raspberry 4 (2GB)

Description of problem:
Cannot start zigbee2mqtt with desden-elektornik's RaspBee on homeassistant OS (Superviced)

Zigbee2mqtt add-on version (if edge, please report commit hash):

Current version: 1.17.1-4

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://homeassistant'
  user: replaced
  password: replaced
serial:
  port: /dev/ttyAMA0
  adapter: deconz
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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
zigbee_herdsman_debug: true

Running platform (details from Suypervisor > System)

Core:
Version core-2021.2.3
Newest Version core-2021.2.3 

Supervisor:
Version supervisor-2021.02.9
Newest Version supervisor-2021.02.9 

Host:
IP Address 192.168.178.55/24
Operating System Home Assistant OS 5.11

Your logs from Home Assistant Supervisor

[15:47:04] INFO: Zigbee Herdsman debug logging enabled
[15:47:05] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
2021-02-18T14:47:09.131Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2021-02-18T14:47:09.139Z zigbee-herdsman:deconz:driver Set delay to 300
CREATED DECONZ ADAPTER
2021-02-18T14:47:09.144Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyAMA0","adapter":"deconz"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"concurrent":null,"delay":null}}'
2021-02-18T14:47:09.146Z zigbee-herdsman:deconz:driver Opening with /dev/ttyAMA0
2021-02-18T14:47:09.156Z zigbee-herdsman:deconz:driver Serialport opened
2021-02-18T14:47:09.159Z zigbee-herdsman:controller:log Started with result 'resumed'
2021-02-18T14:47:09.159Z zigbee-herdsman:controller:log Injected database: true, adapter: true
2021-02-18T14:47:09.240Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 1 paramId: 1
2021-02-18T14:47:12.144Z zigbee-herdsman:deconz:adapter checking coordinator simple descriptor
2021-02-18T14:47:12.151Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x0 EP:0 SeqNr. 2 request id: 1
2021-02-18T14:47:20.139Z zigbee-herdsman:deconz:driver Timeout for request - CMD: 0xa seqNr: 1
Zigbee2MQTT:error 2021-02-18 15:47:20: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-02-18 15:47:20: Failed to start zigbee
Zigbee2MQTT:error 2021-02-18 15:47:20: Exiting...
Zigbee2MQTT:error 2021-02-18 15:47:20: undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-18T14_47_20_216Z-debug.log

Addon wont start because /dev/ttyZ2M is read only

I'm using zigbee2mqtt with socat with the default configuration values where /dev/ttyZ2M gets created as device (as per example config).

Since latest version of supervisor (supervisor-2021.02.6) this does break and throws a error stating that /dev/ttyZ2M is read-only in the 1.17.1-1 release. 1.17.1 release would just keep restarting socat without extra information. (sorry dont have logs anymore!)

It seems that changing from the socat configuration from /dev/ttyZ2M to /share/zigbee2mqtt/ttyZ2M would fix my issue.

After investigation it seems that this supervisor commit does change /dev/ to read-only state:
home-assistant/supervisor@b8a976b

I would like to suggest to change config.json from:
"master": "pty,raw,echo=0,link=/dev/ttyZ2M,mode=777",
to
"master": "pty,raw,echo=0,link=/share/zigbee2mqtt/ttyZ2M,mode=777",

No traffic to MQTT after upgrade

Description of problem:
Version upgraded to latest. Edge version will boot, non-edge version crashes immediately.

[16:16:51] INFO: MQTT available, fetching server detail ...
[16:16:52] INFO: MQTT credentials not configured, trying to auto-discovering ...
[16:16:52] INFO: Configuring'addons' mqtt user

If I monitor MQTT, absolutely nothing is received from zigbee2mqtt
Monitoring for this: Zigbee2MQTT:info 2021-02-12 16:16:59: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'

All other devices using MQTT are working fine.

[Enhancement] Allow editing settings using built-in Zigbee2mqtt web interface

Zigbee2mqtt now has a pretty nice build in web interface. It's also possible to edit most configuration settings using the web interface. These config changes are overwritten by a restart of the add on. This makes the settings part of the interface unusable. All configuration needs to be done in the add on configuration. This is a pity, because the settings in the web interface are actually more comprehensive then what's being passed trough by the add on. (last_seen for example, is missing)

Perhaps it's worth considering to rely on zigbee2mqtt's native web interface for configuration from now on. That way you don't have to keep track of configuration options of zigbee2mqtt in the add on.

Alternatively, you could perhaps make this in itself an option?

Improve issue template

zigbee2mqtt add-on version (if edge, please report commit hash):

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:

Your entire configuration from the frontend (with sensitive fields redacted):

// replace this line with your pasted configuration

Your logs from Home Assistant

No Log output in Addon. Stops after `> node index.js`

Description of problem:
I followed the instructions in the post by TheStigh on this issue after restoring a backup. There is now no log output form the addon it just stops at > node index.js

Zigbee2mqtt add-on version (if edge, please report commit hash):

// > [email protected] start /app

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto:1883'
  user: xxxxxxxxxxxx
  password: xxxxxxxxxxx
  client_id: zigbee2mqtt
serial:
  port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
advanced:
  log_level: warn
  pan_id: 6755
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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
zigbee_herdsman_debug: false

Running platform (details from Suypervisor > System)

Operating System: HassOS 5.12

Your logs from Home Assistant Supervisor

21-02-25 22:33:44 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-audio with version 2021.02.1
21-02-25 22:33:44 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
21-02-25 22:33:45 INFO (SyncWorker_0) [supervisor.docker.audio] Starting Audio homeassistant/aarch64-hassio-audio with version 2021.02.1 - 172.30.32.4
21-02-25 22:33:45 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-cli with version 2021.02.1
21-02-25 22:33:45 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
21-02-25 22:33:46 INFO (SyncWorker_0) [supervisor.docker.cli] Starting CLI homeassistant/aarch64-hassio-cli with version 2021.02.1 - 172.30.32.5
21-02-25 22:33:46 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-observer with version 2020.10.1
21-02-25 22:33:46 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-multicast with version 3
21-02-25 22:33:46 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
21-02-25 22:33:46 INFO (SyncWorker_0) [supervisor.docker.multicast] Starting Multicast homeassistant/aarch64-hassio-multicast with version 3 - Host
21-02-25 22:33:46 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-02-25 22:33:46 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/raspberrypi4-64-homeassistant with version 2021.2.3
21-02-25 22:33:46 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
21-02-25 22:33:47 INFO (MainThread) [supervisor.hassos] Detect HassOS 5.12 / BootSlot A
21-02-25 22:33:47 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR
21-02-25 22:33:47 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR Beta (outdated)
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/15d21743 repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/ccab4aaf repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/773cbd65 repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/7ad98f9c repository
21-02-25 22:33:47 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a889bffc repository
21-02-25 22:33:47 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR
21-02-25 22:33:47 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR Beta (outdated)
21-02-25 22:33:47 INFO (MainThread) [supervisor.store] Loading add-ons from store: 74 all - 74 new - 0 remove
21-02-25 22:33:47 INFO (MainThread) [supervisor.addons] Found 4 installed add-ons
21-02-25 22:33:48 INFO (SyncWorker_4) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/tasmoadmin/aarch64 with version 0.14.0
21-02-25 22:33:48 INFO (SyncWorker_7) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-mosquitto with version 5.1.1
21-02-25 22:33:48 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to esphome/esphome-hassio-aarch64 with version 1.16.2
21-02-25 22:33:48 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-samba with version 9.3.1
21-02-25 22:33:48 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-02-25 22:33:48 INFO (MainThread) [supervisor.discovery] Loaded 1 messages
21-02-25 22:33:48 INFO (MainThread) [supervisor.ingress] Loaded 1 ingress sessions
21-02-25 22:33:48 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
21-02-25 22:33:48 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-02-25 22:33:48 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-02-25 22:33:48 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-02-25 22:33:48 INFO (MainThread) [__main__] Running Supervisor
21-02-25 22:33:48 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
21-02-25 22:33:48 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
21-02-25 22:33:48 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 2 add-ons
21-02-25 22:33:49 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-mosquitto with version 5.1.1
21-02-25 22:33:49 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_a0d7b954_sonweb application
21-02-25 22:33:50 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/tasmoadmin/aarch64 with version 0.14.0
21-02-25 22:33:52 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
21-02-25 22:33:55 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 1 add-ons
21-02-25 22:33:55 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-samba with version 9.3.1
21-02-25 22:33:55 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'Stephen'
21-02-25 22:33:55 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
21-02-26 08:36:41 INFO (MainThread) [supervisor.core] Start Home Assistant Core
21-02-26 08:36:41 INFO (SyncWorker_1) [supervisor.docker.interface] Starting homeassistant
21-02-26 08:36:41 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-02-26 08:36:42 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'Stephen'
21-02-26 08:36:42 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
21-02-26 08:36:57 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-02-26 08:37:02 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-02-26 08:37:02 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 0 add-ons
21-02-26 08:37:02 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
21-02-26 08:37:02 INFO (MainThread) [supervisor.core] Supervisor is up and running
21-02-26 08:37:02 INFO (MainThread) [supervisor.host.info] Updating local host information
21-02-26 08:37:03 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-02-26 08:37:03 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-02-26 08:37:03 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-02-26 08:37:03 INFO (MainThread) [supervisor.host.services] Updating service information
21-02-26 08:37:03 INFO (MainThread) [supervisor.host.network] Updating local network information
21-02-26 08:37:05 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-02-26 08:37:05 INFO (MainThread) [supervisor.host] Host information reload completed
21-02-26 08:38:05 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-02-26 08:38:34 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-02-26 08:38:42 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-02-26 08:39:00 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/7ad98f9c_zigbee2mqtt
21-02-26 08:39:00 INFO (SyncWorker_6) [supervisor.docker.interface] Downloading docker image zigbee2mqtt/zigbee2mqtt-aarch64 with tag 1.17.1-4.
21-02-26 08:39:36 INFO (MainThread) [supervisor.addons] Add-on '7ad98f9c_zigbee2mqtt' successfully installed
21-02-26 08:41:31 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.17.1-4
21-02-26 08:41:47 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:41:48 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:41:58 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD usb hardware /dev/bus/usb/001/003
21-02-26 08:41:58 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD serial hardware /dev/ttyUSB0 - /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
21-02-26 08:42:02 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.17.1-4
21-02-26 08:48:10 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:48:11 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:50:13 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
21-02-26 08:50:23 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/raspberrypi4-64-homeassistant
21-02-26 08:50:31 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-02-26 08:50:57 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-02-26 08:53:58 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.17.1-4
21-02-26 08:55:32 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:55:34 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:55:43 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.17.1-4
21-02-26 08:58:13 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:58:14 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_7ad98f9c_zigbee2mqtt application
21-02-26 08:59:36 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.17.1-4
21-02-26 08:59:46 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'Stephen'
21-02-26 08:59:47 INFO (MainThread) [supervisor.auth] Successful login for 'Stephen'

Addon Logs

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[08:59:37] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[08:59:38] INFO: MQTT available, fetching server detail ...
[08:59:38] INFO: Previous config file found, checking backup
[08:59:38] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[08:59:38] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:59:39] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js

Zigbee2mqtt not visible in Official add-ons (version for PI4 64 bit)

Description of problem:
Zigbee2mqtt is not listed in the add-on store on my RPI4 running Home Assistant OS 5.12

https://github.com/home-assistant/operating-system/releases/download/5.12/hassos_rpi4-64-5.12.img.xz

Add support to show channel clutter on startup

zigbee2mqtt add-on version (if edge, please report commit hash):

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:

Your entire configuration from the frontend (with sensitive fields redacted):

// replace this line with your pasted configuration

Your logs from Home Assistant

1.18.1 does not start

After migrating to this new repository and installing v1.18.1, I cannot get Zigbee2MQTT to start.
Since the old v1.17.1-4 comes from another repository apparently, I now have 2 Zigbee2MQTT installations in my system...

So I stopped v1.17.1.-4, and copied the configuration settings (mosquitto user/pass, serial port) over to v.1.18.1, and try to start it.

Then I get these errors:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[13:19:15] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[13:19:15] INFO: MQTT available, fetching server detail ...
[13:19:15] INFO: Previous config file found, checking backup
[13:19:15] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[13:19:15] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:19:15] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:error 2021-03-05 13:19:36: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-05 13:19:36: Failed to start zigbee
Zigbee2MQTT:error 2021-03-05 13:19:36: Exiting...
Zigbee2MQTT:error 2021-03-05 13:19:36: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-05T12_19_36_026Z-debug.log
[13:19:36] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js

This is the configuration as it stands now:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: nope
  password: jerite
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2231282-if00
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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
ota: {}

This is running on core version core-2021.3.1
Supervisor version is supervisor-2021.03.4

Rebooting or reseating the USB stick does not help.

After updating to 1.18.0-1 Zigbee2mqtt does not start because: "No such image: zigbee2mqtt/zigbee2mqtt-aarch64:1.18.0-1"

Hi,

after updating to 1.18.0-1 and changing the configuration regarding ota: i get the following error when trying to start:

404 Client Error for http+docker://localhost/v1.40/containers/create?name=addon_45df7312_zigbee2mqtt: Not Found ("No such image: zigbee2mqtt/zigbee2mqtt-aarch64:1.18.0-1")

I have already restarted RaPi4.

How do I get the missing image?

Error: serial.adapter should be equal to one of the allowed values - not accepting EZSP on 1.18.1-2

Attempting to use Sonoff ZBbridge (EZSP)
stable ZIGBEE2MQTT 1.18.1-2

Core
core-2021.3.4

Supervisor
supervisor-2021.03.4

Operating System
Home Assistant OS 5.12

Error shown:

serial.adapter should be equal to one of the allowed values

Despite CONFIG.JSON mentioning ezsp as being a valid and allowed value. - what am I missing?

    "serial": {
      "port": "str",
      "disable_led": "bool?",
      "adapter": "match(^zstack|deconz|zigate|ezsp$)?"
    },

Maybe @Koenkk has to update the settings.schema.json to allow the new adapter type?

         "adapter": {
          "type": ["string", "null"],
          "enum": ["deconz", "zstack", "zigate"],

CONFIGURATION:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto:1883'
  user: <USER>
  password: <PASS>
serial:
  adapter: ezsp
  port: 'tcp://10.0.2.23:8888'
advanced:
  log_level: warn
....
....
...

LOGS:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[10:40:35] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[10:40:35] INFO: MQTT available, fetching server detail ...
[10:40:35] INFO: Previous config file found, checking backup
[10:40:35] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[10:40:36] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:40:36] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:
**- serial.adapter should be equal to one of the allowed values**
If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-14T13_40_38_565Z-debug.log
[10:40:38] INFO: Handing over control to Zigbee2mqtt Core ...

Zigbee2mqtt not starting zigbee-herdsman, SyntaxError: Unexpected token m in JSON

Description of problem:
Zigbee2mqtt simply stopped functioning and will not connect. No system updates or changes were occurring, connection just failed. I've re-flashed the firmware on the CC2531 and removed/reinstalled zigbee2mqtt, but no change. I've reset the entire system several times. This is running in a Synology VM and has worked fine for more than a month since transitioning from a Docker setup. Z-Wave Js to mqtt, Mosquitto broker, and Node Red are all still functioning properly.
Zigbee2mqtt add-on version (if edge, please report commit hash):

[email protected] start /app

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://10.0.xxx.xxx:1883'
  user: <user_id>
  password: <user_pass>
serial:
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2AC54-if00
  disable_led: false
advanced:
  log_level: debug
  log_directory: /share/log/%TIMESTAMP%
  log_file: log.txt
  log_output: file
  pan_id: 6754
  channel: 20
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  host: 10.0.xxx.xxx
  port: 8099
experimental: {}
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: true

Running platform (details from Suypervisor > System)

Core: core-2021.3.2
Supervisor: supervisor-2021.03.4
Operating System: HassOS 5.12

Your logs from Home Assistant Supervisor

> [email protected] start /app
> node index.js
Zigbee2MQTT:debug 2021-03-08 11:14:42: Loaded state from file /share/zigbee2mqtt/state.json
Zigbee2MQTT:info  2021-03-08 11:14:42: Logging to console and directory: '/share/log/2021-03-08.11-14-41' filename: log.txt
Zigbee2MQTT:debug 2021-03-08 11:14:42: Removing old log directory '/share/log/2021-03-08.11-13-11'
Zigbee2MQTT:info  2021-03-08 11:14:42: Starting Zigbee2MQTT version 1.18.1 (commit #1.18.1)
Zigbee2MQTT:info  2021-03-08 11:14:42: Starting zigbee-herdsman (0.13.71)
Zigbee2MQTT:debug 2021-03-08 11:14:43: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null},"backupPath":"/share/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","databasePath":"/share/zigbee2mqtt/database.db","network":{"channelList":[20],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2AC54-if00"}}'
Zigbee2MQTT:error 2021-03-08 11:14:43: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-08 11:14:43: Failed to start zigbee
Zigbee2MQTT:error 2021-03-08 11:14:43: Exiting...
Zigbee2MQTT:error 2021-03-08 11:14:43: SyntaxError: Unexpected token m in JSON at position 73
    at JSON.parse (<anonymous>)
    at Function.open (/app/node_modules/zigbee-herdsman/dist/controller/database.js:17:35)
    at Controller.<anonymous> (/app/node_modules/zigbee-herdsman/dist/controller/controller.js:106:48)
    at Generator.next (<anonymous>)
    at fulfilled (/app/node_modules/zigbee-herdsman/dist/controller/controller.js:24:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

generate random PAN_ID doesn't work

Description of problem:
When I want to gerenerate my pan_id I use because I switched from adapters and want to repair my network. I wanted to use
pan_id: GENERATE
As can be read from: https://www.zigbee2mqtt.io/information/configuration.html
But it is giving me an error.

Zigbee2mqtt add-on version (if edge, please report commit hash):

[email protected]

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyUSB0
advanced:
  log_level: info
  pan_id: GENERATE
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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

Running platform (details from Suypervisor > System)

core-2021.2.3
supervisor-2021.02.11
Home Assistant OS 5.12

Your logs from Home Assistant Supervisor

Failed to save addon configuration, not a valid value for dictionary value @ data['options']. Got {'data_path': '/config/zigbee2mqtt', 'external_converters': [], 'devices': 'devices.yaml', 'groups': 'groups.yaml', 'homeassistant': True, 'permit_join': True, 'mqtt': {'base_topic': 'zigbee2mqtt'}, 'serial': {'port': '/dev/ttyUSB0'}, 'advanced': {'log_level': 'info', 'pan_id': 'GENERATE', 'channel': 11, 'network_key': [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13], 'availability_blocklist': [], 'availability_passlist': []}, 'device_options'...

Cannot bind since button is greyed out

Description of problem:
@Koenkk

I created a group of 2 ikea light which I want to bind to the ikea witch (tadfri on/off) but the bind button is "greyed out". I did unbind it from the default group (went ok). But when I want to bind the switch to the group (on/off option) I can't select the blue button.

Zigbee2mqtt add-on version (if edge, please report commit hash):

Current version: 1.18.1-2

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyUSB1
advanced:
  log_level: warn
  pan_id: 6753
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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

Running platform (details from Suypervisor > System)


core-2021.3.4
supervisor-2021.03.6
Debian GNU/Linux 10 (buster)
Docker versie 20.10.5

Your logs from Home Assistant Supervisor

21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-03-21 13:43:16 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-03-21 13:45:50 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-03-21 14:06:32 INFO (MainThread) [supervisor.host.info] Updating local host information
21-03-21 14:06:32 INFO (MainThread) [supervisor.host.services] Updating service information
21-03-21 14:06:32 INFO (MainThread) [supervisor.host.network] Updating local network information
21-03-21 14:06:39 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-03-21 14:06:39 INFO (MainThread) [supervisor.host] Host information reload complete

and mqtt

Error Nothing to bind from 'Wc schakelaar' to 'Coordinator'
Error Nothing to bind

CC2358 on UART won`t talk to Z2M addon

Description of problem:
Zigbee-herdsman will not connect to adapter.
I`m not sure that this addon problem but as far as I investigate it it has to be something with socat.

I`m switching from CC2531 to CC2538 -precisely this one.
I have flashed JETHOME fw.
Used esp2866 as serial bridge (tried both ESPeasy and tasmota).

My first concern is that it does not send anything*. So I am assuming that it has to get some request from Z2M - correct me if I am wrong.
* - except ▒A▒ after pushing reset button with both FTDI/UART and ESP serial connection.
link=/share/zigbee2mqtt/Z2M - it created a file but it was empty.
link=/tmp/ttyZ2M - it have not created file.
In both cases socat was not complaining about anything.

Finally I have also to remove and re-install addon but that did not help.

Zigbee2mqtt add-on version (if edge, please report commit hash):

1.18.1-1

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.0.111:1883'
  user: mqtt
  password: XXXXXXXX
serial:
  port: /tmp/ttyZ2M
advanced:
  log_level: info
  pan_id: 6755
  channel: 11
  network_key:
X
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: true
  master: 'pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777'
  slave: 'tcp-listen:7777,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: true
zigbee_herdsman_debug: true

Below yaml config file I have tried few ports 8485, 7777 and so on - to bo honest I do not understand why You have to put port twice in config
Running platform (details from Suypervisor > System)

Core: core-2021.3.4
Supervisor: supervisor-2021.03.6
Operating System: Debian GNU/Linux 10 (buster)

Your logs from Home Assistant Supervisor
All green.

Logs from addon

Socat startup parameters:
Options:     -d -d
Master:      pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
Slave:       tcp-listen:7777,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
[20:59:46] INFO: Starting socat process ...
2021/03/21 20:59:46 socat[294] N PTY is /dev/pts/1
2021/03/21 20:59:46 socat[294] W ioctl(7, IOCTL_VM_SOCKETS_GET_LOCAL_CID, ...): Not a tty
2021/03/21 20:59:46 socat[294] N listening on AF=2 0.0.0.0:7777
> [email protected] start /app
> node index.js
Zigbee2MQTT:info  2021-03-21 20:59:49: Logging to console and directory: '/share/zigbee2mqtt/log/2021-03-21.20-59-48' filename: log.txt
Zigbee2MQTT:info  2021-03-21 20:59:49: Starting Zigbee2MQTT version 1.18.1 (commit #1.18.1)
Zigbee2MQTT:info  2021-03-21 20:59:49: Starting zigbee-herdsman (0.13.71)
2021-03-21T19:59:49.799Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2021-03-21T19:59:49.801Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6755,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/tmp/ttyZ2M"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","adapter":{"concurrent":null,"delay":null}}'
2021-03-21T19:59:49.807Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /tmp/ttyZ2M and {"baudRate":115200,"rtscts":false,"autoOpen":false}
2021-03-21T19:59:49.814Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened
2021-03-21T19:59:50.275Z zigbee-herdsman:adapter:zStack:znp:log Writing skip bootloader payload
2021-03-21T19:59:50.276Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2021-03-21T19:59:51.281Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-21T19:59:51.283Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2021-03-21T19:59:57.291Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-21T19:59:57.292Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2021-03-21T20:00:03.297Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2021-03-21T20:00:03.297Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
Zigbee2MQTT:error 2021-03-21 21:00:09: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-21 21:00:09: Failed to start zigbee
Zigbee2MQTT:error 2021-03-21 21:00:09: Exiting...
Zigbee2MQTT:error 2021-03-21 21:00:09: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-21T20_00_09_350Z-debug.log
[21:00:09] INFO: Zigbee Herdsman debug logging enabled
[21:00:09] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js

Zigbee2mqtt version 1.17.0

Is the release of this new version already planned? It needs a bump.

Where might I change the theme/coloring for the pages/tables?

Hey there,
Where might I change the theme/coloring for the pages/tables? Is that within the addon, or is that something I need to ask on the Zigbee2MQTT pages? I spent some time trying to customize the CSS using Stylus, only to realize when I refreshed the page that (presumably) because it was in an iframe that the changes don't seem to keep. It seems like I would need to change it at the source.

Thanks,
-MH

Osram outlet and Tradfri light - On/Off State not updated

Description of problem:
On/Off State is not updated until the corresponding button is clicked. This is annoying because on the home assistant interface it is also desynchronized. The outlet is currently switched on: to switch it off, I have to click On, then Off. The status can be changed with a button on the outlet that communicates directly with the socket without using zigbee. (Same problem with a tradfri light with the remote directly connected on the light.) Is there any solution to force updating every 30sec for example?

Zigbee2mqtt add-on version (if edge, please report commit hash):

> [email protected]

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: false
}

Running platform (details from Supervisor > System)

Core: core-2021.3.1
Supervisor: supervisor-2021.03.4
Operating System: HassOS 5.12

Your logs from Home Assistant Supervisor

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[18:39:11] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[18:39:12] INFO: MQTT available, fetching server detail ...
[18:39:12] INFO: MQTT server settings not configured, trying to auto-discovering ...
[18:39:13] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[18:39:13] INFO: MQTT credentials not configured, trying to auto-discovering ...
[18:39:13] INFO: Configuring'addons' mqtt user
[18:39:13] INFO: Previous config file found, checking backup
[18:39:13] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[18:39:13] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[18:39:14] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js

No Status-Update in HA Group-Bound-Switch-Action

Description of problem:

I have organized my IKEA lights into groups and tied an IKEA switch to the group. When I switch the group via HA, the status of the lights and the group changes. However, if I switch via the switch, the light is switched but the status in HA does not change.

Zigbee2mqtt add-on version (if edge, please report commit hash):

Zigbee2mqtt add-on Current version: 1.18.1-2

Running platform (details from Suypervisor > System)

core-2021.3.4
supervisor-2021.03.6
Home Assistant OS 5.12

Addon wont start because /dev/* is read only (Operation not permitted)

Description of problem:
There seem to be a problem with the combination of Supervisor & Zigbee2mqtt that causes problems with both Serial Port or Socat setup.

Creating this issue to correlate multiple issues created to try and pinpoint the best solution.

According to #24 the new Supervisor 2021.02.06 introduced new code that might cause this: home-assistant/supervisor@b8a976b

Zigbee2mqtt add-on version (if edge, please report commit hash):
n/a

Your entire configuration from the frontend (with sensitive fields redacted):
n/a

Running platform (details from Suypervisor > System)

Please make sure you post your details around Core & Supervisor & Operating System below

// Example
Core: core-2021.2.2
Supervisor: supervisor-2021.02.6
Operating System: HassOS 5.4

Related issues:
#26 #24 danielwelch/hassio-zigbee2mqtt#535

Can the addon share styles with the Home Assistant?

Hello, can't add this one as a feature request so I created an issue.

Is there any reason why zigbe2mqtt don't share the look and components with the home assistant? Isn't it more efficient and elegant? Was it considered in the past?

Thank you for the brilliant job and for the answer in advance.

Kind regards,
Przemek.

Unknown option 'initialdelay' for Zigbee2mqtt

Description of problem:
In my Home Assistant Supervisor log it has the following entry
21-03-11 16:59:20 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)

Zigbee2mqtt add-on version (if edge, please report commit hash):

1.18.1-1

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: false
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.0.3:1883'
  user: 
  password: 
serial:
  adapter: deconz
  port: /dev/ttyACM0
advanced:
  availability_timeout: 600
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

Running platform (details from Suypervisor > System)

// Example
Core: core-2021.3.3
Supervisor: supervisor-2021.03.4
Operating System: Ubuntu

Your logs from Home Assistant Supervisor

As above

Zigbee2mqtt 1.17.1

zigbee2mqtt add-on version (if edge, please report commit hash):

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:
Zigbee2mqtt 1.17.1 has been released few days ago, when this addon will be udpated?

Your entire configuration from the frontend (with sensitive fields redacted):

// replace this line with your pasted configuration

Your logs from Home Assistant

Improve PR template

zigbee2mqtt add-on version (if edge, please report commit hash):

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:

Your entire configuration from the frontend (with sensitive fields redacted):

// replace this line with your pasted configuration

Your logs from Home Assistant

Add-on doesn't start - unknown option restartdelay, initialdelay and new_api

i cant connect again BW_SPH13

Zigbee2mqtt
Current version: 1.17.1-4

21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:32:32 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'initialdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt)
21-03-07 09:33:10 WARNING (MainThread) [supervisor.addons.options] Unknown option 'restartdelay' for Zigbee2mqtt (7ad98f9c_zigbee2mqtt

Promote EZSP (PR#50) from dev to master -edge branch (for supervisor users)

No issue - just asking to promote the EZSP adapter build from dev to master (-edge) so hass.io supervisor users can also install and test. We`re unable to install a specific branch tag from home assistant .

as of now, master -edge branch is on 1.17.1-4

Zigbee2mqtt won't start after updating to 1.17.1-1

After updating to 1.17.1-1 my add-on won't start, printing this error message:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[11:45:15] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[11:45:16] INFO: MQTT available, fetching server detail ...
[11:45:16] INFO: Previous config file found, checking backup
[11:45:16] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[11:45:16] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:45:17] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:error 2021-02-12 11:45:21: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-02-12 11:45:21: Failed to start zigbee
Zigbee2MQTT:error 2021-02-12 11:45:21: Exiting...
Zigbee2MQTT:error 2021-02-12 11:45:21: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-12T10_45_21_998Z-debug.log

Core: core-2021.2.3
Home Assistant OS 5.11

Release tag validation

Add back tag vs config version validation for stable builds
Add stable build validation for base version between config and docker file

Make sure the tag done on dev branch for releasing Stable respects all required criteria:

tag corresponds to the version in zigbee2mqtt/config.json

Zigbee2mqtt HA add-on won't start after updating from 1.17.1-4 to 1.18.0-1

Description of problem:
Zigbee2mqtt HA add-on won't start after updating from 1.17.1-4 to 1.18.0-1

After today's update my add-on refused to start, I had to manually edit configuration file by adding:

ota:
  update_check_interval: 10
  disable_automatic_update_check: false

This should be done automatically during update

Cant Change Colour via Alexa on Lidle E27 bulbs

Description of problem:
Lidl E27 bulb connects fine to CC3521 USB dongle and runs on the Zigbee2 MQTT Addon in Home Assistant. I can change colour OK from Home Assistant and also Node Red but if I ask for Alexa to change the colour, it changes it on the Alexa App and the notification noise it makes to say complete but the bulb does not change colour.

Zigbee2mqtt add-on version (if edge, please report commit hash):

Current version: 1.18.1-1

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  server: 'mqtt://192.168.0.4:1883'
  user: USERNAME
  password: PASSWORD
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyACM0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
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

Running platform (details from Suypervisor > System)

supervisor-2021.03.6
core-2021.3.4
Home Assistant OS 5.12

Your logs from Home Assistant Supervisor

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[11:05:51] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[11:05:51] INFO: MQTT available, fetching server detail ...
[11:05:51] INFO: Previous config file found, checking backup
[11:05:51] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[11:05:51] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:05:52] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:error 2021-03-13 23:00:22: Publish 'set' 'brightness' to 'Living Room Lamp Bulb' failed: 'Error: Command 0x588e81fffef49b46/1 genLevelCtrl.moveToLevelWithOnOff({"level":127,"transtime":150}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
Zigbee2MQTT:error 2021-03-13 23:00:39: Publish 'set' 'color_temp' to 'Living Room Lamp Bulb' failed: 'Error: Command 0x588e81fffef49b46/1 lightingColorCtrl.moveToColorTemp({"colortemp":153,"transtime":150}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'

Failed update notification

Good evening,
I have hassio installed on an rp4 with the zigbee2mqtt addon at version 1.17.1-4, I don't get the notification of the update to 1.18.1-1.
How can I do to force the update?
I need to remove the addon and reinstall it?

My system config:
Home Assistant OS core-2021.3.1
Home Assistant OS 5.12 supervisor-2021.03.4
Docker version 19.03.13
rpi4-64

Thank you

Socat unable to create Serial Device in /dev

zigbee2mqtt add-on version (if edge, please report commit hash):

1.17.1

Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

HassOS

Description of problem:

As of 1.17, Socat is unable to create serial devices in /dev i.e. /dev/ttyZ2M:

Extract from the log: /share/zigbee2mqtt/socat.log

2021/02/10 22:06:54 socat[257] N PTY is /dev/pts/0
2021/02/10 22:06:54 socat[257] E unlink("/dev/ttyZ2M"): Read-only file system
2021/02/10 22:06:54 socat[257] N exit(1)

NOTE: Creating the device in /tmp works. But the default configuration uses /dev.

Your entire configuration from the frontend (with sensitive fields redacted):

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server:  [REDACTED]
  user:  [REDACTED]
  password:  [REDACTED]
serial:
  port: /dev/ttyZ2M
advanced:
  log_level: info
  pan_id: [REDACTED]
  channel: 11
  network_key:
     [REDACTED]
  availability_blocklist: []
  availability_passlist: []
  rtscts: false
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: true
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp4:[REDACTED]:8485,ignoreeof'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: true

Your logs from Home Assistant

N/A

Addon does not want to run because can't create './node_modules/zigbee-herdsman-converters/devices.js'

config:

zigbee_shepherd_devices: true

log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[07:17:15] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[07:17:16] INFO: MQTT available, fetching server detail ...
[07:17:16] INFO: Previous config file found, checking backup
[07:17:16] INFO: Creating backup config in '/share/zigbee2mqtt/.configuration.yaml.bk'
[07:17:17] INFO: File devices.js found, copying to ./node_modules/zigbee-herdsman-converters/
cp: can't create './node_modules/zigbee-herdsman-converters/devices.js': No such file or directory
[cont-init.d] zigbee2mqtt.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Where should the directory be?
Thank you for your help
Marek

zigbee2mqtt / hassio-zigbee2mqtt Goto Github PK

hassio-zigbee2mqtt's Introduction

Official Zigbee2MQTT Home Assistant addon

Installation

Restoring data from a standalone installation

Changelog

Issues

Testing changes locally

Credits

hassio-zigbee2mqtt's People

Contributors

Stargazers

Watchers

Forkers

hassio-zigbee2mqtt's Issues

Recommend Projects

Recommend Topics

Recommend Org