describe the problem in Detail. What do you expect to happen ? What does happen ?
When installing the adapter as zigbee.0, the Admin interface strictly loads the old legacy Materialize UI (gray layout, old labels like CC2531).
When installing a second instance (zigbee.1), the modern React UI (blue layout, full features) is correctly loaded for .1. However, the React UI suppresses the menu entry for zigbee.0 completely, making it impossible to access the .0 instance from the left sidebar.
To Reproduce:
Install ioBroker.zigbee v3.5.5 as zigbee.0.
Open the Admin UI -> shows legacy Materialize UI.
Add a second instance zigbee.1.
Open the Admin UI -> zigbee.1 shows the modern React UI. The menu entry for zigbee.0 disappears.
Expected behavior:
zigbee.0 should load the modern React UI just like any other instance.
Environment:
JS-Controller version: 7.2.2
Node version: v22.23.2
Additional context:
Checking the system.adapter.zigbee.x objects confirms that both instances have identical UI parameters ("adminUI": { "config": "materialize", "tab": "materialize" }), yet they are rendered completely differently by the Admin adapter. Clearing browser caches, incognito mode, or iobroker fix do not resolve the fallback behavior of instance 0.
Adapter version
3.5.5
Coordinator firmware version
(Ember ZNet 8.0.2)
Coordinator
Sonoff Zigbee 3.0 Dongle Plus MG24 (Ember ZNet 8.0.2)
Setup
Debian/Linux (Raspberry Pi 5)
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response
describe the problem in Detail. What do you expect to happen ? What does happen ?
When installing the adapter as zigbee.0, the Admin interface strictly loads the old legacy Materialize UI (gray layout, old labels like CC2531).
When installing a second instance (zigbee.1), the modern React UI (blue layout, full features) is correctly loaded for .1. However, the React UI suppresses the menu entry for zigbee.0 completely, making it impossible to access the .0 instance from the left sidebar.
To Reproduce:
Expected behavior:
zigbee.0 should load the modern React UI just like any other instance.
Environment:
Additional context:
Checking the system.adapter.zigbee.x objects confirms that both instances have identical UI parameters ("adminUI": { "config": "materialize", "tab": "materialize" }), yet they are rendered completely differently by the Admin adapter. Clearing browser caches, incognito mode, or iobroker fix do not resolve the fallback behavior of instance 0.
Adapter version
3.5.5
Coordinator firmware version
(Ember ZNet 8.0.2)
Coordinator
Sonoff Zigbee 3.0 Dongle Plus MG24 (Ember ZNet 8.0.2)
Setup
Debian/Linux (Raspberry Pi 5)
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response