rct
August 12, 2023, 11:34pm
42
@chintito4ever - Thanks for posting this. That’s interesting that you were able to change the authentication using a different browser/platform. I only tried Firefox on Windows and assumed it was something about my account.
Also, do you have just an electric meter, or do you also have a gas meter?
I’ve been unable to get the sensors with current usage to come up. I get an exception because the gas account doesn’t support hourly aggregation. Sebmaster (on Github), who added the ConEd support only has an electric meter, so it works for him.
blando
August 13, 2023, 1:23am
43
I’m getting both electric and gas data in the sensors. Note there are some related PRs pending for HA that address the different time resolution between electric and gas, etc.
home-assistant:dev
← tronikos:opower
opened 05:40AM - 05 Aug 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Some utilities provide a read resolution different than the one previously assumed. Previously code assumed for electricity the read resolution is at least hourly while for gas it's at least daily. Now respect the read resolution as returned by the API.
This depends on https://github.com/home-assistant/core/pull/98144 being merged first (its changes are included here).
This also depends on https://github.com/home-assistant/core/pull/98141 being merged first (its changes are included here).
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] 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
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #97814, fixes #97924
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] 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][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] 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`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
That is scheduled to be in 2023.8.3 on 8/17.
rct
August 14, 2023, 6:47pm
44
I found the bug that was causing the electricity forecast data not to be populated, which kept the sensors from showing up.
So now I have sensor.current_bill_electric_*
and sensor.typical_monthly_electric_*
I’m not seeing a forecast response for the gas meter/account. If @blando is getting gas sensors, I’ll have to dig into it a bit more.
Also, I’ve yet to see my consumptions sensors actually update without me reloading the integration or restarting Home Assistant.
Currently I only have electric meter with ConEd, my gas utility company is different.
yeah I’m also seeing similar behavior. It only updates if I manually restart Home Assistant.
rct
August 14, 2023, 10:15pm
46
Ok thanks. Since I know it’s not just me, I’ll try to dig into it and see what I can find.
I’m using this for increased logging, but I’ve also had to edit the opower module’s opower.py
to see the responses. The scattered logging selectors is an attempt to catch the changing component names depending on how the component/integration got loaded.
logger:
default: warning
logs:
custom_components.opower: debug
homeassistant.components.opower: debug
opower: debug
opower.py: debug
blando
August 15, 2023, 5:25am
47
This is what I’m presently seeing:
ncd
January 5, 2024, 4:08pm
48
I have the officially supported version and I’m experiencing the same issue. It stops updating and if I do not restart home assistant or reload the integration within about 24 hours it starts showing 0. Seems really broken .
1 Like