[BUG] Missing many data for some of the inverters after upgrading to 0.6.x

[upsuper]

Describe the bug After upgrading to 0.6.x, most inverters are working fine (albeit I need to remove some old sensors and update the ID of the new sensors), but there are some inverters lose majority of its sensors. See the comparison below:

Screenshots showing different inverters

Inverter that works normally	Inverter that loses majority of the sensors

Account type

• [ ] Installer
• [x] DIY / DHZ
• [ ] Home Owner (This integration is not (fully) functional with a home owner account!)

Envoy

• [x] Metered with CTs installed

• [ ] Metered without CTs

• [ ] Standard

• FW version: D8.2.127

• Amount of micro inverters connected: 56

Home Assistant

• Version: 2024.12.1

Additional context

I took a look at some other issues, specially I saw https://github.com/vincentwolsink/home_assistant_enphase_envoy_installer/issues/189#issuecomment-2512484180 and also tried to fetch data from ivp/pdm/device_data, and it seems that it only lists 50 inverters, and the inverters lose the sensors can't be found in that data. So it seems like this endpoint doesn't work as reliably as the previous one I suppose?

[upsuper]

And indeed I can found the inverters in the previous ivp/peb/devstatus endpoint but not the new one.

[vincentwolsink]

Hi! That is a serious amount of inverters 😁

Can you please provide the output of the ivp/pdm/device_data endpoint?

[catsmanac]

Looks like the tail-end of device_data shows the limit of 50. Device count matches my 24 inverters and 1 q-relay.

    "deviceCount": 25,
    "deviceDataLimit": 50

[upsuper]

Oh, good point. I have 56 inverters + 2 relays so there should be 58 devices in total. Maybe that's over the limit of this endpoint?

[catsmanac]

Might be something that can be configured as datasheets state it can communicate with up to 300 inverters.

[upsuper]

Maybe @krbaker can help shed some light on how to use a different limit or do pagination on this endpoint?

[vincentwolsink]

For now, what I can do is if there are more than 50 devices, fallback to the devstatus endpoint. This is not ideal though. Better is to find out how to do pagination..

[upsuper]

Sounds good. This is quite unfortunate but it's probably better than lacking a lot of sensors for some of the devices.

[vincentwolsink]

Things are now getting a bit too complex for my liking. But I made usage of the old devstatus endpoint configurable for now in #195 .

[vincentwolsink]

Keeping this open, since pagination on the new endpoint would still be the preferred solution.

[upsuper]

I can confirm that enabling devstatus endpoint option in configuration and reload the integration makes those information come back, thanks! (It does mean all the new sensors become unavailable but that's okay.)