Skip to content

Add solar production sensors to neurio_energy#159533

Merged
joostlek merged 1 commit into
home-assistant:devfrom
W7RZL:neurio-energy-add-solar-production
Dec 23, 2025
Merged

Add solar production sensors to neurio_energy#159533
joostlek merged 1 commit into
home-assistant:devfrom
W7RZL:neurio-energy-add-solar-production

Conversation

@W7RZL
Copy link
Copy Markdown
Contributor

@W7RZL W7RZL commented Dec 21, 2025

Add two new sensors for solar/generation monitoring:

  • Energy Production (W): Real-time solar generation power
  • Daily Energy Production (kWh): Daily solar energy generated

The Neurio API provides generationPower and generationEnergy fields. This change extracts these values from the existing API responses without additional API calls.

Proposed change

I use the Neurio Energy Monitor to monitor usage in my home. I have solar panels and wanted to see the generation values reflected in the sensor. Happily, that information is already in the API response but wasn't being used in the current implementation. So, I added 2 sensors to reflect the energy produced to match the existing consumption sensors.

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

Checklist

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link
Copy Markdown
Contributor

@home-assistant home-assistant Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @W7RZL,

When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).

The commits that are missing a linked GitHub account are the following:

Unfortunately, we are unable to accept this pull request until this situation is corrected.

Here are your options:

  1. If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

  2. If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

    • If you only made a single commit you should be able to run
      git commit --amend --author="Author Name <email@address.com>"
      
      (substituting "Author Name" and "email@address.com" for your actual information) to set the authorship information.
    • If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
      1. You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
      2. You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
    • Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.

Thanks, I look forward to checking this PR again soon! ❤️

@home-assistant home-assistant Bot marked this pull request as draft December 21, 2025 02:04
@home-assistant
Copy link
Copy Markdown
Contributor

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.

Add two new sensors for solar/generation monitoring:
- Energy Production (W): Real-time solar generation power
- Daily Energy Production (kWh): Daily solar energy generated

The Neurio API provides generationPower and generationEnergy fields.
This change extracts these values from the existing API responses
without additional API calls.
@W7RZL W7RZL force-pushed the neurio-energy-add-solar-production branch from 9744be5 to 74c566a Compare December 21, 2025 02:08
Copy link
Copy Markdown
Contributor

@home-assistant home-assistant Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @W7RZL

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!

W7RZL added a commit to W7RZL/home-assistant.io that referenced this pull request Dec 21, 2025
Add documentation for the two new production sensors:
- Energy Production (W)
- Daily Energy Production (kWh)

Companion to home-assistant/core#159533
@W7RZL W7RZL marked this pull request as ready for review December 21, 2025 02:40
@home-assistant home-assistant Bot dismissed stale reviews from themself December 21, 2025 02:40

Stale

W7RZL added a commit to W7RZL/home-assistant.io that referenced this pull request Dec 21, 2025
Add documentation for the two new production sensors:
- Energy Production (W)
- Daily Energy Production (kWh)

Companion to home-assistant/core#159533
Copy link
Copy Markdown
Member

@joostlek joostlek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks okay, there are some things that could be improved here.

It would be really cool if you'd be able to help with getting this integration modernized and for example configurable via the UI. So feel free to send me a message on discord if you're interested :)

@joostlek joostlek merged commit 85311e3 into home-assistant:dev Dec 23, 2025
31 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Dec 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants