generated from ludeeus/integration_blueprint
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Add selector to choose between image and camera entities? #676
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bumping to keep open. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Although this is very similar to #608, I'm opening this issue to discuss whether it would be possible to add a selector to control whether
image
orcamera
components are visible in Home Assistant.The main reason for this suggestion is that the
image
entity type does not currently have feature parody with thecamera
component. Specifically:image
entity. A thoughtful community member submitted a Pull Request to the HA core, so hopefully this will be added soon, but for now the PR is a draft and so usingimage
components makes custom automations trickier.binary_sensor
to thecamera
integration and get automatic notifications the way you can withcamera
. In fact, you can't see snapshots from Frigate within HomeKit at all since there's no support forimage
entities.Proposed Change
Because of these issues, I'm wondering if it would be possible to add a toggle to select between exposing
image
andcamera
components to Home Assistant. This would allow existing features to work while still allowing users who want the advantages of theimage
component to migrate to it when they are ready (in fact,image
could be default if that is preferable). Aside from the above-mentioned issues, some other custom integrations may be relying on acamera
entity and this would allow interoperability with them as well.Alternatives
One alternative is just to bring
image
in feature-parody withcamera
. Work here is ongoing, but it's not just the Home Assistant core that would need to be worked on - built-in integrations like HomeKit as well as any custom integrations would need to be updated too.The text was updated successfully, but these errors were encountered: