Homekit showing wrong state for roller shutter on Shelly 2.5

[victor-vz]

I am using a Shelly 2.5 in roller shutter mode and got it connected via Home Assistant Homekit Controller/Bridge and exposed back to the Home App.

Since a week my Roller Shutter shows wrong states. Either it say opening for multiple hours or shows open in Homekit/HA even though it got closed via an Automation.

I am on the latest firmware on everything and unsure if this is a buck in the Shelly Software or in HA.

[victor-vz]

Rebooting the Shelly fixes the issue momentarily.

Version:2.12.1
Build:
20240623-075101/2.12.1-g417cbdf

[github-actions]

This issue is stale because it has been open 3 weeks with no activity. Comment or this will be closed in 1 week.

[gmuth]

I have a similar problem. Position (0-100) does not reflect the actual physical state. Usually the shutter get's 'stuck' opened. The state says 0 while the shutter is completely open. Closing requests are rejected or ignored. I guess because it thinks it's already closed. (20240912-181946/2.12.2-gfff6707)
Workaround: calibrate again.

Position 100 (really is closed) - pressing "Open" via Webinterface:

46521710704 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46522635486 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46523758930 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46524782587 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46525806113 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46526729657 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46527735266 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46528754773 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46528898839 shelly_main.cpp:477     Up 46528.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46529776525 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46530795854 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46531815365 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46532835195 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46533855237 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46534877925 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46535897657 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46536899038 shelly_main.cpp:477     Up 46536.89, HAP 0/1/12 ns 1, RAM: 26892/19448; st 36; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46536916637 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46537935523 mg_rpc.c:311            Shelly.GetInfoExt via WS_in 192.168.2.154:58684
46544898335 shelly_main.cpp:477     Up 46544.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 36; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46552898132 shelly_main.cpp:477     Up 46552.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46560898296 shelly_main.cpp:477     Up 46560.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46568898699 shelly_main.cpp:477     Up 46568.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46576898337 shelly_main.cpp:477     Up 46576.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46584898288 shelly_main.cpp:477     Up 46584.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46592898370 shelly_main.cpp:477     Up 46592.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 35; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46600898415 shelly_main.cpp:477     Up 46600.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46608898418 shelly_main.cpp:477     Up 46608.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46616898497 shelly_main.cpp:477     Up 46616.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46624898398 shelly_main.cpp:477     Up 46624.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46632898292 shelly_main.cpp:477     Up 46632.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46640898374 shelly_main.cpp:477     Up 46640.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46648898480 shelly_main.cpp:477     Up 46648.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2
46656898236 shelly_main.cpp:477     Up 46656.88, HAP 0/1/12 ns 1, RAM: 26892/19448; st 34; 4.1: c:1 mp:109.79 ip:5.00 mt_ms:23890 cp:100.00 tp:100.00 md:0 lmd:2

[markirb]

Thanks for posting. I think this is a duplicate of #1420

lets continue there. I tried to push a firmware there which might fix it