Add last_reset for Sense trend sensors

[kbickar]

Proposed change

Adds the last_reset attribute for trend sensors. This prevents them from showing a large spike at the start of the day

A small update was needed for the sense api library to allow the date to be passed to fix a problem with the last_reset not being set correctly if the timezone of the HA machine didn't match.
https://github.com/scottbonline/sense/releases/tag/0.9.4
https://github.com/scottbonline/sense/releases/tag/0.9.5
https://github.com/scottbonline/sense/releases/tag/0.9.6

scottbonline/sense@0.9.3...0.9.6

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)
• 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 Sense Trend Sensors Incorrect 'last_reset' Value #59801
  • fixes Sense integration long-term statistics broken #62568
  • fixes Sense shows negative consumption in Energy dashboard #63226
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[epenet]

Please add a link to the changelog in the description

[kbickar]

@emontnemery Made some updates to the library - it seems the API will return the start of the trend data if you pass it what it'd expecting. Much less difference in HA now

[bdraco]

Thats a lot cleaner. I'll install this on my production systems and report back in a few days

PR rewritten

[emontnemery]

This looks perfectly fine from a Home Assistant POV now.

A comment on the change in the library though, please don't do bare excepts, do like this instead:

        try:
             start_iso = self._trend_data[scale]['start'].replace('Z', '+00:00')
             return datetime.strptime(start_iso, '%Y-%m-%dT%H:%M:%S.%f%z')
-       except:
+       except Exception:
             return None

[bdraco]

So far so good. Waiting for the day to roll over to confirm

[bdraco]

Looking good. Waiting for the sun to come up and the solar to kick in for a full test cycle

[bdraco]

Looks like its working as expected 👍

Please fix the bare excepts in the upstream lib in a followup.

Thanks!

[emontnemery]

awesome, thanks @bdraco for testing!

[wjhrdy]

How do we get access to this bugfix? Is there any configuration or is it transparent to the user?

[kbickar]

@wjhrdy It'll be in the next release or you could take the files changed and put them in your installation

[404FNF]

So not in new 2021.12.10 update just installed?

[bdraco]

2022.02