shelly-homekit icon indicating copy to clipboard operation
shelly-homekit copied to clipboard

Rollershutter with Shelly 2.5 on big Window (2x2m) fails to calibrate correctly

Open Joumann opened this issue 2 years ago • 18 comments

I Installed 10 Shelly 2.5 with Homekit FW and had no issues at all with calibrating, or use. In fact, 8 Windows Size 1,3x1,3m and 2 Windows Size 1,8x1,3m.

Just my 2x2m Window with an even stronger motor stops in half while calibrating with the Homekit Firmware and does noch react at all. I swapped shellys around to check if this one failed, but no change. Also with the standard shelly Firmware everything works fine with no issue at all. I guess it is about the power consumption, or the extended time the roller shutter takes to shut the 2m down.

Anyhow, just tried it again and I need to revert to the original shelly firmware again.

Maybe anyone has a "walkaround" how I could implement the big one as well to Homekit.

Thanks in advance for any helpful support!

Joumann avatar May 02 '22 15:05 Joumann

Please test it with 2.11 beta, see #868 for how to do. We have changed the calibration parameters there.

timoschilling avatar May 02 '22 20:05 timoschilling

I tested 2.10 stable and 2.11 beta3 on my shelly2.5 in roller shutter mode, and I have a similar issue. I try to calibrate it and it just doesn't calibrate, the relay seems to go into an on/off infinite loop. I can't get it to open or close properly from the web interface. I also tried flipping the motor wires to see if the the calibration sequence only worked with the wires in a certain order, which didn't change anything. I also tried switching the output directions in both configs, it also did nothing to fix the issue.

The shelly2.5 does work fine with the default firmware although and the curtain motor works fine with my aeotec mini roller shutter controller for z-wave. The curtain motor is a Dooya KT82TS-1.2/14 from 2016.

Motor stats: 1.2Nm , 14cm/s, 50/60hz , 110-240V, 10W, 0.12A

theontho avatar May 12 '22 04:05 theontho

Here is a log. My guess because average power is 3W, because your moving curtains horizontally, and your software is expecting much higher numbers, that it gets stuck in a loop. Is there a way to set power thresholds for calibration?

"movement time: 1.088 s, avg power: 3 W"

calibration_loop_log.TXT

theontho avatar May 12 '22 04:05 theontho

@rojer can you help?

timoschilling avatar May 12 '22 05:05 timoschilling

I had what looks like the same problem with my window.

Looking at your log file, it appears that either the roller shutter was completely open when you calibrated (you should close it) or you should swap the outputs in the settings. I say this because for the open calibration the motor is drawing zero power for the first five seconds:

362131390 shelly_output.cpp:63    Output 1: off -> on (precal0)
362137471 shelly_hap_window_c:326 WC 1: State: precal0 -> cal0 (10 -> 11)
362473201 shelly_hap_window_c:463 WC 1: P0 = 0.000
363273450 shelly_hap_window_c:463 WC 1: P0 = 1.012
364073091 shelly_hap_window_c:463 WC 1: P0 = 0.000
364873293 shelly_hap_window_c:463 WC 1: P0 = 1.195
365673133 shelly_hap_window_c:463 WC 1: P0 = 0.000
366473104 shelly_hap_window_c:463 WC 1: P0 = 0.000
367173833 shelly_output.cpp:63    Output 1: on -> off (cal0)

And I think the next problem is exactly as you said: the threshold for idle motor detection is 5W which is too high for your motor which seems to pull about 3W: https://github.com/mongoose-os-apps/shelly-homekit/blob/8d0f98d5a6d672f34b0b77f5847cda22546e6751/mos.yml#L78

You should change that wc.idle_power_thr setting to something like 2.0 for your motor. I'm not sure how to do that without altering mos.yml and reflashing like I did. There must be a way though?

jonnylamb avatar May 23 '22 22:05 jonnylamb

I have the same problem see my request for help #1041 Thank you for your help

ghost avatar Jul 23 '22 10:07 ghost

why close my request #1041 I know this is probably the same problem as request #985 but for now no one has given the solution.

Can you help us?

ghost avatar Jul 23 '22 13:07 ghost

will there be a solution or should we give up and find another system to manage the bay windows? Thanks a lot

ghost avatar Jul 24 '22 02:07 ghost

Hello

is there anyone to solve this problem?

there is a new shelly, the shelly plus 2PM suitable for rolling shutters. This may be the solution to our problem but unfortunately it is not yet possible to switch it to Homekit.

thank you.

ghost avatar Aug 11 '22 17:08 ghost

I get my Shelly Plus 2 PM today, so maybe support will come in the next weeks

timoschilling avatar Aug 12 '22 20:08 timoschilling

thank you timoshilling

Can you let me know when you have flashed it homekit?

ghost avatar Aug 12 '22 20:08 ghost

Simply subscribe on #1013, I will push a prerelease version there

timoschilling avatar Aug 13 '22 10:08 timoschilling

thank you timoshilling

ghost avatar Aug 13 '22 13:08 ghost

Hello, always the same problem for me despite the installation of the last update 2.11.2, is it possible to help me? Thanks in advance

ghost avatar Sep 05 '22 17:09 ghost

Hello, is it possible to create an update that solves this problem? If not, what solution is there? Thanks in advance

ghost avatar Sep 12 '22 09:09 ghost

Same problem here. It is the only window that gives me problems, the biggest one I have. Every so often I have it stops working, I have to disconnect and reconnect everything and even then I have a hard time configuring it because it restarts every so often. I have changed the Shelly and I have put another new one (already 3) and the same thing happens to it, I have come to the conclusion that it is because of the size of the window.

TheMecha avatar Mar 13 '23 10:03 TheMecha

Solution is here!!! Just bought one of the new eltako ESB62NP-IP/110-240V, which have been made for Apple Homekit native integration. Just replaced the shelly 2.5 with it and it works instantly via HomeKit!!!!

I was waiting for this my entire life! (Maybe a bit to overwhelming...) But anyways, it just works - simple, quick and easy!!! image

Joumann avatar Mar 22 '23 13:03 Joumann

Did you fix it ? I'm having almost if not the same issue. It gives me either implausible_power_consumption_in_close_dir after unsuccessful calibration or too_few_steps....

grimmaldus avatar Apr 01 '23 15:04 grimmaldus