-
Notifications
You must be signed in to change notification settings - Fork 89
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
All available streams created as default #36
Comments
Great idea. I'll do this. |
May i ask what is the status of this feature request? Thanks |
I can't find a way to figure out the available streams. If I could find the available streams then I could add this. I'll do more digging today on this. |
Looks like I can use |
This is now released in https://github.com/rroller/dahua/releases/tag/0.9.29 All streams are released by default. Please let me know if you have any issues. |
Current setup:
When adding a camera you have to choose what stream you want (main, sub, both).
My camera has 2 sub streams, and the 2nd has other resolution options then the 1st, so I use them both for diffrent scenarios.
2 problems:
A. The 2nd Substream is not available at all (for other cams maybe even 4 streams?).
B. When changing/adding a scenario, I have to remove/re-add the camera to enable or disable (sub)streams.
Possible solution
Allways create all available streams as entity.
Correct me if i'm wrong, but as long you just make a stream available in the config this will not cost any extra overhead as long it is not used in streaming?
For streams that have no activity, those can be created as DISabled entities automaticly when cam is added.
Or...
Show all possible streams as option to user to enable/disable when cam added (as select list/tick boxes), and create entities as disabled when not tagged by user.
Whatever option is choosen, at least create all cam streams as entitie so they can be enabled/disabled with a click of the mouse.
I've seen other Integrations create some disabled entities by default. So should be possible.
And for trigger entities the same request (see issue #38 ), so this whole integration works the same for streams as entity triggers.
My Substream options config screenprint
Regards, The Duke.
The text was updated successfully, but these errors were encountered: