Homey BLE Proxy script is stopped when Shelly app is restarted.

[v61]

Hi,
After the latest upgrades (3.27.*) I have issues with my BLE devices not reporting.
I have found that the "Homey BLE Proxy" script in the Shelly proxy is stopped and set to "not autostart".
It happens when the Shelly app is started (Restart of Homey, restart of Shelly app or shelly app is being enabled after it was disabled.
I need to start the script in my proxies manually.
Best Regards, Valter

[v61]

This is the log from one of the Shelly devices when I restart the Shelly app:
shelly_http_client.:606 0x3ffe3fd0: Finished; bytes 365, code 101, redir 0/3, auth 0, status OK
15:41:30
shelly_notification:163 Status change of ws: {"connected":false}
15:41:3015:41:34
shos_rpc_inst.c:230 Shelly.GetDeviceInfo via HTTP_in GET 192.168.4.30:42298
15:41:39
shos_rpc_inst.c:230 Shelly.GetDeviceInfo via HTTP_in GET 192.168.4.30:42310
15:41:39
shos_rpc_inst.c:230 Shelly.GetConfig via HTTP_in GET 192.168.4.30:42322
15:41:39
shos_rpc_inst.c:230 Shelly.GetConfig via HTTP_in GET 192.168.4.30:42332
15:41:39
shos_rpc_inst.c:230 Script.Delete via HTTP_in POST 192.168.4.30:42340
15:41:40
shos_sys_config.c:330 Saved to conf9.json
15:41:40
shelly_notification:163 Status change of script:1: {"id":1,"running":false}
15:41:40
shelly_notification:163 Status change of sys: {"cfg_rev":43}
15:41:40
shelly_notification:209 Event from sys: {"component":"sys","event":"component_removed","target":"script:1","restart_required":false,"ts":1709390500.69,"cfg_rev":43}
15:41:40
shos_rpc_inst.c:230 Script.Create via HTTP_in POST 192.168.4.30:42356
15:41:40
shos_sys_config.c:330 Saved to conf9.json
15:41:40
shelly_notification:163 Status change of script:1: {"id":1,"running":false}
15:41:40
shelly_notification:163 Status change of sys: {"cfg_rev":44}
15:41:40
shelly_notification:209 Event from sys: {"component":"sys","event":"component_added","target":"script:1","restart_required":false,"ts":1709390500.89,"cfg_rev":44}
15:41:40
shos_rpc_inst.c:230 script.getconfig via WS_in 192.168.25.11:53931
15:41:41
shos_rpc_inst.c:230 script.getstatus via WS_in 192.168.25.11:53931
15:41:41
shos_rpc_inst.c:230 script.getconfig via WS_in 192.168.25.11:53931
15:41:41
shos_rpc_inst.c:230 script.getstatus via WS_in 192.168.25.11:53931
15:41:41
shos_rpc_inst.c:230 Script.PutCode via HTTP_in POST 192.168.4.30:42360
15:41:41
shos_rpc_inst.c:230 Script.PutCode via HTTP_in POST 192.168.4.30:42368
15:41:42
shos_rpc_inst.c:230 Script.PutCode via HTTP_in POST 192.168.4.30:42372
15:41:42
shos_rpc_inst.c:230 Script.PutCode via HTTP_in POST 192.168.4.30:59256
15:41:43
shos_rpc_inst.c:230 Script.PutCode via HTTP_in POST 192.168.4.30:59266
15:41:43
shos_rpc_inst.c:207 No handler for rpc/Script.SetConfig
15:41:43
shelly_http_client.:306 0x3ffe4258: WS ws://192.168.4.30:6113/
15:41:58
shelly_http_client.:606 0x3ffe4258: Finished; bytes 0, code 0, redir 0/3, auth 0, status -1: Connection error: -14
15:41:58
shelly_notification:163 Status change of switch:1: {"id":1,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1709390520,"total":1809.495},"ret_aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1709390520,"total":0.000}}
15:42:00
shelly_notification:163 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1709390520,"total":4091.045},"ret_aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1709390520,"total":0.000}}

[jghaanstra]

Thanx, but I'm already aware. There will be a fix in the next release.

[v61]

Thanks :) Best Regards, Valter 2 mars 2024 kl. 15:54 skrev Jelger Haanstra ***@***.***>: Thanx, but I'm already aware. There will be a fix in the next release. — Reply to this email directly, view it on GitHub<#219 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH237O737TP4SMJ37R2L5Q3YWHRYVAVCNFSM6AAAAABEDEBK5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUHAZDCNBZGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>