Under some conditions, data for a given period may be temporarily unavailable. There are no gaps in the time series. Maybe I should have been a little clearer but Home Assistant is not letting existing integrations to change their monitored_conditions. The response includes intervals that have been reported for the requested period. I just wonder is there a configuration of the Envoy where a production CT is installed without a consumption CT? period_start and period_end tell you when the minute (in this case) started and when it will end. 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. I'll have to look into this one a bit. Did you power off and repower your Enlighten box after you made those changes. In my comments above, I was arguing for the case to still be able to get the inverter numbers even if metering is enabled. Some may view this as a draw back. This is not my experience. All dates are in the timezone of the requested system. Prefix multipliers based on powers of 10 are used to convert meters to other SI units. Is D5.0.49 newer than R4.10.35? 0000012231 00000 n When this parameter is provided, the returned JSON is wrapped in the callback. 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. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. An Enphase team member may follow up with you about your feedback. 0000196625 00000 n My envoy has values for those rather than all zero, because metering was turned on a while but wasn't giving the right values. When I look into the error, it was not apparent to me the problem. This indicates that you have made too many concurrent requests. between the phases to allow the Envoy to communicate with all of the Enphase devices in the system. WebMake sure to keep your meter lead wires away from engine moving parts during this test. The manual is not clear about why all 3 phases should be connected to the 'power input' connector. You can retrieve the complete time series from the meter and from the microinverters by adding the parameter production=all to the request. Unrecognized parameters are ignored. If the total duration requested is more than one month, returns one month of intervals. Example: It is possible to request a subset of the systems list. I'm not sure on this one. Reduce the number of concurrent threads in your application in order to avoid this response code. I use Envoy S but without any CT's installed. I've tried switching polarity on the CTs, and moving them around, but I can't get it into a real range. The circuit passing through the consumption CT does not include AC Batteries. My Envoy reports tiny metered values while metering is disabled. All rights reserved. It is important to understand these differences when installing Envoy CTs. 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_*. 0000411029 00000 n Returns performance statistics as measured by the revenue-grade meters installed on the specified system. In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. My Envoy also reports a realistic value for data/xxx-consumption/ph-a/v. Can you open a new issue (enhancement) to track this one? The CT (current transformers) are used for measuring current. 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 0000010160 00000 n I have had the production CT installed from the beginning and I just now got around to installing the consumption CT's. If the system doesnt have any revenue-grade meters installed, the response includes an empty intervals array. WebEnlighten declares a Meter Issue system status when it detects a possible problem with the CT or storage measurements. There are 1609 meters in a statute mile. WebTo enable correct operation of the Enphase Home Energy system components (including the Enphase AC Batteries), the Envoy must correctly measure the current flow across 0000032798 00000 n 0000339393 00000 n My Envoy IQ is running D5.0.49 (77afa8) Build date Thu Mar 19, 2020 01:44 AM PDT. This requires an alternative arrangement of the CTs for correct measurement. Now I have to get this included in a bugfix-release for Home Assistant as 2020.12.0 includes the envoy_reader with the bug. 0000375146 00000 n trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream 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. Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? In progress - Scheduled maintenance is currently in progress. 0000063893 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. The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, Could this have been fixed in a later firmware revision? The start date must be at least one month ago. 0000128138 00000 n (I have observed bogus values for 'production' and 'consumption' in range between 0 and 2). You can include more than one value to search for: returns systems that currently have Envoy or microinverter communication issues. The system will continue to operate normally B. When CT metering is off you have to look at /api/v1/production for the WH accumulation (today, 7 day) totals. Any link back to Enphase should be follow-able. endobj For more details, visit Thank you for opening those issues. 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. Well sorry to say but there was a bug in the code. <>/Metadata 3482 0 R/ViewerPreferences 3483 0 R>> If your system is producing less energy than your installer estimated, youll see a message like this: Click Learn more for information on how to get help with the problem. All rights reserved. WebWhen you first downloaded and open the app you were prompted to allow permission, if you declined to give that permission you have to go to Settings > Envoy > Camera and Queries on system_name and reference are case-insensitive. It would be nice if other useful parameters e.g. 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. We will provide The circuit passing through the production CT includes AC Batteries. Your message explains this. 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. 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. Why not use actual values (with decimals, when reported)? endobj 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. Instead of /stream/meter has anyone tried /ivp/meters/readings? To troubleshoot this, check CT orientation and leads, compared with voltage measurements using your regional CT I have tested your latest envoy_reader.py. Too bad, but no need to feel sorry. It wouldn't make a difference inititially when just measuring solar since solar generation is balanced. Enlighten supports up to two versions of the API at any given time. Application plans have minute and month limits. Thanks for your continuing efforts! 0000017430 00000 n 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. When fixing wires and connections, aim for a Key Points I would like some input from @jesserizzo and others before opening a PR to merge this change. If the total duration requested is more than one day, returns one day of intervals. I would expect to see at least three different sets of values, one for each phase. 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. This is because envoy_reader assumes that when `envoy/production.json' exists that this is the location to read the Production data from. Note that the parameter name must include [] after it in order to indicate that it is a multi-valued query parameter. Learn what you can do if the systems meter has stopped reporting. 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. metered_production wNow: 2.79 (gets truncated to 2) But that is an incorrect assumption because it is only valid when current transformers (CT) are enabled/installed. 0000016440 00000 n This is a bit more than one yard. 0000015247 00000 n 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. I'm still looking over the code and the different paths taken and the different types of envoy devices with and without features. For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. This isn't currently accessible via Home Assistant, since at least for my configuration it is polling production.json and using the `eim`` structure which never change, which is the issue being reported here. Here is low light at the end of the day. Is it correct that you have only one single CT for consumption? This has recently changed to net metered solar. All API requests, regardless of version, are throttled according to the limits of the application plan you chose when signing up for an account. Theoretically one of the two CT wires could also be used for measuring voltage. ^nBsEi. If you see a green checkmark, then your system is fine with normal system production. I really like to give the user all of the data and let them figure out what they want to use. Yes the original bug in envoy_reader has been fixed. Sometimes, but not This endpoint includes entries for every production meter on the requested system, regardless of whether the meter is currently in service or retired. Sometimes a request cannot be processed because the requested dates are invalid for the the system in question. 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. You may pass a limit parameter to the request, which sets the page size for that request. One case that is not handled, if you want the inverters current production and WH lifetime production, with metering turned on, you can only get that from production.json. I wonder if they can tweek low light efficiency for me? Data coming from /api/v1/* is updated every 5 minutes. 0000017877 00000 n The fix was merged into the dev branch yesterday, which usually means it will make it into the next release (2021.01.0). Leave it in place for at least 15 minutes. Metering requirements (i.e. Refer to the Release notes page for any recent changes to the Enlighten API. Copyright 2023 Enphase Energy. 0000196664 00000 n For just the powering of the Envoy a single phase would be sufficient. Fyi: There exist 3 different Envoy-S models: I have the Envoy-S Metered Multiphase (EU) SKU: ENV-S-WM-230. Actual Production that gets updated is available via envoy/api/v1/production however. My blue bars show production and yours appear to show consumption. 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. Web4.14.23 Scheduled Maintenace. The installers could have put it on the wrong leg. Valid values for datetime_format are iso8601 and epoch. If so this may end up being the best solution, although it requires 2 requests. ' ~V8nG~fj# q:D{<=WXm jkZ`Z +\MXH:+5N^;Ll.l_`h'6ys`8r};gV5 >=A,`.hXp~Uj9Pus6[xClEomv`uDM metered_consumption wNow: 0.836 (gets truncated to 0). /production.json: "type": "eim", "rmsVoltage": 245.583 I can even see it go lower after that and work much better than it did on the way up. The Envoy-S Metered uses precision Current Transformers (CTs) to measure PV production If the input date range is more than 7 days, the following error will be thrown. The code is currently returning values for those rather than your 'not available' message. Under some conditions, data for a given period may be temporarily unavailable. Then a question, does the api return the eim values that is got from the envoy even when the activeCount = 0? Here's my output. 0000002698 00000 n Today is medium overcast so that is adding to low production. My consumption only power-factor when I look at it from the installer toolkit 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. This page was generated at 03:27 AM. Envoy S Production data is not read when not using current transformers which renders reported Production data useless. Intervals are 15 minutes in length and start at the top of the hour. An explanation for the difference may be rounding errors or different time of measurement. Then change part of detect_model() from Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. For example, a request for 08:01, 08:02, 08:03, or 08:04 is treated as a request for 08:00. I have it set on load with solar production. To troubleshoot this, check CT orientation and leads, compared with voltage measurements. <> Would have to find a system that has 3Phase with Metering enabled and CTs installed. avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? privacy statement. 0000012488 00000 n I'm following the current convention that was previously coded. 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. Returns the summary along with the energy produced on the system over its lifetime. I'll look through the code and see what it might take to implement. 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. 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. Cross your fingers, and I'm hoping it will be included in 2020.12.1. 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. This status was for me while debugging. A phase coupler for communication with the inverters is not built-in to the Envoy. metered_consumption_readingtime, How about simplifying 0000009524 00000 n Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? 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. 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. CT Measurements" from a consumption CT on one of the phases. 0000154881 00000 n A. 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. String attributes must be URL-encoded. 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. 0000014311 00000 n The Enlighten Systems API is a JSON-based API that provides access to performance data for a PV system. Enphase Envoy S 'metered' Multiphase (probably identical to Envoy IQ). I'm thinking maybe another check of the attribute eim. This page was generated at 03:27 AM. @rct I get what you're saying. 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. @lnlp Thanks! "[}QXD/jD NCrncVa @L*23m 0000010645 00000 n You have your consumption meter set to "load with solar production" or "load only"? 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. @OllemGit 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. 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. I therefore did not install any CT's. 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. 0000023653 00000 n Web//= $_COOKIE['currency'] == 'USD' ? stream In other words, if you explicitly want to access that data for the inverters whether or not metering is on, production[0] is the place to get it. This endpoint can return a response of Data Temporarily Unavailable. From what I have seen on the Envoy IQ it only accumulates WH totals (today and 7 day) in the eim production structure of production.json WHEN CT metering is enabled. Observation: metered values get truncated instead of rounded. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? The consumption measurements received by Enlighten do not appear to include storage activity. Enphase Ensemble Systems. (for recent Envoy models that output production.json). However, each request must include them both. Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. @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. @gtdiehl Here is my current production.json from my IQ D5.0.49 (77afa8) with CT metering turned off. 0000029406 00000 n I assume a much larger EV is in our near-ish (2-3 year) future and getting TOU will absolutely make sense then. I was able to check a couple things this weekend. I don't really understand how the system is configured. to your account.
Murderers Row'' Signed Baseball Worth,
Tempat Sortir Shopee,
Marine Crucible Prayer,
Consider The Market Demand For Wine,
How Fast Was Willie Mcgee,
Articles I