# Shelly1 - doorbell - no notification

**URL:** <https://community.homey.app/t/shelly1-doorbell-no-notification/84241>\
**Category:** Questions & Help\
**Created:** [July 9, 2023, 9:43am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241 "2023-07-09T09:43:25Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 9, 2023, 9:43am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/1 "2023-07-09T09:43:25Z")

</div>

I’ve installed a Shelly1 with a ‘dummy’ doorbell. Shelly1 is working, app is working…only homey app isn’t receiving a notification if I push the doorbell. Only if I push longer (what nobody will do usually). The shelly app is set button type-toggle mode. I’ve tried all the other options but Homey isn’t receiving a notification. what am I missing

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [July 9, 2023, 9:54am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/2 "2023-07-09T09:54:12Z")

</div>

> [@Bert-Jan\_Piek](#):
>
> what am I missing

I assume to read the trouble shooting infos in the first topic of the [Homey Shelly thread](https://community.homey.app/t/app-pro-cloud-shelly/765). Maybe this info can be helpful.

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 23, 2023, 9:36am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/3 "2023-07-23T09:36:15Z")

</div>

I’ve read the trouble-info but haven’t found a solution. the shelly is only triggered if I hold the doorbell button for a bit longer. Which nobody will do in real life. will continue searching but open for any input

---

<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:** [July 23, 2023, 9:48am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/4 "2023-07-23T09:48:35Z")

</div>

> [@Bert-Jan\_Piek](#):
>
> I’ve read the trouble-info but haven’t found a solution

Can you show the CoAP/Outbound Socket settings of your Shelly? And also the button configuration.

---

<div class="post-metadata">

**Author:** ![To\_Lou](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/to_lou/32/79159_2.png) [@To\_Lou](https://community.homey.app/u/To_Lou)\
**Post date:** [July 23, 2023, 9:54am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/5 "2023-07-23T09:54:59Z")

</div>

Have you set Homey to check ‘Input 1’ changes?  
Maybe if you switch Shelly to ‘External Input’ and use that instead?

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 23, 2023, 10:15am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/6 "2023-07-23T10:15:23Z")

</div>

![Screenshot_20230723_120843_Shelly](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/6/f6355198360d129ceee18d6fba3cdd0baf311078.jpeg)  
 ![Screenshot_20230723_121112_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/65124f0d23b5cc68837e5dddd7bb348c0f6badf2.jpeg)  
see attached screenshots

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 23, 2023, 10:19am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/7 "2023-07-23T10:19:39Z")

</div>

yes but no result. The status of ‘input 1’ isn’t triggered. only with a longer push

---

<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:** [July 23, 2023, 10:31am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/8 "2023-07-23T10:31:57Z")

</div>

If you have a Homey Pro 2023 model connected to Ethernet, make sure that 192.168.68.73 is the correct IP address for the Ethernet port, and not for Homey’s WiFi. There was an issue a few firmwares ago where the two where switched by accident, causing problems with the Shelly app setting the incorrect IP address.

You can find the correct address here: [Homey Developer Tools](https://tools.developer.homey.app/tools/system)

Also, if your Homey doesn’t yet have a fixed IP address in your router, you need to make sure that it does.

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 23, 2023, 10:56am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/9 "2023-07-23T10:56:01Z")

</div>

let me double check the fix IP setting which I should have done already. I’ve a homey pro (early 2019). Only wifi. still not sure if should buy the 2023 version

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [July 23, 2023, 11:41am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/10 "2023-07-23T11:41:07Z")

</div>

All the devices are having a fixed IP. Have re-installed the shelly1 within the shelly app becuase even the app itselfs isn’t reacting on a short push. Have contacted shelly support if they’ve a solution. still open for any suggestion and will react if I’ve a reply from shelly

---

<div class="post-metadata">

**Author:** ![To\_Lou](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/to_lou/32/79159_2.png) [@To\_Lou](https://community.homey.app/u/To_Lou)\
**Post date:** [July 23, 2023, 11:47am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/11 "2023-07-23T11:47:20Z")

</div>

> [@To\_Lou](#):
>
> Maybe if you switch Shelly to ‘External Input’ and use that instead?

Then the Shelly should switch and subsequently update 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:** [July 23, 2023, 2:25pm UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/12 "2023-07-23T14:25:23Z")

</div>

> [@Bert-Jan\_Piek](#):
>
> All the devices are having a fixed IP. Have re-installed the shelly1 within the shelly app becuase even the app itselfs isn’t reacting on a short push.

Apparently the Shelly needs a longer contract to actually detect the input. I highly doubt Allterco Robotics will be able to help you with that. Sounds like a hardware limitation.

---

<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:** [July 23, 2023, 2:43pm UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/13 "2023-07-23T14:43:13Z")

</div>

Relevant: [ShellyForHASS | Shelly Input Switch Delayed Response On HA](https://www.facebook.com/groups/shellyforhass/posts/727619877867565/)  
_“…but it means instead of being able to ‘tap’ the push button when entering a room you have to hold for approx 1s before the command is seen”_

Someone in the thread there suggests that the delay doesn’t happen when Shelly published to MQTT.

---

<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:** [July 23, 2023, 3:11pm UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/14 "2023-07-23T15:11:32Z")

</div>

Worth investigating but that thread seems more about a delay and not a complete miss. And it would be strange if MQTT would work but CoAP wouldnt. Although I’m aware Shelly firmware handles different actions sequentially (something like first own cloud, mqtt, coap/websocket, http action events) I would still think that the actions, once fired, would all run.

---

<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:** [July 23, 2023, 3:15pm UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/15 "2023-07-23T15:15:52Z")

</div>

> [@Phuturist](#):
>
> Worth investigating but that thread seems more about a delay and not a complete miss.

How I’m reading it is that short taps don’t register, only when the button is pressed at least a second is it passed to HA. Which seems to be similar to what OP is experiencing.

---

<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:** [July 23, 2023, 3:17pm UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/16 "2023-07-23T15:17:27Z")

</div>

> [@robertklep](#):
>
> How I’m reading it is that short taps don’t register, only when the button is pressed at least a second is it passed to HA. Which seems to be similar to what OP is experiencing.

You are right (again). So it’s probably a hardware limitation. I’m interested in what Allterco Robotics is going to respond.

---

<div class="post-metadata">

**Author:** ![Bert-Jan\_Piek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert-jan_piek/32/48846_2.png) [@Bert-Jan\_Piek](https://community.homey.app/u/Bert-Jan_Piek)\
**Post date:** [August 31, 2023, 11:11am UTC](https://community.homey.app/t/shelly1-doorbell-no-notification/84241/17 "2023-08-31T11:11:05Z")

</div>

With the support of Shelly I’ve tested several settings but with no positive result. Shelly suppport offered a Shelly 1 Plus with no charge and today I’ve installed the SHelly 1 Plus succesful. Doorbell - short push - with a notification and Homey nofication ! Have already created some flows. THanks all for your replies and special thanks to Shelly support !
