-
Notifications
You must be signed in to change notification settings - Fork 71
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
Events not triggered if too many are selected #171
Comments
You could try what is suggested in this thread by tweaking the client.py file. I have done it and although it has not fixed my issues, it doesn't appear to of broken anything either so may well work in normal circumstances. |
@mooton85 Thank you for the suggestion, I applied the same change to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a IPC-5442T-ZE camera and I noticed that some events are never triggered in home assistant (listening for
dahua_event_received
), for example theParkingDetection
event. The camera is running the latest available firmware.After a bit of testing with my camera's event stream in
/cgi-bin/eventManager.cgi
what I noticed is that when the list of events specified incodes[]
is too long, the camera's firmware will simply trim it and only trigger some of the events (it seems to trim at around 100 chars).For example this works to trigger
ParkingDetection
:/cgi-bin/eventManager.cgi?action=attach&codes=[VideoMotion,CrossLineDetection,VideoBlind,CrossRegionDetection,SmartMotionHuman,ParkingDetection,SmartMotionVehicle]&heartbeat=5
while this doesn't work:
/cgi-bin/eventManager.cgi?action=attach&codes=[VideoMotion,CrossLineDetection,VideoBlind,CrossRegionDetection,SmartMotionHuman,SmartMotionVehicle,ParkingDetection]&heartbeat=5
I think it would be better to always listen for
codes=[All]
in client.py instead of using a specified list of events or at least give users the option to selectAll
as one of the options when defining the list of events for the plug-in.The text was updated successfully, but these errors were encountered: