Fix state class in Enphase Envoy

[vpathuis]

Proposed change

The Enphase Envoy integration uses TOTAL_INCREASING for several entities. I think these should be TOTAL.
Documentation says: "It's recommended to use state class total without last_reset whenever possible".

Also this log error appears for two of these entities, as issued in #85172:
Entity sensor.envoy_122131003872_last_seven_days_energy_consumption from integration enphase_envoy has state class total_increasing, but its state is not strictly increasing

Tested this locally and seems to work without a problem.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Enphase Envoy - 2 cumulative sensors are decreasing instead of increasing #85172
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @gtdiehl, mind taking a look at this pull request as it has been labeled with an integration (enphase_envoy) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of enphase_envoy can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign enphase_envoy Removes the current integration label and assignees on the issue, add the integration domain after the command.

[epenet]

Are all of them causing an issue?
I would think maybe only Last Seven Days sensors need adjustment.

[vpathuis]

Are all of them causing an issue? I would think maybe only Last Seven Days sensors need adjustment.

True.
Although I'd also fix the daily sensors. Although these sensors are not created in my instance, These would also have the same problem.
But it's only 6 lines, so why not fix them all.

[epenet]

Are all of them causing an issue? I would think maybe only Last Seven Days sensors need adjustment.

True. Although I'd also fix the daily sensors. Although these sensors are not created in my instance, These would also have the same problem. But it's only 6 lines, so why not fix them all.

If daily is "since midnight" the total_increasing is correct
If daily is "last 24hrs" then total is correct.

I would only correct the ones causing an issue.

[vpathuis]

If daily is "since midnight" the total_increasing is correct If daily is "last 24hrs" then total is correct.

I would only correct the ones causing an issue.

Good point. Let's make the other sensors something to address later if neccessary.

[epenet]

Lgtm 👍