issue with envoy meter measurementswhen will pa vote on senate bill 350 2021

In your case it should be "load with solar production" as the solar breaker is on the load side. I will make a capture tomorrow when it's light and the system is actualually producing. (My solar installer did not connect L2 and L3 on the 'power input' connector so I am currently unable to verify for ph-b and ph-c.). 0000470581 00000 n 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 Production CT Installation on sites with multiple solar systems. WebC. 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. Observation: metered values get truncated instead of rounded. production_readingtime (source: production.json production inverters readingTime) When the production version of envoy_reader will be updated, will this get automatically updated in existing Home Assistant (Enphase Envoy add-in) installations? 0000093464 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. ct_enabled with default value True (requires no changes in existing client code). So I swapped the leads on the Envoy for the consumption CT's and have been monitoring all day and the data looks good. My 8x320W=2.56 kw mono array gets the IQ6+ inverters running at pf=1 at 700 VA. Some batteries havent charged or discharged recently. The Envoy backend should actually have both values, and the API retrieving the data I currently check the /api/v1/production data in a browser and refresh manually. 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. An Envoy S (and probably Envoy IQ) without CT's enabled should be handled as 'endpoint_type' "P" instead of 'endpoint_type' "PC". Regarding bullet 2: No, not only those two values. A phase coupler for communication with the inverters is not built-in to the Envoy. 2 0 obj returns systems that currently have production issues. please contact Enphase Technical Support. (Envoy-S metered multi-phase (EU) with no CT's installed.). D`TR2 (P@$D j+C"qa7%A]4(uWP7T! Copyright 2014 SolarReviews All rights reserved. 0000154623 00000 n Since installation the system has shown an intermittent error: "Meter Issue. And for the nice to have wishlist: Key Points Requests for times that do not fall on the 5-minute marks are rounded down. 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. 0000232378 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. Active does not imply that the device is currently reporting, producing, or measuring energy. Here is the output of envoy_reader from various Envoys. This is useful where you need to capture the production data of another PV installation where this is wired to a different location in a property. The output suggests there are four data sources production from the inverters, and then a type "eim" reporting production, a type "eim" reporting "total consumption", and a type "eim" reporting "net consumption". But envoy_reader does not read it. (Maybe you are mistaking with the cloud API's update frequency?). Can you open a new issue (enhancement) to track this one? Meters that have been retired from a system will show an end_at that doesnt change, and that eventually is far away from the current time. If the meters milliamp scale goes up to 500mA, then Do not violate the other restrictions described in the Enphase, Copyright 2023 Enphase Energy, Inc. All rights reserved. The time series includes one entry for each day from the start_date to the end_date. If the system doesnt have any revenue-grade meters installed, the response includes an empty intervals array. I just wanted to let you know the logic might not be working as intended. My blue bars show production and yours appear to show consumption. 0000063893 00000 n I've got the old (non-IQ) version of the envoy. trailer <]/Prev 1017858/XRefStm 2698>> startxref 0 %%EOF 907 0 obj <>stream 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. The code currently does a check to see if the attributes of production and consumption exist in the web page. If the input date range is more than 7 days, the following error will be thrown. Are all three phases wired to your Envoy power connector_(most-left connector on the Envoy)_? The code is on one of my branches. & The circuit passing through the production CT includes AC Batteries. 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. 3.48 kW of SolarWorld panels and Enphase IQ7 micros. 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. I have had my solar setup for 1.5 years so far, no issue. 0000303679 00000 n (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. I like the suggestion of using /api/v1/production by default and add the additional metered_* parameters for /production.json. Valid values for datetime_format are iso8601 and epoch. 0000048797 00000 n Electrical system: 3-phase 230V. A difference of 1 Watt, which may be caused by a rounding error, or by a small difference in moments of measurement. This is just low sun with overcast far to the side of the array. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? It appears that this value is probably taken from the same L1 input, but its value differs few-thousand's of a volt. Have a question about this project? While much of the rest of the world uses the metric system of centimeters, meters, and kilometers, US has continued to the English units. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? Or maybe the Envoy combines the data of all three phases and the differentiation gets lost? 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. 3 0 obj The darkish overcast looked like possible little snow storm coming. This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. : I suggest to add the following two output parameters for this (so they can be read as sensor values in Home Assistant also); Can you open a new issue (enhancement) to track adding new parameters? Attributes that are times are named accordingly (e.g., operational_at, last_report_at, start_at, end_at). I have made the change to fix it, actually just removed a single line of code, PR #51. Last one. I'm sorry about this! Attributes that are dates are named accordingly (e.g., summary_date, start_date, end_date). @lnlp Thanks! Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. ' ~V8nG~fj# q:D{<=WXm jkZ`Z +\MXH:+5N^;Ll.l_`h'6ys`8r};gV5 >=A,`.hXp~Uj9Pus6[xClEomv`uDM Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Maybe this is only of interest to me. I have an Enphase system but it only has production and the blue bars are in the same orientation as in your chart. Unrecognized parameters are ignored. 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 0000016440 00000 n In Home Assistant ('Enphase Envoy' add-in which uses envoy_reader) I do not get actual values for all 4 values shown in /api/v1/production. I have assumed it was 'Voltage and Current Metering' using the ohm's law variables (P = EI), so EIM. Returns a time series of energy produced on the system over its lifetime. I hope you get the help you need. I think it is working as you intended, but see. My consumption only power-factor when I look at it from the installer toolkit I just tested it in Windows Sandbox: No authentication required for both url's. 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. Do you know what the "eim" stands for? Note: I've got production and consumption metering turned off (activeCount == 0). When they can finally talk it tells the Envoy this and the system averages it Did you power off and repower your Enlighten box after you made those changes. Returns performance statistics as measured by the revenue-grade meters installed on the specified system. 1 m is about 39.37 inches. 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 Intervals are 15 minutes in length and start at the top of the hour. If the total duration requested is more than one day, returns one day of intervals. Would have to find a system that has 3Phase with Metering enabled and CTs installed. 0000017430 00000 n Each envoys element includes the following: Returns a list of systems for which the user can make API requests. 0000018303 00000 n The Envoy-S Metered is a system monitoring tool, and control device. 0000410990 00000 n This status was for me while debugging. 0000004163 00000 n I tried to take a screenshot but it did not come through very well. When using Envoy S without having CT's enabled then production data in envoy/production.json is NOT updated. I see now that there was mention of these URLs in the Envoy-S data scraping blog that I missed previously. The maximum page size is 1000. Meters are abbreviated using a lower case "m" in measurements. I would like some input from @jesserizzo and others before opening a PR to merge this change. Anyway, I tried reversing both the production CTs and swapping their phases. A. So I thought I'd update people on what I found just in case someone else runs into this problem. By default, systems are returned in batches of 100. Copyright 2014 SolarReviews All rights reserved. Any link back to Enphase should be follow-able. 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). It was like this for a Could this have been fixed in a later firmware revision? See following comment in #46 for more information. /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 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_*. There are 1609 meters in a statute mile. 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. 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. All API requests, regardless of version, are throttled according to the limits of the application plan you chose when signing up for an account. This is called the merged time series. In addition, the response includes the attribute meter_start_date, to indicate where in the time series the meter measurements begin to be used. I would also prefer if the timestamp of when the values were updated can be added, e.g. Example: It is possible to request a subset of the systems list. Some may view this as a draw back. 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. 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. lastReportDate and readTime (there's little consistency in the different names unfortunately). Endpoints that receive times expect the time to be expressed in Unix epoch time. As a result the reported Production values are either 0 or some bogus value. All measurements are in Watt hours. Interesting, /ivp/meters gives some configuration/status information such as phaseCount and phaseMode that I haven't seen elsewhere: http://envoy.local/ivp/meters/readings seems to be very useful. It is important to understand these differences when installing Envoy CTs. ^nBsEi. I upgraded to HA 2020.12.1 today and the /api/v1/production counters now appear to report properly in HA. 0000161348 00000 n Not sure what the actual url for the page is though. If these are zero than poll data from the other production page. 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 am just grasping at straws here. If your application does not allow for you to include an image, you must include the text Powered by Enphase Energy. Wherever you display information from the. 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. 0000007176 00000 n You can sign up to be notified by email if your system experiences either type of production issue. Do you expect to get the fix into the next (bug-fix) release (presumably 2020.12.1)? I'll have to look into this one a bit. If you are installing in a multiphase application, the power line communication signal must be coupled I can even see it go lower after that and work much better than it did on the way up. "Metered Production data not available for your Envoy device." Install a phase coupler on the load side of the over-current protection device. Web//= $_COOKIE['currency'] == 'USD' ? In progress - Scheduled maintenance is currently in progress. 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. According to the IQ Envoy manual this is possible if the user wants revenue-grade production metering. 9 kW solar, 42kWh LFP storage. 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. Depending on if the Envoy is configured as Net or Total Consumption could impact the values you are seeing in Home Assistant. I agree a better solution would be to have additional parameters. In that case, where is the total power reported in /production.json ? 0000004049 00000 n envoy_reader should handle all these (4) situations correctly. The start date must be at least one month ago. measure resistance from black wire at lgm connector (while disconnected) to ground behind side panel inside rear cargo area. I'm not sure what would be a good way to name production Watts data elements to allow referencing either or both of them in Home Assistant's configuration. 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. No Home Assistant will not get fully updated automatically. Input date range for rgm_stats is restricted to 7 days. I've tried switching polarity on the CTs, and moving them around, but I can't get it into a real range. @rct I get what you're saying. There are no gaps in the time series. Here is heavy overcast at the end of the day with sun low and far to the side of the array. The circuit passing through the consumption CT does not include AC Batteries. % The new version of API (v4) is available at: developer-v4.enphase.com. %PDF-1.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. There is an issue with the meter measurements. My Envoy homepage shows "Software version R4.10.35 (6ed292)" is that the Envoy's firmware version? 3.48 kW of SolarWorld panels and Enphase IQ7 micros. 0000010160 00000 n 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. The Enphase Home Energy System meters solar production and home electrical loads. Keeping in mind that consumption monitoring is an optional add on that doesnt interfere with the core functionality of the solar system. 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. They can always filter these values out in Home Assistant by specifying which monitored_conditions they want to see. This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. So I just display the values unless the device actually does not support metering. 0000339432 00000 n Yes, I do want and think the values for both inverters and eim should be accessible if available. This is not my experience. I haven't reached out to Enphase yet. CT Measurements" from a consumption CT on one of the phases. In my comments above, I was arguing for the case to still be able to get the inverter numbers even if metering is enabled. Solar Production CT MUST measure all solar circuits on site. The epoch format returns all temporal values in Unix epoch time. The response includes intervals that have been reported for the requested period. 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. 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. 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. 0000011718 00000 n 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. I have had my solar setup for 1.5 years so far, no issue. And the metered_* parameters come from the appropriate section of /production.json that contains type of eim. 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 hope we can see it being updated in Home Assistant as well soon. )bJ60F-phEZ The CTs accommodate conductors up to 4/0 RHW, 350MCM THWN, The system will continue to operate normally B. For example, midnight on 5 May, 2015, in Pacific Daylight Time is 1430809200. If your systems meter has stopped reporting, youll see a problem message like this: For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. EV owner since 2012. When fixing wires and connections, aim for a 0000232417 00000 n

Usga Senior Am Qualifying 2022, Slingshot Ride Accident 2021, Is A Tablet An Embedded System, Articles I