Skip to content

Add a note that PG&E for Opower currently only works for old accounts #39761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Jun 29, 2025
Merged

Add a note that PG&E for Opower currently only works for old accounts #39761

merged 3 commits into from
Jun 29, 2025

Conversation

tronikos
Copy link
Member

@tronikos tronikos commented Jun 29, 2025 •
edited by coderabbitai bot
Loading

Proposed change

SSIA

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Updated the Opower integration documentation to clarify support limitations for Pacific Gas & Electric (PG&E) accounts, specifying it only supports accounts created before June 2025 that do not require multi-factor authentication.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Jun 29, 2025
@netlify Netlify
Copy link

netlify bot commented Jun 29, 2025 •
edited
Loading

✅ Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit c3bc36b
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/686103d2e18d750008bbd60e
😎 Deploy Preview https://deploy-preview-39761--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 29, 2025 •
edited
Loading

📝 Walkthrough

Walkthrough

The documentation for the Opower integration was updated to include a note specifying that only Pacific Gas & Electric (PG&E) accounts created before June 2025 without multi-factor authentication (MFA) are currently supported. No other changes were made.

Changes

File Change Summary
source/_integrations/opower.markdown Added a note clarifying account creation date and MFA limitations for PG&E in Opower docs.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot]
coderabbitai bot reviewed Jun 29, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
source/_integrations/opower.markdown (1)

52-54: Tighten wording & align with doc-style note format

Minor phrasing/formatting nit:

  1. “prior to” → “before” (concise).
  2. Prefix with Note: to match other admonitions.
  3. Keep MFA acronym expanded once for clarity.
-  > Currently only works for old PG&E accounts prior to June 2025 that don't require MFA
+  > **Note:** Currently only works with PG&E accounts created **before June 2025** that do not require multi-factor authentication (MFA).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between a40b921 and aece3ef.

📒 Files selected for processing (1)
  • source/_integrations/opower.markdown (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`source/_integrations/*`: Integration documentation must use the provided template structure and section order.

source/_integrations/*: Integration documentation must use the provided template structure and section order.

📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)

List of files the instruction was applied to:

  • source/_integrations/opower.markdown
🪛 LanguageTool
source/_integrations/opower.markdown

[style] ~53-~53: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...rently only works for old PG&E accounts prior to June 2025 that don't require MFA - Port...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

coderabbitai[bot]
coderabbitai bot reviewed Jun 29, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
source/_integrations/opower.markdown (1)

53-53: Minor wording tweak – consider dropping the hyphen in “multi-factor”

Internal docs elsewhere in Home Assistant tend to use “multifactor authentication (MFA)” (see auth.mfa_* references). Aligning here avoids style drift:

- that do not require multi-factor authentication (MFA).
+ that do not require multifactor authentication (MFA).

Feel free to ignore if there’s an established preference for the hyphen in this file.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between aece3ef and c3bc36b.

📒 Files selected for processing (1)
  • source/_integrations/opower.markdown (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`source/_integrations/*`: Integration documentation must use the provided template structure and section order.

source/_integrations/*: Integration documentation must use the provided template structure and section order.

📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)

List of files the instruction was applied to:

  • source/_integrations/opower.markdown
🪛 LanguageTool
source/_integrations/opower.markdown

[misspelling] ~53-~53: This word is normally spelled as one.
Context: ...before June 2025* that do not require multi-factor authentication (MFA). - Portland Genera...

(EN_COMPOUNDS_MULTI_FACTOR)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
🔇 Additional comments (1)
source/_integrations/opower.markdown (1)

52-54: Addition looks good – concise clarification for PG&E users

The note clearly communicates the current limitation and is placed in the right spot within the utilities list. No structural or formatting issues detected with the block-quote inside the list item.

@silamon silamon merged commit d484e27 into current Jun 29, 2025
9 checks passed
@silamon silamon deleted the tronikos-patch-3 branch June 29, 2025 12:22
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@silamon silamon silamon approved these changes

Assignees
No one assigned
Labels
current This PR goes into the current branch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

PG&E new authentication does not seem to work with opower can't login to OPOWER with PG&E
2 participants
@tronikos @silamon