Take this as a rambling request... Like most of my posts.... Take what you will and I'll be grateful for any improvements I can contribute....
In recent times there's been a mixed bag of conversations re tracking devices in a particular state for a period of time. It feels to me like something that would be "nice" to have captured by the HE platform as a default piece of data for a device.... regardless of the efforts of the driver developer or my choices in device settings.
My theory revolves around state changes that relate to one another. So a switch being on and then off is all good in terms of events, and is something worth reporting in and of itself, but to know the time between the on and off events is something that users may find useful.
Anything "built-in" in this space would be appreciated.... Acknowledging that my request is a little light on...
I'm not sure why anyone would care about time between events. I mean we do have a wait for event option that allows for time countdown but unless you're looking at lets say how often someone is walking into a room and setting off a sensor to turn on the lights, I dont see much of a point...(Then again I'm lazy and couldn't care less lol)
We do get some historical state changes on variables and attributes of devices but the reporting is tabular on the device events page. Storage is limited in the device so keeping long term data needs to be external. With that in mind I log important data externally using the InfluxDB driver and send it to a external InfluxDB server and then graph it with Grafana.
I too look for trends like stuck battery reporting which I am now doing with a InfluxDB query and posting the status in Grafana. Battery reporting on devices is problem with many battery devices where they just stop reporting the levels around 30% and go dead a few weeks later.
I guess I'm still not getting it... I mean I monitor laundry and dryer. Why worry about time between alerts? Same with a sump pump. Sure get notified WHEN it goes off but why monitor time in between? Not arguing, just trying to understand the actual WHY...
This is what I do. It’s how I figured out why one of my bathroom fan automations was a bit wonky - one of my Aqara H/T sensors is oscillating/going bad (only the humidity, temp is fine). I also used it e.g. to balance my many line thermostats around the house when Away. Et cetera.
Not sure if this is exactly what this thread is about, but I wish there was someway to know when a device drops off the network.
I have a Zigbee sensor on my mailbox that lets me know when I get mail. It has worked great. We don't get much mail anymore so it can go days without sounding. Yesterday I realized it had been quite a while. Looked at the events and it hadn't shown anything for several days. Went out to the mail box, end of driveway, and there was mail but no alert. So I replaced the battery. When I did the indicator light started blinking which means it was in pairing mode. I had to re-pair it to get it to work. There was nothing wrong with the battery as it turned out. So have no idea why it would have dropped off the network.
You mean like a built in device watchdog of sorts? I'd love that. Right on the devices page, another column for how long a device has been non-responsive.
If it is raining outside and time between on/off for sump pump exceeds a threshold that indicates a failing pump or float switch. You could also monitor compressor run times on appliances/HVAC to know if its failing too.
I get it, edge cases, but still useful information.
I'm thinking something like mashup of that app and
The second app requires having the healthStatus capability. I could see something like the new ZigBee status feature for the last message time being added to all devices by the platform to be used with that app. Then the usage tracker features of how long something is on an active state.
I am going to share my sure to be unpopular opinion. I do not want the platform tracking devices. Sure, having the data points available for users to do it on their own is great but I'd rather it not be built-in.
A major reason I jumped to Hubitat, over five years ago, was SmartThings' poor implementation of "Device Health". The platform deciding certain functioning devices were offline would render a significant potion of my house dumb. My wife wasn't pleased as I was working away from home 30 weeks per year and wasn't there to cycle all of the switches on a daily basis.
I am hesitant to ask the hub to do any more behind the scenes. Remember, there is a finite amount of resources in our little hub. I don't want to shorten my already pathetic reboot cycle (5 days) because of something else that eats memory. A couple of years ago I'd go about six weeks before the hub would get a little sluggish, but each shiny new platform feature has cut into that.
I'm paranoid that even the @thebearmay 's excellent Hub Information driver consumes resources and haven't been running it regularly. I imagine that self monitoring memory, etc, would be impossible without it, but I wouldn't even know if there's a way to remotely reboot or shutdown without it.
I'm not taking sides for or against the feature request (mostly because what part of it I would use already exists through some other means), but just answering this question.
Knowing whether the intervals between sump pump cycles are getting shorter or longer is critical information for us during a hurricane, or the 3-6" of rain we got earlier this month. I've got a whole section of dashboard dedicated to it. Is the soil saturated so much that the sump pump is running? How often? Is the soil getting more saturated, or beginning to dry out?
Getting this data from the sump pump is a proxy for keeping a close watch on the septic tank. We know from experience by levels of soil saturation just how the septic system is doing. I've got a camera in the septic tank (as one does) but monitoring this dashboard is a lot more pleasant.
Not the full mesh. You need something like an Xbee and it's software XCTU to do a full mapping. The hub will only show what it's aware of (devices 1 hop or less away). So if an end device is on a router and that router is going through another router, it will not show up in the hubs routing table.
So anything that shows up from this is those items that are directly connected to the hub? All the other devices are connected back thru those direct devices? Is that correct?
