Data from /stream/meter (updates every second) shows the data separately for each phase but unfortunately this requires installer permissions. Each envoys element includes the following: Returns a list of systems for which the user can make API requests. Did you power off and repower your Enlighten box after you made those changes. 0000004049 00000 n Returns the summary along with the energy produced on the system over its lifetime. Details about my Envoy: limit is how many requests are allowed per period. WebThe use of any other type of CT will result in incorrect power measurements, and may permanently damage the WattNode meter. But that is an incorrect assumption because it is only valid when current transformers (CT) are enabled/installed. 0000020597 00000 n Yes the original bug in envoy_reader has been fixed. Valid values for datetime_format are iso8601 and epoch. (Envoy-S metered multi-phase (EU) with no CT's installed.). I've connected them using Enpase IQ7+ micro inverters and bought also a Envoy-S Metered with them to read out the production statistics. (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.). Meters are abbreviated using a lower case "m" in measurements. Are all three phases wired to your Envoy power connector_(most-left connector on the Envoy)_? Envoy firmware gets updated by Enphase automatically. 0000033020 00000 n 0000014056 00000 n 0000011718 00000 n 0000161348 00000 n To troubleshoot this, check CT orientation and leads, compared with voltage measurements. Is that new Envoy firmware? 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. So I'm having a hell of a time with my enphase envoy consumption measurements. There is a limit to the number of systems that can be returned at one time. If there is a problem, MyEnlighten and the Enlighten mobile app show a message to help you know what to do next. Enphase seems to have a bug where they sum the amperage values for each phase and then multiply that by 240 to get VA. That's wrong and results in a VA value for TOTAL CONSUMPTION that's upwards of twice what it should be. What use are values of e.g. 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. 0000014311 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. Observation: metered values get truncated instead of rounded. My envoy has values for those rather than all zero, because metering was turned on a while but wasn't giving the right values. So far, I haven't seen a flag from the Envoy API that indicates whether it is using the inverter measurements or the CTs, but maybe I haven't looked deeply enough. I'll return values with a decimal. I need to understand how the Home Assistant configuration interface interacts with envoy_reader to configure it. If so this may end up being the best solution, although it requires 2 requests. Then change it so any polling of the original production parameters only come from /api/v1/production. 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 Requests for times that do not fall on the 15-minute marks are rounded down. The rmsVoltage may actually be measured by the Envoy, but without any CT's installed, the rmsCurrent value apparently is a bogus value(?). The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. Example: It is possible to request a subset of the systems list. From the 'Envoy-S Metered Multiphase (ENV-S-WM-230) Installation and Operation Manual': Use a Phase Coupler for a Multiphase Site Enphase consumption CT measurement problem. If there is an issue with the Envoy meter measurements, youll see a message like this: If one or more of your AC Batteries hasnt charged or discharged for the last 72 hours, youll see a message like this: This may not indicate a problem, especially if there hasnt been enough sunshine to produce energy that exceeds your homes consumption, or if your homes energy use has gone down to the point that the batteries dont need to discharge. /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 Note: If a system does not include a given device type, that key is left out of the returned hash. I'm producing 1-5 kWh/day and I see almost the exact daily amount reducing my consistent 7 kwh daily usage. I can even see it go lower after that and work much better than it did on the way up. For just the powering of the Envoy a single phase would be sufficient. I assume a much larger EV is in our near-ish (2-3 year) future and getting TOU will absolutely make sense then. 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. Very interesting indeed. 0000161309 00000 n 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. 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). Can you confirm that you can get this without any authentication? A device is considered active if it has not been retired in Enlighten. Not sure what the actual url for the page is though. Envoy reader makes an assumption depending on the type of Envoy whether CT metering is being used. Here is heavy overcast at the end of the day with sun low and far to the side of the array. That's one line changed on the Home Assistant side and as long as the reviewer is okay with the API side change log the updated API will be included in the next Home Assistant release. 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. 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 In cases such as these, the response code is 422 and the response body includes an error reason as well as the parameters used to process the request. Active does not imply that the device is currently reporting, producing, or measuring energy. My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. It causes Home Assistant to not update after a couple of polls. 0000375185 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. My blue bars show production and yours appear to show consumption. It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. Key Points 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. 0000015247 00000 n To troubleshoot this, check CT orientation and leads, compared with voltage measurements. The darkish overcast looked like possible little snow storm coming. WebThere is an issue with the meter measurements. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details By default, systems are returned in batches of 100. The CT (current transformers) are used for measuring current. Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. As a result the reported Production values are either 0 or some bogus value. In some extreme cases, you may receive a 503 error instead of a 409. Your message explains this. All measurements are in Watt hours. For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. 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 . I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. Copyright 2023 Enphase Energy. endobj "Metered Production data not available for your Envoy device.". @lnlp - trying to answer a few of your questions with what I've learned so far. The circuit passing through the production CT includes AC Batteries. )bJ60F-phEZ I wonder if they can tweek low light efficiency for me? @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? So in practice it can be possible that only CT('s) for consumption are installed. 0000048897 00000 n %PDF-1.5 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. 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. Manual: Add an extra parameter e.g. The new version of API (v4) is available at: developer-v4.enphase.com. 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. 0000013177 00000 n For example, a request to. I would like some input from @jesserizzo and others. Some may view this as a draw back. There are no gaps in the time series. I would also prefer if the timestamp of when the values were updated can be added, e.g. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. /api/v1/production, Here is my current http://envoy.local/api/v1/production. The heating system is just resistance heaters on that car so it's like a giant toaster oven. I currently check the /api/v1/production data in a browser and refresh manually. And the metered_* parameters come from the appropriate section of /production.json that contains type of eim. Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream The API accepts a number of parameters. Some batteries havent charged or discharged recently. Copyright 2014 SolarReviews All rights reserved. https://github.com/dlmcpaul/EnphaseCollector. I'm following the current convention that was previously coded. 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. In general, a Meter Issue indicates a system where on This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. Have a question about this project? 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 I'll look through the code and see what it might take to implement. I would have to look into how to send specific data from the envoy_reader API to Home Assistant. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? The code is currently returning values for those rather than your 'not available' message. My Envoy reports tiny metered values while metering is disabled. Have you tried flipping the CTs 180 degrees? 0000139340 00000 n |nxv&T["mhQ zt.f&Q4W?t4:?TrJdoV1EBEJ!,^G@-C'[lUZTD;Z*fd'w?Z:Fo77c[iZ=vWKc~Wv6c? 0000032874 00000 n Intervals are 15 minutes in length and start at the top of the hour. Learn what you can do if the systems meter has stopped reporting. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. 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. Solar Production CT MUST measure all solar circuits on site. 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. 0000410990 00000 n 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. Got your message a little before 11am my time so low production is just winding down. Electrical system: 3-phase 230V. All rights reserved. Does that get installed automatically? 0000018303 00000 n WebAN_6612_032 Energy Measurement in Split Phase Systems Using 78M6612 Rev. And possibly add another parameter called activeCTCount to tell the user if the Metering feature is enabled on their Envoy? Reported values while metering disabled: You can sign up to be notified by email if your system experiences either type of production issue. A CT is installed and Metering is only monitoring Production. measure resistance from black wire at lgm connector (while disconnected) to ground behind side panel inside rear cargo area. With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. 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. 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. 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 (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. It is important to understand these differences when installing Envoy CTs. Here's my output. Better ($) electric cars are using heat pumps more effectively to heat. Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. @lnlp I'll release the new version on pypi this weekend and open a PR on the Home Assistant side as well. The output suggests there are four data sources production from the inverters, and then a type "eim" reporting production, a type "eim" reporting "total consumption", and a type "eim" reporting "net consumption". 0000016703 00000 n Do not violate the other restrictions described in the Enphase, Copyright 2023 Enphase Energy, Inc. All rights reserved. % Actual Production that gets updated is available via envoy/api/v1/production however. The circuit passing through the consumption CT does not include AC Batteries. Keeping in mind that consumption monitoring is an optional add on that doesnt interfere with the core functionality of the solar system. Examples in this documentation exclude the API key and the user_id for clarity. 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. You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. ct_enabled with default value True (requires no changes in existing client code). lastReportDate and readTime (there's little consistency in the different names unfortunately). See following comment in #46 for more information. An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". 0000154623 00000 n You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. If ct_metering_consumption is false then the. 0000139882 00000 n 0000017403 00000 n 0000011207 00000 n Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? Under some conditions, data for a given period may be temporarily unavailable. So this voltage is apparently read from L1 on the 'power input' connector. Enphase Ensemble Systems. 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. Do not nofollow your links to Enphase. If the system doesnt have any microinverters installed, the response includes an empty intervals array. This is caused by my Envoy not by envoy_reader. 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. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. It could be the CTs are plugged into the wrong socket. A phase coupler for communication with the inverters is not built-in to the Envoy. 0000017430 00000 n 0000093917 00000 n metered_consumption_readingtime, How about simplifying Gaps in reporting are not filled with 0-value intervals. I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? please contact Enphase Technical Support. Regarding measurements for each phase, he Envoy has a URL that deliveries a stream of measurements -. Copyright 2023 Enphase Energy. So to make changes unfortunately we can't add a new sensor and display the new data. 0000470581 00000 n A faulty speed sensor will often be accompanied by a check engine light and trouble code. 0000003706 00000 n I see where you are coming from but to keep the code simple I'm retrieving inverter production values from /api/v1/production rather than pulling a value from /production.json and the rest from /api/v1/production. The installers could have put it on the wrong leg. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. 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. 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. 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. Already on GitHub? /production.json: "type": "eim", "rmsCurrent": 0.534 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. I've tried switching polarity on the CTs, and moving them around, but I can't get it into a real range. Can you open a new issue (enhancement) to track this one? 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. 0000303679 00000 n This is just low sun with overcast far to the side of the array. Copyright 2014 SolarReviews All rights reserved. 0000016440 00000 n I'm sorry about this! This is because envoy_reader assumes that when `envoy/production.json' exists that this is the location to read the Production data from. But have to think about current users. The time series includes one entry for each day from the start_date to the end_date. It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's @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. /api/v1/production does not contain "readingTime" but /production.json "type": "inverters" does. All times are GMT-5. In general, a Meter Issue indicates a system where on-site maintenance may be required. <> When the Envoy and the microinverters cannot talk for extended periods of time the microinverters try to hold a basic record of I produced x much power from x date to x date. Here is the output of envoy_reader from various Envoys. 0000016000 00000 n Refer to the Release notes page for any recent changes to the Enlighten API. (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? There are 1609 meters in a statute mile. Data coming from /api/v1/* is updated every 5 minutes. My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. 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 For more details, visit 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. Do you expect to get the fix into the next (bug-fix) release (presumably 2020.12.1)? 827 0 obj <> endobj xref 827 81 0000000016 00000 n Learn what you can do if the systems meter has stopped reporting. WebUnplug the Envoy from the AC outlet and plug it in once again. So if the Envoy has Metering enabled values will be retrieved from /production.json and if Metering is not enabled values will be retrieved from /api/v1/production. The Enphase Home Energy System meters solar production and home electrical loads. 0000339432 00000 n I use Envoy S but without any CT's installed. Input date range for rgm_stats is restricted to 7 days. Any link back to Enphase should be follow-able. There are no gaps in the time series. I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. You have your consumption meter set to "load with solar production" or "load only"? Note: I've got production and consumption metering turned off (activeCount == 0). I've seen that referred online as being able to get the individual readings and maybe it doesn't require the installer password. Or atleast get reporting working for all attributes for each hardware platform. EV owner since 2012. Please refer to the Enphase technical system wiring examples for further clarification of correct CT placement across the electrical cabling of the site. meter types, electrical connections) can vary across Australia. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. The review process is greater. Currently I do not have TOU rate pricing. The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. meter_issue One or more meters on the system are reporting unusual When I investigate the raw numbers from interrogating the envoy direcly it actually shows me the low power factor. I've got the old (non-IQ) version of the envoy. I will make a capture tomorrow when it's light and the system is actualually producing. If the total duration requested is more than one month, returns one month of intervals. Use production_meter_readings or energy_lifetime instead. Can you confirm that you can get this without any authentication? Better ($) electric cars are using heat pumps more effectively to heat. Looks like you are checking for not set/zero vs. checking activeCount. All times are GMT-5. 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. This requires an alternative arrangement of the CTs for correct measurement. 0000128138 00000 n The system will continue to operate normally B. 0000139909 00000 n I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. hQILSQ=S?H)B) B$4 0000001916 00000 n 'active' : 'js-change-currency' ?> //= plugin_dir_url( __FILE__ ) . All API requests require your API key and a user_id. But envoy_reader does not read it. Why not use actual values (with decimals, when reported)? If production or consumption measurements received by Enlighten are negative, there could be a CT Measurement issue. We will provide When current transformers (CTs) are wrapped around a live I would like some input from @jesserizzo and others before opening a PR to merge this change. 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. 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. By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. WebThe Envoy brings you the real-time, module-level performance data that makes it easy to monitor your system or fleet from any web-connected device. Could this have been fixed in a later firmware revision? Well sorry to say but there was a bug in the code. Thank you for opening those issues. New releases (due to incompatible changes) are communicated well in advance of removing the older one. 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. Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. I hope you get the help you need. According to the Envoy-S Metered Multiphase Installation manual there are 3 CTs installed on the Production and Consumption sides. Please note that the Enlighten Systems API does not provide performance data at a panel or microinverter level. Like I said I'm still thinking about it and weighing the pros and cons. That may be a clue. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. The text was updated successfully, but these errors were encountered: @lnlp Would it be possible for you to post a copy of your /production.json? returns systems that currently have production issues. If your system has AC Batteries: Some batteries havent charged or discharged recently. Why not use actual values (with decimals, when reported)? Returns consumption as measured by the consumption meter installed on the specified system. 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. On the MyEnlighten desktop application, the icon to the left of your system name tells you how your system is doing. 0000268048 00000 n 0000012488 00000 n My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. 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). 0000033107 00000 n 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. WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. Examples in this document exclude the callback parameter for clarity. Completed - The scheduled maintenance has been completed. 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. production_readingtime (source: production.json production inverters readingTime) Can you open a new issue (enhancement) to track this one? 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. 0000009524 00000 n I agree a better solution would be to have additional parameters. 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. According to the IQ Envoy manual this is possible if the user wants revenue-grade production metering. Recently my meter box was moved and the sparkie put the consumption CT backwards.
Noose Emoji Copy And Paste,
Juwan Howard House Ann Arbor,
Articles I