bobslaede
commented
5 days ago I got the same issue
Open ov1d1u opened 5 days ago
bobslaede
commented
5 days ago I got the same issue
ov1d1u
commented
5 days ago For me it was the groups:
'1':
friendly_name: living_lamp
retain: false
devices:
- 0x2c1165fffeb96125/1
- 0x2c1165fffed484d8/1
'2':
friendly_name: desk_lamp
retain: false
devices:
- 0x00124b001b79a492/1
'901':
friendly_name: default_bind_group
retain: false
devices: []
'65289':
friendly_name: living_remote_lamp
retain: false
devices:
- 0xbc33acfffe0f09a9/1
- 0x2c1165fffeb96125/1
- 0x2c1165fffed484d8/1
'65290':
friendly_name: fluffy_bed
retain: false
devices:
- 0xa4c1389782d8b904/1I removed the one under '65289' and everything started. Not sure how and why this impacted the startup.
So this seems it was not an addon issue, but I'm leaving this open until we find the root cause and create an issue on the right repository.
bobslaede
commented
5 days ago I dont have a group with those high IDs. I have up to 11 groups
ov1d1u
commented
5 days ago I don't think the high ID number was the issue. I had to recreate the group (because it was appearing in the UI but I could not delete it) with empty devices array and Zigbee2MQTT was still booting, so probably the issue lies somewhere regarding devices in a group.
bobslaede
commented
4 days ago I removed the contents of my groups.yaml file, and restartet zigbee2mqtt. It now starts the frontend, and I will recreate the groups.
Renaming them gives errors, but doing it anyways, and restarting seems to make it work.
Description of the issue
Since upgrading to 1.39.0-1 I cannot access Zigbee2MQTT's frontend, getting "502: Bad Gateway" instead. Other addon frontends are accessible via ingress. There's nothing interesting in logs either:
[09:16:27] INFO: Preparing to start... [09:16:28] INFO: Socat not enabled [09:16:28] INFO: Enabled Zigbee2MQTT watchdog with value 'default' [09:16:28] INFO: Starting Zigbee2MQTT... Starting Zigbee2MQTT with watchdog (60000,300000,900000,1800000,3600000).
This is my configuration file:
And this is the add-on configuration:
I also tried uninstalling and reinstalling the addon. The addon itself is working, I can control Zigbee devices and I get sensor data into HomeAssistant. What can I do further to debug the issue?
edit: comparing with the logs from the edge version I already had installed, I see that in the logs there should be a line
Started frontend on port 8099, so the frontend is clearly not starting. Any reason for that?Thanks.
Addon version
1.39.0-1
Platform
Core 2024.6.4 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240610.1
Logs of the issue (if applicable)