No.
As you can see I also use the Homewizard P1
SHS v12.10.1:
Pro2026 v12.10.1:
Homey app, tested both v9.6.7.1869 & v9.7.0.1876 (Android)
SMA app v2.8.1
HW app v3.12.0
.
Similar phenomenon:
Athom pointed to the Homewizard app some time ago, when the energy tab (or the app) crashed after users had added more than one Homewizard home batteries.
In the end it appeared to be a bug in the Energy tab, but it’s not explicitly mentioned in the firmware changelogs (‘fixed various bugs’).
For testing purposes, what are your settings in the Homey Energy tab, i.e. prize download from where 60/15 minutes etc?
Hi Jorgen,
My provider uses 60 minute pricing.
Not sure what you mean by “etc.” 
I didn’t change anything else in the E-tab AFAIK.
I have no Home batteries by the way (a while ago, using multiple Homewizard batteries made the E-tab crash), but I did add a virtual battery per Home Assistant.
If I only add my SMA energy meter and inverter as devices and exclude them from Homey Energy in advanced settings the Homey gets stable. Keeping them in Homey Energy the Homey crashes completely with unknown reason as error.
I am using this SMA app on my Homey and TL9000 inverter. Working fine.
However I run into a problem with the power limit setting adjustment. I have a flow reducing power when power price gets negative.
When opening the flowcard on my phone to adjust the power limit value it says something like: there is a 1000 changes limit and to protect your SMA device only 1 change per 20 hours is allowed.
This effectively makes this flowcard unusable. Price = high = high or no power limit. Price = negative = aggressive power limit. This can even change a few times during the day (eg clouds).
I also notice this as I changed the power limit values and the inverter does not seem to react.
What are the true facts? Am I misunderstanding something? If so why do the power settings not adjust?
Maybe read it again. It’s not related to this app:
The flash memory of the inverter can be destroyed by too many parametrizations in specific sections.
This event is triggered to protect the inverter hardware by blocking further parametrization.
The event is triggered after 1000 parameter changes. Once triggered the parameter changes are limited to 1 change per 20 operation hours. This is to protect the hardware from final damage.
Example: If the inverter counted 40 operation hours after the event, then 2 further parameter changes / settings are possible.
The number of changes was calculated for the complete lifetime of the inverter.
The flow card is usable just fine, only the inverter takes max 1 change each 20h once you’ve changed the parameters over a 1000 times (power limiter being one of the parameters).
So, Only after you somehow managed to change parameters over a 1000 times, a protection mechanism gets activated, in order to protect your inverter becoming useless way before its expected EOL, and therefore it limits the amount of changes to 1 in 20 hours. Any parameter incl. the power limiter is a change.
This sounds like the inverter cannot be repaired by replacing the flash memory, which is quite peculiar imho
I would not limit the power more than 1 time a day when prices dive below -€0.16 that day.
How many days will that be annually? 20? 10?
Let’s say 20: in that case the power limit gets changed 40 times a year.
1000/40 = 25 years
.
Can’t relate. If it works when testing 20h after your post, you might have hit the 1000 changes limit.
Peter, many thanks for your extensive answer.
I did double check the SMA Tripower manual - no reference to limitations for power setting adjustment. The Modbus manual does mention restrictions, however NOT for grid management services such as limiting the nominal PV power. From EDMx-Modbus-TI-en-16 | Version 1.6.
**EDIT: When using Sunny Portal online and checking settings I find there are multiple power limiting settings. The app should use the System & Device control level, NOT the Device itself which may use the flash memory. I am afraid the app is using the wrong adjustment.
With a different control parameter there are NO adjustment counter limits. I have sent the developer a PM requesting an updated control method.
Not related to this app? You have the text and I found it is under the i symbol in the flowcard so within the Homey app. I did not notice before. This particular statement is true if writing to the flash memory to adjust te power setting. I see no hard 1000 cycle limit in SMA manuals, but it must come from somewhere that is why I think there is some counter in the app.
YW, Erik.
Please discuss with Richard. The way I read the flow card info is, Richard tries to warn app users about the apparent possible restrictions of (certain) inverters. But only Richard knows.
It can be somewhat more clear 
No reaction yet from Richard.
I have done some research using MODBus docs from SMA and found the power limit registers probably are:
SMA has done a amazing job to hide the details and which register to use for what. I am by far not an expert but I find it hard to believe they sell expensive inverter kit with docs that do not explicitly show parameters/registers with cycle limitations.
Using the Homey MODBus app I should be able to write the above registers to limit the power as calculated using a Homey advanced flow.
Getting the MODBus app setup is fairly easy, ID = 3, port 502 with correct IP address. After you need to write the correct format, something I need yet to figure uit. Perhaps just decimal. To be continued. But it is good to know that if parameters are missing from the SMA app you can use MODBus to complement.
Look at post number 455 to 461 above.
You find settings for homemanager 2.0 to anable zero export.
@Peter_H69 thanks for your hint and pointing to these posts. So my cycle limit “problem” did already surface. I see there is a Modbus register list from SMA with exclamation marks flagging cycle limits. I have done my best to find such it but missed it.
I do not have the Sunny Homemanager 2.0. I intent to use the Homewizard P1 + Homey to do more or less the same as the Homemanager, sending dynamic power limit instructions either through the Modbus app, or through Richard’s SMA app (preferred).
I hope Richard is able to make 2 new flow cards with the correct volatile register address and parameters. The current one can stay but with a more clear text such as semi-permanent power limit card. I overlooked the info comment on the card when I put it in the flow.
Btw I have immediately disabled the flow using the current version of the power limiting card.
In relation to my posts above, the bugfix delivered for Insights in firmware version 12.12.0 seems to fix my issues with Homey crashes that was introduced with the 12.10.0 firmware in December.
I am migrating my old Homey 2019 to my new 2026 Pro. On the old one I used a battery device, with the same IP as my inverter, enabling me to read the battery charge status and use it in flows.
When trying to add a battery on the 2026 it does not find the battery but says “Omvormer Toevoegen” or add inverter and asks for an IP address. The when entering the address of the inverter (like I did on the 2019) there is no further reaction from the app.
I can use the inverter device of the app, but that does not give me any battery information.
My problem on the Homey Pro 2026 was partly solved after some experimentation.
I removed my inverter from the devices. I than specifically added a battery device. The device was not found, and I was prompted for an IP. I entered the IP of my inverter (the battery does not have an IP) and the inverter appeared in devices.
The difference now however, was that I got the battery state of charge in the data pane, and in the available card.
I hope this workaround also works for others!
Good morning all,
I’m trying to get an answer here from someone that has encountered this before (hopefully!)
We are trying to get a easy data overview from quite a large SMA installation.
Strange part is that we are having difficulties connecting all SMA Inverters stationed at the site, but the Sunny Island 8.0 inverter clusters are integrating seamlessly.
All modbus TCP is enabled on inverters (when using modbus polling we get data).
We have the following inverters we would like to add;
4x Sunny Island 8.0H battery inverter (working!) - Modbus adress 1 tm 4
These are not willing to be added:
STP6.0-3AV-40 - Modbus adress 10
STP10.0-3AV-40 - Modbus adress 11
STP-X 25 - Modbus adress 12
STP 25000TL-30 - Modbus adress 13
STP6.0-3AV-40 - Modbus adress 14
STP6.0-3AV-40 - Modbus adress 15
STP6.0-3AV-40 - Modbus adress 16
STP 20000TL-30 - Modbus adress 17
STP 15000TL-30 - Modbus adress 18
STP 20000TL-30 - Modbus adress 19
STP 25000TL-30 - Modbus adress 20
STP4.0-3AV-40 - Modbus adress 21
STP4.0-3AV-40 - Modbus adress 22
This is a complete off-grid situation at one of our projects. Controls are done by Data Manager M and derating is done with frequency shifting. This is only being used for simple monitoring of visitors and park manager.
Would be nice if we can get this to work 
P.s.
Homey is in 192.168.31.xxx VLAN and all inverters are in 192.168.32.xxx VLAN
Battery inverters are integrating within the same settings so we are sure Port 502 and routing is working.
Just to confirm that we have found the solution (if someone else is wondering)….
We have to set each modbus adress to 3 in order to add the inverter to Homey.
Different IP adresses are avoiding conflicts.
Hi Richard,
I have a question/problem.
My system are 2 inverters, one stp20tl30 and a stpse8.
Today I added a byd hvb battery to my system.
Now the status indicator is not showing the watts pv yealt anymore, its showing the watts pulling from the system to charge the battery.
Is there a way to change this back to pv yealt?
grts Peter
