Yes, they have been installed in the app, see below. The ‘besturingstoegang’ hasn’t been updated since 2 months. The Gateway has been updated yesterday though.
Deleting device and re-pairing didn’t work.
So, I had Enphase enabling my Modbus, but still it says ‘Nee’ at ‘besturingstoegang’. Any clues?
Controller access (“Besturingstoegang”) is solely dependent on the account-type that’s being used. Modbus/CT-clamps are not a factor. A normal “owner” account will not give you controller access. You need an Installer or Maintainer account. Please refer to the startpost of this thread and read the stuff under “Instructions for getting Maintainer (Control) access to your Enphase system”.
If you already did that, and if you’re absolutely sure you’re authenticating in the app with an Installer or Maintainer account, send me an App Diagnostic after (re)trying the login with the correct account credentials. Put “account not recognized as installer/maintainer” in the description please.
For others monitoring this thread:
I’m currently working on a 2.0 release with support for the Enphase Battery (thanks to work done by @Niels ). Test versions for this release will come soon (1.9.x).
Heads up: in this release I’ll be refactoring a bunch of device drivers to make the internal structure off the app better for including more Enphase products. In 2.0 most existing devices will therefore become deprecated (but will still work).
- After granting access, right below that you’ll find a “PV system maintainer” pull down. Select your fake company there.
Unfortunately, no pull down menu to be found. Maybe my installer has blocked this option? Any workaround?
Thats a new one for me; you’re the first to report no PV system maintainer. I’ve look at my “Access control” page to be sure, and the pulldown is still there for me. Does that page list 2 companies under “Companies”. Its should mention your original installer plus your own fake company.
Hi Bram, metered IQ Gateway (fw D8.3.5169) apparently without production CT clamps, app 1.5.2, owner account. Even after deleting and re-adding “Enphase Solar” today, Metered gateway = Yes, power stays 0.5–3 W day and night and energy today = 0 kWh, while the inverters device shows ~150 W total at the same time (utility meter: 5.38 kWh yesterday). Diagnostic report: de76598c-90d9-4420-8d19-c1b265265390. Could the app fall back to the inverters sum when no production CT is active? Thanks!
Thanks for the report. I’m looking into what’s happening here and I’ll see if I can include a patch in the upcoming 2.0.
sorry, my mistake.
I misread “Een ander bedrijf toegang verlenen door het e-mailadres op te geven van een Enlighten-gebruiker uit dat bedrijf.” as add email address from the existing company only.
Just added my fake company now and installation went smoothly. Will play around now..
Hi, and thanks for the report. It looks like your gateway is reporting that it does have CT clamps, but they are not connected, so the app only reads the “noise” (0.5-3 W).
I’ve added an option “Ignore production meters” to the Solar device settings. During pairing, the app will detect both values, and if a large enough discrepancy is detected, it will turn this setting on for you. If you pair during the night, the app obviously can’t see this discrepancy and you’ll need to enable the setting manually.
This will be added in the upcoming 2.0 release (which is imminent).
Version 2.0 test is out now.
Changelog:
- This release reworks several internal systems for more reliability and future updates. Unfortunately some devices will have to be re-added.
- Adds Enphase battery monitoring.
- Adds animated energy flow widget (only for metered systems).
- Homey alarm support for inverter problems.
- Adds deprecation notices to timeline for older drivers.
- Adds French and German language support.
- Support for unwired production meters.
Battery support and the widget are copied and adapted from here, thanks @Niels!
installed it, not have to reinstall devices.
Added Battery now and added widget.
Thanks, let me know how it works for you!
FYI, the existing devices will still work for now. But you’ll get a warning message on your timeline when installing 2.0, and those devices will stop working in a future version.
