Failed to call 'Frontend' #25715
Comments
|
According to the debugs, Z2M is running and collecting data from zigbee devices but it's not passing the data on to Home Assistant. Whether this is related to the Frontend issue, I don't know. |
|
I have the same issue, Z2M add-on is running and connected to my Zigstar, but frontend fails to load and it is not possible to access any Zigbee devices in HA. |
|
Could you provide the debug log of this? See this on how to enable debug logging. |
…operties of undefined (reading 'close')` #25715
|
Could you provide the debug log directly from starting z2m? |
|
I could’ve sworn those logs included that info. Unfortunately I don’t have access to the logs anymore as I restored to a backup then ended up installing the Z2M Edge version of the Home Assistant Add On. Happily for me, this fixed the issue but the logs are long gone now |
|
I can install 2.0 again and add full debug log later today if that helps? |
|
I have the same issue right now and zigbee2mqtt won't enable debug logs but keeps at the defaults as it seems 😒 I'll try to create debug logs later. |
|
After enabling debug in |
|
Same issue on my updated z2m install. So, no zigbee works in my homeassistant currently :( |
|
to me this started to happen after fw update on tube-zb-gw-cc2652p2-v2 (2023 -> 2024 fw versions).. I updated because some of the buttons stopped sending action even when using legacy.. Some buttons was working, others didnt. |
|
ok, I found the reason.. don't know how and why but the config server location in configuration.yaml for z2m has changed to mqtt://core-mosquitto:1883.. don't know what caused it as I certainly haven't changed that.. but it should be mqtt://localhost:1883 |
|
I finally managed to start my broken zigbee2mqtt addon again. @Koenkk Can it be that the frontend cannot start with some specific database entries after the recent update? My now removed entries in the db: And here my full database.db Could it be something with the cluster problem that was noted here? At least in my log from above I found some frameparser errors of it: |
|
@mcneilc can you try removing the entries of your zigbee database.db device by device and look when/if the z2m frontend starts again? (backup your original database somewhere before) Possibly you also have a device type in your database that prevents the frontend from starting like in my case the Popp thermostats, mentioned in the above comment. |
|
Hi Folks, What I noticed? In the same time, when the problems started, this device switched to mounting state (M on device) and lost connection. |
|
@dommolHA Oh nice, at your setup it works with the 3 other Danfoss thermostats, though? So only one of the 4 devices caused z2m to break? |
|
@manuelkue yes, it works with these 3 Danfoss thermostats I wasn't able to find differences, these database-entries look similar for me:
EDIT: into row with data with "id":26 - without success, FE doesn't start. |
|
@dommolHA do you probably use a ConBee adapter as well? E.g. a ConBee II / III?
Do you mean by that, when you just add the Temporary fix: |
|
@manuelkue ConBee II, SLZB-06 is waiting for replacement...
I replaced "ieeeAddr" too. One more thing about these 3 devices - I was able to start FE, but not able to set temperature, gauges were greyed out. I fixed it by removing all of these devices and re-pairing. FE doesn't crash after restarts. |
|
I'm also experiencing the same issue but with Hive UK7004240 TRV`s which also show as Danfoss in the database.db. I currently run 2 Zigbee2MQTT instances, one running the HA addon and one running via docker in unraid, both using UZG-1. The valves were originally on the addon instance a couple of weeks ago which refused to start after rebooting the Pi4 HA is running on. I removed all the valves from that instance and paired them with the one on unraid just to get the heating running again. I manually edited the database.db to remove the valves and the HA addon started without issue and I though "wierd, but ok". The unraid instance had been running fine, even surviving a few restarts due to backups and OS updates. Then last night that instance crashed and refused to start up. I removed them from the database.db and re-paired them last night and they all seemed to work fine after that, then this morning I tried restarting Zigbee2MQTT and it once again hung on startup. Rolled back to 1.42.0 and everything started up fine. @Koenkk if you still need debug logs I should be able to supply them tomorrow assuming my house survives storm Éowyn and we still have power. |
The SLZB-07p7 arrived, I re-paired all devices including the TRVs and restarted the server multiple times since then. So far, no z2m- crashes happened since the coordinator replacement 🤷♂️ |
I ended up moving to Z2M Edge which worked first time so I don't have any logs to provide. Very interesting that it's been narrowed down to Danfoss TRVs as I've got about 12 Hive TRVs plus the Hive thermostat and boiler control which to my knowledge are just the same as Danfoss. Whatever the issue was/ is, it's went away in Edge |
|
I have the same issue with Danfoss Ally TRV. Lots of frameparser errors and no frontend. However, in my case the frontend would not be accessible immediately, but somehow it became accessible after 1 day or so. Really strange. Moved Z2M Edge, the frontend is immediately available after a restart, but the frameparser errors persist, and the entities are unavailable in home assistant
|
|
Same problem for me with lots of errors, no frontend, and no communication with HA or node-red. Also just paired four Danfoss Ally TRVs, but I have a SLZB-06. So the issues doesn't appear to be linked to the coordinator from what others have said. Everything runs as normal when the TRVs are removed from my db. |
|
Removed my 10 Danfoss Ally TRVs from the database.db and frontend runs now again. Seems like it stopped during the backup this night. |
|
SLZB-06M here, same issue. |
|
At least for me the issues was fixed by updating to latest-dev. I guess the fix by @Koenkk helped. |
|
Should be fixed in z2m 2.1.0 indeed! |
Have updated to 2.1.0 and looking great so far. Many thanks! |
log.log
What happened?
Restarted previously working Zigbee2MWTT add on in Home Assistant. Z2M either halts on the error message below or hard crashes
What did you expect to happen?
Z2M to load up without errors
How to reproduce it (minimal and precise)
Start Z2M. No changes were made to a previously working set up
Zigbee2MQTT version
2.0.0.2
Adapter firmware version
2.6.8.dev26
Adapter
SLZB-06
Setup
Home Assistant Add On
Debug log
[07:59:36] INFO: Preparing to start...
[07:59:36] INFO: Socat not enabled
[07:59:36] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-01-10 08:00:52] error: z2m: Failed to call 'Frontend' 'stop' (TypeError: Cannot read properties of undefined (reading 'close')
at /app/lib/extension/frontend.ts:132:52
at new Promise ()
at Frontend.stop (/app/lib/extension/frontend.ts:132:15)
at Controller.callExtensions (/app/lib/controller.ts:368:17)
at Controller.stop (/app/lib/controller.ts:233:9)
at stop (/app/index.js:172:5)
at process.handleQuit (/app/index.js:180:13))
The text was updated successfully, but these errors were encountered: