Unknown device card in flow due to Matter issues - UI needs improvement!

Hi everyone (and especially Athom)

I have a complex flow for determining when to roll down the bedroom curtain.

However, I have had issues with a couple of device Hubs lately that were connected to Homey through Matter.

Now I have tried to fix the Philips Hue Hub connection by reconnecting the Hub to Homey… This created duplicate devices (the old failing ones and the “new” responsive ones) - and as a part of that I am going through the flows to see where the device cards of the new Hue devices should replace the “old” failing ones.

This made me realize that there is a BIG problem with the interface for failing devices.

In the screenshot above, can you tell me which device card I should insert instead of the “card unavailable”-one?

After having wrecked my brain I have come to the conclusion that it is probably an Aqara window sensor (where the Matter connection to the Aqara Hub also has been failing for the last couple of weeks).

The big issue is that when you try to repair or remove a single device connected via a Hub that is connected to Homey through Matter, this would remove all other devices from that hub - and leave you guessing about cards in flows.

So my questions are:

  1. Is there somewhere where we users can see/identify which flows a failing device has been connected to - instead of having to go through each and every flow manually?
  2. Why is the flow interface so unhelpful so adjusting a single device affects ALL devices and removes them - leaving a lot of empty cards.
    In large flows it is completely impossible to figure out which device card to insert as a replacement.

You now assume they read every forum post; that’s not true. You’d write to homey.app/support instead.

Sure:

A very nice tool (app) reports broken flows within a few minutes (amongst many other things):
Flow Checker

.

Yeah this a big Adv Flow flaw, it annoys me as well. But you’d discuss with Athom support.

By adding Simple log cards and flow notes, it"s easier to “reverse engineer” your flow cards.
Next, when you “hover” the :information_source: on the missing card

it shows the function of the flow card, like onoff, dim etc., which makes it a bit easier to recall what card it would have been.

1 Like

Thanks.
Yeah, I will try to report it to Athom… Though, honestly my idea of posting here was to hopefully motivate others to also report it to Athom, so they would receive several reports instead of just a single, which they can give a lame answer and ignore.

Because, the last time I reported stuff I received an answer that seemed like it was written automatically without really reading what I was reporting… which basically made it seem like a waste of time.

In terms of devices connected via hubs and from there Matter to Homey, this I believe actually has an entire other UI issue, which is when you think that you remove a single malfunctioning device you are actually removing that hub and all of its devices. This removes the devices from the device list so you no longer see them as failing - and can no longer detect the flows they were connected to… Which leaves the empty cards in the flows, where the detective work now starts.

To prevent this kind of detective work I have begun using groups for matter connected devices and then address the group in the flow.

This means I always only need to fix the group, when reconnecting Matter devices - because the flows still use the group(s).

This use of groups to create “pseudo” devices makes flow-maintenance easier for these annoying Matter issues - but does present another issue of making it harder to know if a flow is missing a device (in the group).