I have also still salderen.
but i want it to test it for 2027 ![]()
i thougt i could enter the value what i want to export in Wattage
Hi,
I just started to get serious with home energy management and found this app for my Enphase system which is really handy. I have a metered gateway with CT’s and the latest version of the app (1.5.2). However in flows I do not have the possibility to set ‘doelvermogen’ etc, I only have ‘turn on’ / ‘turn off’.
What am I doing wrong? It would be great to set production limiting to my own energy usage.
You’re not doing something wrong (probably
)
The app tries to detect what hardware is present and adjusts the available features accordingly. There’s probably something wrong with the detection for your specific combination (and history) of hardware.
The “Enphase Solar” device dashboard-page has indicators for what hardware/features are present (like “metered gateway”). What do they tell you?
If some of those indicators are wrong, please delete the device, re-add it and within 15 minutes send an App Diagnostic Report so I can take a look. Thanks for helping out!
Thanks for your quick reply.
On the dashboard-page ‘productiebeperking’ was on ‘nee’. I deleted the device and re-added it. That made ‘productiebeperking’ to ‘ja’. I checked in flows and there I have the extra options now.
Thank you.
Cool, problem fixed I guess. ![]()
I would’ve still liked to have know what went wrong in the first place. The reason I mentioned the 15 minute window though is because the App Diagnostic Report only sends me the last X verbose/debug lines (don’t know the exact number). So the next time something funky happens, please use the App Diagnostic Report within that timeframe. Thanks!
The above also goes for other users here who encounter a bug/something strange ![]()
I’ve come across a problem with the app.
It could no longer connect to the Gateway as of 7.35 this morning (UTC+1)
“not available
request to https://xxx.xxx.xxx.xx/production.json failed, reason: connect EHOSTUNREACH XXX.XXX.XXX.XX:443”
When trying to repair I get the error “Error: Unknown_error_getting_file”.
I’ve tried rebooting the app but that didn’t seem to work.
Just now at 10.54 it started functioning again.
So all is fine for now, but there might is a reliability issue.
PS. The official Homey Enphase app kept working without any hick ups, so its not the actual gateway.
@bramtops I can forward you a diagnostic if you want?
I’ve received the diagnostic report and looked it over, thanks.
What happened is that the gateway wasn’t reachable or wasn’t responding to polling requests from the app. This actually happens way more than you’d might think. The app has a 30-minute grace period before it marks the connection as actually lost to Homey. This would simply be the first time the connection wasn’t restored within 30 minutes.
Besides the usual causes (i.e. unstable wifi), this also happens when the gateway is ‘overloaded’; the ‘webserver’ on the gateway has limited resources. It might be that other app(s) were hogging the connection- and/or sessionpool. If this happens to often, try disabling other apps that are also polling the gateway – like the official Enphase app.
(I haven’t implemented the Homey repair function for this app yet, which is causing the “Unknown_error_getting_file” error, but the app will auto-heal/auto-repair anyway.)
Thank you for the quick response and explaining what probably happened. I’ve been running these apps next too each just to try and see both their accuracy, stability and functions. Maybe the day has come to disable the official Enphase app and reroute the flows.
Much obliged!
I’m reading this topic with interest, I have an Envoy S metered, only with version R5.0.55 which has no support for https. Is it useful to upgrade to R7/R8? Because R5 has unrestricted API access which for sure is gonna break in the R7/R8 releases.
So maybe you can build something you can choose between http / https? For me http is not a real issues, because the smart devices are on a separate IoT VLAN.