Skip to content
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.

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

Pushover - can't revise API key for an entry once it is created #139026

Open
cdl86 opened this issue Feb 22, 2025 · 1 comment
Open

Pushover - can't revise API key for an entry once it is created #139026

cdl86 opened this issue Feb 22, 2025 · 1 comment

Comments

@cdl86
Copy link

cdl86 commented Feb 22, 2025

The problem

Hi,

Under the 3-dot menus of existing "integration entries", there's no option to edit their API key or user key.

Image

Image

I recently created a new "Application" within my Pushover account. I called it "CCTV". That way, I can filter my Pushover notifications on my web/phone client and see just my camera image notifications, for example. It also allows for different notification settings.

However, the only way to use this new Application's API key in the integration is to create a new entry ("Add entry") which brings up this dialog:

Image

But if I add a new one, I would have to go into all of my notification automations and replace the integration entity with the newly created one.

It would be easier if we could instead just freely edit the API key any time after creation. Can we get the same dialog options as in the "add entry" (API key, user key)?

Furthermore, it seems like if I use the "rename" option in the 3-dot menu, that new name isn't reflected in automations when trying to choose the entry.

Thank you

What version of Home Assistant Core has the issue?

2025.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Pushover

Link to integration documentation on our website

https://www.home-assistant.io/integrations/pushover/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

Hey there @engrbm87, mind taking a look at this issue as it has been labeled with an integration (pushover) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of pushover can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign pushover Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


pushover documentation
pushover source
(message by IssueLinks)

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

No branches or pull requests

1 participant