External integration request for ISYPOWER Energy Tracking

Delivered features
1

My solar panels and battery are controlled by the ISYPOWER Cloud app, and I would like to integrate them with my Gladys Assistant.

On Home Assistant, I found this:

and the following information:

  1. Authentication:
    • POST call to the login endpoint (e.g., /api/login on Isypower Cloud servers).
    • Payload: { "username": "your_email", "password": "your_password" }.
    • The API returns an authentication token (JWT Token) to be included in the headers (Authorization: Bearer <TOKEN>).
  2. Data Retrieval:
    • Discovery of the plants/systems associated with the account.
    • Retrieval of telemetry metrics from your installation (instantaneous and indexed).
  3. Refresh Frequency:
    • No need to query the API every second: the ISYPOWER box sends its data to the cloud every 3 minutes. Polling every 2 to 3 minutes is therefore recommended to avoid account banning / rate-limiting.
2

I can take care of it

3

Here is the external integration to follow a solar installation from Isypower (Materfrance, formerly Izypower) in Gladys.

What it does

It connects to Isypower Cloud with the application’s email and password, and reads your power plants, micro-inverters, and batteries every 3 minutes (the rate at which the boxes send their data). This is a cloud integration: the data goes through Materfrance’s cloud, just like in the application. There is no native Isypower integration in Gladys.

Features

  • One device per power plant: solar production, home consumption, exchange with the grid (positive when buying, negative when selling), battery levels and power, and cumulative indices: production, energy bought from the grid (which powers consumption and cost in Gladys), energy sold, energy stored and restored.
  • One device per battery: level, stored energy, power, temperature, emergency outlet, and the control mode (intelligent, manual, schedule) and manual mode (standby, charge, discharge) in dropdown lists.
  • 3 widgets: « Solar Installation Â» (power + curves of the last 24 hours), « Energy Balance Â» (day, month, year, since installation), « Home Battery Â» (with buttons to change mode and set minimum charge).
  • 4 triggers: the battery is charging / discharging / stopping, a device goes offline or comes back, firmware update available, power plant silent for 20 minutes.
  • 3 scene actions: change a battery’s mode (with power in manual), set its minimum charge, read the energy balance of a period.

Scene examples:

  • Every evening at 9 p.m. → read the day’s balance → send the summary on Telegram (« Home, today: 9.8 kWh produced, 6.1 kWh consumed… Â»).
  • Start of peak hours → battery in manual discharge at 800 W; end of peak hours → back to schedule.
  • A micro-inverter offline or the power plant silent → notification.

Installation

  • From Gladys store: available within the day, pending indexing.
  • Or from the repository URL: https://github.com/William-De71/gladys-isypower.
  • Gladys 5.2.0 minimum.

Configuration:

  1. Enter the Isypower Cloud email and password, save.
  2. In « Discovery Â», create the power plant and batteries.
  3. Add widgets and create scenes.

Screenshots

The three widgets (generated illustration, not a screenshot)

Generated illustration from the integration code, not a screenshot.

Real screenshots coming soon

I don’t have an Isypower account: real screenshots (configuration, discovery, devices) will be added as soon as a user tests it.

Known limitations

  • Never tested on a real account: I don’t have an Isypower installation. The API is not documented; it is used as done by the Home Assistant izypower_cloud integration. Only the connection error responses have been verified on the real server.
  • The direction of the battery power from the power plant (positive when charging) is deduced from the Home Assistant integration: to be confirmed.
  • Not yet managed: individual battery modules, smart meter injection limitation, charging stations (EVSE), emergency outlet and calibration in writing, the application’s fast « live Â» mode.
  • A slave battery follows its master: only the modes of the master (or an autonomous battery) are modifiable.

Feedback
Thanks in advance for your feedback and don’t hesitate if something is missing.

4

Thanks, I’ll install it tomorrow morning and I’ll get back to you later in the day when I have some stats.

5

Who would have thought just 6 months ago that full support could be available just 1 hour after the request!!.. This era is crazy… completely crazy!! :sweat_smile:

6

Yes, you’re right, it’s completely crazy the job being done right now…

7

Will, here is the test log

[2026-10-18T06:43:26.802Z] [INFO] Starting the Isypower integration 0.1.0...
[2026-10-18T06:43:27.004Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-10-18T06:46:48.507Z] [INFO] Configuration updated
[2026-10-18T06:47:00.505Z] [INFO] Isypower diagnostic 1/2: {"version":"0.1.0","timeZone":"Europe/Paris","today":"2026-10-18","interval":3,"account":true,"authBlocked":false,"readAt":"2026-10-18T06:46:49.033Z","stations":[{"id":"25273","capacity":2400,"created":false,"info":{"lastUpdate":"2026-10-18T06:45:05.000Z","power":{"production":0,"consumption":1217,"grid":1217,"battery":0},"soc":9,"production":{"day":0,"month":29.45,"year":782.51,"all":782.51},"deviceTypes":{"all":"All","meter":"Meter","battery":"Battery"}},"today":{"consumption":10.62,"selfConsumption":0,"gridImport":9.11,"gridExport":0,"batteryCharge":1.93,"batteryDischarge":1.51,"selfSufficiency":0,"selfConsumptionRate":0},"totals":{"consumption":4824.04,"selfConsumption":338.05,"gridImport":4091.95,"gridExport":9.37,"batteryCharge":435.09,"batteryDischarge":394.04,"selfSufficiency":98.8,"selfConsumptionRate":7},"equipment":[{"type":"meter","typeName":"Meter","online":true,"firmware":"1.1.9","cluster":0},{"type":"battery","typeName":"Battery","online":true,"firmware":null,"cluster":1002}],"batteries":[{"created":false,"modes":true,"live":{"soc":10,"energy":0.201,"temperature":27,"state":"standby","chargePower":0,"dischargePower":0,"offGridPower":0,"modules":0},"settings":{"controlMode":"calendar","manualMode":"charge","manualPower":800,"minSoc":10,"hasMeter":true,"maxCharge":2000,"maxDischarge":800}}],"upgrades":1}],"shapes":{"stations":{"top":["app","code","data"],"data":["countId","current","maxLimit","optimizeCountSql","orders","pages","records","searchCount","size","total"]},"info":{"top":["app","battery_power","battery_pv_power","battery_soc_kwh","code","data","extraData","grid_power","ev_power","consumption","battery_soc","hasEv","subDev","hasMeter","deviceTypes","grid_status","hasBattery","hasVm","lastUpdate","power","signal","status"],"data":["accountName","address","afterSaleContactId","allSum","authority","country","countryTimeZone","createBy","createTime","createTimeStr","createUserName","deleteTerms","deviceCount","energyVal","favorite","field2","hasAuthorized","hasBattery","hasDelete","hasEdit","hasMeter","hasSubDev","img","installationPosition","installedCapacity","installer","lastUpdate","lastUpdateStr","latestFeedback","latitude","longitude","markForDel","minRssi","model","monthSum","needUser","onlineState","operatingState","orgId","orgName","ownerUser","ownerUserId","power","powerVal","signal","stationName","stationsId","status","syncDate","timezone","timezoneId","todaySum","updateBy","updateTime","updateUserName","yearSum"]},"report":{"top":["app","storage_in","code","cover_rate","data","storage_in_rate","meter_energy_n","meter_energy_p","energy_self_rate","consumption","ev_rate","meter_energy_n_rate","ev","total_consumption","storage_out_rate","energy_self","consumption_rate","storage_out","meter_energy_p_rate","energy","production_rate"],"data":{"array":4,"item":["data","key","lineType","name","unit"]}},"report_all":{"top":["app","storage_in","code","cover_rate","data","storage_in_rate","meter_energy_n","meter_energy_p","energy_self_rate","consumption","ev_rate","meter_energy_n_rate","ev","total_consumption","storage_out_rate","energy_self","consumption_rate","storage_out","meter_energy_p_rate","energy","production_rate"],"data":{"array":6,"item":["data","key","lineType","name","unit"]}},"devices":{"top":["app","code","data"],"data":["countId","current","maxLimit","optimizeCountSql","orders","pages","records","searchCount","size","total"]},"battery":{"top":["app","code","data"],"data":["avgSocKwh","avgSoc","chargeData","consumptionPower","pvList","soc","offGridPower","socTemp","dischargeData","solarPower","pvPower","socKwh","items","batteryPower","onlineState"]},"battery_settings":{"top":["app","code","data"],"data":["mode","intelligent","manual","calendar","calendarV2","calendarName","offGrid","fullCharge","power","httpControl","min_soc","allBatteries","isClusterAvailable","hasMeter"]},"upgrades":{"top":["app","code","showAll","data","showUpgrade"],"data":{"array":7,"item":["canUpgrade","cmd","currVerison","device","deviceName","deviceType","needUpgrade","newVerison","remark","sn","upgrading","versionLogs"]}}},"lastError":null,"failures":0,"requests":{"total":9,"logins":1,"errors":0}}
8

Hello,

A quick update: the Isypower integration is now running on my real installation with panels + battery, and I would like to contribute to the next step: making certain energy data accessible to HomeKit via Gladys.

I’ve started looking at the code with Copilot.

On the Isypower side, the SOC is properly exposed as:

BATTERY_STORAGE / BATTERY_LEVEL

On the Gladys HomeKit bridge side, I already see the management of Service.Battery / BatteryLevel for standard batteries, but no mapping for BATTERY_STORAGE.

I thought I would start with a very small POC:

Isypower Battery SOC → BATTERY_STORAGE/BATTERY_LEVEL → HomeKit BatteryLevel

Then, if it works, I will study PV production, home consumption, grid, and charge/discharge next.

Before modifying the Gladys core, is this the right direction in your opinion?

And what is the recommended method for developing/testing a modification of server/services/homekit when using Gladys in Docker on a Raspberry Pi?

I can test on my real Isypower installation and share logs/results if it can help.

9

Hi @Steph38230!

The ISYPOWER tracking is in the catalog: the external integration published by @Will_71.

You installed it, and @Seb.c confirmed it runs on a real installation. Production, battery, and the measurements exposed by the cloud are in Gladys, so in the graphs and scenes.

I’m moving this topic to « Delivered Requests Â». If there’s still a case that doesn’t match, open a new topic: it will be easier to follow.