Homey Community Forum

[APP] Shelly

There is something wrong with your network. Requests are timing out

2020-04-06 18:21:02 [log] [ManagerDrivers] [shelly2-rollershutter] [3] { FetchError: request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:04 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:04 [log] [ManagerDrivers] [shelly25-rollershutter] [0] { FetchError: request to http://192.168.6.70/status failed, reason: connect ETIMEDOUT 192.168.6.70:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.70/status failed, reason: connect ETIMEDOUT 192.168.6.70:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:05 [log] [ManagerDrivers] [shelly25-rollershutter] [1] { FetchError: request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:05 [log] [ManagerDrivers] [shelly1] [8] { FetchError: request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:38 [log] [ManagerDrivers] [shelly2-rollershutter] [5] { FetchError: request to http://192.168.6.43/status failed, reason: connect ETIMEDOUT 192.168.6.43:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.43/status failed, reason: connect ETIMEDOUT 192.168.6.43:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:38 [log] [ManagerDrivers] [shelly2-rollershutter] [0] { FetchError: request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:38 [log] [ManagerDrivers] [shelly2-rollershutter] [1] { FetchError: request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:39 [log] [ManagerDrivers] [shelly2-rollershutter] [2] { FetchError: request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:39 [log] [ManagerDrivers] [shelly2-rollershutter] [3] { FetchError: request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:39 [log] [ManagerDrivers] [shelly2-rollershutter] [4] { FetchError: request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:39 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:40 [log] [ManagerDrivers] [shelly2-rollershutter] [0] { FetchError: request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:40 [log] [ManagerDrivers] [shelly2-rollershutter] [1] { FetchError: request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:40 [log] [ManagerDrivers] [shelly2-rollershutter] [3] { FetchError: request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:40 [log] [ManagerDrivers] [shelly2-rollershutter] [2] { FetchError: request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:41 [log] [ManagerDrivers] [shelly2-rollershutter] [4] { FetchError: request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:41 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:41 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:42 [log] [ManagerDrivers] [shelly1] [8] { FetchError: request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:42 [log] [ManagerDrivers] [shelly2-rollershutter] [6] { FetchError: request to http://192.168.6.44/status failed, reason: connect ETIMEDOUT 192.168.6.44:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.44/status failed, reason: connect ETIMEDOUT 192.168.6.44:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:42 [log] [ManagerDrivers] [shellydimmer] [4] { FetchError: request to http://192.168.6.27/status failed, reason: connect ETIMEDOUT 192.168.6.27:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.27/status failed, reason: connect ETIMEDOUT 192.168.6.27:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:43 [log] [ManagerDrivers] [shellydimmer] [3] { FetchError: request to http://192.168.6.31/status failed, reason: connect ETIMEDOUT 192.168.6.31:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.31/status failed, reason: connect ETIMEDOUT 192.168.6.31:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:43 [log] [ManagerDrivers] [shelly25-rollershutter] [0] { FetchError: request to http://192.168.6.70/status failed, reason: connect ETIMEDOUT 192.168.6.70:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.70/status failed, reason: connect ETIMEDOUT 192.168.6.70:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:21:43 [log] [ManagerDrivers] [shelly25-rollershutter] [1] { FetchError: request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 18:22:33 [log] [ManagerDrivers] [shelly1] [8] { FetchError: request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.11/status failed, reason: connect ETIMEDOUT 192.168.6.11:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }```

It must be something like the WiFi not stable, something is blocking traffic, the IP addresses have changed since pairing, etc. Connection issues is not something I can solve in my app.

Thats not good what can i do the best?

As mentioned earlier, make sure the IP address of the device in your router matches the IP address of the device in Homey. I still think you do not have static IP addresses configured in your router.

Is thit al the conflict of more?

Its better?

That looks like a KPN Experiabox, in which case I’m not surprised about your network being unstable. I recently bought a new house and was using the Experiabox until we moved in, and it was terrible. After we moved in I quickly replaced it with a proper router, no issues since.

There’s a very similar issue with Ziggo’s Connectbox, which also is pretty unstable.

I think it’s fair to say that Homey just doesn’t work well in combination with either one of these routers. It’s partly Homey’s fault too, because it apparently doesn’t recover when it loses its connection with the router.

Its synology rt2600ac no Kpn

Okay, that would (likely) rule out the router (and we’re back to Homey’s networking just being pretty terrible :frowning: ).

Hi its working now we have homey reset and its al working, 4efac78b-945c-45ca-a6f7-dacbac164298

I dare not restart the app everything works but it is not delayed quickly and I have enough memory free in homey

Still a load of network timeouts in the log.

---- stdout ----
2020-04-06 20:42:00 [log] [ShellyApp] Initializing Shelly App ...
2020-04-06 20:46:37 [log] [ManagerDrivers] [shelly2-rollershutter] [2] { FetchError: request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:46:40 [log] [ManagerDrivers] [shelly2-rollershutter] [2] { FetchError: request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:48:37 [log] [ManagerDrivers] [shelly2-rollershutter] [2] { FetchError: request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.26/status failed, reason: connect ETIMEDOUT 192.168.6.26:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:17 [log] [ManagerDrivers] [shelly25-rollershutter] [1] { FetchError: request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.71/status failed, reason: connect ETIMEDOUT 192.168.6.71:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:18 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.81/status failed, reason: connect ETIMEDOUT 192.168.6.81:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:18 [log] [ManagerDrivers] [shelly25] { FetchError: request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.51/status failed, reason: connect ETIMEDOUT 192.168.6.51:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:18 [log] [ManagerDrivers] [shelly2-rollershutter] [1] { FetchError: request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.24/status failed, reason: connect ETIMEDOUT 192.168.6.24:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:19 [log] [ManagerDrivers] [shelly2-rollershutter] [0] { FetchError: request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.22/status failed, reason: connect ETIMEDOUT 192.168.6.22:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:19 [log] [ManagerDrivers] [shelly2-rollershutter] [3] { FetchError: request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.41/status failed, reason: connect ETIMEDOUT 192.168.6.41:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:19 [log] [ManagerDrivers] [shelly2-rollershutter] [4] { FetchError: request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.42/status failed, reason: connect ETIMEDOUT 192.168.6.42:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }
2020-04-06 20:53:19 [log] [ManagerDrivers] [shelly2-rollershutter] [6] { FetchError: request to http://192.168.6.44/status failed, reason: connect ETIMEDOUT 192.168.6.44:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  message: 'request to http://192.168.6.44/status failed, reason: connect ETIMEDOUT 192.168.6.44:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT' }

How can this i am not understand this

c61137f0-f9ef-4fb7-b1d2-9b24732f0c3a

Morning I only ordered a homey pro, maybe the slowness is solved with that, I also have 20 apps running and a total of 90 devices

Question, when do you add the shelly smoke detector?

You are the first to request support this device. My experience with Homey integration of the Shelly devices that use batteries are pretty bad though. These devices only wake up periodically to report their status. Homey has no way of knowing when they wake up and might miss the window when polling the device and thus not update the status within Homey. That said, please submit a feature request on Github. I’ll pick it up when I have some time.

Thanks. It’s better then the z-wave smoke detectors I guess because it works via wifi?

No, there is no better or worse here for the protocols.
Z-wave makes your batteries live longer, but if distance is large and no relays (z-wave devices on fixed power) then wifi could be a better choice.

The only thing what counts is: does the smoke detector actuality detect smoke and report that to the homey using a push message (instead of a frquent pull from the homey)?

According to the API documentation of the smoke detector it does not (yet) support push messages. I have already requested this functionality at Allterco Robotics (the company behind Shelly) but never got a response. So based on the documentation and my experience I’d say you might actually miss an incoming signal of detected smoke on Homey side. Ofcourse the detector itself would make a lot of noise.

There is something wrong with the app.
The shelly 1 and 1pm wont work any longer since last update.
The devices are unreachable.
See screenshote