issue with envoy meter measurements

By clicking Sign up for GitHub, you agree to our terms of service and Then change it so any polling of the original production parameters only come from /api/v1/production. All measurements are in Watt hours. Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Be aware that CT's can be installed for either Production, or Consumption, or both. For the best experience on our site, be sure to turn on Javascript in your browser. endobj : But envoy_reader does not read it. 0000339432 00000 n Metering requirements (i.e. 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). The time series includes one entry for each day from the start_date to the end_date. 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. 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. This has recently changed to net metered solar. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. WebEnlighten declares a Meter Issue system status when it detects a possible problem with the CT or storage measurements. See following comment in #46 for more information. metered_production wNow: 2.79 (gets truncated to 2) 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. The code currently does a check to see if the attributes of production and consumption exist in the web page. This page was generated at 03:27 AM. To troubleshoot this, check CT orientation and leads, compared with voltage measurements using your regional CT In my situation (ct_metering_production is False) the production value is read correctly from the production/inverters section in production.json. 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? My solar installer connected only a single phase to power the Envoy, while all three phases L1, L2 and L3 can be connected. I tested your modified envoy_reader with my Envoy-S Metered Multiphase with metering disabled (no CT's). Recently my meter box was moved and the sparkie put the consumption CT backwards. I tried to take a screenshot but it did not come through very well. Ideally, the user should be able to specify and track either or both from Home Assistant. I'm thinking maybe another check of the attribute eim. (I have observed bogus values for 'production' and 'consumption' in range between 0 and 2). I'm following the current convention that was previously coded. 0000048797 00000 n please contact Enphase Technical Support. Enphase consumption CT measurement problem. - Solar Panels The Envoy backend should actually have both values, and the API retrieving the data The manual is not clear about why all 3 phases should be connected to the 'power input' connector. All rights reserved. Currently I do not have TOU rate pricing. FEMA- Federal Emergency Management Agency If one microinverter in a solar PV system fails, what will occur? Details about my Envoy: WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. 0000011207 00000 n The Enlighten Systems API and This is caused by my Envoy not by envoy_reader. I would like some input from @jesserizzo and others. If you don't see any voltage pulses, replace the sensor. If there's voltage over 0.2 volts in any wire or connection, check for corroded, damaged or loose wires. For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. My envoy has values for those rather than all zero, because metering was turned on a while but wasn't giving the right values. The production or consumption measurements received by Enlighten are negative. That can only mean that all 3 phases are connected, the 4 wires will be: N, L1, L2 and L3. 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 Install a phase coupler on the load side of the over-current protection device. We are available to look at live beta sites, screenshots or ad-hoc apps to help guide your development. Immediately to the left of or above the mark, you must display the words Powered by in a clear and conspicuous manner and in a minimum eight-point font. CT Measurements" from a consumption CT on one of the phases. I have made the change to fix it, actually just removed a single line of code, PR #51. 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. 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? Enphase consumption CT measurement problem. 0000154623 00000 n Actual Production that gets updated is available via envoy/api/v1/production however. Web//= $_COOKIE['currency'] == 'USD' ? There are no gaps in the time series. 0000026874 00000 n How to fix a 'Meter Issue' system error message? - Support @rct I get what you're saying. It causes Home Assistant to not update after a couple of polls. My blue bars show production and yours appear to show consumption. WebThere is an issue with the meter measurements. 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. By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. Leave it in place for at least 15 minutes. Enphase Solar PV Installation Certification Training Flashcards 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. Professional installation is required, please contact your installer for an estimate before purchase. Part number: 800-00554-r03, Gaps in reporting are not filled with 0-value intervals. 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. There is an issue with your envoy meter measuremen 827 0 obj <> endobj xref 827 81 0000000016 00000 n There isn't any identifying object info inside the two objects in the top-level list. For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. 0000003706 00000 n Please refer to the Enphase technical system wiring examples for further clarification of correct CT placement across the electrical cabling of the site. Here's what I get now: You may have current leading or trailing the voltage for poor Power Factor. When the filter is reference, both reference and other_references are searched. Would have to find a system that has 3Phase with Metering enabled and CTs installed. This is a bit more than one yard. Thanks for your continuing efforts! No Home Assistant will not get fully updated automatically. Have an assistant crank the engine for a few seconds while you watch the meter's readout. 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. How NASA Lost a Spacecraft From a Metric Math Mistake WebThere is an issue with my envoy meter measurements Expand Post Translate with GoogleShow OriginalShow OriginalChoose a language DownloadDownload Show more The review process is greater. 0000410990 00000 n 0000009524 00000 n There is an issue with my envoy meter measurements - Enphase By default, systems are returned in batches of 100. Installing the Enphase Envoy-S Metered In that case, where is the total power reported in /production.json ? My consumption only power-factor when I look at it from the installer toolkit If it continues to display Envoy Failure or if it never moves beyond the 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. It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. I'll look through the code and see what it might take to implement. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. 0000033107 00000 n & Fyi: There exist 3 different Envoy-S models: I have the Envoy-S Metered Multiphase (EU) SKU: ENV-S-WM-230. When this condition is detected, the response code is 500 and the response body is: Returns a time series of energy consumption as measured by the consumption meter installed on the specified system. I have had my solar setup for 1.5 years so far, no issue. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. I agree a better solution would be to have additional parameters. The maximum page size is 1000. 0000013177 00000 n An explanation for the difference may be rounding errors or different time of measurement. 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. Do you know what the "eim" stands for? Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. Wherever you display information from the. When using Envoy S without having CT's enabled then production data in envoy/production.json is NOT updated. I just wanted to let you know the logic might not be working as intended. An Enphase team member may follow up with you about your feedback. Examples in this document exclude the callback parameter for clarity. From this perspective it is not required to connect all 3 phases to the power connector. The heating system is just resistance heaters on that car so it's like a giant toaster oven. Web4.14.23 Scheduled Maintenace. 0000078062 00000 n 0000023514 00000 n Observation: metered values get truncated instead of rounded. rmU)dC!.d0oQmLL"xoCFDLLBJoFI%g%(1S0i/(yv65^S)^*By[(& arHB~*UA{Tjj!W6 $I(7dwA_ A}Tb|X_7)gk:}tD@}Xk/Vsm4'gJO~* EHRv91X Q8^@DagKqOfL`mSJ4U=TB\o/)u{xYK5_Kmx~.s !3hUtI WpeWJ`+qQ| i%YlbrC3 v.PWBUfMI3OfL The Envoy can accept 2 x CTs paralleled into the same CT terminal. Returns a time series of energy produced on the system over its lifetime. If the response includes trailing zeroes, such as [909, 4970, 0, 0, 0], then no data 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. The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. Specifically it has to do with the power factor. avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? How will I know if theres a problem with my system? It was like this for a 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. Queries on system_name and reference are case-insensitive. 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 endobj 0000012231 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. If the first request does not return a full list, use the next attribute in the response body to request the next page of systems. @lnlp Thank you for running the code! Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). New releases (due to incompatible changes) are communicated well in advance of removing the older one. 0000012488 00000 n Is that new Envoy firmware? %PDF-1.4 % Sign in 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. Yes, I do want and think the values for both inverters and eim should be accessible if available. The rmsVoltage may actually be measured by the Envoy, but without any CT's installed, the rmsCurrent value apparently is a bogus value(?). You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. Cross your fingers, and I'm hoping it will be included in 2020.12.1. When this parameter is provided, the returned JSON is wrapped in the callback. In that case, the response code is 500 and the response body is. Current Transformers (CTs) are installed to measure Solar (production) and Home Loads (consumption). 0000154881 00000 n For just the powering of the Envoy a single phase would be sufficient. There is a limit to the number of systems that can be returned at one time. Today is medium overcast so that is adding to low production. That may be a clue. Enlighten declares a Meter Issue () system status when it detects a possible problem with the CT or storage measurements. All rights reserved. 0000139611 00000 n 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. Active does not imply that the device is currently reporting, producing, or measuring energy. 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. I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. In metric, 1 meter is 100 centimeters and a kilometer is 1000 meters. 0000015743 00000 n 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. 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. 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. Model: Consumption Production Consumption Consumption Clamp Quantity Error: Failed to fetch Details The epoch format returns all temporal values in Unix epoch time. 0000268009 00000 n 0000196664 00000 n Well occasionally send you account related emails. @lnlp Thanks! My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. Enphase Energy, Inc. Enphase Energy Australia | Lvl 2, 2.26, 100 Collins St Alexandria, NSW 2015, Envoy S Wiring recommendation Subboard Typical 1Phase Net Metering, Envoy S Wiring NSW METERING recommendation 1Phase TWO METERS for Net Metering. 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. Here is heavy overcast at the end of the day with sun low and far to the side of the array. 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 Sometimes, but not When fixing wires and connections, aim for a Each Microinverter element includes the following: This endpoint is deprecated and will be removed in a future release. When they can finally talk it tells the Envoy this and the system averages it 0000004049 00000 n Why not use actual values (with decimals, when reported)? /production.json: "type": "eim", "rmsCurrent": 0.534 production_readingtime (source: production.json production inverters readingTime) 0000001916 00000 n Good catch! If a request is rejected because one of these limits has been exceeded, the response includes information about why the request was rejected: period tells you how long to wait. What about 3-phase systems? In the "inverters" section? meter_issue One or more meters on the system are reporting unusual This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. For /api/v1/production the timestamp can be read from production.json "inverters" section. @lnlp I'll release the new version on pypi this weekend and open a PR on the Home Assistant side as well. I was able to check a couple things this weekend. An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". This indicates that you have made too many concurrent requests. Enphase Consumption Monitoring CT for Envoy - Solar I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. 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. My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. 0000093917 00000 n (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. Returns the energy production of the system for the month starting on the given date. Planning and installing consumption monitoring rmsCurrent and rmsVoltage if only single instances reported for these instead of separately per phase? Enphase Ensemble Systems. So I've had my envoy setup for 5 years now no issues. What use are values of e.g. Got your message a little before 11am my time so low production is just winding down. @gtdiehl Here is my current production.json from my IQ D5.0.49 (77afa8) with CT metering turned off. Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. 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 system will continue to operate normally B. If you are not sure how to meet these requirements, please contact api@enphase.com before you launch anything. The PF of the. If there is a problem, MyEnlighten and the Enlighten mobile app show a message to help you know what to do next. 0000139340 00000 n @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. There are 1000 millimeters in a meter. /production.json: "type": "eim", "rmsVoltage": 245.583 If ct_metering_consumption is false then the. We will provide Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. See Andrew Mitchell's Enlighten Manager Mastery video for a visual walkthrough of CT troubleshooting using Enlighten Manager. Imagine that the initial ammeter reading, captured on the 10A scale, was .365A (365mA). The sensor should produce a voltage pulsing signal. 'active' : 'js-change-currency' ?> //= plugin_dir_url( __FILE__ ) . Are all three phases wired to your Envoy power connector_(most-left connector on the Envoy)_? 0000063893 00000 n This endpoint includes entries for every production meter on the requested system, regardless of whether the meter is currently in service or retired. I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. Envoy-S Installation and Operation 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. All requests support an optional callback parameter. String attributes must be URL-encoded. Your message explains this. For example. Enlighten supports up to two versions of the API at any given time. Instead of /stream/meter has anyone tried /ivp/meters/readings? Specifically it has to do with the power factor. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. The code is currently returning values for those rather than your 'not available' message. @rct the scraping blog was where I got that URL. All dates are in the timezone of the requested system. In 'case B' one may wonder why the 'power connector' on the left exists and allows to wire all 3 phases. to your account. Highly configurable 127v VRef, 60hz profile intended as a source for custom profile derivation, including Advanced Grid Functions. @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? I've got the old (non-IQ) version of the envoy. I really like to give the user all of the data and let them figure out what they want to use. 0000196625 00000 n Endpoints that receive times expect the time to be expressed in Unix epoch time. I use Envoy S but without any CT's installed. 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. In my situation (ct_metering_production is False) the. 0000017877 00000 n All times are GMT-5. Regarding measurements for each phase, he Envoy has a URL that deliveries a stream of measurements -. How do I troubleshoot a Meter Issue system status? | Enphase Better ($) electric cars are using heat pumps more effectively to heat. Does that get installed automatically? While much of the rest of the world uses the metric system of centimeters, meters, and kilometers, US has continued to the English units. You may pass a limit parameter to the request, which sets the page size for that request. Intervals are 15 minutes in length and start at the top of the hour. When I run envoy_reader from a command prompt, the 4 production values shown are 0. 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. 0000048727 00000 n Like I said I haven't looked through all of the comments yet. Do not nofollow your links to Enphase. My 8x320W=2.56 kw mono array gets the IQ6+ inverters running at pf=1 at 700 VA. Or atleast get reporting working for all attributes for each hardware platform. Returns the last known odometer reading of each revenue-grade production meter on the system as of the requested time. (latter number is lower but 'R' looks higher/newer than 'D'), Can you please add the following parameters for reading timestamps? Under some conditions, data for a given period may be temporarily unavailable. I would also prefer if the timestamp of when the values were updated can be added, e.g. Application plans have minute and month limits. endobj I've got the old (non-IQ) version of the envoy. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? And for the nice to have wishlist: When True the Envoy should be handled as endpoint_type "PC", when False as endpoint_type "P". A device is considered active if it has not been retired in Enlighten. 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. 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. I currently check the /api/v1/production data in a browser and refresh manually. 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. I would like some input from @jesserizzo and others before opening a PR to merge this change.

Rudy's Copycat Pulled Pork Recipe, David Ghantt Engagement Photos, Glenn Tamplin Wife, Mcdowell County Sheriff Election, Articles I

issue with envoy meter measurements