# \[FeatureRequest\] "Card not available" info

**URL:** <https://community.homey.app/t/featurerequest-card-not-available-info/148290>\
**Category:** Ideas & Suggestions\
**Created:** [January 1, 2026, 2:56pm UTC](https://community.homey.app/t/featurerequest-card-not-available-info/148290 "2026-01-01T14:56:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![johbiraus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johbiraus/32/78856_2.png) [@johbiraus](https://community.homey.app/u/johbiraus)\
**Post date:** [January 1, 2026, 2:56pm UTC](https://community.homey.app/t/featurerequest-card-not-available-info/148290/1 "2026-01-01T14:56:15Z")

</div>

Hi,

When troubleshooting flows that contain removed devices, it can be quite hard to remember or understand what cards that now say ‘Card not available’ did previously. My suggestion is to add a preview of the card’s previous function when hovering over the info button.

---

<div class="post-metadata">

**Author:** ![BasMilius](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/basmilius/32/146560_2.png) [@BasMilius](https://community.homey.app/u/BasMilius)\
**Post date:** [January 1, 2026, 3:10pm UTC](https://community.homey.app/t/featurerequest-card-not-available-info/148290/2 "2026-01-01T15:10:02Z")

</div>

Would love this, or at least that you can view the arguments that were once set.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [January 1, 2026, 9:32pm UTC](https://community.homey.app/t/featurerequest-card-not-available-info/148290/3 "2026-01-01T21:32:03Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 2, 2026, 12:05am UTC](https://community.homey.app/t/featurerequest-card-not-available-info/148290/4 "2026-01-02T00:05:20Z")

</div>

The function (capability) is showed already, albeit not very clear.

 ![521](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/4/54fabbd1d608e9d7f21f5e869b22022779bf41f2.jpeg)

 ![524](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/1/510864580b4126c84244afe017733b798dacbd7a.jpeg)

 ![527](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/4/6498665da1a39aa3273b921aa1c67853c0e10fce.jpeg)

When you regularly run this script and save the results, you can find the corresponding device name, if it’s ID is specfied in the tooltip

```auto
// To find device IDs

const devices = await Homey.devices.getDevices();
console.log(`\nDevices overview`);

for (const device of Object.values(devices)) {  

  log(`\nName:\t\t ${device.name} \nID:\t\t ${device.id}`);
  // To show ALL of the device data, uncomment the next lime:
  //log(device);
};

return true;

```