# Keep info in card when device is missing

**URL:** <https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134>\
**Category:** Ideas & Suggestions\
**Created:** [June 25, 2023, 9:41am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134 "2023-06-25T09:41:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\
**Post date:** [June 25, 2023, 9:41am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/1 "2023-06-25T09:41:33Z")

</div>

Hi Homeys!

This might be “impossible” to achieve but I thought I’d present the issue anyway.

As it is now if a device is deleted or gone for some other reason the cards regarding this device grays out with the text “Card unavailable”. All the parameters are gone and even what device the card was connected to is missing. This means that if one deletes a device for some reason and forget that the device is used in a flow it can be really hard to know what device it was and what parameters were set to it when you open up the flow chart.

Here is an example from my pool pump automation flow. (Sorry or the poor resolution…I had to zoom out in my browser to fit the whole flow to screen dump it.)

 ![Skärmavbild 2023-06-25 kl. 10.54.34](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/2/7221eb7bdb3821a7bf260c945085376b48e73770.jpeg)  
After this screen dump I had to change the battery in the “Pooltemp” 433 MHz sensor which uses a new channel when batteries are changed.

 ![Skärmavbild 2023-06-25 kl. 11.10.20](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/c/6c5f5a2bdaf567a3ed57e034d3f65f60bc102bb1.jpeg)  
This is the result. Four cards are grayed out and there is no information at all what device the card was for and no information what parameters were set.

It would be really nice if that information was still there so you just have to click replace device and find the one that has been changed and, in my example, the temperature parameter would still be there…ready to “attach” to the new sensor. There could be a symbol that indicates that the device is no longer in the system…maybe a red exclamation mark like in the list of flows when there is something wrong with a flow?

---

<div class="post-metadata">

**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\
**Post date:** [June 25, 2023, 10:41am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/2 "2023-06-25T10:41:30Z")

</div>

There is a script to replace the old device ID by a new device ID  
@Peter_Kawa knows where to find it 👍

---

<div class="post-metadata">

**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\
**Post date:** [June 25, 2023, 10:52am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/3 "2023-06-25T10:52:21Z")

</div>

That would be really helpful! 👍

---

<div class="post-metadata">

**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\
**Post date:** [June 25, 2023, 12:34pm UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/4 "2023-06-25T12:34:02Z")

</div>

Have a look at this:

> [@\[HOW-TO\]\[Pro\]\[Cloud\] - Tool to FIX (advanced) flows after removing and re-adding devices](https://community.homey.app/t/how-to-pro-cloud-tool-to-fix-advanced-flows-after-removing-and-re-adding-devices/65018):
>
> rotating_lightwarning Use at own risk! warning rotating_light Hi, So I just go a new house and wanted to make my Zigbee network a bit better by removing an re-adding my devices so I get a stable network. But the issue with this is you have to fix all your flows. (Ofcourse [Flow Checker App for Homey | Homey](https://homey.app/a/com.athom.flowchecker/) can indicate the broken flows) I made a small script which can help with fixing the flows. So what do you need: Device ID you would like to update - You can get this via t…

---

<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:** [June 25, 2023, 4:44pm UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/5 "2023-06-25T16:44:30Z")

</div>

> [@JPe4619](#):
>
> [Peter\_Kawa](https://community.homey.app/u/peter_kawa) knows where to find it 👍

I see you found it as well 😉😁

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [June 26, 2023, 9:42am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/6 "2023-06-26T09:42:10Z")

</div>

And if you just want to know which parameters were used, you can use HomeyScript to see the flowcards:

```auto
let flows = await Homey.flow.getAdvancedFlows();
return _.find(flows,flow=>flow.name=='Test Advanced Triggers');

```

---

<div class="post-metadata">

**Author:** ![Paxman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paxman/32/128050_2.png) [@Paxman](https://community.homey.app/u/Paxman)\
**Post date:** [June 26, 2023, 10:46am UTC](https://community.homey.app/t/keep-info-in-card-when-device-is-missing/83134/7 "2023-06-26T10:46:39Z")

</div>

Than you all for your suggestions! I will try to test them out and see if I can get my head around them. I have not yet dived in to Homey scripts…so it’s still uncharted territory for me. 😊
