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. Envoy reader makes an assumption depending on the type of Envoy whether CT metering is being used. I have not done the math to calculate the cost savings for such a small battery (10 kWh) on the Ford. 9 kW solar, 42kWh LFP storage. Observation: metered values get truncated instead of rounded. Other than reducing http calls to the envoy device, is there another benefit to pull the production data from the two pages rather than one? It causes Home Assistant to not update after a couple of polls. Like I said I'm still thinking about it and weighing the pros and cons. metered_consumption wNow: 0.836 (gets truncated to 0). The darkish overcast looked like possible little snow storm coming. between the phases to allow the Envoy to communicate with all of the Enphase devices in the system. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. meter types, electrical connections) can vary across Australia. Active does not imply that the device is currently reporting, producing, or measuring energy. An explanation for the difference may be rounding errors or different time of measurement. EV owner since 2012. Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. I'm not sure what would be a good way to name production Watts data elements to allow referencing either or both of them in Home Assistant's configuration. Where's the Leak? Servicing Today's Cooling Systems | MOTOR The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. Refer to the Release notes page for any recent changes to the Enlighten API. In cases such as these, the response code is 422 and the response body includes an error reason as well as the parameters used to process the request. There is an issue with the meter measurements. The PF of the. Ideally, the user should be able to specify and track either or both from Home Assistant. Envoy Status If the system has both production and consumption CTs installed, you can see which meter is affected by checking the meter status on the Devices screen. If you don't see any voltage pulses, replace the sensor. 0000013432 00000 n I was able to check a couple things this weekend. I suggest to add the following two output parameters for this (so they can be read as sensor values in Home Assistant also); Can you open a new issue (enhancement) to track adding new parameters? If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. In your case it should be "load with solar production" as the solar breaker is on the load side. For example, there are 100 centimeters in a meter. You have your consumption meter set to "load with solar production" or "load only"? Correct me if I'm wrong, without CT metering, Also, If state was kept and easily accessible in either envoy_reader (or Home Assistant), today's WH production and the last seven days of WH production could be determined from tracking the, If CT metering isn't turned on, and the user wants to see the Envoy's inverter totals for today and the last seven days, then. There was a reply in the Home Assistant Community forum where a person took this screenshot. It could be the CTs are plugged into the wrong socket. I'm a bit puzzled here because I have a 3-phase system with no CT's installed, and (only) a single "eim" production section shows up where a single rmsVoltage (and rmsCurrent) are specified while each phase has its own different voltage (which my smart electricity meter shows). An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". Some may view this as a draw back. Use production_meter_readings or energy_lifetime instead. Why not use actual values (with decimals, when reported)? For example, P0500 (VSS circuit malfunction) is the most popular code In that case, where is the total power reported in /production.json ? My /api/v1/production/inverters inverter data is already properly read and output by envoy_reader (I can see the values in Home Assistant). "Metered Production data not available for your Envoy device.". Thanks for your continuing efforts! Whether this is actually implemented (case B') when CT's are installed or that only the power input lines (left connector) are used ('case A') for voltage measurement I'm not sure. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. /api/v1/production does not contain "readingTime" but /production.json "type": "inverters" does. I've connected them using Enpase IQ7+ micro inverters and bought also a Envoy-S Metered with them to read out the production statistics. I would expect to see at least three different sets of values, one for each phase. 'lqgs:~>_A,XJNBPyF^h@~.]:XUaSeJmi*`L6Aj$FaLQPzi_~l[U66RO57YYZA/O3](8LLIFAZrsf/=qNe~^sjW9f+L`l7?d A 5K There is an issue with your envoy meter measuremen rmsCurrent and rmsVoltage if only single instances reported for these instead of separately per phase? I think it is working as you intended, but see. The circuit passing through the consumption CT does not include AC Batteries. If the consumption measurements received by Enlighten do not appear to include storage activity, there are two possible wiring issues that can cause this: The Meter Issue status will continue to display until Enlighten receives 24 hours of meter measurements that indicate the problem has been addressed. My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. 0000014311 00000 n WebThe LEDs on the Envoy-S are solid green when a function is enabled or performing as expected, flashing when an operation is in progress, or solid amber when Because envoy_reader appears to read them from /production.json where the names are present but their values are 0 and do not get updated. Other than reducing http calls to the envoy device, is there another benefit to pull the production data from the two pages rather than one? 0000017430 00000 n |nxv&T["mhQ zt.f&Q4W?t4:?TrJdoV1EBEJ!,^G@-C'[lUZTD;Z*fd'w?Z:Fo77c[iZ=vWKc~Wv6c? The code is currently returning values for those rather than your 'not available' message. Enlighten supports up to two versions of the API at any given time. @gtdiehl - I think the only cases where you'd want to use /api/v1/production are: I don't have code changes that are worth submitting. I therefore did not install any CT's. This isn't currently accessible via Home Assistant, since at least for my configuration it is polling production.json and using the `eim`` structure which never change, which is the issue being reported here. Then change it so any polling of the original production parameters only come from /api/v1/production. You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. No Home Assistant will not get fully updated automatically. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion In metric, 1 meter is 100 centimeters and a kilometer is 1000 meters. There are two possible wiring issues that can cause this: The Meter Issue status will continue to display until Enlighten receives 24 hours of meter measurements that indicate the problem has been addressed. Maybe this is only of interest to me. 0000003055 00000 n If the system does not have a meter, returns 204 No Content. I did notice that there was only one solar CT and that may need to be on a particular leg as well. (for recent Envoy models that output production.json). Could this have been fixed in a later firmware revision? For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. Fyi: There exist 3 different Envoy-S models: I have the Envoy-S Metered Multiphase (EU) SKU: ENV-S-WM-230. Enphase consumption CT measurement problem. Envoy S Production data is not read / read incorrectly when Copyright 2023 Enphase Energy. WebThere is an issue with my envoy meter measurements Expand Post Translate with GoogleShow OriginalShow OriginalChoose a language DownloadDownload Show more To troubleshoot this, check CT orientation and leads, compared with voltage measurements. That can only mean that all 3 phases are connected, the 4 wires will be: N, L1, L2 and L3. WebIf the system has both production and consumption CTs installed, you can see which meter is affected by checking the meter status on the Devices screen. Sometimes, but not Actual Production that gets updated is available via envoy/api/v1/production however. Envoy reader doesn't have the flexibility to allow the user to override envoy reader's assumption and specify which data items or sources you'd like to track in Home Assistant. Exactly: I have only CT's installed for measuring Consumption "CT's" is plural but consumption/eim/activeCount only shows 1. If you are upgrading with Enphase microinverters to an existing string inverter installation, follow one of these options: All solar AC cables must pass through the Production CT. 0000016440 00000 n When the query parameters include production=all, returns meter and microinverter-measured time series: Returns a listing of all active Envoys currently deployed on the system. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details 3 0 obj Have an assistant crank the engine for a few seconds while you watch the meter's readout. How to fix a 'Meter Issue' system error message? - Support So I'm having a hell of a time with my enphase envoy consumption measurements. Requests for times that do not fall on the 5-minute marks are rounded down. @gtdiehl Here is my current production.json from my IQ D5.0.49 (77afa8) with CT metering turned off. Webmeter There is a communication problem between an Envoy and a revenue-grade meter on the system. Copyright 2023 Enphase Energy. please contact Enphase Technical Support. This page was generated at 03:27 AM. @atTD+JNE\:R About the Enphase Envoy-S Metered The Enphase Envoy-S Metered communications gateway enables performance monitoring and remote software and firmware updates of an Enphase Microinverter System. I Enphase Envoy S 'metered' Multiphase (probably identical to Envoy IQ). 3.48 kW of SolarWorld panels and Enphase IQ7 micros. Enphase Envoy When the filter is system_name, the results include all systems whose name includes the requested substring; for example, given the following system names, The filter ?system_name=Green would return. Here is the output of envoy_reader from various Envoys. period_start and period_end tell you when the minute (in this case) started and when it will end. The start date must be at least one month ago. After period_end, you can make another request. /production.json "type": "inverters", "wNow": 2235 WebThe split-core consumption CTs open and clamp around an existing conductor or busbar without rewiring. If there is a problem, MyEnlighten and the Enlighten mobile app show a message to help you know what to do next. This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. 0000339432 00000 n WebMake sure to keep your meter lead wires away from engine moving parts during this test. My 8x320W=2.56 kw mono array gets the IQ6+ inverters running at pf=1 at 700 VA. 0000015743 00000 n Planning and installing consumption monitoring trouble with enphase envoy consumption measurements If the system doesnt have any consumption meters installed, the response includes an empty intervals array. When I mean fully is that if something can be fixed on the Api side, such as the original bug of the Production values being zero than I can make a change here and request Home Assistant through a PR to update the version of the API being used. Queries on system_name and reference are case-insensitive. In addition, the Envoy-S Metered provides revenue-grade production data and allows for the monitoring of a sites energy load, thus offering significant advantages over other PV system monitoring equipment. Users can access energy production and consumption data through Enphase Enlighten cloud based monitoring software. There is an issue with my envoy meter measurements - Enphase There are 1000 millimeters in a meter. When this parameter is provided, the returned JSON is wrapped in the callback. This status was for me while debugging. I have a 3 phase power system, so I also have 3 CT's which each measure 1 fase, but in the Ephase app the value is shown as a single Power consumption parameter. %PDF-1.5 I just tested it in Windows Sandbox: No authentication required for both url's. 0000128138 00000 n If the response includes trailing zeroes, such as [909, 4970, 0, 0, 0], then no data has been reported for the last days in the series. 0000011718 00000 n Intervals are 15 minutes in length and start at the top of the hour. This does not require to connect all 3 phases to the power connector. Last one. So far, I haven't seen a flag from the Envoy API that indicates whether it is using the inverter measurements or the CTs, but maybe I haven't looked deeply enough. Sign in Have a question about this project? I wonder if that is why your blue bars are labeled production but look like they follow a consumption pattern? Parameter order does not matter in any request. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. 0000001916 00000 n Part number: 800-00554-r03, Enphase Energy, Inc. Enphase Energy Australia | Lvl 2, 2.26, 100 Collins St Alexandria, NSW 2015, Envoy S Wiring recommendation Subboard Typical 1Phase Net Metering, Envoy S Wiring NSW METERING recommendation 1Phase TWO METERS for Net Metering.