[OBSOLETE] Device Monitor - Get Notified if Devices Stop Reporting

Thanks, app has been updated.

Thanks, that solved my error issue with the app too… lol

outstanding, I’m going to install this :slight_smile: is it possible to change your repo fork name to something other than SmartThingsPublic? I have 4 of these now - to find the correct repo I need to go to settings, find it, see which position it is in, cancel out, and then select that one.

understand this might break the link to folks who have already pulled from you - not sure.

I just renamed my repo in gitHub -
go to github

  • pull down the icon in the top right → select Your Profile
  • select the repositories tab
  • select your fork
  • click settings
  • change name
  • click rename
    go to smart things IDE
    smart apps
  • select settings
  • update the name of your repo

@pascal If I change the repo fork name, will it break every link posted that links back to my device handlers & smartapps (as well as those who have linked to my repo through the ide)? I have the same problem as you so I understand. I have a list of the repo names on my computer that I reference. It isn’t elegant, but I think the really, really, simple solution is for SmartThings to list the authors name next to the repo name in the drop down list. So, erocm123: SmartThingsPublic (master). I know others would like that as well:

@craig 1) I could probably implement this pretty easily. I’ll look into it. 2) I have actually designed it to work that way. I didn’t like getting notifications with a bunch of devices listed that I already new about. I figured I could always open up the app and hit refresh if I needed to go back and remember what wasn’t reporting. Maybe I’ll add full notifications as an option down the road.

1 Like

The thread you referenced adding authors is a better solution as it would help globally.

It shouldn’t break anything if you rename it.

Check out my two posts here:

FAQ: Github Integration How to Add and Update from Repositories

1 Like

Nice App, I actually started working on something similar last night. I agree with GitHub integration, I have 4 projects that use SmartThingsPublic, so updating is like a guessing game.

@erocm1231 Do you have advice for the setting of how long a device should be considered inactive? I’m not familiar enough with all the devices to make this determination. Many of my devices don’t do much for many hours.

Well, personally I have a couple instances of the app installed. One of them I set up for 12 hours. In that one’s config I added devices that communicate frequently and are pretty important. For example, I have smart vents that adjust throughout the day based on the temperature in each room. If a temperature isn’t being reported, it could cause problems.

The other instance is just set for 48 hours and it has devices that report less frequently and aren’t as critical.

3 Likes

I constantly get random devices reporting that it’s not reporting events even when they’re fine. Anyone else?

FYI:

@krlaframboise I don’t mind you pointing people in this thread to other Apps, but that doesn’t answer his question. If there is a bug in this app, I would like to know about it.

As for me, I do not have this problem. The app only has the ability to look at the events a device creates. So, if the device is not sending events, or it’s events are not getting recorded by the SmartThings system (SmartThings no longer takes record of repeat events by the majority of devices), then it will think the device is offline. So, you could have a device that is working perfectly fine that the app believes isn’t.

Anyway, for the devices you are having issues with, can you look in the events list for the device and see if anything is showing there?

I see, thanks for pointing that out.

That’s not quite what I’m seeing. It seems that it randomly selects devices as not responding. If I refresh it will choose some devices, if I hit refresh again it’ll be others. Seems I might have some issues with my system rather than your app.

Would this app work well for open close sensors on windows that are not often used. I am look for a deterrent to prevent certain young inhabitants in my house from leaving undetected. Unfortunately, he is smart enough to pop the battery on an open close sensor.

Ah! That’s what “Tamper Alerts” are for!

My Garage Door tilt sensor has a tamper detect (a little spring that flics and sends a tamper event when the battery cover is taken off)… I think one of my Z-Wave modules does too.

While it still is a good idea to track for inactive devices, it’s important to have the right solution to the particular problem. Gotta wonder if the Centralite contact sensors (etc) have tamper detection, but just not written into the DTH. Look for a little button that is depressed by the battery cover? I recall one in the motion sensor, but ought to look…

What would you recommend as a solution for a window/door that would sense it being open but also alert me if the unit is tampered with (battery removed). As I am relatively new to smart things, how do I automate tamper alerts?

I currently own the hub and a few of the Samsung motion sensors and open/close sensors but I am open to other ideas.

I just checked 2 of my Contact sensors, and they both have a “tamper detect” (battery cover removed) in the hardware.

This is Z-Wave:
https://www.amazon.com/Ecolink-Z-Wave-Window-Sensor-DWZWAVE2-ECO/dp/B00HPIYJWU/ref=sr_1_2?ie=UTF8&qid=1466541628&sr=8-2&keywords=z-wave+contact+sensor

The other is the standard SmartThings Centralite Contact Sensor.


As for getting it reported, the DTH and/or related SmartApps have to be modified or written to properly report and act on the Event.

####In the case of the first device (Z-Wave), for example, SmartThings definitely is capturing the Event:

####In the case of the SmartThings ZigBee:
No Event is shown in the Event log in the IDE! (Though I didn’t check “Live Logging” to be sure, nor have I looked at the source code).

So… as far as a starting point is concerned, the Z-Wave device is closer to being able to report the “Tamper Event”; and, if you wanted to be really lazy, so that it would work with any normal Contact Sensor SmartApp, we could modify the DTH to just report a “Tamper Event” as an “open” Event.

Otherwise, you have to add Capability Tamper Alert to both the DTH and any SmartApp(s) that you need to detect that Event. Really, we could do both (i.e., report Tamper and also claim the contact is “open” just to be sure!).

Using my DTH, the GoControl/Linear Door/Window Sensors can notify you if the cover is removed. The kits are on clearance at Home Depot, but most places are probably already sold out.

1 Like

The modification required to the Ecolink Z-Wave contact sensor (and tilt sensor, …) is pretty small, but again, SmartThings doesn’t offer Community Developers any incentive to make the change and submit for publication.