Replies: 37 comments 48 replies
-
|
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!) |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Sorting is not being remembered as with the old frontend. I need that to check on my last seen devices. Reported a bug. |
Beta Was this translation helpful? Give feedback.
-
|
Suggest adding |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
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). |
Beta Was this translation helpful? Give feedback.
-
|
To be honest...how can someone even think that this looks good compared to the old frontend?
|
Beta Was this translation helpful? Give feedback.
-
|
Can you please add the option of sorting by battery and by manufacturer like in the original frontend? |
Beta Was this translation helpful? Give feedback.
-
|
Sort by Battery low seems to have a problem too: |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
Network map is not shown in firefox - just empty screen. Same works fine in edge/chrome |
Beta Was this translation helpful? Give feedback.
-
|
Can we have a version with less rainbowy colours? |
Beta Was this translation helpful? Give feedback.
-
|
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 ? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Tip: Keep the permit joint button visible when the menu is collapsed.
|
Beta Was this translation helpful? Give feedback.
-
|
I don't have any objection against the new frontend, but I really miss some features which were working in the old one.
I use these two features as part of normal troubleshooting. |
Beta Was this translation helpful? Give feedback.
-
|
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. 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. +1 for the request to make the "Permit Join" button available when the column is collapsed. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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:
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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:
|
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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: And this is what I see after switching to the new front-end: note port 443 is not present anymore. I see no errors starting the service: Just the front end is not starting. Here is the relevant content of my configuration.yaml file that works: And this is the one that does not work: Hope there is enough information provided. |
Beta Was this translation helpful? Give feedback.
-
|
I noticed on the new UI that is can generate graphviz data. |
Beta Was this translation helpful? Give feedback.
-
|
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:
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. |
Beta Was this translation helpful? Give feedback.








Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a continuation of the old feedback discussion. In the October release, WindFront will become the default frontend.
To switch to Windfront, change the following setting:
About the original frontend:
packageis explicitly selected) will change to WindFront in the future releaseBeta Was this translation helpful? Give feedback.
All reactions