-
Notifications
You must be signed in to change notification settings - Fork 13
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
Periodic error 400 "while setting the Motion schedule". #4
Comments
Hi, today I switched on debuging and now get a bit more logging: I checked in the app and there does not seem to be a schedule for motion detection there, either. Hm. |
I am going to rewrite the whole Adapter because the Doorbird-Developerteam is not very helpful with their support regarding changes and bugs of the API. 😞 |
I also received the error, my problem was / my solution is: I had an own HTTP API call registered. When I went into the app to see the schedule "Administration => schedule for doorbell" in the upper left corner you have to switch to "HTTP calls" there I realized, that trying to set a schedule it told me "blocked by ... (my own http call)" It seems that all HTTP calls have one schedule. I deleted my own http call and the error is gone. And the adapter works great now. |
I get this error periodically and after start of the adapter:
'doorbird.0 | 2018-11-28 22:12:16.323 | error | null (Statuscode: 400)
doorbird.0 | 2018-11-28 22:12:16.322 | error | There was an Error while setting the Motion schedule.'
Not sure what that means. I have a DoorBird D2101V and everything else seems to work ok. But motion snapshots do not work, either. In the doorbird app I have motion detection disabled (cloud recording & push messages). Not sure if that is connected? I tried to enable it, but the error did stay.
The text was updated successfully, but these errors were encountered: