[Request] last seen / triggered time

[ks2018ks]

Hello, Any chance the last seen / triggered time [ago] could be could be displayed in the devices settings display along with the battery level?

[Thorarin]

While technically possible, I feel this would abuse the settings system somewhat.

Why do you ask? 😃

[ks2018ks]

"Why do you ask?"

• because it's routine / standard in Fibaro Homecenter which is what I am used to. It will allow me to see instantly whether the device is still communicating properly with the homey, and for example, how long a window or door has been left open.

"abuse the settings system"
How do you mean?

[mruiter]

Mmm i thought thats why insights is available in homey 🤔 Verstuurd vanaf mijn iPhone

…

Op 31 mei 2018 om 17:48 heeft ks2018ks ***@***.***> het volgende geschreven: "Why do you ask?" because it's routine / standard in Fibaro Homecenter which is what I am used to. It will allow me to see instantly whether the device is still communicating properly with the homey, and for example, how long a window or door has been left open. "abuse the settings system" How do you mean? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ks2018ks]

So did I, but's it's not fit for purpose. 'Insights' is a misnomer - It gives no insight at all - not even data labels or a scale, and of course for that, you have to go to the insights area, scroll lots to find your device, try to work out what it means, or else export to some reporting tool, etc. I'm talking about something much simpler, at the point where it is relevant. For example. You check your room, and see that the temperature is low but before concluding your heating might need adjusting, you can see the window has been opened 3 hours ago. Or, you're wondering if the device is still working properly because something happened or didn't happen as expected and the battery indicator is suspect. You can just look at the last triggered time - if it says 'x weeks ago' but you know it should have been triggered since, you can begin to diagnose. This is how it is in Fibaro:

[mruiter]

I think the best place to slam on the door is at Athom in Enschede . The new app already has something in place. Only iTs still static fixed at 13:37 for a year of Athom devtime now. The web interface is gonna be dropped soon so ask them for the updated working app and you Will have youre wishes . Dont forget to say a lot of thanks to Thorarin for the updated sdkv2 app . Lesmateriaal not forget . You can demand everything you want but its all free work of a community member Verstuurd vanaf mijn iPhone

…

Op 31 mei 2018 om 18:15 heeft ks2018ks ***@***.***> het volgende geschreven: So did I, but's it's not fit for purpose. 'Insights' is a misnomer - It gives no insight at all - not even data labels or a scale, and of course for that, you have to go to the insights area, scroll lots to find your device, try to work out what it means, or else export to some reporting tool, etc. I'm talking about something much simpler, at the point where it is relevant. For example. You check your room, and see that the temperature is low but before concluding your heating might need adjusting, you can see the window has been opened 3 hours ago. Or, you're wondering if the device is still working properly because something happened or didn't happen as expected and the battery indicator is suspect. You can just look at the last triggered time - if it says 'x weeks ago' but you know it should have been triggered since, you can begin to diagnose. This is how it is in Fibaro: — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ks2018ks]

@mruiter, I make no demands, only requests

[mruiter]

But i did not see any thank you to the dev het ;)

Here is the pic btw

[ks2018ks]

Well this is a good example. In mine, not only is the app time wrong, the window days the contact alarm is triggered when in fact it's not and the window is closed, so possibly the device lost contact when it was open but the status remained. This is exactly the use case I was thinking of. If the 'last triggered' time/date was accurate I could work out for sure what is going wrong.

[mruiter]

The thing that is going wrong is that Athom Made this value static . You Will see the same time on every device on homey. Thats what i was saying that iT would be best to bang on the door af Athom at support@athom.com that the release a new version of the app. This one is already half a year old and the broke promise after promise in releasing a update Verstuurd vanaf mijn iPhone

…

Op 31 mei 2018 om 19:42 heeft ks2018ks ***@***.***> het volgende geschreven: Well this is a good example. In mine, not only is the app time wrong, the window days the contact alarm is triggered when in fact it's not and the window is closed, so possibly the device lost contact when it was open but the status remained. This is exactly the use case I was thinking of. If the 'last triggered' time/date was accurate I could work out for sure what is going wrong. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Thorarin]

Hmm, "Turned on since" is not exactly the same as a "last seen", but I agree that ideally this should be solved in a generic way by Homey itself.

Adding to the settings would be a hack. Customizing the card in a way that it would be like Homecenter is not possible as far as I know.

Strips should report in at least once every 24 hours (default setting), if it doesn't, the driver could in theory do one of the following:

• Send a notification. Requires extra permissions.
  Personally I don't even look at all the Homey notifications; way too many of them.
• Force tamper alarm or battery alarm ON
  This is something flows could respond to; you could have all the lights in your house flashing red until the situation is resolved 😉
• Set the device as unavailable in the UI

The latter is perhaps a bit drastic though, since you can no longer access some of the device's UI.

It's a bit tricky to get right, and it wouldn't address your "how long has the window been left open" question for example. I'm not convinced yet it's worth the effort to be honest.