I will make a capture tomorrow when it's light and the system is actualually producing. Reduce the number of concurrent threads in your application in order to avoid this response code. I have made the change to fix it, actually just removed a single line of code, PR #51. 0000232417 00000 n When True the Envoy should be handled as endpoint_type "PC", when False as endpoint_type "P". There are no gaps in the time series. Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). 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. You can change this in the. Perhaps for compatibility there should be three available entities for the wNow values in Home Assistant: Having these three elements would allow the user to override Envoy reader's choice if necessary as well as track both on systems with CTs if the user chooses that. I You can sign up to be notified by email if your system experiences either type of production issue. For the best experience on our site, be sure to turn on Javascript in your browser. There are 1000 millimeters in a meter. I'm following the current convention that was previously coded. The circuit passing through the consumption CT does not include AC Batteries. rmsCurrent and rmsVoltage could be reported by envoy_reader as well. Last one. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details What does the "Envoy Failure" message mean? - Enphase Support The CT direction arrow of each CT, in a Net metering (load with solar) configuration, will always face towards the load circuits of the site. Unrecognized parameters are ignored. 0000110513 00000 n So I'm having a hell of a time with my enphase envoy consumption measurements. You may change the format of returned date and time values by passing the query parameter datetime_format on any endpoint that returns date or time values; for example. For example, P0500 (VSS circuit malfunction) is the most popular code 0000154623 00000 n Here's what mine looks like: I think the negative power factor happens when you're sending power back to the grid, but I could be wrong. When I investigate the raw numbers from interrogating the envoy direcly it actually shows me the low power factor. To troubleshoot this, check CT orientation and leads, compared with voltage measurements using your regional CT They can always filter these values out in Home Assistant by specifying which monitored_conditions they want to see. I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. metered_production wNow: 2.79 (gets truncated to 2) About API v4. I see information in /api/v1/procuction and /api/v1/production/inverters being updated every 5 minutes. Did you power off and repower your Enlighten box after you made those changes. It is important to understand these differences when installing Envoy CTs. If the answer to the above question is true, then it would also be useful to have inverter_lifetime_production in addition to metered_lifetime_production. Intervals are 15 minutes in length and start at the top of the hour. I wonder if they can tweek low light efficiency for me? This is not my experience. @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. There is an issue with my envoy meter measurements - Enphase The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. Have a question about this project? Attributes that are times are named accordingly (e.g., operational_at, last_report_at, start_at, end_at). For just the powering of the Envoy a single phase would be sufficient. Unless I'm wrong about that, it would be useful to be able to get wNow (production) for both, so hopefully your naming would also include inverters_production. Cross your fingers, and I'm hoping it will be included in 2020.12.1. There is a limit to the number of systems that can be returned at one time. 0000017877 00000 n How to fix a 'Meter Issue' system error message? - Support I'll return values with a decimal. So I've had my envoy setup for 5 years now no issues. Observation: metered values get truncated instead of rounded. (for recent Envoy models that output production.json). 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. In general, a Meter Issue indicates a system where on-site maintenance may be required. & Envoy 0000128068 00000 n When the filter is reference, both reference and other_references are searched. avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? For more details, visit Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. 0000016000 00000 n How do I troubleshoot a Meter Issue system status? "Metered Production data not available for your Envoy device." trouble with enphase envoy consumption measurements @lnlp Thank you for running the code! Under some conditions, data for a given period may be temporarily unavailable. Similarly, if you see no message in the Enlighten mobile app, your system is doing fine. %PDF-1.5 The new version of API (v4) is available at: developer-v4.enphase.com. So this voltage is apparently read from L1 on the 'power input' connector. Instead of /stream/meter has anyone tried /ivp/meters/readings? I haven't reached out to Enphase yet. If the system has a meter, the time series includes data as measured by the microinverters until the first full day after the meter has been installed, when it switches to using the data as measured by the meter. It'll be removed from the code. 0000009524 00000 n After period_end, you can make another request. 0000002893 00000 n Leave it in place for at least 15 minutes. 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. metered_consumption wNow: 0.836 (gets truncated to 0). 2 0 obj The rmsVoltage may actually be measured by the Envoy, but without any CT's installed, the rmsCurrent value apparently is a bogus value(?). Enphase Solar PV Installation Certification Training Flashcards Queries on system_name and reference are case-insensitive. @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? According to the IQ Envoy manual this is possible if the user wants revenue-grade production metering. In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. Input date range for rgm_stats is restricted to 7 days. Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. 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. It seems the the values are almost the same and they are both updated every 5mins. The circuit passing through the production CT includes AC Batteries. If a meter or meters are installed on the system, measurements come from the meter; otherwise, measurements come from the microinverters. For example, if your API key is 123ABC and you are making a request for user_id 4d6a51330a, your requests would look like the following: To learn more about user_ids, see the Quick Start page. I really like to give the user all of the data and let them figure out what they want to use. This has recently changed to net metered solar. For /api/v1/production the timestamp can be read from production.json "inverters" section. Imagine that the initial ammeter reading, captured on the 10A scale, was .365A (365mA). Envoy Status If the system doesnt have any revenue-grade meters installed, the response includes an empty intervals array. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? I would like some input from @jesserizzo and others. Or atleast get reporting working for all attributes for each hardware platform. 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. I tested your modified envoy_reader with my Envoy-S Metered Multiphase with metering disabled (no CT's). For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. 0000014311 00000 n I'll look through the code and see what it might take to implement. If you dont have permission to view consumption data, the response code is 401. The Enlighten Systems API WebMake sure to keep your meter lead wires away from engine moving parts during this test. This endpoint includes entries for every production meter on the requested system, regardless of whether the meter is currently in service or retired. WebUnplug the Envoy from the AC outlet and plug it in once again. If the total duration requested is more than one month, returns one month of intervals. By default, systems are returned in batches of 100. If the system doesnt have any microinverters installed, the response includes an empty intervals array. The darkish overcast looked like possible little snow storm coming. Here is low light at the end of the day. 0000013177 00000 n By default envoy_reader should automatically determine whether CT's are enabled and act accordingly. Can you confirm that you can get this without any authentication? 0000007176 00000 n You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. All measurements are in Watt hours. By clicking Sign up for GitHub, you agree to our terms of service and Will there be / shouldn't there be 3 separate "eim" sections, each for one phase? 0000003706 00000 n If the system does not have a meter, returns 204 No Content. My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. In that case, the response code is 500 and the response body is. If the meters milliamp scale goes up to 500mA, then => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's All times are GMT-5. The code is on one of my branches. As a result the reported Production values are either 0 or some bogus value. The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. "[}QXD/jD NCrncVa @L*23m Handle Envoy S (and Envoy IQ) without CT's as 'endpoint_type' "P" instead of 'endpoint_type' "PC". It would be nice if other useful parameters e.g. Reported values while metering disabled: By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. An Enphase team member may follow up with you about your feedback. Sign in Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. 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. I've got the old (non-IQ) version of the envoy. 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. envoy_reader should handle all these (4) situations correctly. Wherever you display information from the. You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. When I look into the error, it was not apparent to me the problem. This does not require to connect all 3 phases to the power connector. 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 Currently I do not have TOU rate pricing. 0000048797 00000 n metered_production_readingtime My Envoy reports tiny metered values while metering is disabled. 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. 0000375146 00000 n This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. 0000033107 00000 n It only reads envoy/production.json. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. All API requests require your API key and a user_id. 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. Completed - The scheduled maintenance has been completed. @gtdiehl 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. |nxv&T["mhQ zt.f&Q4W?t4:?TrJdoV1EBEJ!,^G@-C'[lUZTD;Z*fd'w?Z:Fo77c[iZ=vWKc~Wv6c? The time series includes one entry for each day from the start_date to the end_date. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. I just wanted to let you know the logic might not be working as intended. The CT (current transformers) are used for measuring current. Would have to find a system that has 3Phase with Metering enabled and CTs installed. 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. 0000139882 00000 n Enphase Handy Tips - Wiring your CTs for Gross vs Net Metering dsmr-reader . WebWhen you first downloaded and open the app you were prompted to allow permission, if you declined to give that permission you have to go to Settings > Envoy > Camera and (I have observed bogus values for 'production' and 'consumption' in range between 0 and 2). endobj 0000232378 00000 n My utility company (Xcel) has a great program where the rate is ~$0.04 per kWh which is awesome. For a Net metering arrangement (load with solar), the Consumption CT must be positioned to measure the site loads AND all of the solar export. Got your message a little before 11am my time so low production is just winding down. Remote problem-solving The Envoy lets you pinpoint performance issues instantly and resolve them remotely, before they get in the way of system performance. My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. A phase coupler for communication with the inverters is not built-in to the Envoy. My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. If there's voltage over 0.2 volts in any wire or connection, check for corroded, damaged or loose wires. This is the output: 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. Yes the original bug in envoy_reader has been fixed. 0000003895 00000 n fbK1yBE~nF\|WG x0y,x,JX { [J*4 U4%0!AWeZ sPH@@-GTpGs*(zI1YJBBGNN]UU>h`H_))q~u}@a1(%=_n8XH Here are captures of /api/v1/production, /production.json and /api/v1/production/inverters. A difference of 1 Watt, which may be caused by a rounding error, or by a small difference in moments of measurement. In my situation (ct_metering_production is False) the production value is read correctly from the production/inverters section in production.json. Like I said I haven't looked through all of the comments yet. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. My blue bars show production and yours appear to show consumption. It collects energy and performance data from the microinverters over on-site AC power lines, and it forwards that data to Enlighten, via the Internet, for statistical reporting. Each system element includes the following: Return values for status include the following, and are listed in priority order: Returns a listing of active devices on the given system. But that is an incorrect assumption because it is only valid when current transformers (CT) are enabled/installed. (I suspect something like: electrical induction metering). |JU\"K2b WebThe split-core consumption CTs open and clamp around an existing conductor or busbar without rewiring. 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. Regarding measurements for each phase, he Envoy has a URL that deliveries a stream of measurements -. WebIf your meter has a milliamp scale, use it whenever possible because its a more sensitive scale. to your account. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. Announcement: Effective October 1, 2023, Enphase API will only support TLS 1.2 and will not accept any applications on older TLS versions, Announcement: The end of life for Enphase API v2 has been extended from August 15, 2022 to September 30, 2023 I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. Parameter order does not matter in any request. Manual: Add an extra parameter e.g. <> Some may view this as a draw back. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. Envoy-S Installation and Operation