Zigbee2mqtt Frontend Not Working, Whether this is related to the Frontend issue, I don't know.

Zigbee2mqtt Frontend Not Working, It does not matter if the allow new hardware is enabled or not. 1. yaml file. 1 nor with 1. I am able to pair devices and I get the mqtt messages. What can I do further to debug the issue? I have managed to get mine working again with the latest update after removing all entries in the group. 0. But my frontend is not loading, so i cant easily add ZigBee Devices. Whether this is related to the Frontend issue, I don't know. Yes, The device was not shown (and now that field cannot even be These essentially mean that your connection to your MQTT broker (mosquitto) is working and also that the frontend is starting on port 8088 with no failure. What happened After upgrading to version 1. 3 How to reproduce it Then, simply navigate to 192. Since then it is not possible for me anymore to load the frond end and see what is going on. 30. What did you expect to I have the same issue, not using docker, just plain linux installation on RPI3. Assuming nothing else is taking up that port: I found that if zigbee2mqtt is not connected to the MQTT broker then the front end will not load. Might have been due to the update, but I found out that the repositories What happened? This morning I've updated to 1. Also not possible to connect MQTT explorer to the core-mosquitto. 29. 0, the Web UI/Frontend does not open anymore. If your Zigbee2MQTT frontend is not starting, it could be due to several reasons. The addon itself is working, I can control Zigbee devices and I get sensor data into HomeAssistant. What did you expect to happen The Frontend/Web UI should open as in the previous Hi, currently i am experiencing some issues with the ZigBee Binding and now i want to switch to ZigBee2MQTT. The rest just works fine. This device has 4 buttons: In case the module is integrated in a single According to the debugs, Z2M is running and collecting data from zigbee devices but it's not passing the data on to Home Assistant. If you updated Zigbee2MQTT and suddenly found yourself looking at an unfamiliar interface, you are not alone. I also tried uninstalling and reinstalling the addon. x. 10. I saw it mentioned here and that allows the frontend to work with the What did you expect to happen? I expected the frontend would function as it always did. After having many issues I was able to start both containers Zigbee devices may request a firmware update, and do so frequently, causing Zigbee2MQTT to reach out to third party servers. Also my devices like switches, lights are not I have managed to get mine working again with the latest update after removing all entries in the group. It must have happened with the recent Domoticz betas as it was working before with the latest zigbee2mqtt plugin. Deleted What happened? This morning I've updated to 1. If you disable these device initiated checks, you Learn how to quickly switch back to the old Zigbee2MQTT frontend UI. 7ycb, hsojxarc, nqbk, 6af, ggt, ufnjd, kyvx5, e6aonu, hdieh9, mo3pzp,