# Netatmo doorbell doesn’t trigger flow **URL:** \ **Category:** Questions & Help\ **Tags:** app, flow\ **Created:** [July 15, 2021, 2:18pm UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460 "2021-07-15T14:18:57Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Otterkop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otterkop/32/39404_2.png) [@Otterkop](https://community.homey.app/u/Otterkop)\ **Post date:** [July 15, 2021, 2:18pm UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460/1 "2021-07-15T14:18:57Z")
Hi there. Since 2 weeks I have the Netatmo doorbell installed. Of course I connected it to Homey. I created a simple flow that plays a sound over my Sonos speakers. The flow worked perfectly when the doorbell is rang. However, since a couple of days the flow doesn’t respond when the bell is rang. The flow works fine (logically) when I just test it. What changed. Homey installed their latest update. I had to disconnect the doorbell and reconnected it. I have the latest versions of the apps. I tried to repair the connection. What could be the issue here. ---
**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 16, 2021, 6:03am UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460/2 "2021-07-16T06:03:33Z")
> [@Otterkop](#): > > The flow works fine (logically) when I just test it. That means the flow isn’t triggered by the Netatmo app (testing a flow skips the trigger and executes just the AND/OR and THEN parts of a flow). Since the app is developed by Athom, you can try and send a support e-mail to [support@athom.com](mailto:support@athom.com) ---
**Author:** ![Otterkop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otterkop/32/39404_2.png) [@Otterkop](https://community.homey.app/u/Otterkop)\ **Post date:** [July 16, 2021, 9:25am UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460/3 "2021-07-16T09:25:34Z")
> [@Otterkop](#): > > Hi there. Since 2 weeks I have the Netatmo doorbell installed. Of course I connected it to Homey. I created a simple flow that plays a sound over my Sonos speakers. The flow worked perfectly when the doorbell is rang. However, since a couple of days the flow doesn’t respond when the bell is rang. The flow works fine (logically) when I just test it. > > What changed. Homey installed their latest update. I had to disconnect the doorbell and reconnected it. I have the latest versions of the apps. I tried to repair the connection. What could be the issue here. Thanks Robert! Much appreciated!! ---
**Author:** ![Otterkop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otterkop/32/39404_2.png) [@Otterkop](https://community.homey.app/u/Otterkop)\ **Post date:** [August 24, 2021, 7:48am UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460/4 "2021-08-24T07:48:11Z")
My issue proofed to be a bug. Athom send an updated app for Netatmo some days later. Everything works fine again!! ---
**Author:** ![Marcel\_van\_Oosten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_van_oosten/32/29126_2.png) [@Marcel\_van\_Oosten](https://community.homey.app/u/Marcel_van_Oosten)\ **Post date:** [November 2, 2022, 8:10pm UTC](https://community.homey.app/t/netatmo-doorbell-doesn-t-trigger-flow/49460/5 "2022-11-02T20:10:53Z")
I have exact the same problem. Tried everything. - Restarted Homey - Restarted Netatmo app - Removed/Installed Netatmo doorbell device in “Homey devices” - Started “repair” of the Netatmo doorbell (approve API Access) - Made different flows to start different devices - Last effort I will undertake is to reset the Netatmo doorbell and see if things start working again [EDIT] - After not touching anything and within 12 hours everything started working automagically! I did not reset the doorbell. I am happy everything now works as expected but confused as what could have triggered the repair 🙂