# \[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:** 195

<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:** [June 2, 2023, 3:53pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3919 "2023-06-02T15:53:14Z")

</div>

Just checked, nothing special in there. Only one ‘EHOSTUNREACH’ error for a device on IP 192.168.1.4, as it seems during pairing. Homey is telling it cant reach the device, most likely due to bad connection or bad network routing. If it is related to the router in use is not something I can tell from the log. All I can tell is that this is not something with the app.

---

<div class="post-metadata">

**Author:** ![Kraineff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kraineff/32/47228_2.png) [@Kraineff](https://community.homey.app/u/Kraineff)\
**Post date:** [June 2, 2023, 3:57pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3920 "2023-06-02T15:57:01Z")

</div>

192.168.1.4? It’s already on 192.168.1.50 ip. Can you check this one 002fa798-cc21-477a-b777-61bd266fe608

---

<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:** [June 2, 2023, 3:59pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3921 "2023-06-02T15:59:26Z")

</div>

```auto
  cause: Error: connect EHOSTUNREACH 192.168.1.4:80
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
    errno: -113,
    code: 'EHOSTUNREACH',
    syscall: 'connect',
    address: '192.168.1.4',
    port: 80
  }
}

```

Logs dont lie. And you should use static IP addresses. If you changed things around you should reboot Homey (and possibly the Shelly as well) as the mDNS implementation seems to do aggresive caching.

---

<div class="post-metadata">

**Author:** ![Kraineff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kraineff/32/47228_2.png) [@Kraineff](https://community.homey.app/u/Kraineff)\
**Post date:** [June 2, 2023, 4:00pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3922 "2023-06-02T16:00:10Z")

</div>

Oh, will try to reboot Homey

---

<div class="post-metadata">

**Author:** ![Kraineff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kraineff/32/47228_2.png) [@Kraineff](https://community.homey.app/u/Kraineff)\
**Post date:** [June 2, 2023, 4:05pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3923 "2023-06-02T16:05:01Z")

</div>

Wow, its really was a mDNS aggresive caching, after reboot 2.5 was discovered, but Shelly Plus 2pm disappeared from list, so I added it manually!

I think you should write about it in the description that mDNS search caches, and need a Homey reboot 🙂  
Thank you!

 ![Safari qvYxJQft](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/b/db2c283ef53bd34d438bcf750ee271930da12b5d.png)

---

<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:** [June 2, 2023, 4:07pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3924 "2023-06-02T16:07:59Z")

</div>

> [@Kraineff](#):
>
> Wow, its really was a mDNS aggresive caching

As in, you didnt believe me … 🤨

---

<div class="post-metadata">

**Author:** ![Kraineff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kraineff/32/47228_2.png) [@Kraineff](https://community.homey.app/u/Kraineff)\
**Post date:** [June 2, 2023, 4:08pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3925 "2023-06-02T16:08:33Z")

</div>

I believed, I just haven’t encountered it before 🙂

---

<div class="post-metadata">

**Author:** ![Peter\_Verver](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_verver/32/48231_2.png) [@Peter\_Verver](https://community.homey.app/u/Peter_Verver)\
**Post date:** [June 2, 2023, 5:41pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3926 "2023-06-02T17:41:03Z")

</div>

I have 2 Door window sensors. The first shows battery level. The second shows a question Mark. What am I dooing wrong.

---

<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:** [June 2, 2023, 8:38pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3927 "2023-06-02T20:38:03Z")

</div>

Be patient, it will update when the value changes. Battery operated devices aren’t polled because they sleep most of the time. Status relies on updates from the device itself.

---

<div class="post-metadata">

**Author:** ![Carlo\_Filippo\_Follis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/carlo_filippo_follis/32/63053_2.png) [@Carlo\_Filippo\_Follis](https://community.homey.app/u/Carlo_Filippo_Follis)\
**Post date:** [June 7, 2023, 1:19pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3928 "2023-06-07T13:19:07Z")

</div>

> [@Phuturist](#):
>
> As mentioned read the manual.
> 
> > ## Control button
> > 
> > - Press briefly to wake the Device up when it in sleep mode, or put it to sleep mode if it is awake.
> > - Press and hold for 5 sec to activate Device Access Point
> > - Press and hold for 10 sec to factory reset.

_ **Dear Futurist** _,

to wake up a device such as the Shelly H&T, for example, if powered via USB/Micro USB cable, it is sufficient to disconnect the power supply for 15 or 20 seconds and then restore it.

This way everything is faster and simpler!

Homey Pro, through the Shelly App, immediately added the Shelly H&T… 😃👍

See you soon!

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [June 8, 2023, 8:12pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3929 "2023-06-08T20:12:08Z")

</div>

> [@Phuturist](#):
>
> > [@Boris\_Fers](#):
> >
> > I had the same problem today. All shelly devices simply stopped updating their status to homey cloud.  
> > Any info on what could be causing this? Is it possible to detect this somehow and send a push notification?
> 
> I’m afraid not, I dont have much insights on cloud status. As it soley relies on push messages from Shelly cloud to Homey cloud it’s also hard to detect issues other than devices not responding. I personally would never rely on cloud for home automation for these kind of reasons. But next time, send me a diagnostic report before fixing the problem. Perhaps that contains more info on what is going on.

Today I had the same problem, I also created a diagnostic report: 080c0225-e81c-4403-956d-6dd506197d0d

I hope this will help.

---

<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:** [June 8, 2023, 8:53pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3930 "2023-06-08T20:53:47Z")

</div>

As mentioned in the reply to your diagnostic report. This is caused by a bug in Homey Cloud. You should report it to Athom. A work around is to reinstall the app from the app store to force a app restart and restore the connection.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [June 9, 2023, 1:09pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3931 "2023-06-09T13:09:29Z")

</div>

I reinstalled the Shelly app several times until now to fix the problem. The same issue happened 10 mins ago.

Interesting, because I have problems with this connectivity only with Shelly devices. All other devices are working without any problem and I don’t need to reinstall their apps to fix connectivity issues.

---

<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:** [June 9, 2023, 1:38pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3932 "2023-06-09T13:38:50Z")

</div>

> [@Boris\_Fers](#):
>
> Interesting, because I have problems with this connectivity only with Shelly devices. All other devices are working without any problem and I don’t need to reinstall their apps to fix connectivity issues.

What’s interesting about it? The explanation behind it is really simple. Homey Cloud talks to Shelly Cloud (over websocket connection). If this connection breaks for some reason, which can happen, (for instance a re-deploy on Shelly Cloud) and the connection cant be restored because the restore mechanism fails due to a bug in Homey Cloud this only affects Shelly devices. Nothing complex about it. I have reported it to Athom a while back, they choose not to give this a priority. Now I ask the users affected by this to report this to Athom as well to get it higher on their backlog. But it’s not my issue to solve!

My two personal cents, this is why you do not want your home automation to rely on cloud connectivity.

---

<div class="post-metadata">

**Author:** ![Boris\_Fers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/boris_fers/32/74283_2.png) [@Boris\_Fers](https://community.homey.app/u/Boris_Fers)\
**Post date:** [June 9, 2023, 3:18pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3933 "2023-06-09T15:18:53Z")

</div>

Thanks for the explanation, now I understand.

---

<div class="post-metadata">

**Author:** ![maarkuuzze](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/maarkuuzze/32/37697_2.png) [@maarkuuzze](https://community.homey.app/u/maarkuuzze)\
**Post date:** [June 14, 2023, 5:40pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3934 "2023-06-14T17:40:17Z")

</div>

I’ve just installed a Shelly RGBW2 and try to change the dimlevel white, but cant get it to work from Homey. The command works fine directly from browser.  
What am I doing wrong?  
Any easier way?

 ![RGBW2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/0/c032a4876ac355c26d77322de81a0a41134731ac.png)

---

<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:** [June 14, 2023, 6:52pm UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3935 "2023-06-14T18:52:55Z")

</div>

Use `color/0?turn=on&white=60` instead of the full URL.

---

<div class="post-metadata">

**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\
**Post date:** [June 23, 2023, 8:53am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3936 "2023-06-23T08:53:27Z")

</div>

Diag: 585c8411-767a-48e9-89ed-54e484f1e51f

Shelly Pro 2, second channel does not react on commands from homey, but status is updated in Homey when controlled from Shelly phone app.

What I see in the Shelly device debug log is that no command is received for channel 1 (switch:1) by the Shelly Pro 2 from 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:** [June 23, 2023, 9:22am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3937 "2023-06-23T09:22:06Z")

</div>

According to this log there are some authorization issues. Have you tried removing and re-pairing the device to make sure everything is set up correctly?

---

<div class="post-metadata">

**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\
**Post date:** [June 23, 2023, 9:50am UTC](https://community.homey.app/t/app-shelly-smart-solutions-for-every-home-and-office/765/3938 "2023-06-23T09:50:17Z")

</div>

Thanks for replies.

Ok, it now works, repairing with user admin and the password I had chosen. During previous pairing I had not used admin as username, but left the field empty.

Still a bit strange that switch:0 did work without the username and switch:1 not. Normally when credentials are wrong nothing works.

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

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