-
Notifications
You must be signed in to change notification settings - Fork 132
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
Shelly 2.5 Roller Shutter Calibration - Time until movement #324
Comments
Do you need any more information on this issue? #248 seems to be very similar and I'm not alone with this. |
@pivale can you offer any assistance ? |
@rojer , is there anyway we can give a min time for calibration higher to accommodate this situation? Actually I think it's something "bigger" and firmware should still keep power for a couple of seconds even if power consumption is 0... It would solve other problems and power fluctuation... (although not for calibration) I don't see a drawback with this, since motors need to have auto stop anyway for calibration to work, so no strain on motors should happen |
In my opinion and experience with my roller shutter motor 2-3 seconds will be enough. |
i increased it to 5 seconds by default, please install 2.8.0-alpha4 and help test |
This issue has now been closed, as no update was provided after it was marked stale. Feel free to provide updates to reopen this issue. |
Hi All!
I have an issue not with the roller shutter calibration itself, but especially with my motor.
My roller motor takes 1-2 seconds until it really works and starts to move the shutters. I believe it is some kind of motor protection.
This has the effect, that the shelly instantly stops when pressing UP/DOWN after the calibration.
I think it will solve this (special) issue, if the shelly waits a little more time for the power measurement.
BTW: This seems to be an issue with the stock firmware as well. There I cannot calibrate the shutter successfully.
Thank you!
Maybe similar to #248?
The text was updated successfully, but these errors were encountered: