Release Bugfixes and internal changes · Tom-Bom-badil/home-assistant_ugreen-nas

What's Changed

Only for users of the entire-page.yaml example page
The sort field for the auto-entities card has changed: entity_category → nas_part_category
Please correct both the template code and the page code; I corrected it on the Wiki already, so you can use copy/paste again; or simply search/replace in the editor (3+1 occurences in the code).
Sorry for that: Unfortunately, the renaming was necessary to avoid confusion; the previous name entity_category is for HA-internal use only, I had chosen a bad name here that needs to be corrected.

Fix warning if no cpu fan is available (DXP 2800, see discussion 99). Presence of fans is now evaluated on startup.
Fix warning if no UPS is connected. Presence of a UPS is now dynamically evaluated on startup.
Fix deprecation warning "This will stop working in Home Assistant 2025.12" (see discussion 92).

Finalized restructuring of init.py.
Moved a bunch of configuration entities to status entities (polled every 5s now).
Added counters for dynamic entities (stored both in API and HASS object for global access).
Added Serial# + MAC's to device registration (preparation for Multi-NAS and dynamic detection when using DHCP).
Renamed internal sensor attributes. By using those attributes, auto-entities can e.g. filter all 'LAN' or 'POOL' related items of all UGreen NASes in the network (just one of many useful examples):
- device_type → nas_device_type (always "UGreen_NAS"; filter all Ugreen entities without needing fixed item names)
- device_id → nas_device_id (a unique ID of a specific NAS in Multi-NAS environment; also used to sort & filter)
- entity_category → nas_part_category (classification of a specific item for filtering/sorting, e.g 'LAN', 'RAM', 'CPU')

Still more endpoints and entities to be added.
api.py to be cleaned up and 'smallified' (it's functional, but way too long and complex).
setup_flow and config_flow to be further enhanced in preparation to Multi-NAS and DCHP detection feature.
❗Thanks to user rexprojects - he detected a problem in UGOS that gives some headache (details here in discussion 99). For at least 3 important sensors (cpu_temp, cpu_load, ram_load; possibly some more), UGOS only updates the API if either Ugreen Web GUI or UGreen Mobile App is active in parallel. This is considered a priority issue for one of the next updates.