0000128068 00000 n (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? 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. Here is the output of envoy_reader from various Envoys. I wonder if that is why your blue bars are labeled production but look like they follow a consumption pattern? I did notice that there was only one solar CT and that may need to be on a particular leg as well. 0000010160 00000 n Yes, I do want and think the values for both inverters and eim should be accessible if available. Here's my output. This is because envoy_reader assumes that when `envoy/production.json' exists that this is the location to read the Production data from. 0000452685 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. 1 m is about 39.37 inches. Mmm, just wondering: will a HA 2020.12.1 bug-fix release automatically become 2021.01.0 if released in January 2021? It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. (My solar installer did not connect L2 and L3 on the 'power input' connector so I am currently unable to verify for ph-b and ph-c.). Electrical system: 3-phase 230V. It would be nice if other useful parameters e.g. => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's 0000011207 00000 n According to the Envoy-S Metered Multiphase Installation manual there are 3 CTs installed on the Production and Consumption sides. The circuit passing through the consumption CT does not include AC Batteries. An Enphase team member may follow up with you about your feedback. If there's voltage over 0.2 volts in any wire or connection, check for corroded, damaged or loose wires. Instead of /stream/meter has anyone tried /ivp/meters/readings? If the meters milliamp scale goes up to 500mA, then The production or consumption measurements received by Enlighten are negative. 0000232417 00000 n So I just display the values unless the device actually does not support metering. When this parameter is provided, the returned JSON is wrapped in the callback. 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_*. EIM - Your guess on the meaning of the acronym is 'electrical induction metering' is possibly correct. Can you open a new issue (enhancement) to track this one? 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. 0000093917 00000 n For example, there are 100 centimeters in a meter. Ideally, the user should be able to specify and track either or both from Home Assistant. The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, Endpoints that receive times expect the time to be expressed in Unix epoch time. 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. An alternative to polling /api/v1/production is to use production.json type == inverter whLifeTime and compute the delta locally, either within envoy reader, or Home Assistant. This does not require to connect all 3 phases to the power connector. endobj OUTBACK SEALED GRID-TIE INTERACTIVE INVERTERS, Skip to the beginning of the images gallery, Contact us for availability, pricing and freight quote, Contractor and commercial discounts available, Specials and multi-pallet/container discounts, Complete residential and commercial grid-tie Solar kits, Design assistance, Permit submittals, Schematics, Enphase Monitoring CT Getting Started Guide, Enphase Consumption Monitoring CT-200-Split Installation Guide, Enphase Ensemble Technology System Planning Tech Brief, Envoy requires 2 CTs to connect to terminal block. I'll look through the code and see what it might take to implement. I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. Systems that are configured to report infrequently can show large deltas on all meters, especially when end_at is close to the current time. Maybe this is only of interest to me. I WebMeasure for voltage across individual wires and connections in the charging system. If the total duration requested is more than one month, returns one month of intervals. All times are GMT-5. 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). And for the nice to have wishlist: If your application does not allow for you to include an image, you must include the text Powered by Enphase Energy. "Metered Production data not available for your Envoy device." I would like some input from @jesserizzo and others. to your account. Have a question about this project? All rights reserved. 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? 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 0000013432 00000 n 0000012488 00000 n It is important to understand these differences when installing Envoy CTs. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. There is an issue with the meter measurements. The time series includes one entry for each day from the start_date to the end_date. For example, a request to. Some batteries have stopped Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. I'll have to look into this one a bit. Thanks for your continuing efforts! As previously requested please add the following output parameters: Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? 3 0 obj If the system does not have a meter, returns 204 No Content. To enable correct operation of the Enphase Home Energy system components (including the Enphase AC Batteries), the Envoy must correctly measure the current flow across the electrical circuits via the CTs. The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. This is caused by my Envoy not by envoy_reader. 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. There are 1609 meters in a statute mile. 0000161348 00000 n 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. For just the powering of the Envoy a single phase would be sufficient. I will make a capture tomorrow when it's light and the system is actualually producing. Why not use actual values (with decimals, when reported)? 0000161309 00000 n All API requests require your API key and a user_id. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. Web The Envoy-S Metered uses precision Current Transformers (CTs) to measure PV production (accuracy 2.5%) from the solar main supply switch and home energy consumption from the AC mains. When CT metering is off you have to look at /api/v1/production for the WH accumulation (today, 7 day) totals. |JU\"K2b 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. Copyright 2014 SolarReviews All rights reserved. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Each envoys element includes the following: Returns a list of systems for which the user can make API requests. I have assumed it was 'Voltage and Current Metering' using the ohm's law variables (P = EI), so EIM. Vy`|2D(S4{D0d}0z%9"~JkjS}7hrbrr* (Fg^.CVpL54};F3ay|(%QoRpoH"L_ l%gLK{1xD`S=W =(y-}wxu-A3't2vV1vl# 0kl ^EgH}|X'sAPF(SG& GG JWtDBydlGM3 iD1-R\Vb-P?[+1LDpra|pXk=H4/g2+B1b_%11IQ(=Q The time series includes one entry for each day from the start_date to the end_date. If it continues to display Envoy Failure or if it never moves beyond the : 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. All requests support an optional callback parameter. I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? @rct I get what you're saying. My envoy has been updated twice (or more) as far as I remember. Copyright 2023 Enphase Energy. Contact us for sales, quantity discounts and expert reviews for the Enphase CT current transformer for Envoy. My solar installer connected only a single phase to power the Envoy, while all three phases L1, L2 and L3 can be connected. I would like some input from @jesserizzo and others before opening a PR to merge this change. Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. Intervals are 5 minutes in length and start at the top of the hour. CT Measurements" from a consumption CT on one of the phases. 0000339432 00000 n WebMake sure to keep your meter lead wires away from engine moving parts during this test. So this voltage is apparently read from L1 on the 'power input' connector. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? My Envoy homepage shows "Software version R4.10.35 (6ed292)" is that the Envoy's firmware version? 0000048797 00000 n The review process is greater. In general, a Meter Issue indicates a system where on-site maintenance may be required. 0000410990 00000 n WebC. @lnlp Thanks! 0000012231 00000 n We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. It seems the the values are almost the same and they are both updated every 5mins. My 8x320W=2.56 kw mono array gets the IQ6+ inverters running at pf=1 at 700 VA. 0000003741 00000 n Learn what you can do if the systems meter has stopped reporting. 0000033107 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. My Envoy reports tiny metered values while metering is disabled. 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. 0000411029 00000 n I agree a better solution would be to have additional parameters. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. Requests for times that do not fall on the 5-minute marks are rounded down. @lnlp - trying to answer a few of your questions with what I've learned so far. meter_issue One or more meters on the system are reporting unusual Web//= $_COOKIE['currency'] == 'USD' ? 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. This is the output: There is a limit to the number of systems that can be returned at one time. 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. An Enphase team member may follow up with you about your feedback. 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. 0000014056 00000 n stream An Enphase team member may follow up with you about your feedback. Install a phase coupler on the load side of the over-current protection device. 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. Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? 0000154881 00000 n Application plans have minute and month limits. /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 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. 0000016440 00000 n Returns summary information for the specified system. It does show in the HTML output, but scraping should be avoided. That may be a clue. Connecting only a single phase to the 'power input' connector (instead of all 3) already makes the system work (but will cause some values to be reported incorrectly). You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. All times are GMT-5. @gtdiehl - Here's my Envoy IQ (metering turned off) output using your change_polling_pages branch: I originally had the metered values not being returned when metering is disabled (activeCount == 0), but then I thought someone might want these values or some other reason. You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. The circuit passing through the production CT includes AC Batteries. endobj 0000011718 00000 n 0000017877 00000 n Valid values for datetime_format are iso8601 and epoch. privacy statement. Could this have been fixed in a later firmware revision? Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. Like I said I haven't looked through all of the comments yet. Specifically it has to do with the power factor. <> The response includes intervals that have been reported for the requested period. 0000023653 00000 n All were taken at the same time. I have it set on load with solar production. I use Envoy S but without any CT's installed. metered_consumption wNow: 0.836 (gets truncated to 0). 0000139340 00000 n Got your message a little before 11am my time so low production is just winding down. I suggest to use the term 'CT Metering' (or 'CT Metering Enabled') instead of "Metering (CT) Status". On the MyEnlighten desktop application, the icon to the left of your system name tells you how your system is doing. I have an Enphase system but it only has production and the blue bars are in the same orientation as in your chart. A CT is installed and Metering is only monitoring Production. Handle Envoy S (and Envoy IQ) without CT's as 'endpoint_type' "P" instead of 'endpoint_type' "PC". Yes the original bug in envoy_reader has been fixed. /api/v1/production, Here is my current http://envoy.local/api/v1/production. This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. In that case, the response code is 500 and the response body is. 0000014311 00000 n But have to think about current users. (Maybe you are mistaking with the cloud API's update frequency?). Data coming from /api/v1/* is updated every 5 minutes. For a 3-phase installation I would need to buy 4 additional CT's while consumption and production data is already provided by my smart electricity meter (via DSMR P1 port). production_readingtime (source: production.json production inverters readingTime) 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. When the production version of envoy_reader will be updated, will this get automatically updated in existing Home Assistant (Enphase Envoy add-in) installations? The heating system is just resistance heaters on that car so it's like a giant toaster oven. No Home Assistant will not get fully updated automatically. 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. 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. /api/v1/production does not contain "readingTime" but /production.json "type": "inverters" does. m%=747:5e}b6K8W]WQqLLOm+..^l,b09#Sx"Urk`d/2Qo1)I:wsKakSfj+C h`JqYYYvXg/._nl(E,o@8;"9JXq51)j|*)1\.ipYR?g/_1k'J1jO. IF you require further technical clarification for your installationplease contact Enphase Technical Support. 0000023514 00000 n That's why I'm asking to track the above as separate issues. 0000015247 00000 n https://github.com/dlmcpaul/EnphaseCollector. All measurements are in Watt hours. I believe there should be the option to get either or both production wNow values for the inverters and the eim (CT) structures. Exactly: I have only CT's installed for measuring Consumption "CT's" is plural but consumption/eim/activeCount only shows 1. metered_production_readingtime trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. Envoy S Production data is not read when not using current transformers which renders reported Production data useless. 0000375146 00000 n My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. 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. All rights reserved. Use production_meter_readings or energy_lifetime instead. I does give a way of polling the detailed data from each CT for what looks to be all three phases, whether it is installed or not. A. "Metered Production data not available for your Envoy device.". You can change this in the. Envoy firmware gets updated by Enphase automatically. 9 kW solar, 42kWh LFP storage. Thank you for opening those issues. Returns the last known odometer reading of each revenue-grade production meter on the system as of the requested time. I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. And the metered_* parameters come from the appropriate section of /production.json that contains type of eim. Sometimes, but not rmsCurrent and rmsVoltage could be reported by envoy_reader as well. 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 recent Envoy models that output production.json). The Envoy-S Metered is a system monitoring tool, and control device. Software Version: R4.10.35 (6ed292) If your system is producing less energy than your installer estimated, youll see a message like this: Click Learn more for information on how to get help with the problem. See Andrew Mitchell's Enlighten Manager Mastery video for a visual walkthrough of CT troubleshooting using Enlighten Manager. The rationale is so that the Home Assistant sensor monitored_conditions does not have to change which ultimately does not create a breaking change or force users to change their environment. Regarding measurements for each phase, he Envoy has a URL that deliveries a stream of measurements -. Not sure what the actual url for the page is though. 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. The Envoy backend should actually have both values, and the API retrieving the data I was able to check a couple things this weekend. I've seen that referred online as being able to get the individual readings and maybe it doesn't require the installer password. 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. 0000196664 00000 n 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion Metering requirements (i.e. Enphase Ensemble Systems. 0000063893 00000 n % In Home Assistant ('Enphase Envoy' add-in which uses envoy_reader) I do not get actual values for all 4 values shown in /api/v1/production. It could be the CTs are plugged into the wrong socket. 0000001916 00000 n 0000078062 00000 n 0000012600 00000 n 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. The Enphase Home Energy System meters solar production and home electrical loads. With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. 827 0 obj <> endobj xref 827 81 0000000016 00000 n 0000139882 00000 n Examples in this documentation exclude the API key and the user_id for clarity. The code currently does a check to see if the attributes of production and consumption exist in the web page. An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". Question for you or anyone who has CT metering turned on: I believe production.json - production[0].wNow shows the current power from the inverters regardless of whether CT metering is turned on or not. And possibly add another parameter called activeCTCount to tell the user if the Metering feature is enabled on their Envoy? measure resistance from black wire at lgm connector (while disconnected) to ground behind side panel inside rear cargo area. It appears to work fine. The CT (current transformers) are used for measuring current. In 'case B' one may wonder why the 'power connector' on the left exists and allows to wire all 3 phases. I added some more detail in the Issue #41. 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. By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. If your systems meter has stopped reporting, youll see a problem message like this: Under some conditions, data for a given period may be temporarily unavailable. Please note that the Enlighten Systems API does not provide performance data at a panel or microinverter level. 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 From this perspective it is not required to connect all 3 phases to the power connector. I would also prefer if the timestamp of when the values were updated can be added, e.g. <>/Metadata 3482 0 R/ViewerPreferences 3483 0 R>> <>/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>> 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. Reduce the number of concurrent threads in your application in order to avoid this response code. I would expect to see at least three different sets of values, one for each phase. 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 By providing an optional ct_enabled parameter the user can override it for testing purposes.
New Restaurants Coming To Zanesville Ohio, Cognitive Behavioral Therapy Session Transcript, Andersen Window Screens Replacement, Articles I