v2.0.x

[Nerivec]

Important

BREAKING CHANGES

Thank you @thk-socal @thargy @KoalaWerewolf @ams2990 @0rsa for the help in reviewing and debugging all this!

Breaking Notes

• UX: general user experience has changed significantly from previous
• CONFIG: some browser-stored configs are affected (may be reset to defaults due to internal changes) - you can reset this to defaults in the new navbar icon for frontend browser settings
• NAV: some navigation paths have changed (could render previous "deep-link" bookmarks obsolete)

New Features

• feat: [BREAKING:UX,NAV] merge multiple API instances into a single interface (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
  • use tab design wherever merged does not make sense: Network, Logs, Settings
  • quick identification with a set of dots colored based on the API URL index (static). (Note: the dot also changes in case the underlaying WebSocket has a problem. )
  • Note: this remains mostly hidden in case of single-API use
• feat: [BREAKING:UX,CONFIG] unified filtering across the board (interface/logic) (PR feat: refactor filtering - advanced searching #198)
• feat: add global filtering (single input that looks across columns/datapoints) (PR feat: refactor filtering - advanced searching #198)
• feat: [BREAKING:UX,CONFIG] better advanced searches (PR feat: refactor filtering - advanced searching #198)
  • by text, by range, by select, by checkbox
  • select and text with auto-complete (suggestions) based on "all present values"
  • all filters stored in browser local storage, persisting across page close/reload (except private windows & cache clearing)
  • can search even hidden columns
  • beyond filtering: can be used to quickly identify min/max (in range placeholders) & counts (in select & text suggestions parentheses) for specific columns
• feat: batch log and device state updates using requestAnimationFrame for better perf (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• feat: [BREAKING:UX] use notifications drawer instead of toasts for log-derived notifications (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
  • allows quick checking while remaining problems-free for screen space (especially with new multi-instance)
  • a dot will appear next to the notification icon if an error-level notification was received, as well as if an instance requires restarting (e.g. to apply settings)
• feat: improve navigation (map Settings page sub tabs to addresses) (PR feat: various improvements #197)
• feat: add more icons for features (mostly assigned by AI for new ones) (PR feat: various improvements #197)
• feat: add ability to hide static info alerts throughout the UI with a setting (saved in browser local storage) (PR feat: refactor filtering - advanced searching #198)
• feat: AI-driven translations (PR feat: AI-driven partial translations #194)
• feat: add Docker edge version based on last main branch commit. (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)

Fixes

• fix: Dashboard now uses react-table (headless) to handle the data to match filtering capabilities & co with tables (while keeping the masonry layout) (PR feat: refactor filtering - advanced searching #198)
• fix: performance improvement with features filtering (pre-calc during store updates) (PR feat: various QoL improvements #193)
• fix: use virtualized rendering for table layouts (PR fix: refactor tables handling #192)
• fix: use virtualized rendering for card-using layouts (PR fix: refactor device card handling #191)
• fix: debounce re-rendering issues (PR feat: refactor filtering - advanced searching #198)
• fix: switch to built-in row selection for OTA page to cleanup some of the logic (PR feat: refactor filtering - advanced searching #198)
• fix: OTA table not using correct data when selecting all after filtering (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: add ESC support to all modals (PR feat: various improvements #197)
• fix: refactor search inputs to not use type=search for a unified controlled behavior across browsers (with ESC clear support) (PR feat: various improvements #197)
• fix: improve handling of bad URLs (redirect as appropriate if missing segments or unknown device/group) (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: input validation for scene, group (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: firmware ID now in own column in OTA page (PR fix: various OTA page fixes #177)
• fix: wrong group description in card for device groups tab (PR fix: refactor device card handling #191)
• fix: add log message on WebSocket error (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: [BREAKING:UX] use toasts only for success/error feedback in user-driven requests (bridge/request, /get & /set) (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
  • /get & /set errors are parsed to only show the actual error in the toast (full message available in notifications drawer & Logs page)
• fix: [BREAKING:NAV] move Frontend local storage settings into its own page (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: mark required fields with * (PR feat: various improvements #197)
• fix: allow sending null for non-required enums (PR feat: various improvements #197)
• fix: send null to Zigbee2MQTT when setting is cleared (i.e. empty string => null), except for array/boolean types (PR feat: various improvements #197)
• fix: use settings defaults if current config has nullish value (to properly reflect what Z2M is using) (PR fix: show settings defaults and use them if null #180)
• fix: show settings defaults after description (PR fix: show settings defaults and use them if null #180)
• fix: "removed" navigation dead-end issues due to multi-instances switching with new merged design (PR feat: 2.0.0 - Merged multi-Zigbee2MQTT #176)
• fix: [BREAKING:CONFIG] consolidate store keys for tables (PR feat: refactor filtering - advanced searching #198)
• fix: cleanup overuse of memoization (PR feat: various improvements #197)
• fix: truncate not properly applying in some cases (PR fix: refactor tables handling #192, feat: various QoL improvements #193)
• fix: isolate OTA progress bar (PR fix: refactor tables handling #192)
• fix: set default sorting on friendly name (PR fix: set default sorting on friendly name #178)
• fix: match button outline design with a few more prominent buttons (PR fix: various styling fixes #179)
• fix: better align buttons with fieldsets (PR fix: various styling fixes #179)
• fix: add a few icons to buttons (PR fix: various styling fixes #179)
• fix: add short notice for network map page (PR fix: various styling fixes #179)
• fix: change clear icon to x (PR fix: improve search inputs #188)
• fix: disable clear button when search value is empty (PR fix: improve search inputs #188)
• fix: various styling alignments (PR feat: refactor filtering - advanced searching #198)
• fix: refactor card-using layouts to use masonry (PR fix: refactor device card handling #191)
• fix: clear selected in OTA page after check/update triggered (PR fix: various small fixes #181)
• fix: add checks & counters in OTA page (PR fix: various small fixes #181)

Full Changelog: v1.8.1...v2.0.0

---

This discussion was created from the release v2.0.0.

[0rsa]

@Nerivec some points on my side which can be discussed:

• The contrast of the selected segmented tab in the Exposes view is not enough, both (active/inactive) are grey, a primary color should be better
• I'm not able to find the property "power_on_behavior" in the Advanced search (Feature name) of the Dashboard
• It was useful to focus a coordinator quickly to filter a list instead of having to click on Advanced search
• Losing the scroll position between a list and the device details is annoying, this is a tricky feature but it can be done memorizing the scroll position on the list each time the user scrolls and restoring it at the first loading of a list if this scroll position exists

And thanks for the awesome job you did regarding this new release.

[Nerivec]

1. Can you elaborate? I'm not exactly sure what you mean. A screenshot maybe?
2. The Dashboard filters out config-type features to focus on day-to-day actionable/diagnostic stuff. It does this using categories assigned to features by Z2M. The filters are dynamically derived from the stuff that is available on the page.
3. I'm sure other users will have a similar initial feel to a specific filter they used before. Problem is, we'd end up pulling everything back out of advanced search to fit every users 😅
   • I was thinking an extra (future) feature for the advanced search would be having a few saved searches (in-browser ofc), so you can quickly load back a specific search / toggle between them.
4. I'll see what we can do about that, have to check what's doable/reliable with the virtualized rendering.

[0rsa]

[Nerivec]

I see. This is driven by the theme used, I'll check with daisyui (the design library WindFront uses) if they can adjust contrast better, there are a few places where this might benefit for lighter themes.

[0rsa]

About the point 2., I understand that you do not have the hand on that, right?

To elaborate further on this one, I'm surprised to have the "power_outage_memory" in the list and not the "power_on_behavior". I have only one device concerned by the "power_outage_memory" and a lot by the "power_on_behavior"

If you want to check that all your lights have the correct behavior regarding this attribute, you have to go one by one and this is terribly long. However, I understand that this is not necessarily for day-to-day use, but it is very practical.

[Nerivec]

The categories are driven by https://github.com/Koenkk/zigbee-herdsman-converters indeed. Since there are a lot of devices, could be some are missing it, or are mislabeled. Previous behavior was to awkwardly filter on frontend side, but this resulted in far too much noise (there are thousands of features in ZHC, and some devices have hundreds of them alone). Using ZHC's assignments should provide a uniform source for all devices, and avoid occurrences where cards would run a mile long because of highly configurable, specific, devices. However, since this is newly established, no doubt some issues will be found (it was previously only used by HA behind the scene I believe), we can adjust from ZHC's side as appropriate.

After v2 settles down, we can look into adding more complex features, new pages, etc.. If you have ideas in the meantime, don't hesitate to create feature requests.