-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Shutterposition problem on newer versions #10033
Comments
Thread continues at #9906 |
Hi, I saw issue #9906 but as far as I understand it doesnt describes the same issue |
reorder stop to esure direct stop after command
I agree that there is an issue with the stop command. The 0,5sek was quite well observed. I fixed it and submitted an update. The reason for the delay is that you cannot change directly from up to down. there is 0.5sec minimum stop. But the delay was at the wrong position in the code |
I checked the duration of sending the stop until it actually stops. this is 0.2 sek or 4 TASMOTA cycles (50ms). There is a potential delay if the MQTT server responds slow. I try to find a way to avoid sending data to the MQTT before the relay is stopped to minimize time between stop command and the real stop. Anyhow currently the position is correctly calculated as far as I can see with the latest fix. |
@stefanbode Thanks for the fix, I was observing this behavior in #10112, too. I will check whether that issue there is eliminated as well. |
@stefanbode This change solved my problem, too. But there is one glitch left. I will make a new issue out of it, as it has nothing to do with this problem here. btw: Thanks for your great work with the shutters! The shelly implementation was pain in the ass (no updates while moving, no halfway-correction for german shutters, no shutter commands for a remote shelly-button switch (close/stop/open/stop) etc...) Glad that I switched over... |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
ISSUE 1: Iv'e used two new shelly 2.5 as a rollershutter controller with tasmota.
on versions 9.1.0 and 9.1.0.2 (newest dev) when I am opening the shutter to 30% and then to 80% the shutter opens to about 100cm. But, when I open it in stages - from 30 to 50 to 70 to 80 it opens much MORE (almost all the way - about 127cm).
then of course when I try to close the shutter again it wont close all the way because it thinks it is only opened to 80 while it is actually more than that.
To make sure nothing which I configured making that happen Iv'e re-flashed the device and didnt configured anything except than:
and it is still the same.
than I tried to flash version 8.5.0 and looks like it works just fine!
Note that the problem is that the shutter is opening more than it should and not less - therefore the problem is not motor delay
ISSUE 2: Another problem is that I get hardware watchdog restarts - even when I removed all the sensors from the device template.
Thanks.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
explained above
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
shold open to the same opsition +-
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: