Fix peco integration

[IceBotYT]

Proposed change

Bump peco-outage-api to version 0.0.30
Diff here

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 PECO Outage Counter inoperative #109228
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

[IceBotYT]

If this could be in the next patch that would be great 👍

[NECH2004]

manifest, requirements and test requirements changed. All peco related unit tests run locally without errors.

[frenck]

👋 @IceBotYT

It seems like there are multiple things going on here. A dependency dymb and some refactoring. These seem to be unrelated (and such thus be in separate PRs).

Looking upstream, I noticed there are no releases or version tags to be found there. I would strongly encourage you to add those to the GitHub project of the library (enhancing the transparency and adds clarity).

Last but not least, there are some weird files there now in the recent commits. Like:

The file cannot be viewed with GitHub (that seems specifically an issue on GitHub's end, which you might want to report with them?) anyways, I'm not sure why it is there.

../Frenck

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[IceBotYT]

👍 I will remove refactoring and add release tags. Was the first library I've ever made so 😅
But with this:

The file cannot be viewed with GitHub (that seems specifically an issue on GitHub's end, which you might want to report with them?) anyways, I'm not sure why it is there.

../Frenck

I noticed that file too, but when I tried to open it on VS Code it just threw some error saying the file didn't exist (??). I'm thinking of just redoing the local repo on my system and trying to clean that file out.