# Devices missing from flows

**URL:** <https://community.homey.app/t/devices-missing-from-flows/17653>\
**Category:** Questions & Help\
**Tags:** devices, flow\
**Created:** [September 3, 2019, 11:01am UTC](https://community.homey.app/t/devices-missing-from-flows/17653 "2019-09-03T11:01:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonas\_Hermansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonas_hermansen/32/9665_2.png) [@Jonas\_Hermansen](https://community.homey.app/u/Jonas_Hermansen)\
**Post date:** [September 3, 2019, 11:01am UTC](https://community.homey.app/t/devices-missing-from-flows/17653/1 "2019-09-03T11:01:57Z")

</div>

I’m having an issue with the Homey Flow builder.

When I try to build or edit an existing flow none of my devices is shown in the “Add card” list.  
I can see “System” and “Apps”, but not the devices registered on my Homey, even though they are shown in the “Devices” tab on the homescreen (the button at the bottom, between “Home” and “Flows”).

Even if I edit an existing flow where there’s a device card I can’t remove it and add it again.

Does anyone have a possible fix for this?

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [September 3, 2019, 12:06pm UTC](https://community.homey.app/t/devices-missing-from-flows/17653/2 "2019-09-03T12:06:12Z")

</div>

Do you see the zones in the bottom of the screen? Since on of the last Homey updates all devices have been grouped by zone…!

---

<div class="post-metadata">

**Author:** ![Jonas\_Hermansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonas_hermansen/32/9665_2.png) [@Jonas\_Hermansen](https://community.homey.app/u/Jonas_Hermansen)\
**Post date:** [September 3, 2019, 12:25pm UTC](https://community.homey.app/t/devices-missing-from-flows/17653/3 "2019-09-03T12:25:47Z")

</div>

I didn’t have auto update enabled, and was running an older version.  
An update seemed to fix it.

Thanks 🙂
