Dependency Map

It would be very cool to see a visual of all the (non scripted) dependencies throughout variables, actions, triggers, devices. Something similar exists when deleting an object, you get a list of the processes that depend on it.

Seeing this in a visual would be so helpful. I'm sure this is a long shot to be included as a core feature, but killer plugin idea.

While it's not a visual map, you know you can right click on anything in an indigo list and choose "show dependencies", right?

Right. This would be a visual rather than a hunt and peck

Can you talk a bit more about what you'd want to see (output)? I think a map of all dependencies would become overwhelming very quickly.

I monkeyed around with anassociation map just for Z-Wave devices . I found the exercise interesting, but not ideal and think the Z-Wave Node Matrix is better for digesting those relationships.

I realize that you're asking for something different, but representing complex relationships visually is tricky.

Here's a simple example around how link analysis can be used for something like fraud detection. The nodes are represented as they have relationships to one another to help solve fraud cases. I'm interested to see if we can show similar (and less complex) relationships between devices, schedules, variables, and actions. Massively helpful for understanding the many workflows and entities that exist in Indigo in our setups, and perhaps even more valuable for optimization, eliminating redundancy, and troubleshooting.

Use cases could be to drag two devices into the graph, and let the system build the relationship between the two. Another could be to see all relationships in the system and allow you to drill in. Imagine how powerful that could be will additional health data around each device, or finding conflicting IP addresses, or finding that you have a trigger firing that you totally forgot about that it setting a variable.

Gotcha. For on or two objects at a time, I think this would be digestible. For the *system* (i.e., everything all at once) I think it would be overwhelming. This is something that might be doable with a plugin.

I'm not volunteering.

[jay (support)]

I'll just say it: we won't be tackling something like this. While we can see how it would be useful (and cool), there not much demand and it's a complex task, so the ROI would just not work out. The big issue is around how plugins use devices. Indigo knows nothing about how plugins use devices and if they store devices references we know nothing about those dependencies. Same for scripts - they can save device IDs and we know nothing about it.

We would certainly welcome someone else attempting it, and we'd help in any way we could.

Interesting- I volunteer Dave

Dave who?

Dave who?

I actually laughed out loud at that reply.


Sent from my iPhone using Tapatalk Pro

images.jpeg (10.12 KiB) Viewed 2337 times

@FlyingDiver - I totally thought the same thing. That's been following me around since the day it was released.