How to combine multiple sensor status into one <something> that can be shown on a Dashboard

🛎️ Get Help
1

I have a number of water sensors. I would like to have a Dashboard tile showing "OK" if all are dry and "Leakage" if any one senses water.

I know I can create a RM rule but is there another easier method?

Thanks
John

2

Easier method. Tile Builder - multi-attribute!
problem. solved.

2 Likes
3

Could look at Sensor Groups+ [Resurrected]

4

With Tile Builder Advanced using the Attribute Monitor you could do something like this.
image

It there is a leak it would look like this.
image

This uses the filtering feature to only show those lines that match user provided strings.

2 Likes
5

Thanks for all the suggestions. I'll look into both. I like what @garyjmilne showed but I also like simple applications.

John

6

Any app that is maintained and that you didn't write is simple.

1 Like
7

My mistake, should be "an app that uses minimal resources".

1 Like
8

Yes, it's a big app for just that one thing. But I'll hazard a guess that you will end up with multiple custom tiles. That is where Tile Builder really shines.
A) One App instead of multiple apps.
B) One device can hold 25 tiles so you don't end up with a variety of single purpose devices.
C) You can configure your tiles to be consistent in color, font, etc.
D) You are not limited by what someone has already created.

But I wrote it so I'm biased. :laughing:

2 Likes
9

It looks like a great app. I am, however not a "dashboard" person. The singular goal for this need is to allow me the piece of mind when not at home.
So for now a simple OK or not OK for a few sensors is all I need.

BTW your example gave me the idea of capturing the time of the transition from OK to not OK and perhaps displaying that (only for the leak sensors).
Also note I have a Water Cop which in theory I could assume if it's open things are OK, but somehow that isn't enough for me.

10

Not to beat a dead horse but I don't want others to read your statement and assume TB is greedy on resources. Tile Builder uses the very efficient Hubitat event model. A new tile is only generated when one of the monitored attributes changes. For example this is my mailbox tile which as you might expect fires once per day.

image
image1685×97 5.59 KB

First column is milliseconds and second column is instances. So it fired once today and used 136 milliseconds. 5th column is the % of total CPU which is so small it doesn't register.

I know what you are saying though, it's a big application for a small task.