0000017430 00000 n Note: I've got production and consumption metering turned off (activeCount == 0). All requests support an optional callback parameter. When CT metering is off you have to look at /api/v1/production for the WH accumulation (today, 7 day) totals. |nxv&T["mhQ zt.f&Q4W?t4:?TrJdoV1EBEJ!,^G@-C'[lUZTD;Z*fd'w?Z:Fo77c[iZ=vWKc~Wv6c? Have a question about this project? Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. Though this time I had someone add my PR to the list of PRs that should be included in 2020.12.1. 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. It does show in the HTML output, but scraping should be avoided. @gtdiehl Here is my current production.json from my IQ D5.0.49 (77afa8) with CT metering turned off. Returns the last known odometer reading of each revenue-grade production meter on the system as of the requested time. WebC. When they can finally talk it tells the Envoy this and the system averages it I wonder if that is why your blue bars are labeled production but look like they follow a consumption pattern? Data from /stream/meter (updates every second) shows the data separately for each phase but unfortunately this requires installer permissions. However, each request must include them both. WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. %PDF-1.4 % Intervals are 15 minutes in length and start at the top of the hour. Some batteries havent charged or discharged recently. Intervals are listed by their end dates; therefore, the first interval returned is 5 minutes after the requested start date. My consumption only power-factor when I look at it from the installer toolkit Here are the possible messages that may be displayed: Some microinverters have stopped reporting. 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. While my production meter struggles at PF=0.5-0.7 from 8:30 to 11am in this equinox season, it finally gets to pf=1 as the sun clears the trees with VA=700. Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. There's simply no way I have a power factor of 0.52 in the house. Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. 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. Do you expect to get the fix into the next (bug-fix) release (presumably 2020.12.1)? I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. 0000452685 00000 n Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. read_at is the time at which the reading was taken, and is always less than or equal to the requested end_at. I would have to look into how to send specific data from the envoy_reader API to Home Assistant. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. Envoy reader makes an assumption depending on the type of Envoy whether CT metering is being used. For example, there are 100 centimeters in a meter. If the response includes trailing zeroes, such as [909, 4970, 0, 0, 0], then no energy has been reported for the last days in the series. This is caused by my Envoy not by envoy_reader. One case that is not handled, if you want the inverters current production and WH lifetime production, with metering turned on, you can only get that from production.json. Well sorry to say but there was a bug in the code. Completed - The scheduled maintenance has been completed. However, each request may optionally include it. Returns the energy production of the system for the month starting on the given date. I did notice that there was only one solar CT and that may need to be on a particular leg as well. Specifically it has to do with the power factor. Since installation the system has shown an intermittent error: "Meter Issue. My 8x320W=2.56 kw mono array gets the IQ6+ inverters running at pf=1 at 700 VA. 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. 9 kW solar, 42kWh LFP storage. Example: It is possible to request a subset of the systems list. 0000078062 00000 n Observation: metered values get truncated instead of rounded. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. 0000063893 00000 n In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. In that case, the response code is 500 and the response body is. The circuit passing through the production CT includes AC Batteries. You signed in with another tab or window. A faulty speed sensor will often be accompanied by a check engine light and trouble code. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. 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 0000139909 00000 n For example, P0500 (VSS circuit malfunction) is the most popular code Web//= $_COOKIE['currency'] == 'USD' ? 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. Compatible changes do not result in a change to the version number. I would like some input from @jesserizzo and others. CXg*@UDXWkV+-40VwdD$pq l/c=_"8-h.iwF3u;md0I%02XrUy.UZj-CRU Shr{|+r?`vQbqp`ZktIxp16De#~`hze2]@k&}Y"U3F0VKB5tkU)7^9{'?epa #C#fIp];efXilt(cz#4STR42I ,~g^*N*9cU+!d`*,2'd!_]G?n*W& >4. All times are GMT-5. I did not check (yet) where the come from and/or lead to, I did not check (yet) where the come from and/or lead to. I need to understand how the Home Assistant configuration interface interacts with envoy_reader to configure it. The epoch format returns all temporal values in Unix epoch time. To me this isn't a problem right now, unless there winds up being some logic that depends on those being zero vs. not used. 0000018303 00000 n Returns consumption as measured by the consumption meter installed on the specified system. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? It was like this for a Did you power off and repower your Enlighten box after you made those changes. 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. Good catch! I was happy to see it working in 2020.12.0 now but then noticed values reported in HA don't match /api/v1/production. 0000128068 00000 n Remote problem-solving The Envoy lets you pinpoint performance issues instantly and resolve them remotely, before they get in the way of system performance. This status was for me while debugging. I would also prefer if the timestamp of when the values were updated can be added, e.g. 0000015743 00000 n privacy statement. I use Envoy S but without any CT's installed. 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. Reported values while metering disabled: tvd`x]6d=WY fj0A2! That may be a clue. The consumption measurements received by Enlighten do not appear to include storage activity. 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. For more details, visit The installers could have put it on the wrong leg. Some may view this as a draw back. Then change it so any polling of the original production parameters only come from /api/v1/production. D`TR2 (P@$D j+C"qa7%A]4(uWP7T! Here is low light at the end of the day. Under some conditions, data for a given period may be temporarily unavailable. Here is heavy overcast at the end of the day with sun low and far to the side of the array. 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. This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. 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. 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. Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). Similarly, if you see no message in the Enlighten mobile app, your system is doing fine. But envoy_reader does not read it. Enlighten supports up to two versions of the API at any given time. Here is the output of envoy_reader from various Envoys. WebThe Envoy-S monitors the microinverters that are connected to the PV modules. With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. Long explanation that I don't think I have any unique problems, just that the mppt curve does not track well below 28% of peak array power. 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. 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. I tested your modified envoy_reader with my Envoy-S Metered Multiphase with metering disabled (no CT's). Already on GitHub? 0000154623 00000 n 0000410990 00000 n FEMA- Federal Emergency Management Agency If one microinverter in a solar PV system fails, what will occur? In metric, 1 meter is 100 centimeters and a kilometer is 1000 meters. Key Points /production.json: "type": "eim", "rmsCurrent": 0.534 And for the nice to have wishlist: It appears to work fine. Recently my meter box was moved and the sparkie put the consumption CT backwards. endobj Ideally, the user should be able to specify and track either or both from Home Assistant. If you dont have permission to view consumption data, the response code is 401. meter types, electrical connections) can vary across Australia. 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 have tested your latest envoy_reader.py. An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". : 0000161348 00000 n When I modify envoy_reader.phy to explicitly set endpoint_type to "P" then the production values are read from /api/v1/production and are displayed properly. Your message explains this. The darkish overcast looked like possible little snow storm coming. To troubleshoot this, check CT orientation and leads, compared with voltage measurements. No Home Assistant will not get fully updated automatically. This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. Is D5.0.49 newer than R4.10.35? Better ($) electric cars are using heat pumps more effectively to heat. If your system has AC Batteries: Some batteries havent charged or discharged recently. No news is good news! 0000004049 00000 n 827 0 obj <> endobj xref 827 81 0000000016 00000 n ct_enabled with default value True (requires no changes in existing client code). Install a phase coupler on the load side of the over-current protection device. Then a question, does the api return the eim values that is got from the envoy even when the activeCount = 0? 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. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. If you don't see any voltage pulses, replace the sensor. The start date must be at least one month ago. Very interesting indeed. By providing an optional ct_enabled parameter the user can override it for testing purposes. 0000375185 00000 n From above I derive the conclusion that the reason of the presence of all 3 phases on the 'power input' connector must be to measure the voltage of each phase (as there appears no other plausible reason for wiring all 3 phases on this connector). 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. I removed the inverter data and right now the values are zero due to no sunlight, but you should get an idea of what would be sent to Home Assistant once that sensor code is updated. Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? 0000011207 00000 n I'm following the current convention that was previously coded. endobj @rct the scraping blog was where I got that URL. You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. 1 0 obj 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. 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? Looks like you are checking for not set/zero vs. checking activeCount. 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 metering problems. In general, a Meter Issue indicates a system where on-site maintenance may be required. The production or consumption measurements received by the Enphase Cloud are negative. 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. 'lqgs:~>_A,XJNBPyF^h@~.]:XUaSeJmi*`L6Aj$FaLQPzi_~l[U66RO57YYZA/O3](8LLIFAZrsf/=qNe~^sjW9f+L`l7?d A 5K Continue reading for more information about each type of problem. 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 This is because envoy_reader assumes that when `envoy/production.json' exists that this is the location to read the Production data from. rmsCurrent and rmsVoltage if only single instances reported for these instead of separately per phase? So in practice it can be possible that only CT('s) for consumption are installed. The circuit passing through the production CT includes AC Batteries. I agree a better solution would be to have additional parameters. fbK1yBE~nF\|WG x0y,x,JX { [J*4 U4%0!AWeZ sPH@@-GTpGs*(zI1YJBBGNN]UU>h`H_))q~u}@a1(%=_n8XH 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. Instead of /stream/meter has anyone tried /ivp/meters/readings? If ct_metering_consumption is false then the. @rct If you have code changes could you post it to GitHub for a possible merge? Why not use actual values (with decimals, when reported)? It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. (I suspect something like: electrical induction metering). WebAN_6612_032 Energy Measurement in Split Phase Systems Using 78M6612 Rev. This is called the merged time series. In addition, the response includes the attribute meter_start_date, to indicate where in the time series the meter measurements begin to be used. <>/Metadata 3482 0 R/ViewerPreferences 3483 0 R>> 0000154881 00000 n I would like some input from @jesserizzo and others before opening a PR to merge this change. I hope you get the help you need. envoy_reader should handle all these (4) situations correctly. This page was generated at 03:27 AM. metered_production_readingtime Observation: metered values get truncated instead of rounded. I have had my solar setup for 1.5 years so far, no issue. Like I said I'm still thinking about it and weighing the pros and cons. This requires an alternative arrangement of the CTs for correct measurement. I suggest to use the term 'CT Metering' (or 'CT Metering Enabled') instead of "Metering (CT) Status". 0000007176 00000 n 0000023653 00000 n Application plans have minute and month limits. Would have to find a system that has 3Phase with Metering enabled and CTs installed. For just the powering of the Envoy a single phase would be sufficient. Gaps in reporting are not filled with 0-value intervals. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion 0000010160 00000 n metered_consumption wNow: 0.836 (gets truncated to 0). /production.json "type": "inverters", "wNow": 2235 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. The CT (current transformers) are used for measuring current. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details ^nBsEi. meter_issue One or more meters on the system are reporting unusual From the 'Envoy-S Metered Multiphase (ENV-S-WM-230) Installation and Operation Manual': Use a Phase Coupler for a Multiphase Site 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?
State High School Tennis Tournament,
Cantantes Masones Famosos,
Where Are The Virunga Mountains Located,
Articles I
