Is It Just Me Or Do Users Want Device Monitoring Features?

There's info in the forums available or you can start up a new thread. Wouldn't want to derail this one too much.

1 Like

Ok I guess I can see how that might be useful..

This wasn't quite my intent, but I did leave it somewhat open in my title at least. And not to say I disagree, something in this space would be quite popular, as are the Community developed options, acknowledging the difficulties that can come with assessing the health of a device

Yes, that and the earlier Light on Table conversation / app from Bruce was where I started to notice people asking for this most recently.

The Device Health Status @FriedCheese2006 linked might be a step further than what I had in mind, being more in the monitoring space, which again I did not clarify in my original post. Again, a great idea / app, just not where I was heading.

I share your concerns @bjcowles, both in terms of the HE hub reporting a health status and the resource potentially required to deliver it. I could understand it would be problematic to deliver a single status that is reliable across all devices that are often unreliable in their behaviour and reporting. I think capturing various data points to support users achieve what they need is likely the right balance.


Too bad. I took you there :stuck_out_tongue_closed_eyes:

1 Like

The kind of thing I have in mind would be a single attribute that captures the time of the last full period of a key state, such as the total time the device was ON. Once the device next turns off, the attribute would get updated. A preference setting could be included to turn this feature on or off, to reduce load on the hub. I would expect the default would be off, as it is not likely to be a widely used feature.

People could track the events linked to this attribute to see a short history of the periods of the device being on, without need to setup rules to calculate / capture it. The same setup could apply to contact sensors being open, presence, motion activity, etc. The inverse may also be relevant, off, closed, inactive, etc.

The more I think about this the more I think it is likely to be an App, rather than asking for changes to ALL built-in drivers :slight_smile: That doesn't change (too much I hope) my idea of a process of selectively recording an attribute against devices for the most recent time spent in a specific state. While the capability may need to change, hopefully this does not require a change to the drivers that implement it.

I think that's the idea behind the Device Tracker app, but will need a few more iterations to support any attribute. I'm with you in that it should require a change to the driver as long as it sends an event for the attribute.

1 Like

I'd hope that a change to the capability and a new App would be enough.... Trying to avoid the overhead for the dev's to change all their code, just for my thought-bubble... As much as I expect they were chomping at the bit to implement my early design.... Just hold-fire guys... Give us some more time... :wink:

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.