issue with envoy meter measurements

0000139882 00000 n When I run envoy_reader from a command prompt, the 4 production values shown are 0. I'm not sure on this one. The production or consumption measurements received by Enlighten are negative. In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. I have had my solar setup for 1.5 years so far, no issue. The fix was merged into the dev branch yesterday, which usually means it will make it into the next release (2021.01.0). I'll look through the code and see what it might take to implement. Looks like you are checking for not set/zero vs. checking activeCount. Here are captures of /api/v1/production, /production.json and /api/v1/production/inverters. Data coming from /api/v1/* is updated every 5 minutes. Continue reading for more information about each type of problem. 0000023653 00000 n 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. If the total duration requested is more than one month, returns one month of intervals. Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. 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. Currently I do not have TOU rate pricing. I know not a perfect solution but through small changes eventually we will get to a release that meets the needs of Envoy users across all firmwares . 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. 0000020597 00000 n 0000017430 00000 n 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? I have tested your latest envoy_reader.py. All were taken at the same time. I would expect to see at least three different sets of values, one for each phase. I therefore did not install any CT's. All requests support an optional callback parameter. Requests for times that do not fall on the 15-minute marks are rounded down. 0000018303 00000 n Then change part of detect_model() from In other words, if you explicitly want to access that data for the inverters whether or not metering is on, production[0] is the place to get it. My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. Currently to minimize api calls between the envoy and home assistant one function is called to gather up all the data (even if the device does not support the parameter) and send it across. But that is an incorrect assumption because it is only valid when current transformers (CT) are enabled/installed. The sensor should produce a voltage pulsing signal. Here is the output of envoy_reader from various Envoys. Here is heavy overcast at the end of the day with sun low and far to the side of the array. There is a limit to the number of systems that can be returned at one time. Gaps in reporting are not filled with 0-value intervals. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. In other words, without CTs to use the Envoy's accumulation of WH Today and WH Past 7 days, you'd need to be able to get Envoy Reader to poll /api/v1/production. If the total duration requested is more than one day, returns one day of intervals. By providing an optional ct_enabled parameter the user can override it for testing purposes. Not sure what the actual url for the page is though. The code is currently returning values for those rather than your 'not available' message. rmsCurrent and rmsVoltage could be reported by envoy_reader as well. <> 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. The Envoy can accept 2 x CTs paralleled into the same CT terminal. The text was updated successfully, but these errors were encountered: @lnlp Would it be possible for you to post a copy of your /production.json? Right after connecting the power lines to the grid I already have some statistics of the grid meter (in the Netherlands called the Slimme meter, which you can read through the P1-port using i.e. A. Though I wonder if something like this would solve the problem, Add a function called hasMeteringEnabled() which will return True if production[1]eim activeCount is >= 1 else False, envoy_reader/envoy_reader/envoy_reader.py. Unrecognized parameters are ignored. trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream 0000013432 00000 n This indicates that you have made too many concurrent requests. 0000033020 00000 n So as it stands is your original bug of Production values displaying zero fixed? Note that the parameter name must include [] after it in order to indicate that it is a multi-valued query parameter. Current Transformers (CTs) are installed to measure Solar (production) and Home Loads (consumption). This is just low sun with overcast far to the side of the array. 0000110513 00000 n (Envoy-S metered multi-phase (EU) with no CT's installed.). x=r?#Z[Sd{q20$&! That can only mean that all 3 phases are connected, the 4 wires will be: N, L1, L2 and L3. Please note that the Enlighten Systems API does not provide performance data at a panel or microinverter level. My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. Enlighten supports up to two versions of the API at any given time. For example, a request to. Use production_meter_readings or energy_lifetime instead. 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. My utility company (Xcel) has a great program where the rate is ~$0.04 per kWh which is awesome. rmU)dC!.d0oQmLL"xoCFDLLBJoFI%g%(1S0i/(yv65^S)^*By[(& arHB~*UA{Tjj!W6 $I(7dwA_ A}Tb|X_7)gk:}tD@}Xk/Vsm4'gJO~* EHRv91X Q8^@DagKqOfL`mSJ4U=TB\o/)u{xYK5_Kmx~.s !3hUtI WpeWJ`+qQ| i%YlbrC3 v.PWBUfMI3OfL So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. 9 kW solar, 42kWh LFP storage. 0000154623 00000 n Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). If you dont have permission to view consumption data, the response code is 401. I just tested it in Windows Sandbox: No authentication required for both url's. Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. While much of the rest of the world uses the metric system of centimeters, meters, and kilometers, US has continued to the English units. In my situation (ct_metering_production is False) the. Examples in this documentation exclude the API key and the user_id for clarity. The maximum page size is 1000. Intervals are 15 minutes in length and start at the top of the hour. But have to think about current users. Queries on system_name and reference are case-insensitive. When using Envoy S without having CT's enabled then production data in envoy/production.json is NOT updated. ' ~V8nG~fj# q:D{<=WXm jkZ`Z +\MXH:+5N^;Ll.l_`h'6ys`8r};gV5 >=A,`.hXp~Uj9Pus6[xClEomv`uDM Some batteries havent charged or discharged recently. FEMA- Federal Emergency Management Agency If one microinverter in a solar PV system fails, what will occur? 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? 0000033107 00000 n 0000014056 00000 n 0000017266 00000 n 0000014311 00000 n 0000048797 00000 n Too bad, but no need to feel sorry. WebIf the consumption measurements received by Enlighten do not appear to include storage activity, there are two possible wiring issues that can cause this: The circuit passing Webmeter There is a communication problem between an Envoy and a revenue-grade meter on the system. By default envoy_reader should automatically determine whether CT's are enabled and act accordingly. My consumption only power-factor when I look at it from the installer toolkit endobj metered_consumption_readingtime, How about simplifying WebThere is an issue with my envoy meter measurements Expand Post Translate with GoogleShow OriginalShow OriginalChoose a language DownloadDownload Show more For /api/v1/production the timestamp can be read from production.json "inverters" section. I can even see it go lower after that and work much better than it did on the way up. According to the Envoy-S Metered Multiphase Installation manual there are 3 CTs installed on the Production and Consumption sides. % The code is on one of my branches. Leave it in place for at least 15 minutes. The one solar panel connected to that microinverter will be out of operation C. The entire solar PV system will be out of operation B. WebEnvoy-S Standard Compatible Microinverter (s) M215, M250 Primary Use Residential & Small Commercial AC Supply 230 VAC, 50 Hz Production Metering 5% accurate microinverter measurements Warranty Length 5 years Designed for an outdoor enclosure Integrated Wi-Fi & Mobile Connect Ready Consumption Monitoring & Storage Ready EDIT: I actually just found a setup like this. The iso8601 format returns all temporal values, whether dates or times, in an ISO 8601 time format including timezone offset; for example 2015-05-05T00:00:00-07:00 is midnight on 5 May, 2015, in Pacific Daylight Time. This requires an alternative arrangement of the CTs for correct measurement. (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? & So far the readings do not look right. Contact us for sales, quantity discounts and expert reviews for the Enphase CT current transformer for Envoy. 0000017877 00000 n All times are GMT-5. 4 0 obj I tested your modified envoy_reader with my Envoy-S Metered Multiphase with metering disabled (no CT's). Note: If a system does not include a given device type, that key is left out of the returned hash. 0000411029 00000 n The darkish overcast looked like possible little snow storm coming. 0000002893 00000 n Commonly, the reading will be within 30 minutes of the requested end_at; however, larger deltas can occur and do not necessarily mean there is a problem with the meter or the system it is on. Have you tried flipping the CTs 180 degrees? Software Version: R4.10.35 (6ed292) Envoy S Production data is not read when not using current transformers which renders reported Production data useless. I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. My Envoy homepage shows "Software version R4.10.35 (6ed292)" is that the Envoy's firmware version? The inverters and the CTs dont report the same values and Envoy reader can make an incorrect assumption about whether CT metering is being used. 0000375185 00000 n Do not violate the other restrictions described in the Enphase, Copyright 2023 Enphase Energy, Inc. All rights reserved. 0000012231 00000 n Can you open a new issue (enhancement) to track this one? Some may view this as a draw back. Enlighten declares a Meter Issue () system status when it detects a possible problem with the CT or storage measurements. 0000016440 00000 n If there is an issue with the Envoy meter measurements, youll see a message like this: If one or more of your AC Batteries hasnt charged or discharged for the last 72 hours, youll see a message like this: This may not indicate a problem, especially if there hasnt been enough sunshine to produce energy that exceeds your homes consumption, or if your homes energy use has gone down to the point that the batteries dont need to discharge. I don't really understand how the system is configured. Intervals are 15 minutes in length and start at the top of the hour. In my situation (ct_metering_production is False) the production value is read correctly from the production/inverters section in production.json. EV owner since 2012. @lnlp I'll release the new version on pypi this weekend and open a PR on the Home Assistant side as well. An Enphase team member may follow up with you about your feedback. That's why I'm asking to track the above as separate issues. D`TR2 (P@$D j+C"qa7%A]4(uWP7T! 0000026874 00000 n If a request is rejected because one of these limits has been exceeded, the response includes information about why the request was rejected: period tells you how long to wait. The Enlighten Systems API returns JSON. Here's my output. Meters that have been retired from a system will show an end_at that doesnt change, and that eventually is far away from the current time. If so this may end up being the best solution, although it requires 2 requests. 0000009524 00000 n the blue wire goes to a splice pack under the carpet under Your message explains this. 0000023514 00000 n Since installation the system has shown an intermittent error: "Meter Issue. (for recent Envoy models that output production.json). With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. and I see information in /api/v1/procuction and /api/v1/production/inverters being updated every 5 minutes. There was a reply in the Home Assistant Community forum where a person took this screenshot. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. 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. Be aware that CT's can be installed for either Production, or Consumption, or both. When this parameter is provided, the returned JSON is wrapped in the callback. 0000139611 00000 n limit is how many requests are allowed per period. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. We will provide Copyright 2014 SolarReviews All rights reserved. This is not my experience. This has recently changed to net metered solar. Could this have been fixed in a later firmware revision? I Requests for times that do not fall on the 5-minute marks are rounded down. Unlike ratio CTs with current outputs, these CTs are internally burdened to produce a safe 0.333 Vac output voltage, therefore, shorting blocks are not needed. 0000375146 00000 n Does that get installed automatically? Imagine that the initial ammeter reading, captured on the 10A scale, was .365A (365mA). "Metered Production data not available for your Envoy device.". The start date must be at least one month ago. <>/ExtGState<>/Font<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 25 0 R] /MediaBox[ 0 0 612 792] /Contents 4 0 R/Group<>/Tabs/S/StructParents 0>> This is the output: WebThe use of any other type of CT will result in incorrect power measurements, and may permanently damage the WattNode meter. Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? Then change it so any polling of the original production parameters only come from /api/v1/production. Very interesting indeed. I hope we can see it being updated in Home Assistant as well soon. 0000001916 00000 n If it continues to display Envoy Failure or if it never moves beyond the I will make a capture tomorrow when it's light and the system is actualually producing. You can check the systems status in the meta attribute of the response to determine when the system last reported and whether it has communication or production problems. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. At first I seemed to get a 404 for but maybe I didn't get the plurals right though http://envoy.local/ivp/meters/readings. Enphase consumption CT measurement problem. If the system does not have a meter, returns 204 No Content. If some of your microinverters have stopped reporting to the Envoy, youll see a problem message like this: Click the link in the message to see which microinverters are not reporting and their location in your array: Learn what you can do if some of your microinverters have stopped reporting. I would have to look into how to send specific data from the envoy_reader API to Home Assistant. I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? Already on GitHub? When current transformers (CTs) are wrapped around a live Do you know what the "eim" stands for? 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. production.json eim only shows an aggregated number. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. WebAN_6612_032 Energy Measurement in Split Phase Systems Using 78M6612 Rev. endobj 0000161348 00000 n Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? 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. Going down this path means renaming 4 monitored_conditions and adding 4 or5 new ones will appear for each new Envoy sensor added to Home Assistant. This status was for me while debugging. Envoy S Production data is not read / read incorrectly when current transformers are not enabled/installed [bug], https://thecomputerperson.wordpress.com/2016/08/03/enphase-envoy-s-data-scraping/#comment-5838, Add production_readingtime and consumption_readingtime output parameters, Add consumption_ct_metering_enabled and production_ct_metering_enabled output parameters, Support reading values of consumption and production per phase, The envoy is configured without CT metering and the user wants WH totals for today and 7 days which aren't available in. If the system doesnt have any consumption meters installed, the response includes an empty intervals array. => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's @gtdiehl Intervals are 5 minutes in length and start at the top of the hour. Can you confirm that you can get this without any authentication? (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. Yes the original bug in envoy_reader has been fixed. There's simply no way I have a power factor of 0.52 in the house. Envoy-S Metered and Envoy-S Metered Multiphase (IQ Envoy) are both black but the Envoy-S Metered Multiphase has the cover screw on the right side while the Envoy-S Metered has the cover screw on the left side (like Envoy-S Standard). Any link back to Enphase should be follow-able.

Four Weddings Uk Where Are They Now, 204 Ruger 24 Inch Upper, Articles I