-
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
Error calling service dahua/vto_open_door: Bad request 400 #154
Comments
I have this also |
Same here with a VTO2101E-P-S1 |
Same issue, any news ? |
Hi @rroller, did you solve this problem? |
Hi think I found the issue. The GET request should not contain the UserId parameter. |
+1 |
+1 |
Hi, can confirm same issue on a DHI-VTO2201F-P Firmware: 4.500.0000001.0.R,build:2021-07-13. @rroller thank you very much for the great work, form me the integration works great apart this, since this issue has been opened long time ago, is there any chance that will be fixed? As soon as possible I will try the suggested solution provide by @Suxsem and let you know |
After some experiments, unfortunately the work around suggested by @Suxsem didn't work, anyway I have additional info. The VTO manage two contacts , one for cars and one for pedestrians. When I call the service with DoorID = 1, the first gate opens, but 404 is raised. |
+1 |
+1 any updates regarding this issue? |
I have the same issue, any news about this? |
same error with a vto221g-WP |
Version of the custom_component
0.5.0 from latest release
Configuration
I'm using an VTO2202F-P-S2, that's my configuration:

HA integration is added through GUI.
configuration.yaml:
Describe the bug
It's about the button to open the door (
dahua_vto_open_door_btn
akaHaustür öffnen
). Clicking this button sometimes (and sometimes not, I can't see any pattern) throws this error. The service is still called and the door is opened, but HA throws this error. Sometimes there's a voice feedback from the VTO, sometimes not. Sometimes the voice feedback is repeated multiple times (by now three times maximum). It's a very weird behavior.I'd really like to give you a more precise description but I really can't see any pattern for this behavior.
I already reduced the "recognition time" in the VTO configuration (from default 15 seconds to 1 second) but still no change.
Debug log
The text was updated successfully, but these errors were encountered: