Flexpool.io Sensors Integration

[DatDraggy]

Proposed change

I am adding a few sensors for the Ethereum mining pool Flexpool.io to homeassistant as my first integration.
I've been asked by other HA users to try my luck at an integration for this pool.
As mentioned, this is the first time working on HA for me. I've looked at other sensor integrations to get a grasp of how that could look like, but I'm not sure if what I've done makes sense or could be done better.

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

Example Configuration:

Example address for testing 0x5F8A1ae37f7caDA442241BE98b507E2455A3121D

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add flexpool documentation for integration home-assistant.io#17164

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.
• 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.

[DatDraggy]

Checks are done. Thank you for your help with the test, Nathan. :)

[DatDraggy]

I believe review approval is still missing or do you not have permission to fully review PRs? I don't quite know how things work here.

[ntilley905]

If you're asking me, that is correct, I am not a core developer, only a contributor. My review does not give you reviewer approval. One of those devs will be around at some point, they're pretty busy so be patient!

[DatDraggy]

Okay, I thought so. Thank you so much for taking your time to review it anyway. There were changes needed after all

[frenck]

Hi there @DatDraggy 👋

I did an initial review pass, to get some things going and moving.
I think the biggest change you should consider, is implementing the DataUpdateCoordinator.

Some of the suggestions in this review, might require you to rebase this PR onto the latest dev branch first.

../Frenck 🚂

[DatDraggy]

Alright, all feedback was implemented as far as possible. The official python package kind of limits the usage of the update coordinator, but it does reduce the amount of api calls.
I've tested all and it works. For some reason the workflow tests don't run anymore so I'm not sure if they pass.

[DatDraggy]

There will be a new api wrapper soon so I'm going to put this PR on hold for now until I have implemented the new one. It improve performance drastically.

[frenck]

Look at it again, added a comment (besides the comments that are still open at this point). Could you take a look at those @DatDraggy? 👍

[frenck]

Please keep this file alphabetically sorted.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.