After update v2026.05.2 a couple of details not more available

[dhemesbrahma-commits]

Hi,After update v2026.05.2 a couple of details not more available. See the print screen.

I've removed those entities as suggested.

Best regards,
Dhemes

[Tom-Bom-badil]

Yes, just delete those entities. If you filter for 'lan', you'll see that the networking entities are still there.
Make sure you also update the dashboard (see Wiki) - there is a bunch of changes to it, too.
Enjoy! :)

/tom

[CooperRS]

Hmm, not sure I'm missing something, but the LAN Port IP and LAN Port Speed entities do not seem to have a replacement. LAN entities that show the current download/upload rate have a replacement though 🤔

Screenshot

[Tom-Bom-badil]

Good find! There seems to be a missing space in the entity naming. Both my HA instances are showing the following:

But can't find any reason why IP or Link Speed are not in your entities list. Going to dig into it - mind another HA restart?

/tom

[Tom-Bom-badil]

Hmmm - weird, see my screenshot above. There is a space issue in some entities (LAN1 vs LAN 1), but that's pretty much it of what I can find here on my own 2 HA instances.

Just guessing: What NAS model are you guys running? Is it one of those with a single LAN port only? It could be that the API is returning different JSON then, which could lead to a non-creation of those entities.

/tom

[Marcelojv36]

I have a DXP2800 (a single LAN port).
I have captured the Get response from UGOS API when I access the NAS using Chrome. Here is the section related to net information. Is it as you suspected?

"net": [ { "model": "eth0", "ip": "192.168.0.224", "mac": "xx:xx:xx:xx:xx:xx", "speed": 1000, "duplex": "full", "mtu": 1500, "mask": "255.255.255.0" } ]

[CooperRS]

I have a DXP2800 (a single LAN port).

Same here 🙂

[Tom-Bom-badil]

Yeah, pretty much seems like this is the cause.

Background: There was a change in the UGOS API I detected ~March this year, which was causing the LAN data to disappear. So I moved to another endpoint for the static LAN related entities - instead of dealing with /ugreen/v1/sysinfo/machine/common, I was moving to ugreen/v1/network/iface/list instead.

Probably that wasn't my best idea - looks like for devices with 1 LAN port (or for devices not having LAN bridge mode configured - still guessing), the results differ from what I am getting here from my own NAS.

Q: Could you guys please send me examples of your JSON from that endpoint? Just drop the JSON here, and make sure you hide your MAC addresses.

Calling the API endpoint:
http://NAS_IP:NAS_Port/ugreen/v1/network/iface/list?token=your_token

Example call:
http://192.168.178.9:9999/ugreen/v1/network/iface/list?token=ABCDEF0123456789FEDCBA

Example result:

Click to show / hide example JSON repsonse

{ "code": 200, "msg": "success", "data": { "ifaces": [ { "label": "VBR-LAN1", "type": 5, "status": 0, "connection": 1, "interface": "bridge0", "slaves": [ { "label": "LAN1", "interface": "eth0", "type": 0, "connection": 1, "speed": 10000, "duplex": "full", "mtu": 1500 }, { "label": "", "interface": "vnet0", "type": -1, "connection": 1, "speed": 10000, "duplex": "full", "mtu": 1500 }, { "label": "", "interface": "vnet1", "type": -1, "connection": 1, "speed": 10000, "duplex": "full", "mtu": 1500 } ], "mac": "ma:ca:dd:re:ss", "speed": 10000, "mtu": 1500, "mtu_manual": 0, "duplex": "unknown", "ipv4": { "status": 0, "protocol": "static", "ipaddr": "192.168.178.9", "ip6addr": null, "mask": "", "netmask": "255.255.255.0", "gateway": "192.168.178.1", "default_route": "192.168.178.1", "dns": [ "192.168.178.1" ], "route": 1 }, "ipv6": { "status": 1, "protocol": "disable", "ipaddr": "", "ip6addr": null, "mask": "", "netmask": "", "gateway": "", "default_route": "", "dns": null, "route": 0 }, "ieee8021x": { "enable": false } }, { "label": "VBR-LAN2", "type": 5, "status": 0, "connection": 0, "interface": "bridge1", "slaves": [ { "label": "LAN2", "interface": "eth1", "type": 0, "connection": 0, "speed": -1, "duplex": "full", "mtu": 1500 } ], "mac": "ma:ca:dd:re:ss", "speed": 0, "mtu": 1500, "mtu_manual": 0, "duplex": "unknown", "ipv4": { "status": 2, "protocol": "dhcp", "ipaddr": "", "ip6addr": null, "mask": "", "netmask": "", "gateway": "", "default_route": "", "dns": null, "route": 0 }, "ipv6": { "status": 2, "protocol": "dhcp", "ipaddr": "", "ip6addr": null, "mask": "", "netmask": "", "gateway": "", "default_route": "", "dns": null, "route": 0 }, "ieee8021x": { "enable": false } } ] }, "time": 0.03352098 }

How to abtain the token
How to make JSON prettier so you can read it better

Thanks in advance!

/tom

[Marcelojv36]

Hi Tom,
Here is the result with my DXP2800 (single LAN):
Call:
https://my_nas.local:9443/ugreen/v1/network/iface/list?token=my_token

Click to see response

{
    "code": 200,
    "msg": "success",
    "data": {
        "ifaces": [{
                "label": "LAN1",
                "type": 0,
                "status": 0,
                "connection": 1,
                "interface": "eth0",
                "mac": "xx:xx:xx:xx:xx:xx",
                "speed": 1000,
                "mtu": 1500,
                "mtu_manual": 0,
                "duplex": "full",
                "ipv4": {
                    "status": 0,
                    "protocol": "dhcp",
                    "ipaddr": "192.168.0.224",
                    "ip6addr": null,
                    "mask": "",
                    "netmask": "255.255.255.0",
                    "gateway": "192.168.0.1",
                    "default_route": "192.168.0.1",
                    "dns": ["192.168.0.1", "192.168.0.1"],
                    "route": 0
                },
                "ipv6": {
                    "status": 2,
                    "protocol": "dhcp",
                    "ipaddr": "",
                    "ip6addr": ["xxxx::xxxx:xxxx:xxxx:xxxx/xx"],
                    "mask": "",
                    "netmask": "",
                    "gateway": "",
                    "default_route": "",
                    "dns": null,
                    "route": 0
                },
                "ieee8021x": {
                    "enable": false
                }
            }
        ]
    },
    "time": 0.02073828
}

Thanks!

[dhemesbrahma-commits]

Hi Tom, my LAN1 (DXP2800) is in bridge. Seems then it's ok as you were guessing. :) Thank you for your great work.

[Tom-Bom-badil]

Yes, confirmed - we have two separate problems here (single port AND non-bridge LAN configurations). This was caused by my fix for the changed UGOS API in 2026.04, which was incomplete and didn't consider these cases.

I tried to implement a fix for this in v2026.05.3-beta. As I also fixed the different entity naming, you'll likely have a couple of red cards again - just delete the abandoned entities.

Beta testing guide here - can you guys please run a quick test? Thank you! :)

/tom

Edit: Corrected release tag and link.

[Marcelojv36]

Hi Tom. I believe there is a mistake when publishing the branch. When I click on the link v2026.05.3-beta, it redirects to v2026.05.2-beta1.

I cannot find any branch called v2026.05.3-beta

Anyway, your change works for my case (single Port). As v2026.05.2-beta1 was updated 2hs ago, I have tried installing that one.

Now, when the integration is created, I see all the expected entities. I am focused in IP and MAC, but here is the full list in case you want to reviewe it.

Thank you very much!

[Tom-Bom-badil]

Thanks for reporting back! Yes, I was indeed entering a wrong tag during release creation.
Corrected - it should now properly appear as v2026.05.3-beta in HACS.

Good to know the LAN entity issues are fixed for you - let's see if we get some more reports.
Again: Thanks for testing the beta and for reporting back, much appreciated. :)

/tom

[CooperRS]

Just installed the v2026.05.3 Beta as well and LAN IP and Speed are back. I didn’t specifically check the others, but to me it looks good! 👍
Thank you for the timely fix! 🙏🙏🙏