Call for help - testing needed

[Tom-Bom-badil]

Heya dear fellow HA Tinkerers,

first of all: thank you all for using this integration!
As of today, Home Assistant Analytics is showing almost 500 active installations out there – plus those where analytics back-reporting to HA headquarters has been disabled, so they are not included in this graph. Awesome!!! 🚀

What and why

The purpose of this post is to ask you guys for help.
Currently, I have the following items on my ToDo list for the next release (which I hope to ship quite soon):

• ✅ improve device detection / auto-discovery (see discussions Daily request to add new integration and data format issue #164 and Why discovery is finding my Synology NAS? And also a Ugreen NAS I've already set up? #171) → implemented and tested,
  
• ⚠️ include cache device info and cache disks (see discussion No SSD information shown after updating the latest version. #161) → implemented, but not tested yet,
  
• ❌ include switching of cooling profiles / fan levels (see discussions add fan mode control function #151 and Möglichkeit, die Lüfter zu steuern? #129) → implementation not started yet.
  

The second item is a tricky one for me.
I’ve finished the implementation, and the integration starts up cleanly and behaves normally on both my develop and my production HA systems. However, I do not have cache disks on my own NAS, so I’m currently unable to test any of the new functionality myself (“blind mode”).

Therefore, I’m looking for people who can actively help with testing.

How

I have prepared a pre-release v2025.12.1-beta1 from the develop branch for testing. You can install it via HACS:

• open HACS, filter for “ugreen” and click on this integration,
• click the three-dots menu in the top-right corner and choose “Download again”,
• select “Different version”, pick the v2025.12.1-beta1 pre-release, and confirm.
• you can switch back to your currently installed release version the same way at any time.

Please restart Home Assistant after installation. The following should then be available:

• Settings → Devices and Services → UGreen NAS:
  You should now see your general cache devices and cache disks. Clicking any of them should bring up the corresponding entities (for now, this is a minimal set; more entities as well as 'summary entities' with data in attributes will be added once basic testing is complete).
• Developer Tools → States:
  Filtering for “ugreen” or “cache” should show the new cache entities.
• Users of the example dashboard:
  Filtering for “cache” should reveal the new entities.
  Those cards will currently appear in red – this is expected behaviour and will be fixed before the final release.

Thank you very much in advance for reporting back any findings you might come across – ideally with some screenshots and/or log entries. Of course, positive reports are just as welcome 🙂

Appreciate your help – thank you! ❤️

/tom

[TrOjAnUK]

2800 Ugreen 2 x 4tb drives with 1 x 1tb cache and 1 x 1tb storage for apps... let me know what you need, if I can help I will but ask as if speaking to a n00b :)

[Tom-Bom-badil]

Thanks the detailed response, appreciated! :) I assumed the 'single pool' issues were solved in v2025.10.4 (see here - quite some users reported that it was fixed by that release). Therefore, this one leaves me a bit clueless, and it's a bit hard to reproduce here because I have a different pool setup.

• Are there any working pool-related entities? (filter for 'pool' in developer tools)
• Please provide me with the full names of 2 or 3 non-working pool entities. (want to check if numbers are stripped from names)
• Do the entities re-appear after restart when you delete all orphaned entities in Settings > Devices and Services > Entities by hand? (filter by status > unavailable, select and delete in the top-right menu)
• To make sure you don't have a Python related caching issue, I recommend removing the entire integration once by using HACS, reboot HA, checking that the integration folder is really gone (custom_components/ugreen), then re-installing the latest version again through HACS.

Good luck, please keep me posted!

/tom

[Tom-Bom-badil]

p.s. What is also confusing me is the fact that I do not see any of the new 'Summary' entities in your screenshot (those were introduced in 2025.11). There should be one for 'pool', but there isn't. What happens if you filter the dashboard for summary? Should be somthing like that:

/tom

[morbiddk]

Not sure where I'm looking for the working pool-related entitles. On the dashboard I don't see anything when I filter for pools or working in Developer Tools.
As for unavailable entities, I don't see any related to this integration.

I've tried fully removing the integration, rebooting HA and re-installing the latest version, same results. My "Summary" filtered for Pool 1 Summary has a 0 instead of Normal like yours is showing.

Elsewhere in the entities I did see this.

[Tom-Bom-badil]

Yes - I think those 2 screenshots did the trick. Internally, it's generating the string (Pool) instead of (Pool 1) in the names of all related sensors. For the same reason, 'Pool 1 Summary' is showing 0 instead of Normal (all summary entities attributes including 'state' are automatically copied out of the regular sensors 'Pool x - sensorname' - but those for your 'Pool 1' can't be found (as the ' 1' is missing, which leads to different sensor names), so everything is empty).

Quickfix:

Could you please add the following new line 637 in config/custom_components/ugreen/api.py:
single_compact=False, # keep pool1_* even if only one pool

The codeblock in _get_dynamic_config_entities_storage line 629ff. should look as follows (make sure you keep indentations as the are - just add the last line of code):

        entities.extend(await make_entities(
            fetch=_fetch_cached,
            templates=NAS_SPECIFIC_CONFIG_TEMPLATES_STORAGE_POOL,
            endpoint=endpoint_pools,
            list_path="data.result",
            prefix_key_base="pool",
            prefix_name_base="Pool",
            category="Pools",
            single_compact=False, # keep pool1_* even if only one pool
        ))

Then do a reboot. After reboot, check for orphaned entities again; the '(Pool)' entities without number shouldn't be used any longer.

Good luck, please keep me posted! :)

/tom

[morbiddk]

That did the trick! Thank you so much. Great project and great support!

[Tom-Bom-badil]

A new v2025.12.01-beta2 has been published. Appreciate some testing. :)

List of changes:

• ✅ improve device detection / auto-discovery (see discussions Daily request to add new integration and data format issue #164 and Why discovery is finding my Synology NAS? And also a Ugreen NAS I've already set up? #171) → implemented and tested,
  
• ⚠️ include cache device info and cache disks (see discussions No SSD information shown after updating the latest version. #161 and SSD-Cache #88) → implemented, testing started with beta1,
  
• ⚠️ include switching of cooling profiles / fan levels (see discussions add fan mode control function #151 and Möglichkeit, die Lüfter zu steuern? #129) → new: implemented, but no community tests yet.
  

Installation:

• Open HACS, filter for “ugreen” and click on this integration,
• Click the three-dots menu in the top-right corner and choose “Download again”,
• Select “Different version”, pick the v2025.12.1-beta2 (marked with 'pre-release'), confirm and restart HA.
• You can switch back to the latest release version the same way at any time.

Thank you for supporting the development with your tests!

/tom

---

Further infos / expected behaviour

Auto discovery / device detection

Multiple detection of the same NAS, as well as detection of non-UGreen NAS (e.g. Synology) should be gone now.

Cache testing

If you are using SSD Cache, you should now have entities for it in the following sections:

• Developer tools > States: Filtering for 'cache' should show you all cache related entities.
• Settings > Devices and services > Ugreen NAS: You should see new Pool X > Cache as well as Pool X > Cache disk Y devices here. Clicking it will give you the entities for the respective device.
• Example dashboard users: Filtering for cache should show you all cache related entities. Filtering for status should also show cache status entities. Note: I didn't adjust the sample dashboard code yet, so cache entitiy cards will be in red color.

Fan / cooling setting

There is a new entity sensor.ugreen_nas_fans_system_mode, showing the currently selected fan profile (quiet / default / full power). Also, in Settings > Devices and services > Ugreen NAS > Main NAS entry you will note 3 new buttons for switching it.

You could also add a new card somewhere on your dashboards with the following content (requires custom:button-card installed):

type: horizontal-stack
cards:
  - type: custom:button-card
    name: Quiet
    icon: mdi:fan-speed-1
    entity: sensor.ugreen_nas_fans_system_mode
    state:
      - value: quiet
        styles:
          card:
            - background-color: var(--success-color)
    tap_action:
      action: call-service
      service: button.press
      target:
        entity_id: button.ugreen_nas_fan_mode_quiet
  - type: custom:button-card
    name: Default
    icon: mdi:fan-speed-2
    entity: sensor.ugreen_nas_fans_system_mode
    state:
      - value: default
        styles:
          card:
            - background-color: var(--info-color)
    tap_action:
      action: call-service
      service: button.press
      target:
        entity_id: button.ugreen_nas_fan_mode_default
  - type: custom:button-card
    name: Full Power
    icon: mdi:fan-speed-3
    entity: sensor.ugreen_nas_fans_system_mode
    state:
      - value: full power
        styles:
          card:
            - background-color: var(--error-color)
    tap_action:
      action: call-service
      service: button.press
      target:
        entity_id: button.ugreen_nas_fan_mode_full_power

[Tom-Bom-badil]

Just released beta 3. You can now change the polling intervals in the NAS settings.
Also adjusted the code of the 'Example Dashboard Page' to reflect the latest changes in the integration.
Appreciate some testing, thanks! :)

/tom

p.s. Unless some serious reports are coming in, this will be the final code for the 2025.12 release.