We are still waiting for the new official Homey app. (with power limit) Looking at @Doekse What’s the status? Is there any progress yet?
I Still use: https://www.soliscloud.com:13333
Is that a problem? Do I need to change it so https://v3.soliscloud.com:13333?
Same here, still using the “old" url, so not the V3.
Mine is working fine!
Oke, i have change the url to the new one ![]()
Hi,
I am using the app and would like to understand if it is possible to see the SOC of the home batteries through the APP.
In order to understand this better, I contacted Solis to see if they are actually publishing the SOC of the battery through the API and this is what they told me:
You need to use /v1/api/inverterDetail to retrieve the battery SOC.
We have updated our API tool. Please click on the Legacy button and then enter the Key ID and Key Secret. You will find the required details in the Inverter Details section.
You can also use this tool to view the source code and implement it accordingly in your codebase.
Is it possible to add the SOC on the inverter view, or is this something difficult?
install the beta app and add the battery.
Hello guys,
I’ve already searched here for answers but couldn’t find anything.
I managed to add my Solis S6-EH3P10K-H inverter to the Solis Cloud app, however, I don’t see my Pylontech H3 battery, which is connected to the inverter.
Am I doing something wrong, or is this simply not possible?
Thanks for your help.
Hello Tom,
The Solis app has a dedicated topic you’d use (like many apps):
Thank you.
Hello, can you please elaborate what you mean with the beta app? I’m having the same “issue” as Patrick and Tom. I have switched to the beta version of the soliscloud app on my phone, where I can see the SOC on the plant Home Screen.
Edit: i have a Pylontech battery.
@ Homey app store beta apps are described as “test” app.
TL;DR: add /test to the app’s app store URL, press enter, press “install”.
Should read:
You’ll find the test test version at the app page @ homey.app store >
Follow the link to “View changelog” >
Tap the orange “test” button to enable the test version install.
-With the version numbers, notice the “what’s changed” info-
(now you see why wizb0 hinted you to install the test version):
Now when you press “install”, it will install the test version.
→ never uninstall any running version up front; apps get updated/reverted without touching your devices.
→ to revert to the stable app version again, just install the stable version by following this link, if shown (if it’s not shown, it will always install the stable version):
The Test label is a bit odd, as I’ve almost never run into trouble by running test versions of apps (in almost 6y). But keep in mind it has a risk of causing issues.
That’s because app updates usually need to be verified by Athom. That can take some time (usually the next working day). When you publish the app (or update of an app), you can first publish it to Test. This will be published to the test channel instantly. However, when you want to publish it to Live (and there’s a significant update to your app), it needs to be verified by Athom first. Because they can’t ensure the security of an app they haven’t verified yet, it shows that banner to warn users that the app version might be unsafe.
Athom can’t test if apps are bug / error free imho, as they just don’t have all devices laying around. I think they (auto-)check the code for usual mistakes, and “nonsense” code.
Maybe I’m lucky, but I’d like say devs of the test apps I use, or have used, usually publish decent code, checked by Athom or not.
Only with “the great invention” of vibe coded apps we have to be more cautious, as it can cause working devices to malfunction with updates of their test versions.
They auto-verify code for small changes, those are then promoted to Live immediately after submitting for certification. Only the app manifest changes and new apps require a manual review. I don’t know if they only review the app manifest or the code as well, I think actual code review only happens with apps with the API permission, but I’m not sure.
This did the trick, thank you very much!
Thanks to everyone.
It looks like it’s working now.
Hi all. This app is still the app that Peter and I developed and released. It’s been a whole year since we handed the app over to a 3. party that Athom was in contact with.
We had mail correspondance and contact by phone, and still no new replacement-app yet.
Auch ![]()
Hi Kim,
This also describes the core difference between “official” apps and community apps.
Most community app devs care.
Excatly - I have contacted several official apps for missing features and I keep hitting the Homey support-ticket-wall. Shadow “official”.
ALSO I’m not a fan of “suggest feature” - because I kinda get flooded with feature request, when minimum is ok - if that makes sense.


