# \[APP\] Shelly - Smart solutions for every home and office

**URL:** <https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765>\
**Category:** Apps\
**Tags:** app, official, homey, homey-pro, homey-cloud\
**Created:** [August 28, 2018, 8:54pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765 "2018-08-28T20:54:43Z")\
**Posts on this page:** 20\
**Page:** 32

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 11:45am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/626 "2020-04-06T11:45:27Z")

</div>

That is normaal the signal is perfect

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 11:48am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/627 "2020-04-06T11:48:39Z")

</div>

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](https://community.homey.app/t/how-to-cli-install-method/198) 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.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 11:58am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/628 "2020-04-06T11:58:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 12:19pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/629 "2020-04-06T12:19:42Z")

</div>

> ## v1.18.2 - 2020-0406
> 
> Bugfixes for RGBW2 White and the triggercard ‘Meter Power in Wmin changed’ for Shelly 2.5

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 12:58pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/630 "2020-04-06T12:58:29Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/e/9e0a9a35f289f2c88a4bb5273a94c1ee2ed59822.jpeg) We install the update en we have dimmers lost i think problem homey 🤷🏻‍♂️🤷🏻‍♂️

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 1:07pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/631 "2020-04-06T13:07:45Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 1:13pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/632 "2020-04-06T13:13:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 3:08pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/633 "2020-04-06T15:08:20Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 4:25pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/634 "2020-04-06T16:25:21Z")

</div>

24aefb21-9628-4568-b0bd-2fb604ce8eef

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 4:29pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/635 "2020-04-06T16:29:27Z")

</div>

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

````auto
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.
````

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 4:46pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/636 "2020-04-06T16:46:13Z")

</div>

Thats not good what can i do the best?

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 4:50pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/637 "2020-04-06T16:50:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 5:07pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/638 "2020-04-06T17:07:35Z")

</div>

Is thit al the conflict of more?

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 5:56pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/639 "2020-04-06T17:56:37Z")

</div>

Its better?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/5/f52fb38df6806ca32e7eccd2d3483ec83c5b6b0b.jpeg)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 6, 2020, 6:23pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/640 "2020-04-06T18:23:08Z")

</div>

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](https://community.homey.app/t/having-problem-connecting-to-homey-using-app/27919/7), 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.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 6:28pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/641 "2020-04-06T18:28:52Z")

</div>

Its synology rt2600ac no Kpn

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 6, 2020, 6:30pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/642 "2020-04-06T18:30:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 7:06pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/643 "2020-04-06T19:06:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jonathan\_Otte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_otte/32/18025_2.png) [@Jonathan\_Otte](https://community.homey.app/u/Jonathan_Otte)\
**Post date:** [April 6, 2020, 7:47pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/644 "2020-04-06T19:47:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [April 6, 2020, 8:08pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/645 "2020-04-06T20:08:11Z")

</div>

Still a load of network timeouts in the log.

```auto
---- 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' }

```

[Previous page](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765.md?page=31)

[Next page](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765.md?page=33)