hanks for the review, and for flagging the overlap with Michal Stráník’s GoodWe app — I reached out to him directly about it. His app does local Modbus/LAN access, which is genuinely a stronger approach when it’s available; mine is cloud-based via GoodWe’s SEMS+ API, which is the fallback that still works for inverters/dongles where local access isn’t supported (a real, non-trivial subset — GoodWe’s own local protocol depends on inverter firmware version, confirmed against multiple real installs). I see the two as complementary rather than duplicate: cloud vs. local is a genuine technical difference, not just a rebrand.
I’ve also addressed the other feedback: [description/images/icon — regenerated icons at all required sizes, description text updated]. Version 2.3.0 is ready with these changes plus a cloud-API migration (GoodWe is retiring the old SEMS Portal) and a fix for a bug where a bad API response would freeze the Energy tab silently instead of showing an error.
Happy to adjust anything specific you’d still like changed.
Ik heb hetzelfde probleem als eerder door anderen gemeld. Plots geen verbinding meer via Homey naar de Goodwe, via de Sems+ app en website werkt het wel. API update vanuit GoodWe waardoor de Homey verbinding niet meer werkt?
Modbus-koppeling in Homey lijkt niet te werken (ik ben er niet goed bekend mee of dit een hardware ding is van mijn GoodWe, of dat ik de port of iets anders fout kies).
De reguliere koppeling via de server, ik heb opnieuw het apparaat toegevoegd. Behoorlijk complex om in de nieuwe sems+ omgeving je systemID te achterhalen, maar het is gelukt. Uiteindelijk resulteerde het in hetzelfde, namelijk geen verbinding.
De Koelman app hierboven geprobeerd, maar kom daar niet door het checken van het SEMS+ account heen.
I just shipped a fix (should reach Test/Live shortly) so pairing can no longer get stuck on “finding your station” indefinitely — there’s now a visible “enter station ID manually” link from the start, and the auto-detect step times out after 20s instead of hanging. That should at least get you past this specific screen.
That said, I don’t yet know the root cause of why it hung in the first place, and I’d like to find out properly rather than just paper over it. Could you both do one thing:
Send a Diagnostics Report from the GoodWe SEMS app settings on your Homey (Settings → Apps → GoodWe SEMS → “Send Diagnostics Report”), ideally while the problem is still happening rather than after retrying — that sends me the actual recent app logs, which is the only way I can see what’s really going on at your end.
@Olivier_Sauer, a few extra questions for your case specifically (login failing, not just the station search):
Do you get any error message when it fails, or does it just hang silently like Xa4’s case?
Roughly how long did you wait before giving up?
Which Homey are you on — Pro 2023, Pro Mini, or Cloud/Bridge?
Hopefully following this thread to get the goodwe data back. I tried too but was also stuck on this getting station id page.
If needed to put in manually, where can I find this needed url or so? I have been searching arojnd on the Sems+ portal website but cannot find anything. Not in the url nor in any settings.
Click into your station (Station List → your station → Station Details)
Look at your browser’s address bar. The URL looks like: https://semsplus.goodwe.com/#/station_monitor/station_detail?eyJzdGF0aW9uaWQiOiI...
Copy everything afterstation_detail?
Go to any free base64-decode tool (e.g. base64decode.org), paste that string, and decode it
You’ll get something like {"stationid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","appType":"WEB"} — the stationid value (the UUID) is what the app’s manual station-ID field wants
I’m also working on a fix so the app finds this automatically for more accounts instead of requiring this at all — will update here.
This didnt work anymore for me. In the sems+ app and website it is no longer shown in the url. Found it only through the developers tools in the browser.
I’m aware that the GoodWe Cloud integration has recently stopped working due to changes on the SEMS portal side (likely related to API updates, WAF/Cloudflare restrictions, and session handling).
I am currently investigating the issue and actively working on a fix to adapt the driver to these changes. I’ll share an update and push a test version as soon as I have a working solution ready.
