It is important to understand these differences when installing Envoy CTs. 0000013177 00000 n When the filter is reference, both reference and other_references are searched. The Envoy-S Metered is a system monitoring tool, and control device. By default, systems are returned in batches of 100. 0000411029 00000 n Interesting, /ivp/meters gives some configuration/status information such as phaseCount and phaseMode that I haven't seen elsewhere: http://envoy.local/ivp/meters/readings seems to be very useful. Here's my output. I have tested your latest envoy_reader.py. Here is low light at the end of the day. 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. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. Under some conditions, data for a given period may be temporarily unavailable. This is caused by my Envoy not by envoy_reader. limit is how many requests are allowed per period. 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? 0000154881 00000 n I have made the change to fix it, actually just removed a single line of code, PR #51. 0000048897 00000 n I think it is working as you intended, but see. WebEnvoy-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 4 0 obj 0000093464 00000 n Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Actual Production that gets updated is available via envoy/api/v1/production however. It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. 0000063893 00000 n You can sign up to be notified by email if your system experiences either type of production issue. 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. The epoch format returns all temporal values in Unix epoch time. <> Key Points "Metered Production data not available for your Envoy device.". Install a phase coupler on the load side of the over-current protection device. Professional installation is required, please contact your installer for an estimate before purchase. Recently my meter box was moved and the sparkie put the consumption CT backwards. If the first request does not return a full list, use the next attribute in the response body to request the next page of systems. Is that new Envoy firmware? @atTD+JNE\:R 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 The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. My blue bars show production and yours appear to show consumption. 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. So I just display the values unless the device actually does not support metering. When this condition is detected, the response code is 500 and the response body is: Each meter interval includes the following: Returns performance statistics for the specified system as reported by microinverters installed on the system. When I look into the error, it was not apparent to me the problem. I have read through everything yet but I want to point out that when polling uses the /api/v1/production page the envoy appears to only update it every 15mins. This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. CT Measurements" from a consumption CT on one of the phases. 0000010645 00000 n To troubleshoot this, check CT orientation and leads, compared with voltage measurements. Reduce the number of concurrent threads in your application in order to avoid this response code. If the system doesnt have any microinverters installed, the response includes an empty intervals array. Now I have to get this included in a bugfix-release for Home Assistant as 2020.12.0 includes the envoy_reader with the bug. In 'case B' one may wonder why the 'power connector' on the left exists and allows to wire all 3 phases. This does not require to connect all 3 phases to the power connector. and returns systems that currently have production issues. I just wanted to let you know the logic might not be working as intended. The Envoy backend should actually have both values, and the API retrieving the data 0000033107 00000 n 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. The Enphase Home Energy System meters solar production and home electrical loads. Have you tried flipping the CTs 180 degrees? For example, a request to. 0000196664 00000 n & All measurements are in Watt hours. The production or consumption measurements received by Enlighten are negative. 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. 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. 1 m is about 39.37 inches. WebThe split-core consumption CTs open and clamp around an existing conductor or busbar without rewiring. Cross your fingers, and I'm hoping it will be included in 2020.12.1. 0000011207 00000 n I know this may seem like a back step but I'm thinking of changing back to the original output of the envoy_reader api, and have the code get the production values based on the activeCount attribute. WebMake sure to keep your meter lead wires away from engine moving parts during this test. The Net number calculated under the date looks wrong. <>/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>> The new version of API (v4) is available at: developer-v4.enphase.com. tvd`x]6d=WY fj0A2! 0000139611 00000 n If the input date range is more than 7 days, the following error will be thrown. It'll be removed from the code. Systems that are configured to report infrequently can show large deltas on all meters, especially when end_at is close to the current time. Your message explains this. I currently check the /api/v1/production data in a browser and refresh manually. 0000020597 00000 n 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. Queries on system_name and reference are case-insensitive. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. Details about my Envoy: Already on GitHub? When I run envoy_reader from a command prompt, the 4 production values shown are 0. WIRING EXAMPLE:Envoy S Wiring recommendation Subboard Typical 1Phase Net Metering, WIRING EXAMPLE:Envoy S Wiring NSW METERING recommendation 1Phase TWO METERS for Net Metering. I wonder if that is why your blue bars are labeled production but look like they follow a consumption pattern? I haven't reached out to Enphase yet. Are all three phases wired to your Envoy power connector_(most-left connector on the Envoy)_? 0000023653 00000 n The maximum page size is 1000. Manual: Add an extra parameter e.g. (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? I have an Enphase system but it only has production and the blue bars are in the same orientation as in your chart. Requests for times that do not fall on the 5-minute marks are rounded down. stream Note that the parameter name must include [] after it in order to indicate that it is a multi-valued query parameter. So it looks like you need to join with /ivp/meters based on eid to know what you are looking at and whether it is enabled. If the total duration requested is more than one day, returns one day of intervals. Leave it in place for at least 15 minutes. I just tested it in Windows Sandbox: No authentication required for both url's. <> (Maybe you are mistaking with the cloud API's update frequency?). In my situation (ct_metering_production is False) the. The next screenshot shows the cumulative effect of the negative reading on the lifetime measurements; Screen Shot 2019-01-04 at 10.24.51 PM.png, Solar Panels for your Home, Grid Tied Solar PV, Screen Shot 2019-01-04 at 10.24.59 PM.png, Screen Shot 2019-01-04 at 10.22.19 PM.png, Screen Shot 2019-01-04 at 10.26.09 PM.png, Screen Shot 2019-01-04 at 11.25.06 PM.png, https://enphase.com/sites/default/finvoy-EN-US.pdf, https://thecomputerperson.wordpress.com/2018/08/18/what-is-inside-the-enphase-envoy-s-teardown/, https://www.solarpaneltalk.com/filed7&d=1546658760. Returns the energy production of the system for the month starting on the given date. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details Here is the output of envoy_reader from various Envoys. 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. Webmeter There is a communication problem between an Envoy and a revenue-grade meter on the system. WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. 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. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. I really like to give the user all of the data and let them figure out what they want to use. If you dont have permission to view consumption data, the response code is 401. Attributes that are times are named accordingly (e.g., operational_at, last_report_at, start_at, end_at). Thank you for opening those issues. It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. @lnlp Thank you for running the code! Data coming from /api/v1/* is updated every 5 minutes. If these are zero than poll data from the other production page. In the "inverters" section? 0000410990 00000 n Observation: metered values get truncated instead of rounded. In my comments above, I was arguing for the case to still be able to get the inverter numbers even if metering is enabled. If a meter or meters are installed on the system, measurements come from the meter; otherwise, measurements come from the microinverters. And when envoy_reader reads its data from the "eim" section shouldn't that be done for each phase separately and then summed to get totals for all 3 phases? I agree a better solution would be to have additional parameters. My /api/v1/production/inverters inverter data is already properly read and output by envoy_reader (I can see the values in Home Assistant). 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_*. In some extreme cases, you may receive a 503 error instead of a 409. WebThe use of any other type of CT will result in incorrect power measurements, and may permanently damage the WattNode meter. For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. In general, a Meter Issue indicates a system where on-site maintenance may be required. Copyright 2014 SolarReviews All rights reserved. I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. Input date range for rgm_stats is restricted to 7 days. What use are values of e.g. I need to understand how the Home Assistant configuration interface interacts with envoy_reader to configure it. This has recently changed to net metered solar. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. So this voltage is apparently read from L1 on the 'power input' connector. It also includes a $5 a month hook-up charge which covers the extra meter. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. %PDF-1.4 % envoy_reader should handle all these (4) situations correctly. Got your message a little before 11am my time so low production is just winding down. 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. However, each request must include them both. It causes Home Assistant to not update after a couple of polls. Do not violate the other restrictions described in the Enphase, Copyright 2023 Enphase Energy, Inc. All rights reserved. Instead of /stream/meter has anyone tried /ivp/meters/readings? Do not nofollow your links to Enphase. 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. 0000011718 00000 n You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. I have had my solar setup for 1.5 years so far, no issue. This is what is shown on the envoy/home page when CT's are not enabled: Let me know if you need more information or help. Use production_meter_readings or energy_lifetime instead. Yes the original bug in envoy_reader has been fixed. 0000161309 00000 n Valid values for datetime_format are iso8601 and epoch. All API requests require your API key and a user_id. For example. @OllemGit Now to change how things are displayed in Home Assistant, or adding/removing sensors that means probably both an API side code change as well as the sensor code change on the Home Assistant side. So in practice it can be possible that only CT('s) for consumption are installed. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. Unrecognized parameters are ignored. Immediately to the left of or above the mark, you must display the words Powered by in a clear and conspicuous manner and in a minimum eight-point font. avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. Returns a time series of energy produced on the system over its lifetime. Meters are abbreviated using a lower case "m" in 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. @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? Ideally, the user should be able to specify and track either or both from Home Assistant. I've seen that referred online as being able to get the individual readings and maybe it doesn't require the installer password. 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. endobj In metric, 1 meter is 100 centimeters and a kilometer is 1000 meters. Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? )bJ60F-phEZ Then a question, does the api return the eim values that is got from the envoy even when the activeCount = 0? There are no gaps in the time series. The time series includes one entry for each day from the start_date to the end_date. 0000078331 00000 n It could be the CTs are plugged into the wrong socket. Fyi: There exist 3 different Envoy-S models: I have the Envoy-S Metered Multiphase (EU) SKU: ENV-S-WM-230. %PDF-1.5 My Envoy reports tiny metered values while metering is disabled. Imagine that the initial ammeter reading, captured on the 10A scale, was .365A (365mA). I would have to look into how to send specific data from the envoy_reader API to Home Assistant. If Enphase has detected a possible hardware issue that may be affecting system production, youll see a message like this: Click the link in the message to see which microinverters are reporting a production issue and find out how to get help with the problem. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd.
Kohl's Stockroom Associate Job Description,
Football Players Born In 2005,
Articles I