zigbee2mqtt-windfront v2 feedback

[Koenkk]

This is a continuation of the old feedback discussion. In the October release, WindFront will become the default frontend.

• Feel free to leave your feedback here (make sure you are at least on Zigbee2MQTT 2.6.1).
• In case you encounter bugs, submit a new issue here.
• List of changes since 2.6.1 (feedback/issues that are already fixed)

---

To switch to Windfront, change the following setting:

---

About the original frontend:

• it has not been maintained in quite some time
• at some points, due to its use of old libraries, it is expected it will simply stop working properly (which would require a massive overhaul - what WindFront has done)
• new Zigbee2MQTT features are not supported
• the option to use either frontend will remain for now, just the default (when no package is explicitly selected) will change to WindFront in the future release

[rbswift]

Sorry if I missed it but I can no longer find a way to sort devices by battery level the way the old frontend allowed. This is very useful for sites with a lot of battery devices to keep an eye on which batteries will soon need replacement. Thanks

(other than this wind front is looking really great so thanks for your work!)

[chris-1243]

Click on Advanced search and apply a filter. In your case, select power source and battery.

[rbswift]

Hi @chris-1243 I did try that but the option to sort the list by battery level seems to have been removed. Apologies if i was unclear but in the current version, with a single click, I can sort the devices by battery level. Each time I remember to buy a new pack of batteries I then go around replacing the batteries in the devices reporting the lowest level. I am only suggesting to have the battery level column reinstated as an (optional) click-sortable column. Thanks

[Nerivec]

There is a "Battery low" checkbox in Advanced Search. It checks all current "ways" devices report battery statuses (battery level alone would miss devices since some don't report one, just a state).
We can add back the level column too though.

[pawel-tomkiel]

(...) We can add back the level column too though.

That was my default sorting with just one click in old frontend, now it's multiple clicks through advanced search; I'd be really happy if it comes back 🙂

[Nerivec]

You can toggle the "battery low" column and sort it too. Note that it gathers states from all battery states, not just %, (some use %, some use a boolean state, etc.), so you may see a different result from old frontend. Or you can use the "battery level" column, but it's less precise since non-% "battery low" states won't be shown.
https://github.com/Nerivec/zigbee2mqtt-windfront/wiki#tips--tricks

[nephrotranz]

Will there be any possibility to keep the old frontend? Tried Windfront two times, but it is definitely a No Go for me and I would like to keep it simple and clean.
The new dashboard for example is an absolute mess.

[ArtJames]

I removed 'package: zigbee2mqtt-windfront' from the configuration to use the old version.
@Koenkk It would be nice to continue giving users the option to choose between the two interfaces.

Edit: Found the setting to switch interfaces.
It's good to see that you're not forced to use the new interface.

[Koenkk]

Old frontend will still be there for the time being

[sammyke007]

Sorting is not being remembered as with the old frontend. I need that to check on my last seen devices. Reported a bug.

[rbswift]

Suggest adding title attributes to the four icons in the top-right corner so users get a tooltip to indicate what action they might perform.

[weljajoh]

The color coding of the LQI values makes them hard to read when they are at 'warning' level because the contrast between the yellow and the white background is too low. May I suggest keeping the actual value in black and perhaps change the background of the field to yellow so it is easier to read?

[dpgh947]

People are often going to rebel against forced change they didn't know they wanted/needed, but I really don't like the new frontend. The device list is busy, having the power/battery icon shoved in the friendly name field makes it much harder to quickly scan the list, and it seems to default to sorting on friendly name even if no sort is selected on the column headings. I am really used to the devices appearing in the order they were added, especially when adding new devices. The map is horrible. If you zoom so the whole map fits on the screen (I only have 25 devices), the device names are too small to read, the font is tiny. The thick white lines are just eye-boggling. The way the old map gently moves things apart as you drag something makes it far more readable.

Is the old front end going to disappear at some point? If not, I can't see the reason for changing the default.

UPDATE - I see the sort issue has been addressed in the latest version. The other points remain.

[dpgh947]

EDIT - OK, I see this has been addressed in the latest version.

I think it is worth pointing out that you don't need to go editing the z2m config file to switch frontends any more, both versions have the option in their settings to switch now - BUT it takes a few clicks around to find it in the windfront settings.

You click on settings, you get a list of headings that includes "frontend", you click on that and you get some stuff that it says is only saved in the browser. But next to "frontend" in that set of headings is another "settings", click on that, you then get another set of headings that includes "frontend", click on that, and you can then see the "package" selection. This is far from intuitive.

[fapgomes]

The column order doesn't remember between sessions. (When I change to order by last seen, if I leave the z2m windfront page and come back, the order is by name again).

[nephrotranz]

To be honest...how can someone even think that this looks good compared to the old frontend?
Because the attribute field keeps changing size, everything looks completely messed up.

[Nerivec]

Added to the todo list.

Also, with the introduction of new translations, no doubt quite a few places will need adjusting since different languages will alter the sizing of various elements. If you find any other, feel free to open an issue. We have to rely on community feedback for this, since it would require an enormous amount of time otherwise.
If you find errors in translations, feel free to contribute.

[nephrotranz]

It seems the original frontend is working with a fixed size for these fields as you can change to every language and it always looks the same.

[mvoss96]

Can you please add the option of sorting by battery and by manufacturer like in the original frontend?

[rbswift]

Sort by Battery low seems to have a problem too:

screenshot

[Nerivec]

Default sorting didn't work properly due to the value type (that column was mainly meant for advanced searching capability, not display).
Already fixed, and added a battery level column too 👍

[Nerivec]

WindFront 2.1.0 was merged in Zigbee2MQTT dev/edge with some of the early v2 feedback as well as a large WebSocket optimization refactor. Dropdowns have also been refactored due to a Safari bug that's plaguing random iOS versions.

You can also test WindFront separately using the standalone version (Docker containers & Home Assistant add-ons are available). See instructions in the wiki: https://github.com/Nerivec/zigbee2mqtt-windfront/wiki#standalone-serving-with-multi-zigbee2mqtt-support
Note: you can run both the built-in frontend (with whichever package you want) and standalone WindFront, at the same time.

[HenkRenting]

Is there a possibility to change the name of in the middle of the interface, where it now says Zigbee2MQTT? Or otherwise add a name or title to the interface, @Koenkk?
Reason is I have two instances running for both my home and basement and a clear visible title of which instance I am seeing would be great…

[Nerivec]

The best way would probably be for you to look into standalone WindFront. Improving it was the main focus of WindFront v2.
https://github.com/Nerivec/zigbee2mqtt-windfront/wiki#standalone-serving-with-multi-zigbee2mqtt-support
There's a Docker container, and a Home Assistant add-on that can be used for quick setup (baremetal is also possible).

It allows you to merge multiple Zigbee2MQTT instances into a single UI, each instance (device/group/etc) is tagged with a name, which you can display in the UI (and sort/filter like the rest).
Feel free to find me on Discord, or open up a discussion if you need any help.

About changing the title: all non-static data displayed in the frontend is driven by Z2M, which means we'd have to add a configuration specifically to display there that would be in configuration.yaml.

[HenkRenting]

Hmmm, that could be a solution...
Must look into it, might be a bit over my head.

Changing or adding a tile/name (or even image) to the top of the webinterface might be a more suitable and easier option for users...

But will definately take a look, thanks your reply!

[lezruk]

Network map is not shown in firefox - just empty screen. Same works fine in edge/chrome

[Nerivec]

Could you have something that blocks it on your Firefox browser (like a bad detection from an adblocker)?
Also make sure your Firefox is not too outdated.

It should work in both. I primarily test everything with Firefox & Chrome, no issue here.

[lezruk]

This is strange, Firefox is most recent 142.0.1 on win11 (standard security settings) , all extensions are disabled, no ad blockers. This is the error I got in console

THREE.WebGLRenderer: A WebGL context could not be created. Reason:  WebGL creation failed: 
* AllowWebgl2:false restricts context creation on this system. ()

After manually enabling webgl.force-enabled -> true it started working. Looks like webgl is disabled by default in firefox

[Nerivec]

You might have had a customized profile or maybe corrupted. It should be enabled by default.
In case you encounter more issues, you can create a new profile in about:profiles and switch to it or just completely reset Firefox.

[0sy]

Can we have a version with less rainbowy colours?

[Soukyuu]

Have you looked at available themes? Business or Wireframe seem to have what you want.

[sigma415]

What's the problem with the "rainbowy" colours ?

[pxFIN]

I wonder if something is changed in network/radialout2d ?

I changed my dongle from CC2531 to CC2652(better zigbee 3.0 support) and now it seems children are more.. wanting to keep inside than showing router wise outside ?

Pic

[pxFIN]

This might be due to ? router firmware i had before but still.. there is no possibility to have more scattered view of children.. because more children more is cluttered inside there

[Nerivec]

Did you change the sliders at the bottom left maybe? That would affect the layout.
I haven't seen anything in the render library updates that would affect this, but I'll double-check!

[pxFIN]

Did you change the sliders at the bottom left maybe? That would affect the layout. I haven't seen anything in the render library updates that would affect this, but I'll double-check!

Actually no i havent changed the sliders.. This is weird yesterday network map was like the pic i put here.. today it looks 'correct' meaning children are not focused inside but rather like it used to be... i havent changed any settings between yesterday and today.. oh well seems theres no issue here

[zen2]

I've a big enough network with 114 devices so the network map loading is quiet long. I get used so usually I launch the map loading and do something else while this time but with the new frontend when I come back to watch the map, the web interface have somehow reset and have come back to the devices pages so I can't use the map feature or I need to wait the map loading in front of the UI.

[Nerivec]

Can you open an issue and give some context details (is the long loading due to network requests, or the loading of the interface in the browser)?
Some tests were run on much larger networks, I have not seen this reported before. So we'll probably have to look at what could be different in your case.

[zen2]

I've tested it again and it appears the problem is not linked to the z2m web ui but to homeassistant one as I use z2m ui as a home assistant dashboard (web page type). So sorry for the noise ;)

[infabo]

With the recent update, windfront was set as the default. I gave it a try, but unfortunately, the usability feels extremely poor. The aligments are unnaturally. While I’m generally in favor of improvements, this change seems like a significant step backwards.

[Inferi0r]

Agree color, contrast, look and feel and button placements are all a step backwards. I hope most agree and in a few versions we can make the other GUI default again.

[sigma415]

I hope most agree and in a few versions we can make the other GUI default again.

You can switch to the other (old) GUI by yourself.

[walberjunior]

Tip: Keep the permit joint button visible when the menu is collapsed.

[Nerivec]

The limited space makes it hard to properly display which router is selected (and also does not allow router selection). Permit join alone could cause confusion as users may try to open the network on a router they did not intend to.

If you have any ideas, feel free to open up a discussion or even create a PR 😉
https://github.com/Nerivec/zigbee2mqtt-windfront/discussions/categories/ideas

[GSzabados]

I don't have any objection against the new frontend, but I really miss some features which were working in the old one.

• Device's pages is not actively updating, ie.: State tab, I press a button and it does not update the displayed state, I have to navigate to another tab and back to the State tab to see the change, this was working flawlessly before. It just doesn't react active on any of those tabs.
• Devices page is always reverting to some default order, and does not remember the set order setting (I like to see the devices in reverse last seen order, so I can see which device has failed recently.)

I use these two features as part of normal troubleshooting.

[Nerivec]

Make sure you are using the latest version (of Z2M, and WindFront if using standalone). If you still see weirdness, please open an issue.

[GSzabados]

@Nerivec, I am on the latest version, and the sorting seems to be working, might have been a glitch only, but the states tab is still not updating actively. I have to navigation from the tab to another to see it updated.

[bkwar201]

OTA section of the new view doesn't allow for sorting of the Check for update/update device/updating status (last column) This is important when processing updates when you have 150+ devices on the network.
ALL columns listed should be sortable

Also a pretty huge issue imo is the z2m LOG doesn't allow for any scroll back if you F5 or navigate away from z2m "[10/3/2025, 10:11:19 AM] Nothing to display" is shown until something populates.
Besides the access via the HA base logs i do not see a way to scroll back history within z2m itself.

+1 for the request to make the "Permit Join" button available when the column is collapsed.

[Nerivec]

The actions columns has no actual value to sort (it's buttons, progress bars). The State column should provide a much better alternative for what you appear to be wanting to do. It's hidden by default, but you can toggle it on to sort it.

Having historical logs would require a different architecture in Z2M.

[bkwar201]

State will certainly work, i didn't have that enabled so thanks for that!, but really all columns should be sortable.

Logs - is there a reason it isn't just reading from the log file itself?

AND what is up with all the neon colors for things now? Kinda annoying when in dark mode. Any way to change the color scheme?

[Nerivec]

Logs - is there a reason it isn't just reading from the log file itself?

The frontend does not have access to anything except the data that Z2M sends to it. The logs from Z2M are published "when they happen" through MQTT (publishing whole log files could create huge payloads/states). Changing this would require big changes in architecture, in Z2M, frontends, etc..

Any way to change the color scheme?

There are 35 themes to pick from (paint brush icon in menu bar). You can get a quick preview here.

[bkwar201]

Hmm that only seems to be the primary color and the colors for the menu, the Advanced search and the device actions on the right of the Device menu do not follow the color scheme selected. Attempted Black, Wireframe, Forest etc.

Same thing in the OTA section and Device page.
To be clear they do change to an extent between the different views but most appear to be very bright/neon-y

[Nerivec]

That screenshot is one of the themes with the highest contrast, so no doubt that won't fit what you want.
You can maybe try with corporate, or business, but buttons will retain a certain "pull" compared to the rest of the UI no matter what.

Note: I do not maintain the themes, they are from the design library used by WindFront. Due to time constraints, I also cannot test the UI with every single theme, I focus on light & dark.

[MortTalmon]

After update to Z2M 2.6.2 addon gives me "WebSocket: Reconnencting..." message. All previously added devices and automations are working. Can't see devices in Z2M, settings, can't add devices, etc. How can I fix it without rolling back to previous version?

[Nerivec]

Can you open an issue in https://github.com/Koenkk/zigbee2mqtt/issues/new?template=problem_report.yaml and provide some more details (especially debug logs).

Note: ensure you are running a current version of NodeJS. 22 is the recommended one. https://nodejs.org/en/download

[MortTalmon]

I have a same or similar situation as in this message #28442 (comment)
I don't understand what does he means saying logging off/loggin in to fix the issue. And was it fixed?
For me everything UI works only the first time after updating Z2M. If I change the page and then turn back it stops working and gives me "WebSocket: Reconnencting..." message. In Home assistant App not working too...

[annetapo]

As a professional web developer with extensive UI/UX experience, I have to say this is one of the worst interfaces I've ever encountered in terms of usability.

Main Issues:

• Navigation is extremely unintuitive and confusing
• Information architecture is chaotic - can't find basic functions
• Design is cluttered and overwhelming
• No clear visual hierarchy or user flow
• Critical actions are hidden or require too many clicks
• The interface feels like it was never tested with real users

The old zigbee2mqtt-frontend was much better. This new windfront is a massive step backwards in usability. I strongly recommend reverting to the original frontend until this one undergoes serious UX improvements.
As someone who has built professional web applications, I'm genuinely surprised this made it to production in its current state.

[Koenkk]

As someone who has built professional web applications, I'm genuinely surprised this made it to production in its current state.

Would you mind making designs to improve it?

[t3hk0d3]

As someone who has built professional web applications, I'm genuinely surprised this made it to production in its current state.

Would you mind making designs to improve it?

I don't particularity agree with everything OP has said, but having an UX designer to spend 10-20 hours to bring non-"developer-made" UX would be great. I am saying that as backend developer myself.

What about following idea:
Lets organize contest for UX designers, and people troubled with current UX (like myself) would chip in for a prize fund.

I can additionally promote such contest among UX designers community at my workplace.

[annetapo]

As someone who has built professional web applications, I'm genuinely surprised this made it to production in its current state.

Would you mind making designs to improve it?

I understand the “feel free to improve it” response, but my comment wasn’t about missing contribution — it’s about highlighting serious UX regressions.
Even without new mockups, the comparison with the previous UI clearly shows what worked better and why.
It’s valuable feedback, not a request to redesign from scratch.

[GSzabados]

I am absolutely with @Koenkk on this. If you think, that it is not working, and you have general comments about it, then maybe put some effort into it, and try to improve it.

On the other hand I have to agree with some of the comments of the OP, as I've just run into a function in the Dev Console which wasn't intuitive enough.

I have just installed a Zigbee dry contact replay, which has a 10A dry contact relay and can be used with gates and garage doors as a remote push button. The only issue, the device expose only a switch, and no option for auto off. So, I went into Dev Console to check what attributes the genOnOff cluster supports. Tried to read onTime, but no result. Tried to read another one which should work, no result. Then I tried to read an attribute which the device likely not have implemented, and there was the error message. I went back to onTime, still no result. I was so confused, as this function was working without any issues before, so I started to look at the logs, and had to realise the read function in the Dev Console will not give any result unless the log level is set to info. This shouldn't be like this. The Dev Console should give a result disregarding what is the log level for the log, either an error or a successful read. This way it is just not intuitive.

Writing an attribute is even more confusing, in the highlighted field you need to enter the value to write.

[Operrr]

The new frontend looks terrible, it's very hard to read, and the cards tab is a complete mess. I switched back to the old frontend and don't understand why they'd change something that works so well.

[dpgh947]

I assume the obviously huge amount of effort that has gone in to producing this new frontend was primarily driven by the "due to its use of old libraries, it is expected it will simply stop working properly" problem. I am also interested to know what the "new Zigbee2MQTT features are not supported" statement refers to? What are we missing at the moment?

I know we are supposed to be positive and constructive when commenting on such things, but it is really hard here. This new frontend does not just have a few teething problems that need a slight tweak here and there. It is just generally awful across the board. I am reminded of the early days of the internet when everyone was putting up their own websites with hand-written html, apparently following the one main design theme of "how can I make this look and behave surprisingly differently purely for the sake of doing so, how much information and how many different html tags and colours can I cram on to one page?", with no thought whatsoever given to usability.

This new version is busy, jumbled, confusing, inconsistent, unintuitive, and just downright ugly. The dashboard display is beyond useless, completely visually overwhelming, it is impossible to quickly scan it with the varying sizes and different layouts in each device box, it's just an eye-boggling misaligned mess of arrows and sliders and selection boxes and numbers. Someone posted comparison pictures of the old and new dashboards recently which illustrate this, and it has got even worse since then because for yet another inexplicable reason, the top menu bar has now been converted to a massive vertical side menu, wasting more screen width and making the screen even more cramped and busy.

The map/network display is also virtually useless, with its tiny fonts that are unreadable when zoomed to show the whole network (I only have 26 devices) and multiple confusing garish colours. The selection of different display options (3d?) might be fun to play with for a couple of minutes, but add nothing here in terms of actual usefulness. The way the old map gently floats around to arrive at a readable layout is really very good when compared to this.

There are no simple suggestions that are going to fix the new version in my view, apart from "throw it out and start from scratch". Whatever changes are needed under the hood to make it maintainable for the future, make the interface look like the old one to start with, and work from there with whatever changes people really need/want, if indeed there are any.

Making this the default with it still in this state is a huge mistake in my opinion, and is also a very worrying sign of intent - just how long is the old version going to be still available as an option before we are forced on to the new one?

[wesleyRaposo]

I'm a big fan of the previous interface, and for me, the change to the new interface made an impact.

I think these simple adjustments would greatly help this transition:

1. A color scheme identical to the old one (it was great—the current dark themes aren't as appealing as that one).

2. The "Dashboard" page should have an option to display the panels similar to the old one, where they're all the same size and spaced further apart (it looks more organized).

3. The old network/device map option should be brought back, or the current option should have larger icons and the circle borders could be removed.

[pxFIN]

I like the new interface .. new is not old and i on the other hand think something which needs to change.. .. change but using small bits

Network section somehow doesnt work.. i cant get similar network picture of personal network.. and i am starting to think is it good to have magnetism + <-> ? .. rather than switch them off ?

Changing something is always about having points of non .. nothing you can change without thinkin what the new can bring

[IgnacioHR]

Hi,

I tried to switch to new windfront package today but something is not working. I just upgraded to version 2.6.2 from version 2.6.1 and the only change was a line in configuration.yal file explicitly indicating the old front package as the one selected.

Than I went to settings and changed the front-end package as indicated in the first post of this thread. From that moment on the http server didn't start.

This is what I see while using the old front-end package:

root@z2mqtt:/opt/zigbee2mqtt/data# netstat -anp | grep LISTEN
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      373/master
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      95/systemd-resolved
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      95/systemd-resolved
tcp6       0      0 :::22                   :::*                    LISTEN      1/init
tcp6       0      0 :::443                  :::*                    LISTEN      487/node
tcp6       0      0 ::1:25                  :::*                    LISTEN      373/master
tcp6       0      0 :::5355                 :::*                    LISTEN      95/systemd-resolved

And this is what I see after switching to the new front-end:

root@z2mqtt:/opt/zigbee2mqtt/data# netstat -anp | grep LISTEN
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      373/master
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      95/systemd-resolved
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      95/systemd-resolved
tcp6       0      0 :::22                   :::*                    LISTEN      1/init
tcp6       0      0 ::1:25                  :::*                    LISTEN      373/master
tcp6       0      0 :::5355                 :::*                    LISTEN      95/systemd-resolved

note port 443 is not present anymore.

I see no errors starting the service:

root@z2mqtt:~# journalctl -f
-- Journal begins at Fri 2023-12-29 06:08:22 CET. --
...
Oct 07 15:45:03 z2mqtt systemd[1]: Stopping zigbee2mqtt...
Oct 07 15:45:03 z2mqtt systemd[1]: zigbee2mqtt.service: Succeeded.
Oct 07 15:45:03 z2mqtt systemd[1]: Stopped zigbee2mqtt.
Oct 07 15:45:03 z2mqtt systemd[1]: zigbee2mqtt.service: Consumed 8.817s CPU time.
Oct 07 15:45:03 z2mqtt systemd[1]: Starting zigbee2mqtt...
Oct 07 15:45:03 z2mqtt node[452]: Starting Zigbee2MQTT with watchdog (2000,60000,300000,900000,1800000,3600000).
Oct 07 15:45:04 z2mqtt node[452]: (node:452) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
Oct 07 15:45:04 z2mqtt node[452]: (Use `node --trace-warnings ...` to show where the warning was created)
Oct 07 15:45:09 z2mqtt systemd[1]: Started zigbee2mqtt.

Just the front end is not starting.

Here is the relevant content of my configuration.yaml file that works:

frontend:
  enabled: true
  port: 443
  ssl_cert: /etc/zigbee2mqtt/z2mqtt-all.pem
  ssl_key: /etc/zigbee2mqtt/private.key
  url: https://z2mqtt.chiton/
  package: zigbee2mqtt-frontend

And this is the one that does not work:

frontend:
  enabled: true
  port: 443
  ssl_cert: /etc/zigbee2mqtt/z2mqtt-all.pem
  ssl_key: /etc/zigbee2mqtt/private.key
  url: https://z2mqtt.chiton/
  package: zigbee2mqtt-windfront

Hope there is enough information provided.

[ubeaut]

I noticed on the new UI that is can generate graphviz data.
I used to be able to do it before and generate a network map by doing:
mosquitto_sub -C 1 -h $MQTTSERVER -t $ZIGBEE/bridge/response/networkmap/graphviz | $TYPE -Tpng > $OPENHABHTML/$FILE.png & mosquitto_pub -h $MQTTSERVER -t $ZIGBEE/bridge/request/networkmap -m graphviz
How can I do something similar now with the new system as the above doesn't work and hasn't done so for a long time?
Thanks

[pfak]

I've run into an issue where the initial page load AND clicking on any menu (Settings, Dashboard, etc. etc.) takes ~30 seconds the first time, and then is near instant after. This happens on any 'new' browser that visits the site, whether that be Edge or Firefox. I'm not seeing high CPU usage or anything, on either the client or server.

As soon as I switch to windfront, I see a ton of this in the Home Assistant logs:

2025-10-26 20:26:33.376 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140255378252448] Peter from 192.168.1.175 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 Edg/141.0.0.0): Client unable to keep up with pending messages. Reached 4096 pending messages. The system's load is too high or an integration is misbehaving; Last message was: b'{"type":"event","event":{"event_type":"state_changed","data":{"entity_id":"sensor.upstairs_office_closet_overheat","old_state":{"entity_id":"sensor.upstairs_office_closet_overheat","state":"No Alert","attributes":{"friendly_name":"Upstairs Office Closet Overheat"},"last_changed":"2025-10-27T03:24:10.490531+00:00","last_reported":"2025-10-27T03:24:10.490531+00:00","last_updated":"2025-10-27T03:24:10.490531+00:00","context":{"id":"01K8HV3QBTPSJ8N0APAVCYN6TB","parent_id":null,"user_id":null}},"new_state":{"entity_id":"sensor.upstairs_office_closet_overheat","state":"unavailable","attributes":{"friendly_name":"Upstairs Office Closet Overheat"},"last_changed":"2025-10-27T03:26:33.376107+00:00","last_reported":"2025-10-27T03:26:33.376107+00:00","last_updated":"2025-10-27T03:26:33.376107+00:00","context":{"id":"01K8HV82X0EYB7TBNBPP9TDDJ3","parent_id":null,"user_id":null}}},"origin":"LOCAL","time_fired":"2025-10-27T03:26:33.376107+00:00","context":{"id":"01K8HV82X0EYB7TBNBPP9TDDJ3","parent_id":null,"user_id":null}},"id":40}'

As soon as I switch away from the new frontend, the messages go away. The host doesn't seem to have any issues (it's an i7 with 64GB of RAM, and it's only using 50% CPU) and the client is basically idle.