Information for sensor.epcube_systemstatus and request for an additional sensor

[billnis]

I am a Certified EP Cube installer. To be clear I have only installed my system so I don't claim to be a EP Cube system expert but it does give me access to support that may be moe wiling to share information with me than an EP Cube owner.
After talking to support regarding the sensor.epcube_systemstatus in Home Assistant, I have learned what exactly it tells the status of and whet the values mean. I know the values for this have been subject for some discussion.

It is the Gateway Status (0-7) it does not report the status of the complete system only for the gateway. The numeric values represent:
0: 'Self-test'
1: 'Fault'
2: 'Idle'
3: 'Standby'
4: 'Running'
5: 'Not Powered'
6: 'Low Power'
7: 'Under Protection'

EP Cube support confirmed there is a separate PCS Running Status (0–9) for the Inverter in addition to the ECU System Status above. Does the API already return this value, and if so, is it available but not currently exposed as a Home Assistant sensor? The numeric values for that sensor would be:
0: 'Initialization',
1: 'Idle',
2: 'Startup',
3: 'Standby',
4: 'On-Grid',
5: 'Off-Grid',
6: 'Fault',
7: 'Debugging',
8: 'Power Button Off',
9: 'Low Power'

I am hoping Bob Silvio or someone working on this integration could add this sensor if they can find it in the EP Cube API. I have looked through the existing 222 entities and have not found anything that matches up to in my Home Assistant history from what I see on the EP Cube's website for my Inverter for the same time period.

Sent to me from EP Cube support:
The charts that pertain are the System Status and PCS Running Status

I really am loving this integration and I hope this information helps someone.
Bill Nissley

[Bobsilvio]

Hi Bill,

Huge thanks — this closes a long-standing question, and I could confirm both points against EP Cube's own code.

1) System Status: you're right, the integration's mapping was wrong. I verified it against the EP Cube web portal bundle: its device detail page maps systemStatus 1 -> "fault" and 5 -> "notTurnedOn", which matches what support told you and contradicts what the integration had. Fixed in v1.5.0: sensor.epcube_systemstatus is now a proper enum sensor named "Gateway Status" with translated states (Self-test, Fault, Idle, Standby, Running, Not Powered, Low Power, Under Protection).

⚠️ Breaking change: the state is now a text value instead of the raw number.

2) PCS Running Status: it is NOT available through the API the integration uses. I checked every endpoint we poll — homeDeviceInfo (77 fields), deviceList, getSwitchMode, queryDataElectricityV2 and queryDataGraphV2 (34 fields per 5-minute sample) — plus about ten guessed endpoint names. No PCS field anywhere.

It lives in the installer console API instead:

GET /v1/api/device/deviceInfo?id={devId}   -> data.deviceOtherInfo.pcsStatus
GET /v1/api/device/deviceInfoPcsChart      -> the chart you were shown

That API is on a different base path (/v1/api) behind CAS login. An owner-level app token is rejected there (it returns a redirect to casUser/toCasLogin), so the integration can't reach it with the credentials it has.

For reference, the portal's own mapping for that field is:
0 Initialization, 1 Idle/Free, 2 Startup, 3 Standby, 4 On-Grid, 5 Off-Grid, 6 Fault, 7 Debug — matching your list, which adds 8 Power Button Off and 9 Low Power.

So: doable only if EP Cube exposes pcsStatus on the owner API. If you have a channel to support, that's the exact request worth making — "please expose deviceOtherInfo.pcsStatus in the owner-facing API". I'll wire it up the same day it appears.

Thanks again for digging this up,
Silvio

[billnis]

I have sent an email to EP Cube support asking if there technicians can expose the PCS Status thru the owner API. Seems odd the ECU would be exposed but not the PCS.
Your timely response to my original post was much appreciated.

[Bobsilvio]

Thanks Bill — that's the right channel for it, and I agree it's odd: the ECU status is exposed to owners while the PCS one is not, even though both feed the same web dashboard.

If support asks for specifics, the exact request is to expose deviceOtherInfo.pcsStatus (and, if they're willing, pcsWorkStatus) on the owner-facing API — today it only appears under /v1/api/device/deviceInfo, behind the installer console login. The moment it shows up on the owner API I'll add the sensor.

Meanwhile the corrected Gateway Status is out in v1.6.2, published as a proper release so HACS picks it up.

Silvio

[billnis]

I finally got a response from EP Cube support about the PCS Running Status. I don't think further explanation to them would prove helpful and may cause them to remove the Gateway Status from the Owner API since they mention "confusing" and "inconsistent" in their reply. So at this point I think I need to drop it fearing any further pursuit will lead to negative results. I was really hoping for a different response. Thanks for all your work bringing the EP Cube integration to Home Assistant. I make use of it daily. Thank you for taking the time to share this feedback with us. We completely understand the importance of having this information available and how useful it can be for monitoring the system. We truly appreciate your suggestion and will take it into consideration. At this time, however, we are unable to expose the PCS Running Status through the Owner API, as we want to avoid having potentially conflicting or inconsistent information between the different system interfaces. We appreciate your understanding and your continued feedback. We’re always looking for ways to improve the EP Cube experience, and feedback like yours is very valuable to us. Thank you again for taking the time to bring this to our attention. Fernanda Sosa Support Services Technician Technical Support 24/7 - 1(800) 761-2990 Canadian Solar/EP Cube

…

On Tue, Aug 11, 2026 at 12:32 AM Bobsilvio ***@***.***> wrote: *Bobsilvio* left a comment (Bobsilvio/epcube#30) <#30 (comment)> Thanks Bill — that's the right channel for it, and I agree it's odd: the ECU status is exposed to owners while the PCS one is not, even though both feed the same web dashboard. If support asks for specifics, the exact request is to expose deviceOtherInfo.pcsStatus (and, if they're willing, pcsWorkStatus) on the owner-facing API — today it only appears under /v1/api/device/deviceInfo, behind the installer console login. The moment it shows up on the owner API I'll add the sensor. Meanwhile the corrected Gateway Status is out in v1.6.2, published as a proper release so HACS picks it up. Silvio — Reply to this email directly, view it on GitHub <#30?email_source=notifications&email_token=AFY6YCCIX7GXBVX3QGFGZVT5JLDY7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRVGAZTAMZZHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5250303984>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFY6YCHY3ETHNRFUZPZVPYL5JLDY7AVCNFSNUABFKJSXA33TNF2G64TZHM4TMNRYGUZDMMJRHNEXG43VMU5TKMBWG44TQNZXGEZ2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AFY6YCB3ITCLN3SQEODYPAD5JLDY7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRVGAZTAMZZHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AFY6YCBHBQRW5TOZDSMLUQD5JLDY7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRVGAZTAMZZHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>