WebThe Envoy-S monitors the microinverters that are connected to the PV modules. The circuit passing through the production CT includes AC Batteries. In that case, where is the total power reported in /production.json ? Contact us for sales, quantity discounts and expert reviews for the Enphase CT current transformer for Envoy. See following comment in #46 for more information. Copyright 2014 SolarReviews All rights reserved. Intervals are 15 minutes in length and start at the top of the hour. If your system has stopped reporting data, youll see a problem message like this: Learn what you can do if your system stops reporting data. 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. I see information in /api/v1/procuction and /api/v1/production/inverters being updated every 5 minutes. Any link back to Enphase should be follow-able. Can you open a new issue (enhancement) to track this one? 0000196664 00000 n Returns the last known odometer reading of each revenue-grade production meter on the system as of the requested time. I really like to give the user all of the data and let them figure out what they want to use. /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? I hope we can see it being updated in Home Assistant as well soon. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? Learn what you can do if the systems meter has stopped reporting. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. Unrecognized parameters are ignored. My consumption only power-factor when I look at it from the installer toolkit says around 1.0, but the apparent power is nearly double the watt measurement which implies a pf of around 0.5. WebEnlighten declares a Meter Issue system status when it detects a possible problem with the CT or storage measurements. @rct If you have code changes could you post it to GitHub for a possible merge? Enlighten declares a Meter Issue () system status when it detects a possible problem with the CT or storage measurements. 0000013177 00000 n Like I said I haven't looked through all of the comments yet. Data coming from /api/v1/* is updated every 5 minutes. @lnlp - trying to answer a few of your questions with what I've learned so far. In my comments above, I was arguing for the case to still be able to get the inverter numbers even if metering is enabled. Have an assistant crank the engine for a few seconds while you watch the meter's readout. 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. I added some more detail in the Issue #41. 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. I've connected them using Enpase IQ7+ micro inverters and bought also a Envoy-S Metered with them to read out the production statistics. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. An Enphase team member may follow up with you about your feedback. 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). As previously requested please add the following output parameters: Is that new Envoy firmware? 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). => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's You have your consumption meter set to "load with solar production" or "load only"? There is an issue with my envoy meter measurements - Enphase Recently my meter box was moved and the sparkie put the consumption CT backwards. This is not my experience. 0000001916 00000 n 0000140307 00000 n My envoy has been updated twice (or more) as far as I remember. envoy_reader should handle all these (4) situations correctly. 0000093464 00000 n It appears to work fine. Under some conditions, data for a given period may be temporarily unavailable. There isn't any identifying object info inside the two objects in the top-level list. 0000017430 00000 n 0000093917 00000 n 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. 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. The sensor should produce a voltage pulsing signal. 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. If these are zero than poll data from the other production page. There's simply no way I have a power factor of 0.52 in the house. 0000063893 00000 n Under some conditions, data for a given period may be temporarily unavailable. I've got the old (non-IQ) version of the envoy. WebAN_6612_032 Energy Measurement in Split Phase Systems Using 78M6612 Rev. 0000009524 00000 n 3 0 obj In the "inverters" section? With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. A difference of 1 Watt, which may be caused by a rounding error, or by a small difference in moments of measurement. ct_enabled with default value True (requires no changes in existing client code). |JU\"K2b issue with envoy meter measurements Envoy Status I believe there should be the option to get either or both production wNow values for the inverters and the eim (CT) structures. Could this have been fixed in a later firmware revision? My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. Looks like you are checking for not set/zero vs. checking activeCount. Have you tried flipping the CTs 180 degrees? If your application does not allow for you to include an image, you must include the text Powered by Enphase Energy. Electrical system: 3-phase 230V. The fix was merged into the dev branch yesterday, which usually means it will make it into the next release (2021.01.0). If there is a problem, MyEnlighten and the Enlighten mobile app show a message to help you know what to do next. The PF of the. A. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. If ct_metering_consumption is false then the. For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. Returns a time series of energy produced on the system over its lifetime. You can change this in the. One foot is the same as 12 inches, and a yard is 36 inchesand the confusion continues. Anyway, I tried reversing both the production CTs and swapping their phases. Copyright 2023 Enphase Energy. Enphase Consumption Monitoring CT for Envoy - Solar 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. 0000003895 00000 n @OllemGit Would it be possible for you to verify this? 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. Better ($) electric cars are using heat pumps more effectively to heat. For more details, visit 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. 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. IF you require further technical clarification for your installationplease contact Enphase Technical Support. Manual: Add an extra parameter e.g. (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.). 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. Note: If a system does not include a given device type, that key is left out of the returned hash. So I thought I'd update people on what I found just in case someone else runs into this problem. 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. <> Returns the summary along with the energy produced on the system over its lifetime. Better ($) electric cars are using heat pumps more effectively to heat. 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). This is the output: <>/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>> There are no gaps in the time series. This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. Envoy x=r?#Z[Sd{q20$&! It is important to understand these differences when installing Envoy CTs. Observation: metered values get truncated instead of rounded. Envoy Completed - The scheduled maintenance has been completed. 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. metered_production wNow: 2.79 (gets truncated to 2) When this parameter is provided, the returned JSON is wrapped in the callback. 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. Endpoints that receive times expect the time to be expressed in Unix epoch time. How NASA Lost a Spacecraft From a Metric Math Mistake 0000375146 00000 n @lnlp Thanks! Last one. 0000033107 00000 n An explanation for the difference may be rounding errors or different time of measurement. 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. My Envoy homepage shows "Software version R4.10.35 (6ed292)" is that the Envoy's firmware version? This is a bit more than one yard. The response includes intervals that have been reported for the requested period. 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. lastReportDate and readTime (there's little consistency in the different names unfortunately). Examples in this document exclude the callback parameter for clarity. 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 . There is an issue with your envoy meter measuremen 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. Returns summary information for the specified system. Is it correct that you have only one single CT for consumption? String attributes must be URL-encoded. Though this time I had someone add my PR to the list of PRs that should be included in 2020.12.1. Observation: metered values get truncated instead of rounded. In my situation (ct_metering_production is False) the production value is read correctly from the production/inverters section in production.json. All were taken at the same time. 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. If the system doesnt have any consumption meters installed, the response includes an empty intervals array. 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. 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. /production.json: "type": "eim", "rmsVoltage": 245.583 The rmsVoltage may actually be measured by the Envoy, but without any CT's installed, the rmsCurrent value apparently is a bogus value(?). 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. 0000003706 00000 n EDIT: I actually just found a setup like this. Key Points production_readingtime (source: production.json production inverters readingTime) The circuit passing through the production CT includes AC Batteries. Web//= $_COOKIE['currency'] == 'USD' ? If you are not sure how to meet these requirements, please contact api@enphase.com before you launch anything. If you don't see any voltage pulses, replace the sensor. What about 3-phase systems? So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. 0000017877 00000 n 0000155287 00000 n You signed in with another tab or window. Returns the energy production of the system for the month starting on the given date. Thank you for opening those issues. 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. Sign in Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. 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 Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? The CT (current transformers) are used for measuring current. WebUnplug the Envoy from the AC outlet and plug it in once again. 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. Some may view this as a draw back. 0000015247 00000 n Well sorry to say but there was a bug in the code. It would be nice if other useful parameters e.g. If the total duration requested is more than one day, returns one day of intervals. As a result the reported Production values are either 0 or some bogus value. The installers could have put it on the wrong leg. 0000017403 00000 n metered_consumption wNow: 0.836 (gets truncated to 0). I use Envoy S but without any CT's installed. Intervals are 5 minutes in length and start at the top of the hour. Envoy S Production data is not read / read incorrectly when 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. I'm not sure on this one. New releases (due to incompatible changes) are communicated well in advance of removing the older one. On the MyEnlighten desktop application, the icon to the left of your system name tells you how your system is doing. Planning and installing consumption monitoring It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. Example: It is possible to request a subset of the systems list. 0000007176 00000 n It does show in the HTML output, but scraping should be avoided. If you dont have permission to view consumption data, the response code is 401. There was a reply in the Home Assistant Community forum where a person took this screenshot. Energy consumption CT monitoring for home solar systems Metering requirements (i.e. 0000339393 00000 n I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. Returns consumption as measured by the consumption meter installed on the specified system. & 0000161348 00000 n (for recent Envoy models that output production.json). My utility company (Xcel) has a great program where the rate is ~$0.04 per kWh which is awesome. Enphase Envoy S 'metered' Multiphase (probably identical to Envoy IQ). 0000268009 00000 n 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. 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 Got your message a little before 11am my time so low production is just winding down. 0000012488 00000 n Envoy S Production data is not read when not using current transformers which renders reported Production data useless. There is an issue with the meter measurements. This endpoint can return a response of Data Temporarily Unavailable. All measurements are in Watt hours. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. Envoy Yeah hopefully it'll make it into the 0.119 release! Sign up for a free GitHub account to open an issue and contact its maintainers and the community. "[}QXD/jD NCrncVa @L*23m Compatible changes do not result in a change to the version number. WebMake sure to keep your meter lead wires away from engine moving parts during this test. 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. My solar installer connected only a single phase to power the Envoy, while all three phases L1, L2 and L3 can be connected. From what I have seen on the Envoy IQ it only accumulates WH totals (today and 7 day) in the eim production structure of production.json WHEN CT metering is enabled. Some may view this as a draw back. Envoy reader makes an assumption depending on the type of Envoy whether CT metering is being used. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. If a meter or meters are installed on the system, measurements come from the meter; otherwise, measurements come from the microinverters. 'lqgs:~>_A,XJNBPyF^h@~.]:XUaSeJmi*`L6Aj$FaLQPzi_~l[U66RO57YYZA/O3](8LLIFAZrsf/=qNe~^sjW9f+L`l7?d A 5K and Then change it so any polling of the original production parameters only come from /api/v1/production. I tried to take a screenshot but it did not come through very well. Attributes that are times are named accordingly (e.g., operational_at, last_report_at, start_at, end_at). This is caused by my Envoy not by envoy_reader. In some extreme cases, you may receive a 503 error instead of a 409. I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. Use production_meter_readings or energy_lifetime instead. 0000012600 00000 n I'll return values with a decimal. When the filter is reference, both reference and other_references are searched. Enphase Envoy My blue bars show production and yours appear to show consumption. Examples in this documentation exclude the API key and the user_id for clarity. All rights reserved. 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. You can sign up to be notified by email if your system experiences either type of production issue. 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. 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. In general, a Meter Issue indicates a system where on-site maintenance may be required. 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. 0000078062 00000 n 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. The Envoy-S Metered uses precision Current Transformers (CTs) to measure PV production 0000003055 00000 n Here is low light at the end of the day. Examples include asking for stats starting at a time that is later than the systems last reported interval, or asking for stats before a system has started production. Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). 0000139611 00000 n Is D5.0.49 newer than R4.10.35? I would like some input from @jesserizzo and others. In 'case B' one may wonder why the 'power connector' on the left exists and allows to wire all 3 phases. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion Meter The Enlighten Systems API % While much of the rest of the world uses the metric system of centimeters, meters, and kilometers, US has continued to the English units. How to fix a 'Meter Issue' system error message? - Support Did you power off and repower your Enlighten box after you made those changes. production.json eim only shows an aggregated number. Envoy-S Installation and Operation The Enlighten Systems API returns JSON. 0000010645 00000 n 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. Very interesting indeed. Please refer to the Enphase technical system wiring examples for further clarification of correct CT placement across the electrical cabling of the site. 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. 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. Energy Measurement in Split-Phase Systems Using Sometimes, but not So I'm having a hell of a time with my enphase envoy consumption measurements. That may be a clue. Or atleast get reporting working for all attributes for each hardware platform. However, each request may optionally include it. I am quite sure my problem is based in the start-up voltage and minimum voltage. 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. So I just display the values unless the device actually does not support metering. 0000128231 00000 n Why not use actual values (with decimals, when reported)? This page was generated at 03:27 AM. between the phases to allow the Envoy to communicate with all of the Enphase devices in the system. )bJ60F-phEZ 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 As an example, NSW residents previously had gross metered solar systems. All times are GMT-5. I assume a much larger EV is in our near-ish (2-3 year) future and getting TOU will absolutely make sense then. I tested your modified envoy_reader with my Envoy-S Metered Multiphase with metering disabled (no CT's). 0000004049 00000 n Installing the Enphase Envoy-S Metered (Maybe you are mistaking with the cloud API's update frequency?). Part number: 800-00554-r03, Instead of /stream/meter has anyone tried /ivp/meters/readings? Continue reading for more information about each type of problem. 0000012231 00000 n 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. 0000139909 00000 n 0000154623 00000 n 'active' : 'js-change-currency' ?> //= plugin_dir_url( __FILE__ ) . 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. Cross your fingers, and I'm hoping it will be included in 2020.12.1.