Great! I see the error isn’t being handled properly. I’ll fix that in a new version.
New updates in production:
Version 1.2.6
Detecting the device’s availability. If the device’s API doesn’t respond for 5 calls, the device is registered as offline. Once the API or IP address/Port is corrected, the device is reported back online.
Version 1.2.5
An extra option has been added under Settings → Maintenance: toggle the Light setting and the Bypass Socket setting.
This settings takes about 10 to 20 seconds on the battery. Once pressed the maintanance buttons are disabled for 10 seconds.
Screenshots (dutch):
New version in production (v1.2.3) :
Changelog:
1.2.3
8 feb 2026
International support for adding the Powerflex 2000 Eco device has been fixed.
1.2.2
8 feb 2026
International support for pairing new devices has been added. A minor bug in the errorHandler has also been fixed.
1.2.1
6 feb 2026
It is now possible to control the Powerflex from Homey. Control flow action cards have been added for: 1. Retrieve manual update 2. Set operating mode (Self-sonsumed/Real-time/Scheduled) 3. Set State / Power / SOC values. A few important notices: - It takes a moment for the changed operating mode to be visible in the Indevolt app. You will see this faster in a P1 monitoring app. The same applies to the charge status / power / SOC settings. - If you have a cluster setup, only set the value for the Main (or Master). The Sub (or Slave) will follow these settings. Further code cleaning has been done.
———————– UPDATE 12-3-2026 ———————–
New version in production
V1.5.1
- New functionality has been added for Powerflex and Solidflex Hybrid and Eco. You can now set the maximum AC output power using a flow card and monitor this value.
———————– UPDATE 2-3-2026 ———————–
New version in production:
V1.4.3
- Added “Daily PV Production” feature for the Powerflex 2000 Hybrid device.
———————– UPDATES Feb 2026 ———————–
New version in production
V1.4.2
- Fixed a bug on the driver of the BK1600 Device
- Added multi language support for all languages on the Homey platform
There are currently no more requests on the roadmap. Development is therefore complete for now.
Awesome!
Any chance we could get support for setting the “Feed-in Power Limit Setting” (1146)? Charging the battery at full wattage generates quite a bit of heat, and together with the temperature readout it can be used to automate the charging speed limit.
Not sure how it relates to “Inverter Input Limit Setting” though.
No problem, I’ll add it. But on vacation now so that will be in about 2 weeks.
Great, thanks!!
Or it is 1138 Inverter Input
Limit Setting?
I have looked into it. Based on your question, I also think you mean the Inverter Input Limit. This is also known as the Max AC Input. This value has been added, and a flowcard has also been added to set this value. Version 1.6 is currently in production with these options.
Reading further, I suspect the “Feed-in Power Limit Setting” is for mptt (solar) inputs indeed. Disappointing the documentation is so sparse.
The Feed-in power limit is the maximum power supply to the grid (i.e., what you add externally to the grid, in Dutch “teruglevering”).
Update 7-5-2026
Found a small bug in the Flex 2000 Eco driver. Fixed it in release 1.6.1
I tested it and it’s working fine. However, the Indevolt configuration is a bit unclear: in cluster mode, the ‘main’ setting should reflect the total cluster power, meaning it should allow for a capacity of up to 7200W.
Good point, but that of course depends on whether there is a cluster at all and the number of sub-batteries. I will look into whether it is possible to determine this dynamically. At the moment, there is no functionality to retrieve these values. So, the app currently doesn’t know how many batteries there are either. To be continued.
II’ve worked around it by referencing a variable instead of using the slide. It’s perfectly usable now, though mainly for more advanced users—but that’s probably for the best anyway.
Hi Menno, reading along. I have a cluster setup with one tower 10kW and one on 8kW, both on separate groups. So I would like to be able to charge and uncharge with max 4800W. It seems that with the mentioned variable one could work around the slider max of 2400W. Would this mean I could actually steer the two as a cluster with power in/out between 0 and 4800W? If yes, how would that work?
@rchu57 Any reason you’re not reporting the net-power usage to homey? I have a HW kWh-meter hooked up so I can see what they’re doing anyway, but for users without a separate meter it might be useful.
Also, for the cluster-setups, if Indevolt doesn’t report it directly you could consider adding a virtual device that does the clustering for the end-user in Homey – treating it as a single device combining values like SoC/temp/etc while it sends the commands automatically to the main/controlling battery.
Anyway, the app is working perfectly so far (finally got my stacks last saturday), so kudo’s 
Hello,
Thank you for your reply. I do not see a value in the API that allows you to read the battery’s power consumption. The charging and discharging capacities are linked to the relevant parameters in Homey. The battery naturally consumes some power itself, but it is of course intended as a storage device. Perhaps I don’t understand you correctly; if so, please provide some additional explanation and specify exactly which API value you would like to see linked to which Homey parameter. Thanks in advance!
Hello,
With use of a variable and flows or advanced flow with calculation you can manually set these values. The main battery value responds as the max cluster value, the sub batteries have there own individual values. Please only use if you know and understand the risks. Of course at your own responsibility.
Both suggestions is basically so we don’t need apps like this:
But on the other hand… we could also just use that app 
Hi, it works perfectly; I wasn’t aware I could use the variable above slider-max of 2400W. Now I can start thinking about combining EV-charging, battery charge/dis-charge etc. Thanks for help!
