Zigbee2Mqtt control panel not loading [solved] Topic is solved

[Varazir]

Hello,

After I added a IKEA sensor I can't access the control panel.

just stands like this


I get this in the log

Code: Select all

2020-06-25 14:39:19.008 (zigbee2mqtt) Debug logging mask set to: PYTHON PLUGIN DEVICE CONNECTION MESSAGE
2020-06-25 14:39:19.008 (zigbee2mqtt) onStart called
2020-06-25 14:39:19.008 (zigbee2mqtt) Installing plugin custom page...
2020-06-25 14:39:19.009 (zigbee2mqtt) Copying files from /home/pi/domoticz/plugins/zigbee2mqtt/frontend to /home/pi/domoticz/www/templates
2020-06-25 14:39:19.054 (zigbee2mqtt) Installing plugin custom page completed.
2020-06-25 14:39:19.055 (zigbee2mqtt) MqttClient::__init__
2020-06-25 14:39:19.055 (zigbee2mqtt) MqttClient::open
2020-06-25 14:39:19.055 (zigbee2mqtt) Creating device 'Zigbee2MQTT API Transport'.
2020-06-25 14:39:19.059 (zigbee2mqtt) Debug logging mask set to: PYTHON
2020-06-25 14:39:19.059 (zigbee2mqtt) onStart called
2020-06-25 14:39:19.059 (zigbee2mqtt) Installing plugin custom page...
2020-06-25 14:39:19.060 (zigbee2mqtt) Copying files from /home/pi/domoticz/plugins/zigbee2mqtt/frontend to /home/pi/domoticz/www/templates
2020-06-25 14:39:19.120 (zigbee2mqtt) Installing plugin custom page completed.
2020-06-25 14:39:19.120 (zigbee2mqtt) MqttClient::__init__
2020-06-25 14:39:19.121 (zigbee2mqtt) MqttClient::open
2020-06-25 14:39:19.121 (zigbee2mqtt) Protocol set to: 'MQTT'.
2020-06-25 14:39:19.121 (zigbee2mqtt) Transport set to: 'TCP/IP', 127.0.0.1:1883.
2020-06-25 14:39:19.122 (zigbee2mqtt) Connect directive received, action initiated successfully.
2020-06-25 14:39:19.173 (zigbee2mqtt) onConnect called
2020-06-25 14:39:19.173 (zigbee2mqtt) Connected to MQTT Server: 127.0.0.1:1883
2020-06-25 14:39:19.173 (zigbee2mqtt) MQTT CLIENT ID: 'Domoticz_1593088759_7623'
2020-06-25 14:39:19.173 (zigbee2mqtt) onConnect called
2020-06-25 14:39:19.173 (zigbee2mqtt) Connected to MQTT Server: 127.0.0.1:1883
2020-06-25 14:39:19.173 (zigbee2mqtt) MQTT CLIENT ID: 'Domoticz_1593088759_7207'
2020-06-25 14:39:19.173 (zigbee2mqtt) Sending 38 bytes of data
2020-06-25 14:39:19.173 (zigbee2mqtt) 10 24 00 04 4d 51 54 54 04 02 00 3c 00 18 44 6f 6d 6f 74 69 .$..MQTT...<..Domoti
2020-06-25 14:39:19.174 (zigbee2mqtt) 63 7a 5f 31 35 39 33 30 38 38 37 35 39 5f 37 36 32 33 .. .. cz_1593088759_7623
2020-06-25 14:39:19.224 (zigbee2mqtt) Received 4 bytes of data
2020-06-25 14:39:19.224 (zigbee2mqtt) 20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2020-06-25 14:39:19.225 (zigbee2mqtt) MqttClient::subscribe
2020-06-25 14:39:19.225 (zigbee2mqtt) MqttClient::subscribe
2020-06-25 14:39:19.225 (zigbee2mqtt) Sending 27 bytes of data
2020-06-25 14:39:19.225 (zigbee2mqtt) 82 19 00 01 00 14 7a 69 67 62 65 65 32 6d 71 74 74 2f 62 72 ®....zigbee2mqtt/br
2020-06-25 14:39:19.225 (zigbee2mqtt) 69 64 67 65 2f 23 00 .. .. .. .. .. .. .. .. .. .. .. .. .. idge/#.
2020-06-25 14:39:19.276 (zigbee2mqtt) Received 5 bytes of data
2020-06-25 14:39:19.276 (zigbee2mqtt) 90 03 00 01 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю...
2020-06-25 14:39:19.276 (zigbee2mqtt) Received 35 bytes of data
2020-06-25 14:39:19.276 (zigbee2mqtt) 31 21 00 18 7a 69 67 62 65 65 32 6d 71 74 74 2f 62 72 69 64 1!..zigbee2mqtt/brid
2020-06-25 14:39:19.276 (zigbee2mqtt) 67 65 2f 73 74 61 74 65 6f 66 66 6c 69 6e 65 .. .. .. .. .. ge/stateoffline
2020-06-25 14:39:19.276 (zigbee2mqtt) Received 238 bytes of data
2020-06-25 14:39:19.277 (zigbee2mqtt) 31 eb 01 00 19 7a 69 67 62 65 65 32 6d 71 74 74 2f 62 72 69 1뮮.zigbee2mqtt/bri
2020-06-25 14:39:19.277 (zigbee2mqtt) 64 67 65 2f 63 6f 6e 66 69 67 7b 22 76 65 72 73 69 6f 6e 22 dge/config{"version"
2020-06-25 14:39:19.277 (zigbee2mqtt) 3a 22 31 2e 31 34 2e 30 22 2c 22 63 6f 6d 6d 69 74 22 3a 22 :"1.14.0","commit":"
2020-06-25 14:39:19.277 (zigbee2mqtt) 39 30 30 39 64 65 32 22 2c 22 63 6f 6f 72 64 69 6e 61 74 6f 9009de2","coordinato
2020-06-25 14:39:19.277 (zigbee2mqtt) 72 22 3a 7b 22 74 79 70 65 22 3a 22 7a 53 74 61 63 6b 31 32 r":{"type":"zStack12
2020-06-25 14:39:19.277 (zigbee2mqtt) 22 2c 22 6d 65 74 61 22 3a 7b 22 74 72 61 6e 73 70 6f 72 74 ","meta":{"transport
2020-06-25 14:39:19.277 (zigbee2mqtt) 72 65 76 22 3a 32 2c 22 70 72 6f 64 75 63 74 22 3a 30 2c 22 rev":2,"product":0,"
2020-06-25 14:39:19.277 (zigbee2mqtt) 6d 61 6a 6f 72 72 65 6c 22 3a 32 2c 22 6d 69 6e 6f 72 72 65 majorrel":2,"minorre
2020-06-25 14:39:19.277 (zigbee2mqtt) 6c 22 3a 36 2c 22 6d 61 69 6e 74 72 65 6c 22 3a 33 2c 22 72 l":6,"maintrel":3,"r
2020-06-25 14:39:19.277 (zigbee2mqtt) 65 76 69 73 69 6f 6e 22 3a 32 30 31 39 30 34 32 35 7d 7d 2c evision":20190425}},
2020-06-25 14:39:19.277 (zigbee2mqtt) 22 6c 6f 67 5f 6c 65 76 65 6c 22 3a 22 69 6e 66 6f 22 2c 22 "log_level":"info","
2020-06-25 14:39:19.277 (zigbee2mqtt) 70 65 72 6d 69 74 5f 6a 6f 69 6e 22 3a 74 72 75 65 7d .. .. permit_join":true}
2020-06-25 14:39:19.278 (zigbee2mqtt) onMQTTSubscribed
2020-06-25 14:39:19.278 (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/state offline
2020-06-25 14:39:19.278 (zigbee2mqtt) Zigbee2mqtt bridge is offline
2020-06-25 14:39:19.279 (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/config {'version': '1.14.0', 'commit': '9009de2', 'coordinator': {'type': 'zStack12', 'meta': {'transportrev': 2, 'product': 0, 'majorrel': 2, 'minorrel': 6, 'maintrel': 3, 'revision': 20190425}}, 'log_level': 'info', 'permit_join': True}
2020-06-25 14:39:19.279 (zigbee2mqtt) Zigbee2mqtt log level is info
2020-06-25 14:39:19.279 (zigbee2mqtt) Joining new devices is enabled on the zigbee bridge
2020-06-25 14:39:19.279 (zigbee2mqtt) onMQTTSubscribed
2020-06-25 14:39:19.280 (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/state offline
2020-06-25 14:39:19.280 (zigbee2mqtt) Zigbee2mqtt bridge is offline
2020-06-25 14:39:19.280 (zigbee2mqtt) MQTT message: zigbee2mqtt/bridge/config {'version': '1.14.0', 'commit': '9009de2', 'coordinator': {'type': 'zStack12', 'meta': {'transportrev': 2, 'product': 0, 'majorrel': 2, 'minorrel': 6, 'maintrel': 3, 'revision': 20190425}}, 'log_level': 'info', 'permit_join': True}
2020-06-25 14:39:19.280 (zigbee2mqtt) Zigbee2mqtt log level is info
2020-06-25 14:39:19.280 (zigbee2mqtt) Joining new devices is enabled on the zigbee bridge
2020-06-25 14:39:19.055 Error: (zigbee2mqtt) Device creation failed, Domoticz settings prevent accepting new devices.
2020-06-25 14:39:19.121 Error: (zigbee2mqtt) Device creation failed, Domoticz settings prevent accepting new devices.

I have restarted the RPI,
Updated files from github both Zigbee2Mqtt and the plugin
Restarted the domoticz service.
Restarted the Zigbee2Mqtt service
Disabled en enabled the plugin in the hardware page
Tested in another browser

Solved by

To make the Zigbee plugin menu work again, you need to set the api_transport device created in the devices menu to used.

and

Thanks it's working when api_transport was added. Just a note... you can rename device and add $ to beginning to hide it and it will still work.

[Doler]

Do as the last lines suggest: change the setting for accepting new devices.

[Varazir]

Do as the last lines suggest: change the setting for accepting new devices.

Yes but to do that I need to access the the controllpanel to do that.

[Varazir]

I enabled the add new hardware in the global settings and now its' working agian

[Doler]

That's what I meant, sorry for the confusion. Glad that it's working for you now.

[Frankm]

Hi,

I got the same problem, but where can i find the global settings?

Kind regards Frank

[claude2666]

Same here. I cannot access the zigbee2mqtt control panel anymore, and this both in my test setup and Prod environment.

It must have happened with the recent Domoticz betas as it was working before with the latest zigbee2mqtt plugin.
It does not matter if the allow new hardware is enabled or not. The menu does not load.

I need to access the zigbee2mqtt plugin configuration to remove some devices

Anybody has any idea where this configuration is stored?

[EddyG]

Just enable the GUI in zigbee2mqtt by adding to configuration.yaml

Code: Select all

frontend:
  port: 8081

Watch the indent!
Restart zigbee2mqtt.service and there is a GUI on port 8081 of that machine.
You can do everything in that GUI and don't need Domoticz.

[claude2666]

Sure, my zigbee2mqtt control panel works on my Zigbee vm, but I am referring to the custom menu of the zigbee2mqtt plugin creates in Domoticz.
If a zigbee2mqtt plugin device was removed from the devices, re-creation will fail until the configuration is updated in the zigbee2mqtt plugin configuration menu

And loading failure started in the recent betas.

[EddyG]

But it might be that if you remove the devices in the zigbee2mqtt GUI that you wanted to remove, it might work again.
At least you got your devices removed.
Ctrl-F5 in the browser?

[claude2666]

Ctrl-F5 has been tried, clear browser data, 3 different browsers...no success.

The zigbee2mqtt now keep internal configuration, and if a device in domoticz is deleted, you need to delete it also from the zigbee2matt plugin configuration. Removing it in the zigbee control panel does not work as the device has the same id, so adding fails.
Since it is in my test environment, I just deleted the plugin, the zigbee devices , restarted and added the plugin again, Devices are there now.

But the main fact is that the zigbee2mqtt custom menu does not work anymore. (could be related to recent updates that also broke some themes?)

[claude2666]

And the same behaviour with the machinon-beta theme, where in the settings menu, the theme menu does not load.

[waltervl]

Last option to try: use private mode of the browser.

[claude2666]

Just tried in Firefox private mode and chrome incognito mode. Fails to load.

[waltervl]

There should be a zigbee2mqtt.html file (or similar naming) in domoticz/www/templates. That is the custom menu file that should be loading.
When the zigbee2mqtt menu page is open you could press F12 to get the browser debugger and see what errors popup there. Could be a naming issue somewhere.

[EddyG]

And that zigbee2mqtt.html file is copied from domoticz/plugins/zigbee2mqtt/frontend or what ever the 'zigbee2mqtt' dir is.
Are they the same? Otherwise delete the plugin dir and reinstall the plugin, then you should have a 'fresh' copy of the original file.

[claude2666]

t was working with Domoticz build 13703, From build 13704 onwards the problem started. So change between 13703 and 13704 caused the control panel load problem.

[claude2666]

To make the Zigbee plugin menu work again, you need to set the api_transport device created in the devices menu to used.

[EddyG]

Nice find. That's is one of the reasons that I dislike the new zigbee2mqtt plugin. Creating a device for the wrong reason. One of the fields on that device is misused. Should have been a variable if you go that way.

[Frankm]

thx, it's working at my side.