Zigbee2MQTT installation via openhabian-config not working on bookworm?

Setup, Configuration and Use Migration
1

All,
I have been running OH4.3 on bullseye using Zigbee2MQTT without problems.
After I moved my system to bookworm (fresh installation), I tried several times to install Zigbee2MQTT with the menu in openhabian-config but without success. The installation went through, but the interface under :8081 never came up and the server did not start.

Doing a manual installation as described here solved the problem.

Please check

2

please give me more details:

  • was your first try interrupted somehow?
  • did you install mqtt with openhabian?
  • did you install anything manually before z2m
  • did you remove z2m via menu before retrying?

The background is that if there are certain leftovers of failed installations we don’t overwrite for safety reasons. So it might be necessary (in some edge cases) to delete /opt/zigbee2mqtt manually before retrying. But of course the straight forward way should always work.

3
  • was your first try interrupted somehow?
    NO
  • did you install mqtt with openhabian?
    Yes, was installed up and running
  • did you install anything manually before z2m
    NO
  • did you remove z2m via menu before retrying?
    YES
4

ok, thanks. I’ll have a look at it.

5

I did a fresh install in this order:

  • Flash sd with raspberry imager:
    – OS - Other specific-purpose OS - Home assistants - openhab - openhabian - 64bit
  • Prepare the Pi
    – network attached to raspberry by cable
    – zigbee-stick in usb
  • let raspberry start and wait like 20min
  • finish setup with browser
  • ssh to raspberry
  • openhabian-config
    – install mosquitto (remember password)
    – install zigbee2mqtt

Result: Everything works as expected and zigbee2mqtt starts nicely.
So there’s nothing I can do without a log (loglevel: maximium).
Btw: I didn’t succeed to install via Wifi. @ndye : Maybe you could check this too? I tried several times but no access point from comitup was showing up.

6

Interesting, I’ll try to look into it. Its probably some change made upstream that we haven’t accounted for yet.

7

Please provide your first-boot.log with debuglevel=maximum.
Comitup should fire up when Internet cannot be reached.
If it didn’t, you will find hints as to why not yourself.

8

tried again and now comitup came up. Think it was my fault with default settings in raspberry imager.

I prepared the fix to stay on v1.42.0 during install or update. I’ll start the PR in a minute

edit: PR is running