Skip to content

Add integration support for Neptune Systems Apex Aquacontroller#34558

Closed
jpelzer wants to merge 10 commits into
home-assistant:devfrom
jpelzer:add-neptune-apex
Closed

Add integration support for Neptune Systems Apex Aquacontroller#34558
jpelzer wants to merge 10 commits into
home-assistant:devfrom
jpelzer:add-neptune-apex

Conversation

@jpelzer
Copy link
Copy Markdown

@jpelzer jpelzer commented Apr 22, 2020

Proposed change

Adds support for the Neptune Systems Apex Aquacontroller, an IP-connected aquarium controller. Has support for probes and outlet controls.

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

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:

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

@homeassistant

This comment has been minimized.

@homeassistant
Copy link
Copy Markdown
Contributor

Hi @jpelzer,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@jpelzer
Copy link
Copy Markdown
Author

jpelzer commented Apr 23, 2020

Not sure how to get cla-error label removed, as the issue with the committer email has been resolved but the bot hasn't removed the label. Does pinging @homeassistant make the bot recheck?

@Apocrathia
Copy link
Copy Markdown

Well I'll be damned. I had looked into this years ago using the same sort of XML scraping method that your pynepsys library is using, but never pursued it after having some issues with Neptune and abandoning their ecosystem. I'm sure a lot of people still use their products, though. Great work! 👍

@frenck
Copy link
Copy Markdown
Member

frenck commented Apr 24, 2020

@Apocrathia Totally OT... but I have to respond. Your GitHub Avatar just made my brain travel back in time. "Mmmm... I'm thirsty!" 😂 👍

@jpelzer
Copy link
Copy Markdown
Author

jpelzer commented Apr 24, 2020

Alright, so this one should be good to go, ready for reviewers to tear into.

Docs and images are in PR again:
home-assistant/home-assistant.io#13151
home-assistant/brands#1490

@stale
Copy link
Copy Markdown

stale Bot commented Jun 3, 2020

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.

@stale stale Bot added the stale label Jun 3, 2020
Comment thread homeassistant/components/neptune_apex/__init__.py Outdated
Comment thread homeassistant/components/neptune_apex/__init__.py Outdated
Comment thread homeassistant/components/neptune_apex/__init__.py Outdated
Comment thread homeassistant/components/neptune_apex/config_flow.py Outdated
Comment thread homeassistant/components/neptune_apex/light.py Outdated
Comment thread homeassistant/components/neptune_apex/strings.json Outdated
Comment thread homeassistant/components/neptune_apex/strings.json Outdated
Comment thread homeassistant/components/neptune_apex/config_flow.py
Comment thread tests/components/neptune_apex/test_config_flow.py Outdated
Comment thread tests/components/neptune_apex/test_config_flow.py Outdated
@stale stale Bot removed the stale label Jun 9, 2020
@jpelzer jpelzer force-pushed the add-neptune-apex branch from 352a8bb to 3f160a1 Compare June 10, 2020 16:00
Comment thread homeassistant/components/neptune_apex/light.py Outdated
jpelzer and others added 2 commits June 10, 2020 18:52
Don't need 'apex' prefix for unique id.

Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
@stale
Copy link
Copy Markdown

stale Bot commented Jul 11, 2020

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.

@stale stale Bot added the stale label Jul 11, 2020
@stale stale Bot closed this Jul 18, 2020
@davidpesce
Copy link
Copy Markdown

Why wasn't this merged?

@MartinHjelmare
Copy link
Copy Markdown
Member

It went stale with a failed build. The author can request to have it reopened if ready to finish it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants