# How to solve Card unavailable info

**URL:** <https://community.homey.app/t/how-to-solve-card-unavailable-info/144994>\
**Category:** Devices\
**Created:** [November 6, 2025, 7:39am UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994 "2025-11-06T07:39:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Menne\_Talsma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menne_talsma/32/8752_2.png) [@Menne\_Talsma](https://community.homey.app/u/Menne_Talsma)\
**Post date:** [November 6, 2025, 7:39am UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/1 "2025-11-06T07:39:12Z")

</div>

I know, I know, there have been some tpost about this before, but the issue has never been resolved.. so Maybe anyone?

I run A house with over 300 devices and some 50 apps running over my homey Pro 2023

everytime a card becomes “unavailable” I need to get into detective mode…it leads to a long search,

sometimes the remaining card info gives a clue but When the device info is this:  
homey:device:d77c4e68-5465-4f3f-9195-a75c0080e4ab  
homey:device:d77c4e68-5465-4f3f-9195-a75c0080e4ab:off

I don’t have a clue which device has gone haywire..

Is there an app or script or any solution how to find out any of the old device info like the brand, the old name, the device type or something.

Just spent a half an hour to find out an old wall plu had died… I hate that..

If anyone has an more efficient idea, pleas lemme know

Grtz

Menne

---

<div class="post-metadata">

**Author:** ![EdKats](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edkats/32/34977_2.png) [@EdKats](https://community.homey.app/u/EdKats)\
**Post date:** [November 6, 2025, 9:09am UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/2 "2025-11-06T09:09:16Z")

</div>

```auto
I simply have made screenshots of each flow.
So I can see what was written there in the event of something like that.

```

---

<div class="post-metadata">

**Author:** ![JohanP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johanp/32/119002_2.png) [@JohanP](https://community.homey.app/u/JohanP)\
**Post date:** [November 6, 2025, 3:09pm UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/3 "2025-11-06T15:09:12Z")

</div>

Ok, it requires som (or a lot) of work but :

I have a really, really complacated flow that instructs my Heatpump. If one of the used devices would become ‘Unavailable’ it would be a nightmare to reconstruct.

So i decided to replace all cards, tags of these devices with…a variable…

Each 15 seconds I replace the value of these variabled with the value of the Tag.

Eeven if the device dies, I can see with varaible is connected, and thus witch device died.

And if I replace the device I only need to change the card that fills the variable with the value..

Only 4 :

![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/e/0ec1ca852a38bb6187c8d1cf9dd1668fd6959505.png)

But in the Flow it saves me from editing about 30 cards

---

<div class="post-metadata">

**Author:** ![Paul\_Scholte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_scholte/32/16562_2.png) [@Paul\_Scholte](https://community.homey.app/u/Paul_Scholte)\
**Post date:** [November 6, 2025, 5:40pm UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/4 "2025-11-06T17:40:15Z")

</div>

I have a similar approach as @JohanP. In the upperpart of mij canvas of an Advanced Flow I couple devices to a variable or a virtual device, For each device this is done in one Adanced flow only, even if a device is needed in more Adanced Flows.

In the lower part of the canvas and in other Flows that need the device I only use virtual devices and variables to control my house. When a device fails or is broken I only have to change one or two lines in one Advanced Flow.

regards,

Paul

---

<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:** [November 6, 2025, 5:42pm UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/5 "2025-11-06T17:42:46Z")

</div>

I fully agree, but there’s a way to have Homey _inform you_ which card became unavailable

 ![Screenshot_20251106_183619_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/e/8e434771b4dae9400d23366065f913f5df5b2962.jpeg)

When you also have the [Flow Checker](https://community.homey.app/t/app-pro-flow-checker/50986) app running, it informs you @ the timeline which flows are affected, because unavailable cards makes flows break.

 ![Screenshot_20251106_184122_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/8/98f031fb3d815f4b23ee4ab773115eed29c4de3f.jpeg)

.  
I’ve done the mentioned virtual device approach as well, but got into big trouble when the virtual device app malfunctioned. It’s too fragile for me.

---

<div class="post-metadata">

**Author:** ![JohanP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johanp/32/119002_2.png) [@JohanP](https://community.homey.app/u/JohanP)\
**Post date:** [November 6, 2025, 8:18pm UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/6 "2025-11-06T20:18:50Z")

</div>

> [@Peter\_Kawa](#):
>
> I’ve done the mentioned virtual device approach as well, but got into big trouble when the virtual device app malfunctioned. It’s too fragile for me.

Thats why I use variables. Now just for one (major important) flow and one (OTGW) device…

If this works I might followup with others. But I’m allready drowning in variables..

---

<div class="post-metadata">

**Author:** ![Paul\_Scholte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_scholte/32/16562_2.png) [@Paul\_Scholte](https://community.homey.app/u/Paul_Scholte)\
**Post date:** [November 7, 2025, 2:14am UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/7 "2025-11-07T02:14:08Z")

</div>

> [@Peter\_Kawa](#):
>
> .  
> I’ve done the mentioned virtual device approach as well, but got into big trouble when the virtual device app malfunctioned. It’s too fragile for me.

Peter, which virtual app do you consider to be too fragile? I use this virtual device app [Virtual Devices | Homey](https://homey.app/en-us/app/com.arjankranenburg.virtual/Virtual-Devices/) and have not experienced serious troubles. If it would malfunction, I would be in a catastrophy 😫

---

<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:** [November 7, 2025, 4:09pm UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/8 "2025-11-07T16:09:31Z")

</div>

I think it was the one you mentioned. I don’t consider the app fragile, but _ **to me** _, the dependency of all devices on just one app was not the brightest idea, when the VD app unfortunately malfunctioned at one point. That was one time to many for me.  
Because any app (and Homey) has a chance of crashing or malfunctioning at some point.

With a Pro 2019, this construction slowed things down as well; maybe a Pro 2023 is not affected much by it (I don’t own one).

---

<div class="post-metadata">

**Author:** ![Paul\_Scholte](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_scholte/32/16562_2.png) [@Paul\_Scholte](https://community.homey.app/u/Paul_Scholte)\
**Post date:** [November 9, 2025, 1:11am UTC](https://community.homey.app/t/how-to-solve-card-unavailable-info/144994/9 "2025-11-09T01:11:21Z")

</div>

You have a point. I am considering now to change to the Homey native virtual devices. That will keep me sometime “from the street”.

Regards,

Paul
