-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
Fix onvif sensor detection and onvif stop service call #41949
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple additional comments. I don't have any cameras that don't support pullpoint subscriptions, so an integration like this is very hard to test. I am actually about to put up a PR that refactors the ONVIF integration to use zeep[async]==4.0.0
, which replaces the aiohttp async lib. There is already a PR in the upstream library for it as well.
I'll reference this PR in the one I create, but I think I've got a slightly better approach to solving this problem. Would you mind if we waited for that and rebased this PR once it is merged?
Hi @hunterjm, I reply directly on your comments. For me, is not a problem to wait the merge of the other PR and check how much of this becomes unnecessary. |
@Rihan9 - ok, the other PR is now merged. It should hopefully no longer be required to change anything in the device capabilities call. Feel free to rebase off of dev (or open another PR, whichever you are more comfortable with) so we can include your PTZ and Event implementations. Let me know if the new method of PullPoint support detection works for your devices! |
Hi @hunterjm, I managed to do a rebase. I re-added the changes on the stop service call and add the new parser, but i still need to reformat the PullMessages call and remove the SetSynchronizationPoint call, otherwise my cam still can't work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one more change, then this looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more rebase off of upstream dev should fix broken tests, then I'll merge.
…RuleEngine/MotionRegionDetector/Motion
Breaking change
Proposed change
Fix the stop service call, added the Zoom and PanTilt parameters because some cameras required them.
Fix the way how home assistant detect available sensors on camera. Comment out SetSynchronizationPoint because is not always available and correct PullMessages service call. Also add rule for topic: "tns1:RuleEngine/MotionRegionDetector/Motion" and change the name of the sensor to more generic ones.
Type of change
Example entry for
configuration.yaml
:# Example configuration.yaml
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: