The circuit passing through the consumption CT does not include AC Batteries. Going down this path means renaming 4 monitored_conditions and adding 4 or5 new ones will appear for each new Envoy sensor added to Home Assistant. My envoy has values for those rather than all zero, because metering was turned on a while but wasn't giving the right values. I would also prefer if the timestamp of when the values were updated can be added, e.g. It could be the CTs are plugged into the wrong socket. <> 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. I hope you get the help you need. If the total duration requested is more than one day, returns one day of intervals. This would allow access to finer grained energy production data for uses such as graphing 15 minute intervals. 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. Instead of /stream/meter has anyone tried /ivp/meters/readings? I use Envoy S but without any CT's installed. Sometimes, but not New releases (due to incompatible changes) are communicated well in advance of removing the older one. Maybe this is Envoy-S Metered (Multiphase) and or firmware version dependent? See following comment in #46 for more information. My Envoy homepage shows "Software version R4.10.35 (6ed292)" is that the Envoy's firmware version? To troubleshoot this, check CT orientation and leads, compared with voltage measurements using your regional CT 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. 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. 0000410990 00000 n 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). Key Points 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 CT Measurements" from a consumption CT on one of the phases. Correct me if I'm wrong, without CT metering, Also, If state was kept and easily accessible in either envoy_reader (or Home Assistant), today's WH production and the last seven days of WH production could be determined from tracking the, If CT metering isn't turned on, and the user wants to see the Envoy's inverter totals for today and the last seven days, then. I know this may seem like a back step but I'm thinking of changing back to the original output of the envoy_reader api, and have the code get the production values based on the activeCount attribute. (*) Note: I don't know that production[0].type is always inverters and production[1].type is always eim. If the message persists and is not due to unusual production or consumption conditions, contact your installer for help. If a meter or meters are installed on the system, measurements come from the meter; otherwise, measurements come from the microinverters. 0000048727 00000 n 0000093917 00000 n In 'case A' one may wonder why the phase voltages are reported separately for production, net-consumption and total-consumption. Enphase Envoy S 'metered' Multiphase (probably identical to Envoy IQ). If you are not sure how to meet these requirements, please contact api@enphase.com before you launch anything. 0000003055 00000 n WebThere is an issue with the meter measurements. The manual is not clear about why all 3 phases should be connected to the 'power input' connector. 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. 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. Like I said I haven't looked through all of the comments yet. 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. 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. /production.json: "type": "eim", "rmsVoltage": 245.583 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. (Envoy-S metered multi-phase (EU) with no CT's installed.). 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. 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. Refer to the Release notes page for any recent changes to the Enlighten API. The Net number calculated under the date looks wrong. I don't really understand how the system is configured. 0000001916 00000 n 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. 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_*. This is caused by my Envoy not by envoy_reader. I'm sorry about this! 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. 0000004049 00000 n For a 3-phase installation I would need to buy 4 additional CT's while consumption and production data is already provided by my smart electricity meter (via DSMR P1 port). 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. production.json eim only shows an aggregated number. period_start and period_end tell you when the minute (in this case) started and when it will end. I have made the change to fix it, actually just removed a single line of code, PR #51. Each Microinverter element includes the following: This endpoint is deprecated and will be removed in a future release. By default, systems are returned in batches of 100. 0000003706 00000 n 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. Intervals are listed by their end dates; therefore, the first interval returned is 15 minutes after the requested start date. 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. IF you require further technical clarification for your installationplease contact Enphase Technical Support. metered_production wNow: 2.79 (gets truncated to 2) You have your consumption meter set to "load with solar production" or "load only"? If the system does not have a meter, returns 204 No Content. For example, a request for 08:01, 08:08, 08:11, or 08:14 is treated as a request for 08:00. 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. avh]O(ar /I;}z*',)RsB$F8$tE)>}0.B "sk]a/E+sQWTM/Na>GGqJRCX?? rmsCurrent and rmsVoltage could be reported by envoy_reader as well. 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. 0000048797 00000 n I would like some input from @jesserizzo and others. Though I wonder if something like this would solve the problem, Add a function called hasMeteringEnabled() which will return True if production[1]eim activeCount is >= 1 else False, envoy_reader/envoy_reader/envoy_reader.py. Could there there be another (URL) location on the Envoy where differentiated data for each phase is available? 0000029406 00000 n Are all three phases wired to your Envoy power connector_(most-left connector on the Envoy)_? Learn what you can do if the systems meter has stopped reporting. Yes, I do want and think the values for both inverters and eim should be accessible if available. [V6Pq ]_,.7bK~lqq}e~Y4e[./7ew,X*k9IAhR4wgf e EZ%%da'6[kV^n7H"]c$)yRT@S1A| _|w,#G(@!{;? Returns the summary along with the energy produced on the system over its lifetime. As previously requested please add the following output parameters: I was able to check a couple things this weekend. I'll look through the code and see what it might take to implement. This "readingTime" is probably accurate enough to be used as timestamp for data in /api/v1/production. The epoch format returns all temporal values in Unix epoch time. If you dont have permission to view consumption data, the response code is 401. Part number: 800-00554-r03, x=r?#Z[Sd{q20$&! 0000268048 00000 n 0000139340 00000 n All times are GMT-5. 3 0 obj Do not nofollow your links to Enphase. Here are captures of /api/v1/production, /production.json and /api/v1/production/inverters. So I just display the values unless the device actually does not support metering. Note that big power spike in the morning, that is our electric car (Ford C-Max Energi) pre-heating the cabin. Hopefully that data can be read from elsewhere on the Envoy, without requiring installer permissions. WebThe Envoy-S monitors the microinverters that are connected to the PV modules. Recently my meter box was moved and the sparkie put the consumption CT backwards. If your systems meter has stopped reporting, youll see a problem message like this: /api/v1/production/inverters (serial numbers have been obfuscated): /api/v1/production "wattsNow": 2236 According to the IQ Envoy manual this is possible if the user wants revenue-grade production metering. Is D5.0.49 newer than R4.10.35? metered_consumption_readingtime, How about simplifying ^nBsEi. After period_end, you can make another request. Copyright 2014 SolarReviews All rights reserved. For example, there are 100 centimeters in a meter. This is just low sun with overcast far to the side of the array. If so this may end up being the best solution, although it requires 2 requests. 1.0 5 Additional Features Additional features include wrong wiring detection, such as inversion 0000032798 00000 n My utility company (Xcel) has a great program where the rate is ~$0.04 per kWh which is awesome. 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. By using the Enlighten Systems API, you agree to the Enphase Energy API License Agreement. 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. In the "inverters" section? Parameter order does not matter in any request.
