Homey Community Forum

[APP] Shelly

How is the WiFi connection to your dimmer, is it close to your router of far away?

That is normaal the signal is perfect

Than I’m out of clues. As you are the only one having these issues I dont think it’s related to my app but it’s something in your configuration. If you know how to run apps from the command line I could create a debug version of that app that might give more information on what is happening. Just let me know if you want to try that.

[EDIT] I did find something that may cause the red triangle for the RGB2 White devices. I’ll fix that in a next release.

ok i have never done it but maybe it is something to learn i don’t like being alone so i would like to try
to solve it

v1.18.2 - 2020-0406

Bugfixes for RGBW2 White and the triggercard ‘Meter Power in Wmin changed’ for Shelly 2.5

We install the update en we have dimmers lost i think problem homey :man_shrugging:t2::man_shrugging:t2:

everything that update means is so for certain devices every x goes wrong

it’s even so bad when i do shelly app restart it is homey half minute offline

Could you send me another diagnostic report once the app has restarted.

24aefb21-9628-4568-b0bd-2fb604ce8eef

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