search

briancmpbll / home_assistant_custom_envoy

171 stars 76 forks source link

Testers for for next version v0.0.18-DEV-2/v0.0.18-DEV-3 requested. #157

Closed catsmanac closed 9 months ago

catsmanac commented 10 months ago

PR#149 and PR#150 have been added to the code and published in the DEV-TEST repository as beta release V0.0.18-dev-2.

As usual testing before general release is good habit and help with testing is appreciated.

When testing realize it's beta testing, issues may still surface. It was tested before with my ENVOY-S Standard, but as that type is lacking may features this test is more confirmation of not breaking it then anything else. It was also tested with file based static datasets of various envoy types (Metered with and without CT, with battery, 1 or 3 phase and legacy with FW >= 3.9 and < 3.9) to confirm data is processed as expected, but this does not address any dynamic peculiarities of any of these types nor is it a full coverage off all types. You're taking some risk. ( MIT license here.)

If above didn't scared you away, the test version can be downloaded in HACS from https://github.com/catsmanac/home_assistant_custom_envoy. It will show as DEV-TEST. When you have both DEV and DEV-TEST in hacs you can switch between these by re-downloading from the repository you want. Make sure to enable the show beta test option switch on DEV-TEST.

Issues found can be reported here. Also if it works fine. In both cases, if you are wiling, upload the Envoy diagnostic report here after renaming it to a .txt file and removing anything you don't want to share. It allows troubleshooting and fine tuning of the static test files for future testing.

testuser7 commented 9 months ago

I just installed the test version. Everything seems to be working. Only current_consumption, current_production, frequency, power_factor and voltage counters are displayed as disabled by integration. And found one typo: https://github.com/catsmanac/home_assistant_custom_envoy/blob/Dev/custom_components/enphase_envoy_custom/const.py#L454

Maybe the names current_consumption and current_production should be changed to amps_consumption and amps_production?

catsmanac commented 9 months ago

Thanks for testing @testuser7.

Are it both the cumulative and the phase entities disabled by the integration or just the cumulative ones?

Thanks for finding that typo, I'll update it.

As for the names of current, I was in doubt when merging it, but in the end decided to keep it and capitalize Current in the description. I was considering amps as well, but didn't feel it was fully appropriate either. But there is something confusing. Since it is Current I rather would go for consumption_current and production_current.

catsmanac commented 9 months ago

Only current_consumption, current_production, frequency, power_factor and voltage counters are displayed as disabled by integration.

Yes these are added as disabled by default to have users make conscious choice to enable them. Should have mentioned that in the description.

testuser7 commented 9 months ago

As for the names of current, I was in doubt when merging it, but in the end decided to keep it and capitalize Current in the description. I was considering amps as well, but didn't feel it was fully appropriate either. But there is something confusing. Since it is Current I rather would go for consumption_current and production_current.

Or maybe current_electricity_consumption and current_electricity_production? I'm also wondering if we should replace the word Net with Grid in the name of the metrics.

Yes these are added as disabled by default to have users make conscious choice to enable them. Should have mentioned that in the description.

It would be nice to be able to enable/disable metrics in the integration configuration.

madbrain76 commented 9 months ago

I just installed your version - seems to be running OK with my 3 Envoys (1 S, 2 IQ), but it's only been a minute.

Steve2017 commented 9 months ago

I just installed v0.0.18-DEV-2 and it is working as expected. The old data is in-line with the RESTful data I am also getting.

So - it's working and not glitching, but.........

The new data showing amps and voltage doesn't quite align with what I expected. For example, the sun is down, so production is zero, but it is still showing as 0.211 amps. Even accounting for phantom production - ie: the power required to run the inverters, that is 50-watts - still a lot more than I would expect.

The consumption current is about 20% higher than the other data when converted to watts. (the amps * v is showing about 1100 watts where everything else is showing 900 watts).

I am not sure the additional sensors are useful to me, so I would not enable them. I am happy with the existing watts readings and prefer the lifetime energy imports and exports sensors from this V17 repo.

catsmanac commented 9 months ago

Thanks for testing @madbrain76, keep us posted how's going.

catsmanac commented 9 months ago

Thanks for testing @Steve2017.

The amps and volts are coming from ivp/meters/reports on the Envoy, rmsVoltage and rmsCurrent. If you open the diagnostic report of your Envoy you can find what raw data was collected from the Envoy. Data is shown as is in Enphase quality.

Enphase tells to use Watts=Voltage Amps Powerfactor. Does that match any number better?

catsmanac commented 9 months ago

I'm also wondering if we should replace the word Net with Grid in the name of the metrics

prefer the lifetime energy imports and exports sensors

Naming it right is always a complex matter. That's why HA provides the option to use a friendly name on each entity.

Considering that envoy pages all use net-consumption using net consumption and net production is best the middleground.

catsmanac commented 9 months ago

I am not sure the additional sensors are useful to me, so I would not enable them

Mentioning enabling, I'm now finalizing dev-3 that will have an option to not use production json page at the cost of having daily total and last 7 days total unavailable. It will then run from ivp/meters/reports, api/v1/inverters and /ivp/ensemble/inventory. Only at retsrat it will have a peek and production json to determine the model. Only for ENVOY metered with CT

As meters reports returns up to the last second readings from the CT it's an option to update more frequent and maybe avoid daily hog of the production page.

Steve2017 commented 9 months ago

I didn't take into account the power-factor so that might have made the difference.

testuser7 commented 9 months ago

@catsmanac I think the configuration description could look like this:

Additionally, you could add:

in the configuration.

catsmanac commented 9 months ago
  • Enable Today's and Last Seven Days data (use production.json endpoint)

Well that would mean Today's and Last Seven Days data gets broken when updating. That's why it is as it is now, by default everything remains working as it was working before and it's a conscious decision to enable new mode and make Today's and Last Seven Days unavailable.

  • Enable Consumption/Production Current, Frequency, Power Factor and Voltage data

I looked into this but it's not straight forward from the configuration screen and can be done already from the entities screen.

catsmanac commented 9 months ago

V0.0.18 released in production!

Thanks for the help and testing.

Steve2017 commented 9 months ago

Does that mean the right version (token version) is available in the official integration page?

So I can delete these trial versions?

catsmanac commented 9 months ago

v0.0.18 is in @briancmpbll 's custom integration as current version. So it replaces these last trial version and you can install it using HACS and (re)download the Enphase Envoy (Dev) one.

If you are asking if the official Home Assistant version now has token support, yes it has token support as of 2023.9. Some entities it has may differ, missing or others are present.