home-assistant[bot]
commented
21 hours ago Hey there @tkdrob, mind taking a look at this issue as it has been labeled with an integration (skybell) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `skybell` 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 skybell` 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)
skybell documentation skybell source (message by IssueLinks)
The problem
I know I've seen an issue or two pointing to feature request, but Skybell recently pushed an update that has migrated all instances from the old app on to the new one. This means that the current integration is essentially useless and is no longer working.
It seems as though there is an API out there for the new app (https://www.reddit.com/r/skybell/comments/1dij7t5/updated_api_available_before_june_30th_cutover/). But I understand this would take some work to get done.
What version of Home Assistant Core has the issue?
core-2024.9.2
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
skybell
Link to integration documentation on our website
https://www.home-assistant.io/integrations/skybell/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response