Yeah, I published the test version too soon, too fast….
Try this: Test 2
Thanks for the quick fix! Unfortunately I cannot connect via Homey but can via Python API call.
It could be related to one of two issues I have here:
a rather bad Wifi signal since the last firmware update (I’ll address this in the next 1-2 weeks)spotty / bad weather → the inverters (and thus wifi connection, etc) are only online when there’s enough solar power generated
I’ll try to rule out wifi and test under good weather conditions. I’ll also try to figure out of it’s a firewall issue or sth. But the connection from my laptop works so I don’t think it is that.
However, how could I troubleshoot the connection issue for you? Do you use port 8050 for the API call (I can only enter an IP so couldn’t check if that’s the issue).
// Edit: Quick question / idea: since Python is in fact coming to Homey at some point in 2026, should we wait and use the half-official python module? I’d love to see this sooner rather than later, but I don’t want to waste your time when this would be so much easier.
//Edit2: Added another Wifi AP outside and can connect to both my inverters now via Python. Everything works really fast. So I’m ruling out weather and Wifi. Trying to ping it from homey via SSH sandbox but it won’t let me connect so far. I’ll try again tomorrow and hope it’s just a download issue.
Hi Steve, I already mentioned that it probably wouldn’t yield results. Please send me a diagnostic report. I’ts impossible to test the software for me, since I don’t have EZ1 converters.
And yes, I used port 8050. If Python is available for Homey, I think that it won’t integrate with the current app. It would be nice if the app supports multiple converters.
And as I have little experience in coding in Python, there will also be a learning curve, so it will take time to develop the app in Python. Although, with copilot…
Sorry for the delay, had to remove the wifi access point again. Now it’s installed properly and the testing can begin. 
Here’s my diagnostics report from today (tried both my inverters, so you should see at least 2 connection attempts): 0e469c53-7a09-450f-adcf-e5a8092d72f3
About python: don’t worry about it. If it works in JS/TS that’s totally fine.
Best,
Steve
Now I can see that what is returned from the converter (yes, there is something returned) has to be processed in a certain way. So I will look into that.
Python was released a few days ago, haven’t done anything with it yet, first have to read the sdk docs.
Updated the test version, please try and see what happens.
Unfortunately, nothing yet. 
Diagnostics: af9955f3-dd31-489e-af6e-5cd4bcc5a354
When you enter the ip address from the ez1 in a browser, do you get a webpage? The response I see starts with http.
Yes! If I type in the IP followed by the port number, I get: „Nothing matches the given URI“
If I type in „http://{ip}:8050/getOutputData“ I get:
{“data”:{“p1”:0,“e1”:0.00000,“te1”:397.94920,“p2”:0,“e2”:0.00000,“te2”:401.00480},“message”:“SUCCESS”,“deviceId”:“E07010029419”}
But that’s also documented in the API doc starting on p. 7. 
„After EZ1 device switch to Local Mode, EZ1 device will startup the internal Http Server“. If I’m not mistaken the calls return JSON values.
Is your code visible somewhere? Maybe I can help after all as I’ve dealt with JSON before. How hard can a few loops in JS be, right? 
Yes, I know that’s in the API doc. But the diagnostic report you send me, shows that the returned response is not JSON, and starts with HTTP:
The code you can find on Github
I’d like to have the full response from the EZ1, so I made a test version for the EZ1. You can find it here. Run it, it won’t work, and send me the diagnostics
Hey! Moved this to a private conversation as to not spam any followers of this topic any more. Hope that’s ok (for everyone)?
