# OH5 Upgrade, MQTT and all things broken

**URL:** <https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723>\
**Category:** Off-Topic\
**Created:** [October 19, 2026, 4:09pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723 "2026-10-19T16:09:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![james\_2\_roberts](https://community.openhab.org/user_avatar/community.openhab.org/james_2_roberts/32/39585_2.png) [@james\_2\_roberts](https://community.openhab.org/u/james_2_roberts)\
**Post date:** [October 19, 2026, 4:09pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/1 "2026-10-19T16:09:56Z")

</div>

Hi there,

After many years stuck on 4.3.2, I’ve prep’d, backed up etc over the weekend and hit the upgrade button this evening.

Seemed to go ok, except for MQTT, particularly those created with the home assistant prefix. Those created directly before are all working fine, but the HA ones don’t.

I’ve got a load of new things to create, all HA MQTT things, which are duplicates that I’ll need to replace.

The problem is, none of the things have any details, it just show up blank, example non-MQTT thing:

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/a/2a035617397feba44811d1a75ed7c46d666843d2.png)

I’ve spent the last hour or more searching posts, and can’t find anything that helps. ☹

Cheers

James

---

<div class="post-metadata">

**Author:** ![james\_2\_roberts](https://community.openhab.org/user_avatar/community.openhab.org/james_2_roberts/32/39585_2.png) [@james\_2\_roberts](https://community.openhab.org/u/james_2_roberts)\
**Post date:** [October 19, 2026, 4:30pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/2 "2026-10-19T16:30:15Z")

</div>

A bit more info as I remember how to grab pertinent details:

```auto
## Release = Debian GNU/Linux forky/sid
## Kernel = Linux 6.1.0-12-amd64

```

openhabian-config gives me the following warning, which is odd as openhabian was used for the upgrade:

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/a/3/a31d341e9359ca096da2d5dfa084f905e5657ef4.png)

```auto
openHABian Configuration Tool — [openHAB]{2026-09-21T20:08:56+02:00}(167a271d)
openHAB 5.2.3 - Release Build     

```

There’s a way of getting OH status info - I’ll try and find it…

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [October 19, 2026, 4:49pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/3 "2026-10-19T16:49:30Z")

</div>

One thing to note is that the HA Mqtt was moved to a separate binding sometime between oh4 an 5. Is that installed?

---

<div class="post-metadata">

**Author:** ![james\_2\_roberts](https://community.openhab.org/user_avatar/community.openhab.org/james_2_roberts/32/39585_2.png) [@james\_2\_roberts](https://community.openhab.org/u/james_2_roberts)\
**Post date:** [October 19, 2026, 5:05pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/4 "2026-10-19T17:05:17Z")

</div>

OK, I’ve narrowed it down to zigbee2mqtt failing to start:

```auto
 zigbee2mqtt.service - Zigbee2MQTT
     Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2026-10-19 17:33:00 BST; 19min ago
   Duration: 5ms
    Process: 3855 ExecStart=/usr/bin/npm start (code=exited, status=203/EXEC)
   Main PID: 3855 (code=exited, status=203/EXEC)
        CPU: 2ms

Oct 19 17:33:00 openhabian systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 5.
Oct 19 17:33:00 openhabian systemd[1]: Stopped zigbee2mqtt.service - Zigbee2MQTT.
Oct 19 17:33:00 openhabian systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Oct 19 17:33:00 openhabian systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Oct 19 17:33:00 openhabian systemd[1]: Failed to start zigbee2mqtt.service - Zigbee2MQTT.

```

Nothing appears in the logfile, so don’t have anything further to go on…looks to be the main problem right now… other non-zigbee devices/automations are working

---

<div class="post-metadata">

**Author:** ![Larsen](https://community.openhab.org/user_avatar/community.openhab.org/larsen/32/95475_2.png) [@Larsen](https://community.openhab.org/u/Larsen)\
**Post date:** [October 19, 2026, 6:07pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/5 "2026-10-19T18:07:25Z")

</div>

what du you see when you enter  
systemctl status zigbee2mqtt  
Which version of z2m are you running? If i remember correctly there was something breaking when running an older version of nodejs.

---

<div class="post-metadata">

**Author:** ![james\_2\_roberts](https://community.openhab.org/user_avatar/community.openhab.org/james_2_roberts/32/39585_2.png) [@james\_2\_roberts](https://community.openhab.org/u/james_2_roberts)\
**Post date:** [October 19, 2026, 7:07pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/6 "2026-10-19T19:07:45Z")

</div>

thanks Larsen, upgrade of nodejs has fixed the starting of Z2M.

Now I’m just left with the broken Home Assistant binding - I think, it seems to be triggering repeated brightness chages to any Innr zigbee bulbs…

---

<div class="post-metadata">

**Author:** ![james\_2\_roberts](https://community.openhab.org/user_avatar/community.openhab.org/james_2_roberts/32/39585_2.png) [@james\_2\_roberts](https://community.openhab.org/u/james_2_roberts)\
**Post date:** [October 19, 2026, 7:44pm UTC](https://community.openhab.org/t/oh5-upgrade-mqtt-and-all-things-broken/170723/7 "2026-10-19T19:44:08Z")

</div>

Looks like a “leave it long enough” problem. mostly seems to be good now…
