issue with envoy meter measurements

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. 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. 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. 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. Have an assistant crank the engine for a few seconds while you watch the meter's readout. 0000033107 00000 n I am just grasping at straws here. 0000017877 00000 n 0000128138 00000 n If the total duration requested is more than one day, returns one day of intervals. My consumption only power-factor when I look at it from the installer toolkit 0000470581 00000 n Part number: 800-00554-r03, For the best experience on our site, be sure to turn on Javascript in your browser. Have you tried flipping the CTs 180 degrees? &pLlV y*Hv. I hope you get the help you need. Wherever you display information from the. 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. Meters are abbreviated using a lower case "m" in measurements. 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. It could be the CTs are plugged into the wrong socket. 0000339432 00000 n You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. 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. 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. 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. So far the readings do not look right. Imagine that the initial ammeter reading, captured on the 10A scale, was .365A (365mA). 0000002893 00000 n The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. 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. It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? When current transformers (CTs) are wrapped around a live I'm thinking maybe another check of the attribute eim. 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. It does show in the HTML output, but scraping should be avoided. 0000093464 00000 n 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. Solar Production CT MUST measure all solar circuits on site. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. 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? My guess is that data from /stream/meter on your envoy will report realistric (true) voltages for all three of data/production/ph-a/v, data/production/ph-b/v and data/production/ph-c/v. 0000078062 00000 n In my comments above, I was arguing for the case to still be able to get the inverter numbers even if metering is enabled. New releases (due to incompatible changes) are communicated well in advance of removing the older one. If Enphase has detected a possible hardware issue that may be affecting system production, youll see a message like this: Click the link in the message to see which microinverters are reporting a production issue and find out how to get help with the problem. If the consumption measurements received by Enlighten do not appear to include storage activity, there are two possible wiring issues that can cause this: The Meter Issue status will continue to display until Enlighten receives 24 hours of meter measurements that indicate the problem has been addressed. 0000232378 00000 n In that case, the response code is 500 and the response body is. Enphase Envoy S 'metered' Multiphase (probably identical to Envoy IQ). Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. Envoy reader makes an assumption depending on the type of Envoy whether CT metering is being used. 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. This page was generated at 03:27 AM. Automatic: When CT's are not enabled this is shown on the envoy/home page so it should be possible to automatically scrape the status of whether CT's are enabled or not. 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. trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. I have made the change to fix it, actually just removed a single line of code, PR #51. https://github.com/dlmcpaul/EnphaseCollector. production_readingtime (source: production.json production inverters readingTime) 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. 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. 0000411029 00000 n Some batteries have stopped In my situation (ct_metering_production is False) the production value is read correctly from the production/inverters section in production.json. If you are installing in a multiphase application, the power line communication signal must be coupled I hope we can see it being updated in Home Assistant as well soon. I just wanted to let you know the logic might not be working as intended. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. Yes, I do want and think the values for both inverters and eim should be accessible if available. I The Envoy backend should actually have both values, and the API retrieving the data When the filter is reference, both reference and other_references are searched. That may be a clue. read_at is the time at which the reading was taken, and is always less than or equal to the requested end_at. According to the Envoy-S Metered Multiphase Installation manual there are 3 CTs installed on the Production and Consumption sides. Will there be / shouldn't there be 3 separate "eim" sections, each for one phase? 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 . All times are GMT-5. (I suspect something like: electrical induction metering). Looks like you are checking for not set/zero vs. checking activeCount. 827 0 obj <> endobj xref 827 81 0000000016 00000 n 0000033020 00000 n When I look into the error, it was not apparent to me the problem. I can even see it go lower after that and work much better than it did on the way up. By providing an optional ct_enabled parameter the user can override it for testing purposes. endobj Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. What use are values of e.g. 0000003706 00000 n "[}QXD/jD NCrncVa @L*23m By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. to your account. Since installation the system has shown an intermittent error: "Meter Issue. It also includes a $5 a month hook-up charge which covers the extra meter. Would have to find a system that has 3Phase with Metering enabled and CTs installed. I think it is working as you intended, but see. 0000003055 00000 n My blue bars show production and yours appear to show consumption. Enlighten declares a Meter Issue () system status when it detects a possible problem with the CT or storage measurements. For example, P0500 (VSS circuit malfunction) is the most popular code Compatible changes do not result in a change to the version number. 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. In my situation (ct_metering_production is False) the. Manual: Add an extra parameter e.g. In progress - Scheduled maintenance is currently in progress. CT Measurements" from a consumption CT on one of the phases. The installers could have put it on the wrong leg. /api/v1/production, Here is my current http://envoy.local/api/v1/production. Copyright 2014 SolarReviews All rights reserved. Then a question, does the api return the eim values that is got from the envoy even when the activeCount = 0? Your message explains this. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? Active does not imply that the device is currently reporting, producing, or measuring energy. WebEnlighten declares a Meter Issue system status when it detects a possible problem with the CT or storage measurements. Sometimes, but not My /api/v1/production/inverters inverter data is already properly read and output by envoy_reader (I can see the values in Home Assistant). All times are GMT-5. 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. tvd`x]6d=WY fj0A2! Regarding bullet 2: No, not only those two values. 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's what I get now: You may have current leading or trailing the voltage for poor Power Factor. The data from my Envoy (3-phase, no CT's) looks like this (pretty-printed): Based on above it appears that /production.json is not going to contain data for each phase separately (in 3-phase system). measure resistance from orange wires to large power terminal under rear seat.. they should all be under 10ohms and not change when the wires are pulled on. They can always filter these values out in Home Assistant by specifying which monitored_conditions they want to see. envoy_reader should handle all these (4) situations correctly. 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 Software Version: R4.10.35 (6ed292) Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). About the Enphase Envoy-S Metered The Enphase Envoy-S Metered communications gateway enables performance monitoring and remote software and firmware updates of an Enphase Microinverter System. For example, there are 100 centimeters in a meter. In general, a Meter Issue indicates a system where on-site maintenance may be required. Returns the last known odometer reading of each revenue-grade production meter on the system as of the requested time. The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, (Maybe you are mistaking with the cloud API's update frequency?). This is caused by my Envoy not by envoy_reader. 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. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. CT metering can be turned off even on newer Envoys if the CTs aren't installed or are installed incorrectly. Highly configurable 127v VRef, 60hz profile intended as a source for custom profile derivation, including Advanced Grid Functions. 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. Keeping in mind that consumption monitoring is an optional add on that doesnt interfere with the core functionality of the solar system. I have it set on load with solar production. I'll look through the code and see what it might take to implement. 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? After period_end, you can make another request. If you dont have permission to view consumption data, the response code is 401. However, each request may optionally include it. As previously requested please add the following output parameters: 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. Note: my CTs are currently disabled. 0000268009 00000 n Returns a time series of energy produced on the system over its lifetime. 0000032874 00000 n 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. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. 0000010160 00000 n Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. If there is a problem, MyEnlighten and the Enlighten mobile app show a message to help you know what to do next. This requires an alternative arrangement of the CTs for correct measurement. <> 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. If you dont have permission to view consumption data, the response code is 401. 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. To troubleshoot this, check CT orientation and leads, compared with voltage measurements. I have had my solar setup for 1.5 years so far, no issue. 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). period_start and period_end tell you when the minute (in this case) started and when it will end. If your system has AC Batteries: Some batteries havent charged or discharged recently. 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. Be aware that CT's can be installed for either Production, or Consumption, or both. @lnlp Thanks! It was like this for a You may filter on the following attributes: system_id, system_name, status, reference, installer, connection_type. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. 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. If production or consumption measurements received by Enlighten are negative, there could be a CT Measurement issue. 0000014056 00000 n /api/v1/production does not contain "readingTime" but /production.json "type": "inverters" does. Learn what you can do if the systems meter has stopped reporting. The code is on one of my branches. 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. A CT is installed and Metering is only monitoring Production. 0000002698 00000 n 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. The start date must be at least one month ago. All requests support an optional callback parameter. 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. I have had my solar setup for 1.5 years so far, no issue. I've got the old (non-IQ) version of the envoy. Data coming from /api/v1/* is updated every 5 minutes. I am quite sure my problem is based in the start-up voltage and minimum voltage. Specifically it has to do with the power factor. 0000016440 00000 n This indicates that you have made too many concurrent requests. I'll return values with a decimal. @lnlp I'll release the new version on pypi this weekend and open a PR on the Home Assistant side as well. Is it correct that you have only one single CT for consumption? There are 1609 meters in a statute mile. The time series includes one entry for each day from the start_date to the end_date. To troubleshoot this, check CT orientation and leads, compared with voltage measurements. Details about my Envoy: Unrecognized parameters are ignored. Then change part of detect_model() from If there's voltage over 0.2 volts in any wire or connection, check for corroded, damaged or loose wires. A difference of 1 Watt, which may be caused by a rounding error, or by a small difference in moments of measurement. Note: If a system does not include a given device type, that key is left out of the returned hash. 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. The sensor should produce a voltage pulsing signal. "Metered Production data not available for your Envoy device." Though this time I had someone add my PR to the list of PRs that should be included in 2020.12.1. This is the output: 0000026874 00000 n To me this isn't a problem right now, unless there winds up being some logic that depends on those being zero vs. not used. |nxv&T["mhQ zt.f&Q4W?t4:?TrJdoV1EBEJ!,^G@-C'[lUZTD;Z*fd'w?Z:Fo77c[iZ=vWKc~Wv6c? My Envoy reports tiny metered values while metering is disabled. 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? Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. @OllemGit Would it be possible for you to verify this? 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. Some may view this as a draw back. WebWhen used with an Envoy S Metered or IQ Gateway, the Consumption Current Transformer (CT) enables home energy consumption monitoring. Copyright 2014 SolarReviews All rights reserved. rmsCurrent and rmsVoltage if only single instances reported for these instead of separately per phase? If your application does not allow for you to include an image, you must include the text Powered by Enphase Energy. See Andrew Mitchell's Enlighten Manager Mastery video for a visual walkthrough of CT troubleshooting using Enlighten Manager. 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 @lnlp - trying to answer a few of your questions with what I've learned so far. I added some more detail in the Issue #41. @gtdiehl Here is my current production.json from my IQ D5.0.49 (77afa8) with CT metering turned off. 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. 0000003741 00000 n 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. All measurements are in Watt hours. And for the nice to have wishlist: A. I did notice that there was only one solar CT and that may need to be on a particular leg as well. 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. All rights reserved. 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. 0000029406 00000 n It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. 0000013432 00000 n In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. And the metered_* parameters come from the appropriate section of /production.json that contains type of eim. I've seen that referred online as being able to get the individual readings and maybe it doesn't require the installer password. The rmsVoltage may actually be measured by the Envoy, but without any CT's installed, the rmsCurrent value apparently is a bogus value(?). My envoy has been updated twice (or more) as far as I remember. If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. Professional installation is required, please contact your installer for an estimate before purchase. Web//= $_COOKIE['currency'] == 'USD' ? 0000268048 00000 n I've tried switching polarity on the CTs, and moving them around, but I can't get it into a real range. All dates are in the timezone of the requested system. Examples in this document exclude the callback parameter for clarity. There was a reply in the Home Assistant Community forum where a person took this screenshot. endobj 'active' : 'js-change-currency' ?> //= plugin_dir_url( __FILE__ ) . 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. Completed - The scheduled maintenance has been completed. Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. My Envoy reports a realistic value for data/production/ph-a/v while no CT's are installed. You have your consumption meter set to "load with solar production" or "load only"? I was able to check a couple things this weekend. Refer to the Release notes page for any recent changes to the Enlighten API. Does that get installed automatically? 0000048797 00000 n The CT (current transformers) are used for measuring current. And possibly add another parameter called activeCTCount to tell the user if the Metering feature is enabled on their Envoy? For more details, visit 3.48 kW of SolarWorld panels and Enphase IQ7 micros. Like I said I'm still thinking about it and weighing the pros and cons. fbK1yBE~nF\|WG x0y,x,JX { [J*4 U4%0!AWeZ sPH@@-GTpGs*(zI1YJBBGNN]UU>h`H_))q~u}@a1(%=_n8XH 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). Already on GitHub? Webmeter There is a communication problem between an Envoy and a revenue-grade meter on the system. If ct_metering_consumption is false then the. Here are captures of /api/v1/production, /production.json and /api/v1/production/inverters. Sign in metered_consumption wNow: 0.836 (gets truncated to 0). 0000023653 00000 n When using Envoy S without having CT's enabled then production data in envoy/production.json is NOT updated. /production.json: "type": "eim", "rmsCurrent": 0.534 Electrical system: 3-phase 230V. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. All rights reserved. On the MyEnlighten desktop application, the icon to the left of your system name tells you how your system is doing. Contact us for sales, quantity discounts and expert reviews for the Enphase CT current transformer for Envoy. Could this have been fixed in a later firmware revision? An Enphase team member may follow up with you about your feedback. I don't really understand how the system is configured. I'm producing 1-5 kWh/day and I see almost the exact daily amount reducing my consistent 7 kwh daily usage. What about 3-phase systems? There are no gaps in the time series. 0000017430 00000 n "Metered Production data not available for your Envoy device.". WebUnplug the Envoy from the AC outlet and plug it in once again. When I run envoy_reader from a command prompt, the 4 production values shown are 0. 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. Anyway, I tried reversing both the production CTs and swapping their phases. According to the IQ Envoy manual this is possible if the user wants revenue-grade production metering. The heating system is just resistance heaters on that car so it's like a giant toaster oven. => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's An explanation for the difference may be rounding errors or different time of measurement. Please note that the Enlighten Systems API does not provide performance data at a panel or microinverter level. This endpoint can return a response of Data Temporarily Unavailable. I just tested it in Windows Sandbox: No authentication required for both url's. 3 0 obj By default, systems are returned in batches of 100. 4 0 obj @rct If you have code changes could you post it to GitHub for a possible merge? Did you power off and repower your Enlighten box after you made those changes. 0000232417 00000 n endobj 0000012231 00000 n Do not violate the other restrictions described in the Enphase, Copyright 2023 Enphase Energy, Inc. All rights reserved. When this condition is detected, the response code is 500 and the response body is: Each meter interval includes the following: Returns performance statistics for the specified system as reported by microinverters installed on the system. I was happy to see it working in 2020.12.0 now but then noticed values reported in HA don't match /api/v1/production. The fix was merged into the dev branch yesterday, which usually means it will make it into the next release (2021.01.0). EDIT: I actually just found a setup like this. 0000161309 00000 n This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production.

Large Metal Giraffe Sculptures For Sale, How To Pronounce Jehovah Ropheka, Milk Milk, Lemonade Around The Back Fudge Is Made, First Moonflash Horses For Sale, Transaction Central Login Oc2net, Articles I