use shelly 2.5 roller shutter without calibration

[mattod0]

I'm trying to use the shelly 2.5 with a Velux KLF 050. The Velux KLF 050 is a remote for the Velux Solar roller shutter and provides inputs for the opening and closing.

when using the original firmware I can open and close the roller shutter by providing an opening/closing time of about 55 seconds.

Unfortunately it is not possible to use calibration because the KLF 050 won't consume any power unlike a roller shutter engine, so calibration will always fail.

With the homekit-firmware opening/closing is not possible - and i even cannot set the time taken for opening/closing.
and of course opening to 50% isn't possible too because of missing calibration.

without calibration the shelly cannot be used I understand.

Is it somehow possible to circumvent the calibration process and provide the needed data by setting some configuration manually like opening/closing time or calibration data?

[torto-85]

I have a similar problem. And would be happy about a solution for this.

[mattod0]

I changed the configuration to switch and enabled auto off.
so now I've got two accessories in the Home app for every shelly.
I can now open and close my roller shutter completely but will never see in what state the roller shutter is because both accessories will be off after closing or opening is finished.

so this is not a good solution but a least i can use full opening/closing in automations.

the original firmware allows to open, pause and close the roller shutter with my setup. maybe there is an option to not use the power consumption detection and use the provided simple open/close functions somehow?

[torto-85]

Hey,

I use the same configuration at the moment and that works okay. But what happens if someone (me :-) is pressing the two buttons the same time? Or press the UP-button while the shutter is still moving down. This could destroy the shutter.

I prefer if I could customize the movement time in shutter mode.

Cheers
Tom

[juangamnik]

I have a roller shutter which does not consume any power (on the motor inputs). So after calibration I have 1.09sec avg time (instead of 11.8sec what I measured with a stop watch). Could you (and would you) offer a „manual“ calibration, where a manually measured value(s) can be entered?

[juangamnik]

@rojer: if you give me a hint, where to do this, l would give my rusty C skills a chance... but at a first glance I do not find the right spot. The shelly.cpp in shelly2.5/ seems to be a configuration, only. In the main folder I did not find the code for roller-shutters...

...ok it is shelly_hap_window_covering.cpp where the roller-shutter code is situated and in index.html it is the component with id wc-config... correct? But still I am a bit lost 😞

[rojer]

if it does not consume any power, it won't work anyway... as power is used to determine limits of movement.

do i understand correctly that you have mechanism with two buttons that does its own movement and you want to control it with shelly 2.5? can you describe the setup in more detail?

[torto-85]

Hey @rojer,

I love your firmware... Thanks for your great work!!

Like juangamnik some people use a shutter which show no power consumption (in my case the shutters have their own physical switches and automatically stops in end positions controlled by the motor itself) or would like to use their shelly as master controller for two or more roller shutters.

Because calibration won‘t work in this case, It would be great to have at least two simple UP and DOWN buttons in homekit (maybe even without opening status). I know that this could be realized with „switch mode“ and „auto off“ but pressing both buttons the same time could destroy the shutter motor.

So I think it would be nice to add a function in „roller shutter modus“ where we can manually edit the movement time and have these two simple buttons where the UP button is deactivated while the shutter moves DOWN and vice versa. Like it‘s in the original shelly firmware.

What do you think?

Cheers
Tom

[juangamnik]

if it does not consume any power, it won't work anyway... as power is used to determine limits of movement.

in my case three motors are connected via a cutoff relais. So there is <1W consumption on the inputs. But each motor itself has an endpoint, so it shouldn’t be an issue to manually set the closing time and use the shutter in HomeKit... right?

[rojer]

the shutters have their own physical switches and automatically stops in end positions controlled by the motor itself

this is actually what our implementation expects. if you just connect the motor directly to shelly, without any external controller and buttons, this should work. is there any reason not to?

So I think it would be nice to add a function in „roller shutter modus“ where we can manually edit the movement time and have these two simple buttons where the UP button is deactivated while the shutter moves DOWN and vice versa. Like it‘s in the original shelly firmware.

yes, i see clear demand for this. need to think how to implement it.

[torto-85]

this is actually what our implementation expects. if you just connect the motor directly to shelly, without any external controller and buttons, this should work. is there any reason not to?

Yes, but if I use the shelly as "master controller" for five roller shutters so calibration won't work.

yes, i see clear demand for this. need to think how to implement it.

Great @rojer, I'm looking forward to it!!

[juangamnik]

in my case three motors are connected via a cutoff relais. So there is <1W consumption on the inputs. But each motor itself has an endpoint, so it shouldn’t be an issue to manually set the closing time and use the shutter in HomeKit... right?

This is a situation where setting the closing time would help isn‘t it? As I said before I would add this myself in a fork and start a pull request if you would be so kind to give me starting help how this could be done (I do not understand how the components (html frontend/backend) interact and therefore how to add this)

[Storkn]

I have the same problem.
I use my shelly 2.5 for a roof window and the calibration detects 1.05 sec instead of the real 41 sec :-(
The Motor has a auto stop so it's ok for me to set the time manually

[juangamnik]

So I forked the project and added an input field for setting the movement time move_time_ms. It sets the corresponding value in the backend in cfg_. I know that the value is stored since it is displayed in the calibration text Calibration: movement time: 12 s, avg power: 0W. But still opening and closing stops after about a second...

[juangamnik]

The corresponding log output:

7355834451 mg_rpc.c:305            Shelly.SetState via WS_in 192.168.178.20:60749
7355845976 shelly_hap_window_c:350 WC 1: Tgt pos 100.00 -> 0.00 (RPC)
7355878132 mg_rpc.c:305            Shelly.GetInfo via WS_in 192.168.178.20:60749
7355904874 shelly_hap_window_c:330 WC 1: State: idle -> move (0 -> 20)
7356002105 shelly_output.cpp:56    Output 2: off -> on (move)
7356013229 shelly_hap_window_c:330 WC 1: State: move -> rampup (20 -> 22)
7356102026 shelly_hap_window_c:552 P = 0.00 -> 0.00
7356112653 shelly_hap_window_c:330 WC 1: State: rampup -> moving (22 -> 23)
7356204466 shelly_hap_window_c:339 WC 1: Cur pos 100.00 -> 99.33, P = 0.00
7356741143 mg_rpc.c:305            Shelly.GetInfo via WS_in 192.168.178.20:60749
7356802869 shelly_hap_window_c:602 Moving to 0, p 0.00
7357004438 shelly_hap_window_c:339 WC 1: Cur pos 93.44 -> 92.60, P = 0.00
7357202936 shelly_output.cpp:56    Output 2: on -> off (moving)
7357215218 shelly_hap_window_c:330 WC 1: State: moving -> stop (23 -> 24)
7357326327 mgos_sys_config.c:232   Loading conf2.json
7357350972 mgos_sys_config.c:232   Loading conf3.json
7357487461 mgos_sys_config.c:174   Saved to conf9.json
7357499643 shelly_hap_window_c:330 WC 1: State: stop -> stopping (24 -> 25)
7357542234 shelly_hap_window_c:330 WC 1: State: stopping -> idle (25 -> 0)

[juangamnik]

OK I found the issue. When I set the roller shutter to 1% it works. Going back to 99% works either. But opening or closing completely uses the current (at 0W) for knowing when to stop...

So I think I have now everything I need to finish this. I will start a pull request afterwards.

[juangamnik]

I have noticed a new problem.
3: if I move up and down through the homekit percentage bar, very often the shelly keeps both the up and down outputs active!
This is a serious problem because the connected ECU sends me haywire!
Shouldn't this happen, in any case, isn't there a safety (as in automatic mode) that only one of the two outputs must be active at a time?
(In some shutters, if the control unit receives up and down at the same time, it is a limit switch setting mode ... a mess would come out ...)

Please take a look at my explanation here (we should not discuss on two threads). I really think you misunderstand this.

[juangamnik]

@rojer I think it is still too early to approve the change in the official firmware, because many like me will encounter the same problems and you will be inundated with avalanches of requests for help!

@rojer / @lucaspinelli85: could you figure out the issue of Luca in the main code base? It is not related to the minor changes in my fork, right? Can we merge the changes to master now? The issue of Luca should (IMHO) be handled in another issue as a separate (perhaps foundational) problem with the firmware.

[robim385]

Hi all. I have 6 rollers with Shelly 25 and 5 are working fine without any issues. 6th probably has broken limit on motor when shutter is opening while closing limit on motor is working fine. Without opening limit, I am not able to do automatic calibration.

@juangamnik do you think I might be able to use your FW and set everything up by using manual calibration?

[ludalex]

Completely unrelated question to the topic, apologies but I can't find anywhere else to ask... for you who connected a KLF 050 to a roller/shutter switch type: does it work such as:

• short button press: window/blind completely closes/opens?
• button logn press: window/blind keeps moving and stops when you stop pressing?

[nicx]

@rojer any news when this (great!) feature will find its way to your firmware? :)

[nicx]

basically I would also like other users need different times for opening and closing (which is in the original firmware also depositable), but now I have first tried as it is.
it works in principle, but I also have the problem that when opening the shutter stops at 99% in the UI ("idle pos 99 -> 100"). That is, in the Home app, the shutter also stops on "opening...". the closing, however, works perfectly.

what can I do to solve the 99% problem?

[nicx]

any hint to solve the 99% problem?

[MrMarcel24]

Hi everyone :),

I am happy, that I found a solution to integrate my Shelly 2.5 roller shutter into my HomeKit environment (THANK YOU SO MUCH @rojer). I am glad, that it works now even without measuring the power consumption. But I also encounter the 99% problem, but lack the skills to solve the problem 😅. I hope, there will be a solution. Again: Thank you for your work!

[davebacsi30]

Hy!
Please help! I can't upload this firmware switch25-2.11.0-alpha1 .
Work it today?

Thank You!

[davebacsi30]

I have 5 shelly 2.5 roller shutter. 1 work great movement time 52sec. 4 don't work movement time 5-7 sec with automatic calibration.

[dev2ek]

First of all, I would like to thank you for this great project 😊👍👍👍😊

@rojer are there any thoughts from you as to when this great feature can be integrated into the current firmware?

I am using the current version from your link:

http://rojer.me/files/shelly/misc/shelly25-449.zip

Unfortunately this version still has the 99% problem ☹

Thank you very much for your work!

[nicx]

any news to the 99% problem with this special firmware?

[gmuth]

This feature should also help when power metering of the shelly 2.5 is broken (e.g. due to aged capacitors).
Whatever the result of the auto calibration is should be configurable in a manual way.

[nicx]

just a short update: I switched to ESPhome, with this on my shelly 2.5 everything works great :)

[lucassite120]

FYI: I moved to HAA Homekit firmware. It has a lot of roller shutter extra features, and it works with new Plus devices too with OTA flash:
https://www.youtube.com/watch?v=06YHkRkwJE4