[FEAT/enhancement] DPEL sensors mode and limit unavailability

[KeningGruttePier]

Describe the issue 1
After calling the enable_dpel service, the dpel_limit and dpel_mode sensors show as unknown until the next scheduled poll cycle. Since the default poll interval is 60 seconds, this means sensors can be in an unavailable state.
They are unavailable

• when you boot HA
• when you install the integration 1st time

Describe the issue 2
when you fired DPEL command but update did not come back yet. If got DPEL sensor reporting 'on' and Limit and Mode still unavailable. I had to reload the integration to get the sensors available and report values

Account type
[X] Installer

Envoy
[X] Metered with CTs installed

Home Assistant
Version: 2026.5

Request
Initial launch of HA and integration (w/installer account) to set the DPEL limit and mode sensors and report default state to HA (to set initial avialability). Use the API response / POLL results to update and set accordingly the actual settings. Aim: avoid unknown sensors. I'd rather work with:
if DPEL reports 'off' set Production/Export mode to default 'unknown' and Limit to 'unknown' instead of sensor unavailable - until the updates drop in..

[vincentwolsink]

Can you send me the output of https://envoy.local/ivp/ss/dpel (make sure to login first) when DPEL is turned off and the sensors are unavailable?

[KeningGruttePier]

Here you go.
Installer token used on local ivp/ss/dpel endpoint

Initial status matches payload
'off' for sensor.pv_enphase_envoy_######dpel
unavailable sensor for sensor.pv_enphase_envoy#####dpel_limit
unavailable sensor for sensor.pv_enphase_envoy#####__dpel_mode

##ivp/ss/dpel
{
"date": "2026-05-29 15:21:29",
"dynamic_pel_settings": {
"enable": false
},
"filename": "site_settings",
"version": "00.00.01"
}

action: enphase_envoy.enable_dpel
data:
watt: 0
export_limit: true
slew_rate: 100

Refresh on endpoint provides directly
##ivp/ss/dpel
{
"date": "2026-05-29 15:21:29",
"dynamic_pel_settings": {
"enable": true,
"export_limit": true,
"limit_value_W": 0.0,
"slew_rate": 100.0,
"enable_dynamic_limiting": false
},
"filename": "site_settings",
"version": "00.00.01"
}

State of sensors in HomeAssistant updated, only on/off sensor updated right away with correct state. HA does not report/enable the dpel_limit and dpel_mode sensors.
'on' for sensor.pv_enphase_envoy_######dpel
unavailable sensor for sensor.pv_enphase_envoy#####dpel_limit
unavailable sensor for sensor.pv_enphase_envoy#####__dpel_mode

Another command with different DPEL mode and limit parameters does nog trigger HA to make the sensors available and report values. Also not after 2 minutes.

###Reload of integration. Reports correctly.
###no change to the payload of ivp/ss/dpel
'off' for sensor.pv_enphase_envoy_######dpel
'5000W' for sensor.pv_enphase_envoy#####dpel_limit
'Production' for sensor.pv_enphase_envoy#####__dpel_mode

Kortom:
The initial envoy startup has DPEL already enabled with a full payload → sensors will be available from the start
DPEL disabled at startup → sensors unavailable until reload, regardless of later commands

[vincentwolsink]

I agree with you. But I need to think how to implement this. Because the whole "generic" logic for adding sensors in the plugin is to only add them when they are available.