Hi, just added the test version of the app to my homey. But I can’t find the system ID. In the manual you advise to login in sems portal and then go to details,… but I cannot login to sems portal anymore and when I login to the new site Sems+ I can’t find a page called details. Can you help me?
Please try this:
Thanks! It added the inverter again to Homey!
It’s saying ‘no response’ at the moment, but I guess that’s because the inverter is asleep at the moment (23:22 here, so dark)
Hope it will work tomorrow, thanks for the quick response! Very happy with it!
just a question, will there be an update in the near future which will give users the option to shut down the inverter and put it back on again (and use these options in flows)
Again thanks 
Hi,
Glad to hear the inverter was added back successfully! You are right about the “no response” message — when the sun goes down and there is no PV production (or battery activity), many inverters enter a deep sleep/standby mode and stop responding until the morning.
Regarding your question about shutting down and turning the inverter back on via flows:
Unfortunately, this won’t be possible in the cloud version of the app.
Here is why:
-
Cloud API limitations: The public cloud API provided by the manufacturer is strictly read-only for third-party integrations. It exposes telemetry data (power output, energy totals, voltages, battery SOC), but does not provide writable endpoints to control the inverter’s power state.
-
Cloud latency & reliability: Cloud commands typically suffer from delay (often minutes) and rate limits, which makes switching power states in real-time automations unsafe and unreliable.
-
Safety & manufacturer restrictions: Switching off high-voltage PV equipment remotely via a public cloud endpoint is generally locked down by the manufacturer for safety and grid-compliance reasons.
Direct control like switching modes or limiting feed-in is technically only viable via a local Modbus connection (RS485 or Modbus TCP), where you have direct write access to the holding registers without going through the manufacturer’s cloud.
Thank you for understanding, and I hope everything wakes up and reports nicely in the morning!
I would recommend creating a new device and then deleting this one.
What did you try many times? Try to remove current and create it again.
Ja hoor het werk . Je hebt geweldig werk geleverd. Dank je wel.
Currently on V1.15.0 TEST, I’m getting:
“Cannot read data from GoodWe cloud: dict key “outputV” not found”
Both on the old device and on the freshly added.
Using the stationid as SystemID.
Inverter: GW3000-XS
Please try new version.
same error
Perhaps an idea to check which variables you have access to from the API first.
Regarding the outputV issue, having direct API/account access to reproduce it would be ideal, though I understand that sharing credentials can be sensitive.
At the very least, could you let me know the exact inverter model(s) you are running?
I can try to deploy a blind fix with a fallback in the meantime, but without seeing the exact response payload, I can’t guarantee it will cover everything.
Important: Please do not post any credentials or sensitive information publicly here. If you’re willing to share test access or raw JSON data, send it strictly via Private Message (PM).
I have a Goodwe GW3000D-NS
A new test version is now available with a fallback for the missing outputV field:
Please install it and let me know if it resolves the issue for your setup.
If it still fails, please send a Homey Diagnostic Report directly from the app so I can see the exact stack trace:
-
In the Homey app, go to More (…) $\rightarrow$ Settings $\rightarrow$ Apps
-
Select GoodWe Inverter
-
Tap the gear icon (
) in the top right $\rightarrow$ Send Diagnostic Report -
Post the generated Report ID here (or send it via PM) along with your inverter model.
Thanks for helping test this!
this one works 
thanks
