DXP4800PLUS only detecting 12 entities and nothing more no matter what

[LilithSuccubus]

I've just installed the HACS Version v2026.09.1 to monitor my DXP4800PLUS with UGOS v1.19.1.0126.
Upon adding the NAS through the configuration steps I'm being met with only 12 entities instead of the 60-70+ entities I've seen on pictures and video of other people. So I'm wondering what I'm doing wrong.

Image after adding my NAS to the HACS:

The 12 entities I'm being shown:

In the setup i've tried it with HTTPS 9443 and with and without having 2FA enabled.
I connect through direct IP instead of it's hostname.

Is there a known conflict between the current two versions of UGOS and HACS that i'm unaware off?
Really hope i can get a little bit of help to make it functional.

[Tom-Bom-badil]

This usually happens if you are using a non-admin user. Only a very few API endpoints hand out data to non-admins.

/tom

[LilithSuccubus]

That's the weird thing though. I'm using the only account i made on the Ugreen NAS (removed personal info for obvious reasons)

Just incase i made a new admin account and I'm getting the same 12 entities effect there as well (without 2FA).
This makes me think that it's due to something else that is causing the other entities not to be found.

Both HA and the NAS are on the same network and IP range.
Already tried rebooting both the NAS and HA but no changes.
Filter is also not hiding things either.

I did just manage to troubleshoot the problem though.
It seems to be that the issue is in the HACS v2026.09.1 itself. I uninstalled that version and installed v2026.08.1 and now all the entities are being picked up without any issues after this i tried upgrading back to v2026.09.1 but alas it gives issues again but downgrading it back to v2026.08.1 fixes it again.

After upgrading back to v2026.09.1:

Seems like there might be a bug or issue somewhere inside of v2026.09.1 that refuses to pickup entities properly

[Tom-Bom-badil]

Wait - I assume the entities just don't appear on the dashboard, but are availabe when checking in Settings > Tools > States?

Did you read this note on top of the update notes that HACS is showing before updating?

/tom

[LilithSuccubus]

When I'm on version v2026.09.1 remove everything and start from scratch again then these are the only entities that are being displayed:

Devices is still registered with my Admin account.

Just incase i check this page as well when i'm running v2026.08.1 and then it's filled to the brim:

This was a clean install so i assume all the code that i used was directly from github so i assume that's all good?

[Tom-Bom-badil]

That indeed is looking weird and is not a dashboard issue. Is there anything in the logs why it won't create the entities on startup?
(likely all entities are still there, just not activated/at unavailable state; you can check this in Settings > Devices & Services > Entities, just filter for 'ugreen')?

/tom

[LilithSuccubus]

These are two of the things i see in my log files after i add the NAS but that's about it.

Log details (WARNING)
Logger: midealan.device
Source: /usr/local/lib/python3.14/site-packages/midealan/device.py:919
First occurred: 11:26:56 PM (1 occurrence)
Last logged: 11:26:56 PM

[152832118066675] Unable to connect, sleep 320 seconds and retry

Log details (ERROR)
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:455
integration: Sensor (documentation, issues)
First occurred: 11:27:15 PM (1 occurrence)
Last logged: 11:27:15 PM

Error while setting up ugreen platform for sensor: module 'homeassistant.helpers.device_registry' has no attribute 'async_get_device_id_by_identifier'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 455, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/ugreen/sensor.py", line 154, in async_setup_entry
UgreenNasSensor(hass, entry.entry_id, config_coordinator, entity)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ugreen/sensor.py", line 561, in init
self._attr_device_info = build_device_info(hass, entry_id, self._key)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ugreen/device_info.py", line 183, in build_device_info
via_device_id=_via_device_id(root_id),
~~~~~~~~~~~~~~^^^^^^^^^
File "/config/custom_components/ugreen/device_info.py", line 32, in _via_device_id
return dr.async_get_device_id_by_identifier(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'homeassistant.helpers.device_registry' has no attribute 'async_get_device_id_by_identifier'

This is what is shown when i filter on ugreen:

[Tom-Bom-badil]

Quote:

module 'homeassistant.helpers.device_registry' has no attribute 'async_get_device_id_by_identifier'

That helps - good find! It looks this error will happen with non-recent HA Core Versions.

Background: In Core 2026.8, a new way of handling sub_devices was introduced in HA; the 'old' and common way of doing this is now giving a deprecation warning. I've internally already adjusted to that new way in integration v2026.09.1 to remove the warnings from the log, but of course totally forgot about users that might run older core versions.

I'll release a beta v2026.10.1 soon that should fix this behaviour by handling both ways (old and new).

Thanks,
/tom

[Tom-Bom-badil]

@LilithSuccubus pls checkout the new beta here.

/tom

[LilithSuccubus]

Thanks for all the work and effort you put into this. After the update everything is being detected again 🙇

[Tom-Bom-badil]

Perfect, thanks the instant test and the feedback! :)

Hint, just in case you want to make the entities cards fitting at the bottom to the NAS pic: click (if you are fine with 'as is', just ignore it - it's just my inner Monk 😂)

Enjoy!

/tom