issue with envoy meter measurements

Keeping in mind that consumption monitoring is an optional add on that doesnt interfere with the core functionality of the solar system. All rights reserved. The Enlighten Systems API returns JSON. Manual: Add an extra parameter e.g. Thank you for opening those issues. The response includes intervals that have been reported for the requested period. Enlighten declares a Meter Issue () system status when it detects a possible problem with the CT or storage measurements. /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. endobj 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. Better ($) electric cars are using heat pumps more effectively to heat. 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. Data coming from /api/v1/* is updated every 5 minutes. The Envoy can accept 2 x CTs paralleled into the same CT terminal. I have made the change to fix it, actually just removed a single line of code, PR #51. 0000303679 00000 n But have to think about current users. Valid values for datetime_format are iso8601 and epoch. 0000128068 00000 n Have you tried flipping the CTs 180 degrees? It appears to work fine. 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 system has both production and consumption CTs installed, you can see which meter is affected by checking the meter status on the Devices screen. 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. hQILSQ=S?H)B) B$4 0000154623 00000 n EV owner since 2012. The time series includes one entry for each day from the start_date to the end_date. I tried to take a screenshot but it did not come through very well. 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. In general, a Meter Issue indicates a system where on Similarly, if you see no message in the Enlighten mobile app, your system is doing fine. The circuit passing through the production CT includes AC Batteries. As previously requested please add the following output parameters: The CT (current transformers) are used for measuring current. 827 0 obj <> endobj xref 827 81 0000000016 00000 n Metering requirements (i.e. Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. Copyright 2014 SolarReviews All rights reserved. So far the readings do not look right. This page was generated at 03:27 AM. When this parameter is provided, the returned JSON is wrapped in the callback. Returns summary information for the specified system. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. They can always filter these values out in Home Assistant by specifying which monitored_conditions they want to see. The API accepts a number of parameters. This is just low sun with overcast far to the side of the array. I'll look through the code and see what it might take to implement. It was like this for a I have had my solar setup for 1.5 years so far, no issue. My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. <>/Metadata 3482 0 R/ViewerPreferences 3483 0 R>> This has to either be an issue with where the consumption ct clamp has been installed, its orientation (arrow direction) or with a software setting on the envoy or a combination of all 3 possible causes. Envoy S Production data is not read / read incorrectly when current transformers are not enabled/installed [bug], https://thecomputerperson.wordpress.com/2016/08/03/enphase-envoy-s-data-scraping/#comment-5838, Add production_readingtime and consumption_readingtime output parameters, Add consumption_ct_metering_enabled and production_ct_metering_enabled output parameters, Support reading values of consumption and production per phase, The envoy is configured without CT metering and the user wants WH totals for today and 7 days which aren't available in. Parameter order does not matter in any request. => 4 wires enter the most-left connector of the Envoy + 3x2 wires for the CT's <> When I investigate the raw numbers from interrogating the envoy direcly it actually shows me the low power factor. My envoy has been updated twice (or more) as far as I remember. WebAN_6612_032 Energy Measurement in Split Phase Systems Using 78M6612 Rev. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? If you are installing in a multiphase application, the power line communication signal must be coupled 0000339432 00000 n The new version of API (v4) is available at: developer-v4.enphase.com. 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? 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. 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. This is because envoy_reader assumes that when `envoy/production.json' exists that this is the location to read the Production data from. 0000013432 00000 n To troubleshoot this, check CT orientation and leads, compared with voltage measurements using your regional CT (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. 0000016000 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. From the 'Envoy-S Metered Multiphase (ENV-S-WM-230) Installation and Operation Manual': Use a Phase Coupler for a Multiphase Site 2 0 obj We will provide 0000011718 00000 n The dark hours on a system are an example of such a gap, because the microinverters do not produce at night. WebEnvoy-S Standard Compatible Microinverter (s) M215, M250 Primary Use Residential & Small Commercial AC Supply 230 VAC, 50 Hz Production Metering 5% accurate microinverter measurements Warranty Length 5 years Designed for an outdoor enclosure Integrated Wi-Fi & Mobile Connect Ready Consumption Monitoring & Storage Ready metered_production wNow: 2.79 (gets truncated to 2) This is the output: That may be a clue. 0000139909 00000 n Reduce the number of concurrent threads in your application in order to avoid this response code. I suggest to use the term 'CT Metering' (or 'CT Metering Enabled') instead of "Metering (CT) Status". 0000048727 00000 n 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 Intervals are 15 minutes in length and start at the top of the hour. For /api/v1/production the timestamp can be read from production.json "inverters" section. Meters are abbreviated using a lower case "m" in measurements. 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. My consumption only power-factor when I look at it from the installer toolkit And for the nice to have wishlist: In general, a Meter Issue indicates a system where on-site maintenance may be required. 0000303640 00000 n No news is good news! I use Envoy S but without any CT's installed. I'll have to look into this one a bit. )bJ60F-phEZ If you do not want to accept all content types, specify JSON only: Endpoints that receive dates expect the format YYYY-mm-dd. A. Returns the summary along with the energy produced on the system over its lifetime. 0000161309 00000 n 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 Envoy-S Metered uses precision Current Transformers (CTs) to measure PV production period_start and period_end tell you when the minute (in this case) started and when it will end. Maybe this is only of interest to me. This is not my experience. Clients of the API are expected to do the same: Be order-agnostic, and ignore unknown response values. 0000154881 00000 n 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. 0000128138 00000 n 0000018303 00000 n I would have to look into how to send specific data from the envoy_reader API to Home Assistant. stream In that case, the response code is 500 and the response body is. A device is considered active if it has not been retired in Enlighten. WebThe use of any other type of CT will result in incorrect power measurements, and may permanently damage the WattNode meter. Currently I do not have TOU rate pricing. Have a question about this project? By default, systems are returned in batches of 100. If your systems meter has stopped reporting, youll see a problem message like this: 0000268048 00000 n There isn't any identifying object info inside the two objects in the top-level list. 0000015743 00000 n I was able to check a couple things this weekend. When True the Envoy should be handled as endpoint_type "PC", when False as endpoint_type "P". Too bad, but no need to feel sorry. I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? Here is the output of envoy_reader from various Envoys. The sensor should produce a voltage pulsing signal. EIM - Your guess on the meaning of the acronym is 'electrical induction metering' is possibly correct. read_at is the time at which the reading was taken, and is always less than or equal to the requested end_at. With all of the typical tight connections I don't have a way to measure volts and compare to expected IQ6+ performance. 0000011207 00000 n After period_end, you can make another request. The production or consumption measurements received by Enlighten are negative. 3 0 obj If you see a green checkmark, then your system is fine with normal system production. When CT metering is off you have to look at /api/v1/production for the WH accumulation (today, 7 day) totals. Note: my CTs are currently disabled. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? endobj To troubleshoot this, check CT orientation and leads, compared with voltage measurements. I see information in /api/v1/procuction and /api/v1/production/inverters being updated every 5 minutes. Requests for times that do not fall on the 5-minute marks are rounded down. As a result the reported Production values are either 0 or some bogus value. 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. If you dont have permission to view consumption data, the response code is 401. Looks like you are checking for not set/zero vs. checking activeCount. 0000001916 00000 n There is a limit to the number of systems that can be returned at one time. 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. Returns performance statistics as measured by the revenue-grade meters installed on the specified system. Note: I've got production and consumption metering turned off (activeCount == 0). /production.json: "type": "eim", "rmsVoltage": 245.583 This does not require to connect all 3 phases to the power connector. 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. All rights reserved. lastReportDate and readTime (there's little consistency in the different names unfortunately). 0000003741 00000 n trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? WebUnplug the Envoy from the AC outlet and plug it in once again. In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. However, each request may optionally include it. 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 metering problems. Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. 0000032874 00000 n If the total duration requested is more than one month, returns one month of intervals. You may pass a limit parameter to the request, which sets the page size for that request. 0000078062 00000 n <>/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>> I just tested it in Windows Sandbox: No authentication required for both url's. I'm producing 1-5 kWh/day and I see almost the exact daily amount reducing my consistent 7 kwh daily usage. 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. And the metered_* parameters come from the appropriate section of /production.json that contains type of eim. Returns the energy production of the system for the month starting on the given date. I've got the old (non-IQ) version of the envoy. 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. @OllemGit Would it be possible for you to verify this? Then change part of detect_model() from Here is low light at the end of the day. You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. WebThe IQ Envoy uses readings from CTs to report measurement data for energy production and energy consumption. 0000015247 00000 n Enphase Ensemble Systems. I currently check the /api/v1/production data in a browser and refresh manually. These come from mainly 3 pages (excluding Envoy running <3.9 firmware), I would propose removing the original consumption parameters and adding additional parameters (lets prepend them in this example with metered_*. Leave it in place for at least 15 minutes. Envoy S Production data is not read when not using current transformers which renders reported Production data useless. 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. This endpoint can return a response of Data Temporarily Unavailable. 'lqgs:~>_A,XJNBPyF^h@~.]:XUaSeJmi*`L6Aj$FaLQPzi_~l[U66RO57YYZA/O3](8LLIFAZrsf/=qNe~^sjW9f+L`l7?d A 5K 0000110513 00000 n I'm not sure on this one. 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. @lnlp - trying to answer a few of your questions with what I've learned so far. measure resistance from black wire at lgm connector (while disconnected) to ground behind side panel inside rear cargo area. The circuit passing through the consumption CT does not include AC Batteries. Right after connecting the power lines to the grid I already have some statistics of the grid meter (in the Netherlands called the Slimme meter, which you can read through the P1-port using i.e. CT Measurements" from a consumption CT on one of the phases. tvd`x]6d=WY fj0A2! Got your message a little before 11am my time so low production is just winding down. WebThere is an issue with my envoy meter measurements Expand Post Translate with GoogleShow OriginalShow OriginalChoose a language DownloadDownload Show more My /api/v1/production/inverters inverter data is already properly read and output by envoy_reader (I can see the values in Home Assistant). If you don't see any voltage pulses, replace the sensor. If ct_metering_consumption is false then the. This status was for me while debugging. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. Do you expect to get the fix into the next (bug-fix) release (presumably 2020.12.1)? I just wanted to let you know the logic might not be working as intended. Example: It is possible to request a subset of the systems list. Here's what I get now: You may have current leading or trailing the voltage for poor Power Factor. You can sign up to be notified by email if your system experiences either type of production issue. There are no gaps in the time series. I have had my solar setup for 1.5 years so far, no issue. @gtdiehl - Here's my Envoy IQ (metering turned off) output using your change_polling_pages branch: I originally had the metered values not being returned when metering is disabled (activeCount == 0), but then I thought someone might want these values or some other reason. If production or consumption measurements received by Enlighten are negative, there could be a CT Measurement issue. 0000017877 00000 n (I suspect something like: electrical induction metering). 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. 0000470581 00000 n OUTBACK SEALED GRID-TIE INTERACTIVE INVERTERS, Skip to the beginning of the images gallery, Contact us for availability, pricing and freight quote, Contractor and commercial discounts available, Specials and multi-pallet/container discounts, Complete residential and commercial grid-tie Solar kits, Design assistance, Permit submittals, Schematics, Enphase Monitoring CT Getting Started Guide, Enphase Consumption Monitoring CT-200-Split Installation Guide, Enphase Ensemble Technology System Planning Tech Brief, Envoy requires 2 CTs to connect to terminal block. I assume a much larger EV is in our near-ish (2-3 year) future and getting TOU will absolutely make sense then. So to make changes unfortunately we can't add a new sensor and display the new data. Under some conditions, data for a given period may be temporarily unavailable. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. 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. So in practice it can be possible that only CT('s) for consumption are installed. Sometimes, but not Intervals are listed by their end dates; therefore, the first interval returned is 5 minutes after the requested start date. Last one. 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). I've seen that referred online as being able to get the individual readings and maybe it doesn't require the installer password. 0000048897 00000 n The consumption measurements received by Enlighten do not appear to include storage activity. 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. @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. The next screenshot shows the cumulative effect of the negative reading on the lifetime measurements; Screen Shot 2019-01-04 at 10.24.51 PM.png, Solar Panels for your Home, Grid Tied Solar PV, Screen Shot 2019-01-04 at 10.24.59 PM.png, Screen Shot 2019-01-04 at 10.22.19 PM.png, Screen Shot 2019-01-04 at 10.26.09 PM.png, Screen Shot 2019-01-04 at 11.25.06 PM.png, https://enphase.com/sites/default/finvoy-EN-US.pdf, https://thecomputerperson.wordpress.com/2018/08/18/what-is-inside-the-enphase-envoy-s-teardown/, https://www.solarpaneltalk.com/filed7&d=1546658760. I have tested your latest envoy_reader.py. @rct the scraping blog was where I got that URL. 0000014056 00000 n Web4.14.23 Scheduled Maintenace. The Envoy-S Metered is a system monitoring tool, and control device. 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. Examples in this documentation exclude the API key and the user_id for clarity. 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. 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). When the filter is reference, both reference and other_references are searched. I don't really understand how the system is configured. Like I said I haven't looked through all of the comments yet. Wherever you display information from the. Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. I would expect to see at least three different sets of values, one for each phase. 0000023514 00000 n Exactly: I have only CT's installed for measuring Consumption "CT's" is plural but consumption/eim/activeCount only shows 1. My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. So as it stands is your original bug of Production values displaying zero fixed? I'll return values with a decimal. /production.json "type": "inverters", "wNow": 2235 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 PF of the. 0000093917 00000 n Solar Production CT MUST measure all solar circuits on site. Each envoys element includes the following: Returns a list of systems for which the user can make API requests. From this perspective it is not required to connect all 3 phases to the power connector. Enlighten supports up to two versions of the API at any given time. 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

Bank Owned Homes Hillsborough County, Fl, How To Play Boneworks On Oculus Quest 2 Wireless, 17 Paseo Verde Santa Barbara Ca, Carlo Gambino Daughter, Class Of 2027 Basketball Rankings Illinois, Articles I

issue with envoy meter measurements