issue with envoy meter measurements

Continue reading for more information about each type of problem. Actual Production that gets updated is available via envoy/api/v1/production however. If some of your AC Batteries have stopped reporting to the Envoy, youll see a message like this: If this occurs, you can follow the same troubleshooting steps for when microinverters have stopped reporting. What about 3-phase systems? If you are not sure how to meet these requirements, please contact api@enphase.com before you launch anything. In general, a Meter Issue indicates a system where on-site maintenance may be required. For the best experience on our site, be sure to turn on Javascript in your browser. 0000017430 00000 n These come from mainly 3 pages (excluding Envoy running <3.9 firmware), I would propose removing the original consumption parameters and adding additional parameters (lets prepend them in this example with metered_*. This has to either be an issue with where the consumption ct clamp has been installed, its orientation (arrow direction) or with a software setting on the envoy or a combination of all 3 possible causes. Automatic: When CT's are not enabled this is shown on the envoy/home page so it should be possible to automatically scrape the status of whether CT's are enabled or not. Envoy Status It is important to understand these differences when installing Envoy CTs. Maybe this is only of interest to me. Compatible changes do not result in a change to the version number. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details If there's voltage over 0.2 volts in any wire or connection, check for corroded, damaged or loose wires. Enphase seems to have a bug where they sum the amperage values for each phase and then multiply that by 240 to get VA. That's wrong and results in a VA value for TOTAL CONSUMPTION that's upwards of twice what it should be. Some batteries have stopped 3 0 obj I would also prefer if the timestamp of when the values were updated can be added, e.g. 0000033107 00000 n Valid values for datetime_format are iso8601 and epoch. 0000023653 00000 n Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? See Andrew Mitchell's Enlighten Manager Mastery video for a visual walkthrough of CT troubleshooting using Enlighten Manager. Fyi: There exist 3 different Envoy-S models: I have the Envoy-S Metered Multiphase (EU) SKU: ENV-S-WM-230. I'll have to look into this one a bit. When this parameter is provided, the returned JSON is wrapped in the callback. @atTD+JNE\:R By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. Also would need to check this behavior on newer firmware such as D5.0.49 (77afa8) to see what happens when metering is not setup and if the /production.json page returns valid data or not. The installers could have put it on the wrong leg. Yes the original bug in envoy_reader has been fixed. My /api/v1/production/inverters inverter data is already properly read and output by envoy_reader (I can see the values in Home Assistant). I'm following the current convention that was previously coded. @jesserizzo What do you think about moving all of the production polling to /api/v1/production and only use /production.json for metered production and consumption data? If the system doesnt have any revenue-grade meters installed, the response includes an empty intervals array. But there is not a lot of information about it there, apart from the fact that the warranty on the Envoy monitoring hardware is only 5 years. I could do some more research into the Enphase monitoring system, but that would take time and effort and Im a busy person. Ive got places to go, people to avoid, and shoes to nail to my horse. meter types, electrical connections) can vary across Australia. There is a limit to the number of systems that can be returned at one time. When using Envoy S without having CT's enabled then production data in envoy/production.json is NOT updated. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. You signed in with another tab or window. 0000154881 00000 n If these are zero than poll data from the other production page. I wonder if that is why your blue bars are labeled production but look like they follow a consumption pattern? I have assumed it was 'Voltage and Current Metering' using the ohm's law variables (P = EI), so EIM. 0000033020 00000 n Energy Measurement in Split-Phase Systems Using This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. A difference of 1 Watt, which may be caused by a rounding error, or by a small difference in moments of measurement. Then change it so any polling of the original production parameters only come from /api/v1/production. Have you tried flipping the CTs 180 degrees? When metering gets turned on /api/v1/production will switch over to metered values and will no longer have access to the history in the inverter data. Handle Envoy S (and Envoy IQ) without CT's as 'endpoint_type' "P" instead of 'endpoint_type' "PC". @OllemGit Would it be possible for you to verify this? Is it correct that you have only one single CT for consumption? Envoy-S or IQ running D5.0.49 without Metering Enabled, Envoy-S or IQ running D5.0.49 with Metering Enabled, Envoy-S running D5.0.49 without Metering Enabled and the /production.json page does not contain Production or Consumption keys. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. Application plans have minute and month limits. My solar installer connected only a single phase to power the Envoy, while all three phases L1, L2 and L3 can be connected. I'm wondering if someone with a functioning pre-IQ envoy could browse the production json value and post your results. When the filter is reference, both reference and other_references are searched. Installing the Enphase Envoy-S Metered Queries on system_name and reference are case-insensitive. Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. : @rct the scraping blog was where I got that URL. I use Envoy S but without any CT's installed. GMC Envoy Speedometer Not Working: Causes + How to Fix => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's Enphase Consumption Monitoring CT for Envoy - Solar (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? 0000078331 00000 n Yeah hopefully it'll make it into the 0.119 release! (Maybe you are mistaking with the cloud API's update frequency?). Examples in this documentation exclude the API key and the user_id for clarity. Then a question, does the api return the eim values that is got from the envoy even when the activeCount = 0? 0000196664 00000 n The heating system is just resistance heaters on that car so it's like a giant toaster oven. It seems the the values are almost the same and they are both updated every 5mins. I've connected them using Enpase IQ7+ micro inverters and bought also a Envoy-S Metered with them to read out the production statistics.

Bellway Homes Wimborne, Is Brenda Kerrigan Still Alive, Articles I