Shelly 1 No HomeKit Connection Update 2.81

[SteffenHuettner]

All Shelly 1 lost HomeKit Connection after flashing to 1.82. All Shelly 2.5 still work fine. The Shellys are still running and reachable by ip.

[rojer]

@partytrik the log shows a device under memory pressure, unable to allocate memory (E:M nnn messages). there's very little free RAM (under 10K), less than i would expect with 10 active connections... i see it's been up for a while, can you reboot it and start log earlier?

[rojer]

as for allowing more connections - as you can see, we can barely handle 12.

[partytrik]

as for allowing more connections - as you can see, we can barely handle 12.

OK, I see. Maybe less does the trick then? Although in 2.7.3 with also already 12 I did not have these problems.

[partytrik]

@partytrik the log shows a device under memory pressure, unable to allocate memory (E:M nnn messages). there's very little free RAM (under 10K), less than i would expect with 10 active connections... i see it's been up for a while, can you reboot it and start log earlier?

Well, it's not even been a day, but here is another one. I keep closing and launching the home app on the iPhone and keep changing rooms to force a reload of the respective shelly and I keep pressing the respective shelly, but it doesn't show any reaction, neither in the app, nor in the log. In the app it just says "no response". It doesn't seem to connect, even though there are not even 12 connections active. Changing the status with the home app on the computer, also didn't force a connection. So actually it just shows as unresponsve without even trying to update the respective light in the home app. Maybe there is a problem in there?

And!! what also happens is that at some point the shellys do show connected, but I caught this device yesterday showing an "off status" (without a ! in the corner or red text), when the light was actually turned on.

I do have this same problem with half of the shellys, sometimes. not always the same. Usually it's an entire room that is gone (oddly). And then when they do get responsive again, the status is shown in red (off/on) with the same ! in the upper right corner that you get with the "no response" message.

Here's the log:

234519398 shelly_debug.cpp:227 No log file, sending new entries 235271524 mg_rpc.c:305 Shelly.GetInfo via WS_in 192.168.1.4:52153 236523356 mg_rpc.c:305 Shelly.GetInfo via WS_in 192.168.1.4:52153 236992072 shelly_main.cpp:560 Up 236.98, HAP 0/12/12 ns 12, RAM: 19228/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 237271997 mg_rpc.c:305 Shelly.GetInfo via WS_in 192.168.1.4:52153 238274401 mg_rpc.c:305 Shelly.GetInfo via WS_in 192.168.1.4:52153 239273883 mg_rpc.c:305 Shelly.GetInfo via WS_in 192.168.1.4:52153 244991665 shelly_main.cpp:560 Up 244.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 252992210 shelly_main.cpp:560 Up 252.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 260991806 shelly_main.cpp:560 Up 260.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 268991609 shelly_main.cpp:560 Up 268.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 276991548 shelly_main.cpp:560 Up 276.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 284991481 shelly_main.cpp:560 Up 284.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 292991636 shelly_main.cpp:560 Up 292.98, HAP 0/12/12 ns 12, RAM: 19836/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 300991540 shelly_main.cpp:560 Up 300.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 308991572 shelly_main.cpp:560 Up 308.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 316991465 shelly_main.cpp:560 Up 316.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 324993170 shelly_main.cpp:560 Up 324.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 332991603 shelly_main.cpp:560 Up 332.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 340991918 shelly_main.cpp:560 Up 340.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 348991522 shelly_main.cpp:560 Up 348.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 356991499 shelly_main.cpp:560 Up 356.98, HAP 0/12/12 ns 12, RAM: 19668/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 360383752 HAPPlatformTCPStrea:105 0x3fff6d14 192.168.1.39:49585 HAP connection closed, ns 0/12/12 i 2 360391817 HAPPlatformTCPStrea:303 HAPPlatformTCPStreamClose ts 0x3fff614c nc 0x0 0/11/12 364991673 shelly_main.cpp:560 Up 364.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 372991525 shelly_main.cpp:560 Up 372.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 380991630 shelly_main.cpp:560 Up 380.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 388991989 shelly_main.cpp:560 Up 388.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 396991662 shelly_main.cpp:560 Up 396.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 404991628 shelly_main.cpp:560 Up 404.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 412991792 shelly_main.cpp:560 Up 412.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 420991839 shelly_main.cpp:560 Up 420.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 428991892 shelly_main.cpp:560 Up 428.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 436991716 shelly_main.cpp:560 Up 436.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 444991987 shelly_main.cpp:560 Up 444.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 452991665 shelly_main.cpp:560 Up 452.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 460992602 shelly_main.cpp:560 Up 460.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 468991528 shelly_main.cpp:560 Up 468.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 476991642 shelly_main.cpp:560 Up 476.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 484991652 shelly_main.cpp:560 Up 484.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 492991743 shelly_main.cpp:560 Up 492.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 500991853 shelly_main.cpp:560 Up 500.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 508991585 shelly_main.cpp:560 Up 508.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 516991706 shelly_main.cpp:560 Up 516.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 524991523 shelly_main.cpp:560 Up 524.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 532991646 shelly_main.cpp:560 Up 532.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 540991977 shelly_main.cpp:560 Up 540.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 548994842 shelly_main.cpp:560 Up 548.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 556991788 shelly_main.cpp:560 Up 556.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 564991614 shelly_main.cpp:560 Up 564.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 572991666 shelly_main.cpp:560 Up 572.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 580991677 shelly_main.cpp:560 Up 580.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 588991734 shelly_main.cpp:560 Up 588.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 596991547 shelly_main.cpp:560 Up 596.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 604991615 shelly_main.cpp:560 Up 604.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 612991952 shelly_main.cpp:560 Up 612.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 620991533 shelly_main.cpp:560 Up 620.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 628991650 shelly_main.cpp:560 Up 628.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 636991634 shelly_main.cpp:560 Up 636.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 644992343 shelly_main.cpp:560 Up 644.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 652991555 shelly_main.cpp:560 Up 652.98, HAP 0/11/12 ns 11, RAM: 19936/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 660991619 shelly_main.cpp:560 Up 660.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 668991772 shelly_main.cpp:560 Up 668.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 676991964 shelly_main.cpp:560 Up 676.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 684991988 shelly_main.cpp:560 Up 684.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 692992033 shelly_main.cpp:560 Up 692.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 700991952 shelly_main.cpp:560 Up 700.98, HAP 0/11/12 ns 11, RAM: 20068/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 708991798 shelly_main.cpp:560 Up 708.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 716991765 shelly_main.cpp:560 Up 716.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 724991587 shelly_main.cpp:560 Up 724.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 732991544 shelly_main.cpp:560 Up 732.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 740991612 shelly_main.cpp:560 Up 740.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 748991609 shelly_main.cpp:560 Up 748.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 756991735 shelly_main.cpp:560 Up 756.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 764991690 shelly_main.cpp:560 Up 764.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 772993263 shelly_main.cpp:560 Up 772.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 780991510 shelly_main.cpp:560 Up 780.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 788991610 shelly_main.cpp:560 Up 788.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 795508126 shelly_output.cpp:58 Output 1: on -> off (HAP) 797004794 mgos_sys_config.c:232 Loading conf2.json 797024850 mgos_sys_config.c:232 Loading conf3.json 797151290 mgos_sys_config.c:174 Saved to conf9.json 797164469 shelly_main.cpp:560 Up 797.15, HAP 0/11/12 ns 11, RAM: 20004/38552; st 0; 0.1: st:0 in_st:0 inm:1 ininv:0 799676342 shelly_output.cpp:58 Output 1: off -> on (HAP) 805009591 mgos_sys_config.c:232 Loading conf2.json 805029653 mgos_sys_config.c:232 Loading conf3.json 805155290 mgos_sys_config.c:174 Saved to conf9.json 805168471 shelly_main.cpp:560 Up 805.16, HAP 0/11/12 ns 11, RAM: 19964/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 812991755 shelly_main.cpp:560 Up 812.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 820991600 shelly_main.cpp:560 Up 820.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 828991621 shelly_main.cpp:560 Up 828.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 836991681 shelly_main.cpp:560 Up 836.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0 844991652 shelly_main.cpp:560 Up 844.98, HAP 0/11/12 ns 11, RAM: 20300/38552; st 0; 0.1: st:1 in_st:0 inm:1 ininv:0

[seb74600]

https://github.com/mongoose-os-apps/shelly-homekit/issues/561

[chstoll]

Dear @rojer, after two days on 2.8.2. with 25 Shelly 1, we still have very bad homekit connection problems. That was not the case with 2.7.3. Whenever you open a room in the app all shellys start to "update" and sometimes all shellys in a room are unreachable while those in other rooms are normal.

Thats really strange. I had this issue with 2.7.3 (devices allways show update, had to switch rooms to show the status). With 2.8.2 for the first time all shellys are responsive and show their state directly by opening the room. This is the best version so far for me. I have 47 shellys (39 with rojers firmware - Shelly Plug S, Shelly 1, Shelly 2.5, the others are shelly dimmers with orignal firmware which work via homebridge). Actually I'm on iOS 14.5 beta 4 (Apple TV has tvOS 14.5 beta also).

[partytrik]

Dear @rojer, after two days on 2.8.2. with 25 Shelly 1, we still have very bad homekit connection problems. That was not the case with 2.7.3. Whenever you open a room in the app all shellys start to "update" and sometimes all shellys in a room are unreachable while those in other rooms are normal.

Thats really strange. I had this issue with 2.7.3 (devices allways show update, had to switch rooms to show the status). With 2.8.2 for the first time all shellys are responsive and show their state directly by opening the room. This is the best version so far for me. I have 47 shellys (39 with rojers firmware - Shelly Plug S, Shelly 1, Shelly 2.5, the others are shelly dimmers with orignal firmware which work via homebridge). Actually I'm on iOS 14.5 beta 4 (Apple TV has tvOS 14.5 beta also).

Well, my experience with 2.7.3 was that it happens sometimes and then in all the rooms and you could force devices to update by changing rooms or closing the app. Now, for me it’s occasionally ok, and most often one of the rooms doesn’t connect the shellies, while those in other rooms work. And then it’s partly not possible for 30min to connect to them, not forcing an “update”, then they do work, but show text in red and once I witnessed that one showed ok and as off, while the connected light was actually on.

edit: 30min not 3min

[partytrik]

@rojer, any idea regarding the above? What’s really new now is that sometimes the status of a Shelly is not displayed / updated correctly in the home app. So according to the app a light seems to be off, when in reality it’s on. I did never have that with any of the versions since 2.0

[rojer]

i need some more time to think about this and reproduce. there indeed have been changes between 2.7.3 and 2.8 that may have changed the behavior under extreme network pressure, need to think about it.

[partytrik]

i need some more time to think about this and reproduce. there indeed have been changes between 2.7.3 and 2.8 that may have changed the behavior under extreme network pressure, need to think about it.

OK, my brother and friends left now, so only but still 8 iPhones/iPads/macs + 4 home pods + 1 Apple TV left in the house. I will monitor it a little more, if something improves., before going back to 2.7.3.

Thank you very much

[Dag0d]

After 8 days of testing I can tell you from my side, that it works without any flaws in a high density and busy network with many Apple devices. Status is updated quick, response time is fast and no network connections are lost so far from any of my shellies.

[partytrik]

In general yes. Response and update time has been much faster since 2.7.3 already. Just that you keep it in mind: In my case some rooms do not update the status and then what you say is true for most rooms, but one or two don't update. They simply show as disconnected or status off. It now occurs almost daily that some hot water boilers that are put in a schedule are not activated in the morning. To me it almost feels like a flaw in the home app. Just that it occurred right after the update to 2.8. (bear in mind that I did not have the problems other's reported with 2.8.1, really weird). What's also absolutely new is that suddenly 3 Meross homekit plugs and a tado aircon thermostat I use become unresponsive from time to time (apart of these 3 plugs and 1 tado, there are no other non-shelly homekit accessories). So maybe it's a conflict with other homekit devices? I will monitor a few more days with now "only" 13 devices left and eventually go back to 2.7.3 to see if the problems vanish. I keep you posted. I am sorry that I caused you digging in a place where everything was running correctly.

[partytrik]

Edit: third paragraph included

Dear @rojer , so I have been testing and observing. Once the family left the house and there were less Apple devices looking for homekit connections, the situation improved a bit, but we have still major problems with 2.8.2:

The screenshots were taken from devices that I couldn't connect to with homekit for over 12 hours. When opening them in the web interface, you can see that in all of the devices the number of active connections was 0 or way less than the maximum 12 connections, nonetheless the pending connections didn't connect. The pending number would change every second to anything between 4 and 8, so there was movement within the pending connections, but none would connect.

The device .121, did connect some but not all pending connections after a reboot. The others did connect all after a reboot over the web interface.

What might be a hint: Sometimes all devices that make trouble are connected to the same repeater. I am using a Fritzbox 7590 with Fritz 2400 and Fritz 3000 WLAN repeaters, which is by far the most reliable I have experimented with; they form a mesh. Signal strength is usually very good between them. But maybe, if a repeater might lose its signal at some point and hence cuts the Shelly's connection to the router for a bit, maybe then coming back on there is a problem. We did not experience this with 2.7.3.

Unless you want me to observe more on 2.8.2, I would downgrade now to confirm that the problems go away again with 2.7.3. Should I do that?

Best Patrik

[andyblac]

Dear @rojer , so I have been testing and observing. Once the family left the house and there were less Apple devices looking for homekit connections, the situation improved a bit, but we have still major problems with 2.8.2:

The screenshots were taken from devices that I couldn't connect to with homekit for over 24 hours. When opening them in the web interface, you can see that in all of the devices the number of active connections was 0 or way less than the maximum 12 connections, nonetheless the pending connections didn't connect. The pending number would change every second to anything between 4 and 8, so there was movement within the pending connections, but none would connect.

What might be a hint: Sometimes all devices that make trouble are connected to the same repeater. I am using a Fritzbox 7590 with Fritz 2400 and Fritz 3000 WLAN repeaters, which is by far the most reliable I have experimented with; they form a mesh. Signal strength is usually very good between them. But maybe, if a repeater might lose its signal at some point and hence cuts the Shelly's connection to the router for a bit, maybe then coming back on there is a problem. We did not experience this with 2.7.3.

Unless you want me to observe more on 2.8.2, I would downgrade now to confirm that the problems go away again with 2.7.3. Should I do that?

Best Patrik

this is an old bug see here https://github.com/mongoose-os-apps/shelly-homekit/issues/129 that has just been fixed in 2.9.0-alpha2, please try updating to 2.9.0-alpha2 here https://github.com/mongoose-os-apps/shelly-homekit/issues/617

[partytrik]

Great, will try that. Some of the devices were online only for a few days, but hopefully same fix. Thank you

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Comment or this will be closed in 7 days.

[github-actions[bot]]

This issue has now been closed, as no update was provided after it was marked stale. Feel free to provide updates to reopen this issue.