Shelly device turning off automatic

🛎️ Get Help Devices
1

Hi, my shelly one device keeps turning off automatic after about a minute for some reason unknow to me, I've attached the logs which don't mean a lot to me but hopefully do you haha. any help would be very much appreciated.

Show events

Apps and devices

Boiler heating switch

dev:4872025-11-03 05:17:30.898 PM

info

response data: [id:0, output:false, source:HTTP_in, temperature:[tC:57.1, tF:134.7]]

dev:4872025-11-03 05:17:30.895 PM

info

response contentType: application/json

dev:4872025-11-03 05:17:30.893 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Switch.GetStatus?id=0]

dev:4872025-11-03 05:17:30.891 PM

info

Response: Connection : close

dev:4872025-11-03 05:17:30.889 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:30.886 PM

info

Response: Content-Length : 82

dev:4872025-11-03 05:17:30.884 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:17:30.855 PM

info

response data: [:]

dev:4872025-11-03 05:17:30.853 PM

info

response contentType: application/json

dev:4872025-11-03 05:17:30.850 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Shelly.CheckForUpdate]

dev:4872025-11-03 05:17:30.848 PM

debug

Response: Connection : close

dev:4872025-11-03 05:17:30.846 PM

debug

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:30.844 PM

debug

Response: Content-Length : 2

dev:4872025-11-03 05:17:30.842 PM

debug

Response: Content-Type : application/json

dev:4872025-11-03 05:17:30.262 PM

info

Check Device FW

dev:4872025-11-03 05:17:30.260 PM

info

response data: [cfg_rev:22, debug:[file_level:null, level:2, mqtt:[enable:false], udp:[addr:null], websocket:[enable:true]], device:[addon_type:null, discoverable:true, eco_mode:false, fw_id:20250924-062720/1.7.1-gd336f31, mac:FCB467B9D07C, name:Boiler], location:[lat:50.914200, lon:-1.388000, tz:Europe/London], rpc_udp:[dst_addr:null, listen_port:null], sntp:[server:time.cloudflare.com], ui_data:[:]]

dev:4872025-11-03 05:17:30.257 PM

info

response contentType: application/json

dev:4872025-11-03 05:17:30.255 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Sys.GetConfig]

dev:4872025-11-03 05:17:30.253 PM

info

Response: Connection : close

dev:4872025-11-03 05:17:30.251 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:30.249 PM

info

Response: Content-Length : 434

dev:4872025-11-03 05:17:30.247 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:17:30.219 PM

debug

Sys Status called

dev:4872025-11-03 05:17:30.217 PM

info

response data: [app:Plus1, auth_domain:null, auth_en:false, fw_id:20250924-062720/1.7.1-gd336f31, gen:2, id:shellyplus1-fcb467b9d07c, mac:FCB467B9D07C, model:SNSW-001X16EU, name:Boiler, slot:1, ver:1.7.1]

dev:4872025-11-03 05:17:30.214 PM

info

response contentType: application/json

dev:4872025-11-03 05:17:30.212 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Shelly.GetDeviceInfo]

dev:4872025-11-03 05:17:30.210 PM

info

Response: Connection : close

dev:4872025-11-03 05:17:30.208 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:30.206 PM

info

Response: Content-Length : 215

dev:4872025-11-03 05:17:30.204 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:17:30.162 PM

debug

Sys Status called

dev:4872025-11-03 05:17:30.160 PM

info

response data: [bssid:fa:92:bf:5a:d2:c7, rssi:-51, ssid:Smart home, sta_ip:192.168.2.203, status:got ip]

dev:4872025-11-03 05:17:30.157 PM

info

response contentType: application/json

dev:4872025-11-03 05:17:30.155 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/wifi.GetStatus]

dev:4872025-11-03 05:17:30.153 PM

info

Response: Connection : close

dev:4872025-11-03 05:17:30.151 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:30.149 PM

info

Response: Content-Length : 103

dev:4872025-11-03 05:17:30.147 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:17:30.116 PM

debug

WiFi Status called

dev:4872025-11-03 05:17:30.113 PM

debug

Shelly Refresh called

dev:4872025-11-03 05:17:28.097 PM

debug

Response: Connection : close

dev:4872025-11-03 05:17:28.095 PM

debug

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:17:28.093 PM

debug

Response: Content-Length : 15

dev:4872025-11-03 05:17:28.091 PM

debug

Response: Content-Type : application/json

dev:4872025-11-03 05:17:28.029 PM

info

Calling /rpc/Switch.Set?id=0&on=false

dev:4872025-11-03 05:17:28.027 PM

debug

Executing switch.off

dev:4872025-11-03 05:16:31.452 PM

info

response data: [id:0, output:true, source:HTTP_in, temperature:[tC:56.5, tF:133.8]]

dev:4872025-11-03 05:16:31.448 PM

info

response contentType: application/json

dev:4872025-11-03 05:16:31.440 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Switch.GetStatus?id=0]

dev:4872025-11-03 05:16:31.436 PM

info

Response: Connection : close

dev:4872025-11-03 05:16:31.433 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:31.429 PM

info

Response: Content-Length : 81

dev:4872025-11-03 05:16:31.425 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:16:31.390 PM

info

response data: [:]

dev:4872025-11-03 05:16:31.386 PM

info

response contentType: application/json

dev:4872025-11-03 05:16:31.382 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Shelly.CheckForUpdate]

dev:4872025-11-03 05:16:31.378 PM

debug

Response: Connection : close

dev:4872025-11-03 05:16:31.375 PM

debug

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:31.372 PM

debug

Response: Content-Length : 2

dev:4872025-11-03 05:16:31.368 PM

debug

Response: Content-Type : application/json

dev:4872025-11-03 05:16:30.814 PM

info

Check Device FW

dev:4872025-11-03 05:16:30.812 PM

info

response data: [cfg_rev:22, debug:[file_level:null, level:2, mqtt:[enable:false], udp:[addr:null], websocket:[enable:true]], device:[addon_type:null, discoverable:true, eco_mode:false, fw_id:20250924-062720/1.7.1-gd336f31, mac:FCB467B9D07C, name:Boiler], location:[lat:50.914200, lon:-1.388000, tz:Europe/London], rpc_udp:[dst_addr:null, listen_port:null], sntp:[server:time.cloudflare.com], ui_data:[:]]

dev:4872025-11-03 05:16:30.809 PM

info

response contentType: application/json

dev:4872025-11-03 05:16:30.806 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Sys.GetConfig]

dev:4872025-11-03 05:16:30.804 PM

info

Response: Connection : close

dev:4872025-11-03 05:16:30.802 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:30.800 PM

info

Response: Content-Length : 434

dev:4872025-11-03 05:16:30.798 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:16:30.763 PM

debug

Sys Status called

dev:4872025-11-03 05:16:30.760 PM

info

response data: [app:Plus1, auth_domain:null, auth_en:false, fw_id:20250924-062720/1.7.1-gd336f31, gen:2, id:shellyplus1-fcb467b9d07c, mac:FCB467B9D07C, model:SNSW-001X16EU, name:Boiler, slot:1, ver:1.7.1]

dev:4872025-11-03 05:16:30.758 PM

info

response contentType: application/json

dev:4872025-11-03 05:16:30.756 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/Shelly.GetDeviceInfo]

dev:4872025-11-03 05:16:30.754 PM

info

Response: Connection : close

dev:4872025-11-03 05:16:30.752 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:30.749 PM

info

Response: Content-Length : 215

dev:4872025-11-03 05:16:30.747 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:16:30.689 PM

debug

Sys Status called

dev:4872025-11-03 05:16:30.687 PM

info

response data: [bssid:fa:92:bf:5a:d2:c7, rssi:-49, ssid:Smart home, sta_ip:192.168.2.203, status:got ip]

dev:4872025-11-03 05:16:30.684 PM

info

response contentType: application/json

dev:4872025-11-03 05:16:30.682 PM

info

params: [uri:http://null:null@192.168.2.203/rpc/wifi.GetStatus]

dev:4872025-11-03 05:16:30.680 PM

info

Response: Connection : close

dev:4872025-11-03 05:16:30.678 PM

info

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:30.674 PM

info

Response: Content-Length : 103

dev:4872025-11-03 05:16:30.668 PM

info

Response: Content-Type : application/json

dev:4872025-11-03 05:16:30.607 PM

debug

WiFi Status called

dev:4872025-11-03 05:16:30.603 PM

debug

Shelly Refresh called

dev:4872025-11-03 05:16:28.585 PM

debug

Response: Connection : close

dev:4872025-11-03 05:16:28.582 PM

debug

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:28.580 PM

debug

Response: Content-Length : 16

dev:4872025-11-03 05:16:28.578 PM

debug

Response: Content-Type : application/json

dev:4872025-11-03 05:16:28.544 PM

info

Calling /rpc/Switch.Set?id=0&on=true

dev:4872025-11-03 05:16:28.542 PM

debug

Executing switch.on

dev:4872025-11-03 05:16:28.072 PM

debug

Response: Connection : close

dev:4872025-11-03 05:16:28.070 PM

debug

Response: Server : ShellyHTTP/1.0.0

dev:4872025-11-03 05:16:28.068 PM

debug

Response: Content-Length : 16

dev:4872025-11-03 05:16:28.066 PM

debug

Response: Content-Type : application/json

dev:4872025-11-03 05:16:28.040 PM

info

Calling /rpc/Switch.Set?id=0&on=false

dev:4872025-11-03 05:16:28.037 PM

debug

Executing switch.off

2

This is the logs from the shelly device

Connected.
17:26:33
shelly_debug.cpp:236 Streaming logs to 192.168.4.202:54940
17:26:35
wifi I (36746681) wifi:[ADDBA]RX DELBA, reason:39, delete tid:0, initiator:0(recipient)
17:26:49
wifi I (36761721) wifi:[ADDBA]RX DELBA, reason:39, delete tid:0, initiator:0(recipient)
17:27:04
shos_rpc_inst.c:243 Switch.Set [1906300867@] via HTTP_in GET 192.168.2.200:59132
17:27:05
shelly_notification:164 Status change of switch:0: {"output":true,"source":"HTTP_in"}
17:27:05
shos_rpc_inst.c:243 wifi.GetStatus [886334622@] via HTTP_in GET 192.168.2.200:59134
17:27:07
shos_rpc_inst.c:243 Shelly.GetDeviceInfo [371940841@] via HTTP_in GET 192.168.2.200:59136
17:27:07
shos_rpc_inst.c:243 Sys.GetConfig [1906617088@] via HTTP_in GET 192.168.2.200:59138
17:27:07
shos_rpc_inst.c:243 Shelly.CheckForUpdate [270281778@] via HTTP_in GET 192.168.2.200:59140
17:27:07
shelly_update.cpp:355 Checking for updates (1.7.1 20250924-062720/1.7.1-gd336f31 {"bl":16777983,"t":1762190827.319,"ut":36763756701,"hf":136972,"hmf":110980,"fs":393216,"fsf":131072,"pkw":0})
17:27:07
shos_http_client.cp:316 0x3ffe07ac: HTTPS GET https://updates.shelly.cloud/update/Plus1?src=rpc (CA shelly_cloud.pem,ca.pem)
17:27:07
shos_http_client.cp:656 0x3ffe07ac: Finished; bytes 227, code 200, redir 0/3, auth 0, status OK
17:27:07
shos_rpc_inst.c:243 Switch.GetStatus [1424521149@] via HTTP_in GET 192.168.2.200:59142
17:27:07
shos_rpc_inst.c:243 Switch.Set [964213393@] via HTTP_in GET 192.168.2.200:59144
17:27:27
shelly_notification:164 Status change of switch:0: {"output":false,"source":"HTTP_in"}
17:27:27
shos_rpc_inst.c:243 wifi.GetStatus [1393671824@] via HTTP_in GET 192.168.2.200:59146
17:27:29
shos_rpc_inst.c:243 Shelly.GetDeviceInfo [1189094242@] via HTTP_in GET 192.168.2.200:59148
17:27:29
shos_rpc_inst.c:243 Sys.GetConfig [400746560@] via HTTP_in GET 192.168.2.200:59150
17:27:29
shos_rpc_inst.c:243 Shelly.CheckForUpdate [1036352785@] via HTTP_in GET 192.168.2.200:59152
17:27:29
shelly_update.cpp:355 Checking for updates (1.7.1 20250924-062720/1.7.1-gd336f31 {"bl":16777983,"t":1762190849.767,"ut":36786205261,"hf":137068,"hmf":110980,"fs":393216,"fsf":131072,"pkw":0})
17:27:29
shos_http_client.cp:316 0x3ffdf1c0: HTTPS GET https://updates.shelly.cloud/update/Plus1?src=rpc (CA shelly_cloud.pem,ca.pem)
17:27:29
shos_http_client.cp:656 0x3ffdf1c0: Finished; bytes 227, code 200, redir 0/3, auth 0, status OK
17:27:30
shos_rpc_inst.c:243 Switch.GetStatus [1639733102@] via HTTP_in GET 192.168.2.200:59154
17:27:30
wifi I (36806841) wifi:[ADDBA]RX DELBA, reason:39, delete tid:0, initiator:0(recipient)
17:27:49
wifi I (36821881) wifi:[ADDBA]RX DELBA, reason:39, delete tid:0, initiator:0(recipient)

3

Those logs are really hard to read (screenshots or at least careful formatting are easier), but I don't think they'd be helpful. The first thing I'd check is the "Events" tab on the device detail page for this device. Don't actually look for events, just "commands," entries with "command" under the "Type" column. If you see one for "command-off," that would be an obvious clue and would show you what app did it. If you don't, presumably you'll still see an event for switch off, and in that case, it suggest something outside the hub did it -- otherwise you'd see a command. If it's Wi-Fi, check anything else that might be using it (manufacturer's own app? other direct integrations?), or for any device, look for on-device "auto-off"-type settings that could be doing this on their own.

2 Likes
4

Hi, bertabcd1234 thanks for the quick replay, so about the busy logs, they mean nothing to me so I just enabled every logging option available haha. I've sorted it now, I had disabled my Advanced vThermostat Manager but not the child device and for some reason because this device is for my heating and it was part of this rule it was constantly trying to turn the device off. Its all sorted now though. On a different note have you had any experience with the shelly H&T ?

Many thanks
Mike

5

It wasn't so much the amount of logs as the formatting. But glad you got it figured out! I am not familiar with the other device. If you are trying to troubleshoot a similar problem, the same steps are a good place to start, or look here: How to Troubleshoot Apps or Devices | Hubitat Documentation