Well, I guess just running the update.sh doesn't work at all:

Okt 15 22:43:47 homebox systemd[1]: Started Zigbee2mqtt Service.
Okt 15 22:43:47 homebox zigbee2mqtt[22887]: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Okt 15 22:43:47 homebox zigbee2mqtt[22887]:             READ THIS CAREFULLY
Okt 15 22:43:47 homebox zigbee2mqtt[22887]: Refusing to start because configuration is not valid, found the following errors:
Okt 15 22:43:47 homebox zigbee2mqtt[22887]: - Function yaml.safeLoad is removed in js-yaml 4. Use yaml.load instead, which is now safe by default.
Okt 15 22:43:47 homebox zigbee2mqtt[22887]: If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html
Okt 15 22:43:47 homebox zigbee2mqtt[22887]: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

And it looks like it's a really creative error handling - just assume that there is a config mistake if the loading throws an exception 😀

Anyone using zigbee2mqtt within a docker container? I really don't like docker, but it looks like I have too many zigbee devices now that aren't supported on 1.16 😅 But starting the container fails for me:

Okt 19 19:11:53 homebox 5b244dcbf027[33641]: /usr/local/bin/docker-entrypoint.sh: exec: line 17: illegal option --

Basically i do this:

{ config, pkgs, lib, ... }:
let
  unstablePkgs = import <nixos-unstable> { };
  hass = (unstablePkgs.home-assistant.overrideAttrs
    (oldAttrs: { doCheck = false; }));
in {

  services.home-assistant = {
    package = hass;
    enable = true;
    port = 8123;
    openFirewall = true;
    configWritable = true;
  };
}

In reply to @jeroen:simonetti.nl
However, it still does a pytestCheckPhase which takes ages.