-
Notifications
You must be signed in to change notification settings - Fork 85
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
[Bug] Camera feed should be from camera domain, not image domain #531
Comments
Same issue is present on P1 printers, only X1 sends video codec. |
Have you managed to find a workaround @marcinbauer85? I've came across some converters, but I did not have any luck to get it working. |
@honzis1364 unfortunately not. |
Same here, it would make everything much easier to have it as cammera and not as image :/ I have tried a lot of ways to change it, but did not find any workaroud. |
I think the image domain also leads to a LOT of unnecessary database usage since it refreshes every second and writes an entry: (created with the dbstats addon) |
I have the same frustrations with this in my A1 I’d like to bridge the camera to HomeKit but I can’t as it’s an image sensor not a camera |
I've added PR #595 to fix this. |
Resolving as completed with #595. |
Describe the bug
The current camera feed is using the image entity type, rather than camera which makes it difficult to publish via Homekit integration and use in other situations.
To Reproduce
Expected Behaviour
The camera feed should be from the camera domain, not image
What device are you using?
A1
Diagnostic Output
Log Extracts
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: