-
Notifications
You must be signed in to change notification settings - Fork 109
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
Partial Operation not working :/ #78
Comments
you probably need to put the number of seconds it takes your shutter to open/close in that section |
Thats a good point. I took the time it needs to go completely down and wrote 26 seconds into the settings. |
Can you try with 20%. Some slides go down much faster than they go up or vise versa. So maybe that coudl be an issue here, |
Thanks for your answer. Tested with 20% but it went down completely again :/ |
I have the same issue, partioal operation alwas operates the full close and open. It dosent matter wich operation time i set.
|
Hi, I'm interested in that too. Any progress in the meantime on how to do that? |
Hi, I think I found one of the problems. An example: Shutter A is fully opened in the morning an closed for 60% by scheduled operations lets say at 8:00. Shutter A should again be closed by scheduled operations for 60% at 13:00. Between 8:00 and 13:00 the shutter is operated manually. What happens? Lets say Shutter A is moved manually to position 40% between 8:00 and 12:00 --> At 13:00 nothing happens. You will find an error in the logfile Lets say Shutter A is moved manually to position 80% between 8:00 and 12:00 --> At 13:00 Shutter A is moved to positon 60%. Everything is fine Lets say Shutter A is not moved manually between 8:00 and 12:00 at all --> At 13:00 Shutter A is fully closed. I changed the code in my installation and the Problem is gone. I tried to created my first pull request. Hopefully it worked. Never done this before. |
Before making substantial changes to the code may I suggest reflecting each shutter position open/close% state in the web UI? This will help greatly with troubleshooting and understanding when and if the Pi-Somfy state does not correspond with reality. Currently it's very likely that there will be unpredictable results if the shutter is controlled manually outside Pi-Somfy because the code has no way of tracking manual movement. FWIW, I've got a 3 blinds and 2 shutters all running with Pi-Somfy and have found the best option is to put the manual controllers away somewhere safe for emergency use only and do everything either with schedules, scenes or manually on phones. I use Siri/Apple Home > Homebridge > MQTT > Pi-Somfy and it works flawlessly for open/close and partial states. |
@firewiremb and @rbswift, thanks for taking the time to reply. I think rbswift hits the point. Since the 433 MHz system is only unidirectional, you cannot find out the current position if it has been changed with a manual controller.
|
@rbswift and @stalakerob My message from yesterday is a response to the start message from xChr11s |
Hello guys, Thanks |
Hello together,
I installed everything today on my raspberry pi3 and could connect my somfy instantly.
The manual Operation is working fine so far.
I tested a bit around with the Scheduled Operations and figured out, that the shutter is either going completely down or up.
I tried setting 50%, but it went completely down. And the Scheduled operations aren't executed soemtimes ..
Any Idea to debug or fix this?
May I did something wrong? :/
btw. could anyone explain "Operation Time (Seconds)" at the Shutter section? Couldnt find any info about this :/
Kind regards
The text was updated successfully, but these errors were encountered: