I don’t have an iPhone and this isn’t a parent/child SmartApp so I’m not sure what you’re referring to.
Same issue here, immediately following the IOS update Simple Device Viewer no longer works.
Are you on the latest version of the device handler? I just updated the top first to reflect the latest version of GitHub.
What happens when you try to open it?
Are you running into multiple instances like the other person reported?
I’m on the latest and it works fine for me on latest iOS version.
Yes, latest 1.6.3b and a single instance. When clicked I get a quick circle and then nothing. No info in live logging either. I suppose I can remove and re-add and see if that works. Just odd it happened after the IOS update.
I just looked through the update release notes and it sounds like some users are having problems with other SmartApps too.
One user reported that restarting the iPhone fixed the problem so you and @Automatic00 might want to try that.
Thanks, but restarting didn’t work so I dropped back to version 6 and that didn’t work either (same results as above), I ended up reinstalling the latest and I appear to be back in business. Odd, but such is life sometimes. I appreciate your help.
[RELEASE] Simple Device Viewer 1.7
New Feature Improves Last Event Time Reporting!
Some devices silently report things like the battery level at regular intervals. Those events don’t appear in the device’s event list so they can’t be used to determine the device’s last event time.
This version has the new option “Advanced Last Event Check Enabled?” in the “Other Settings” section that works around that problem.
When this option is enabled, it retrieves the time of the device’s most recent event, like it usually does, but if it’s outside of the threshold it checks for state changes within the threshold.
It can detect if any of the device’s attributes have changed within the threshold, but it can’t determine the actual time of the change so it reports the threshold time instead.
Example:
You have a smoke detector that silently reports the battery every 8 hours and you tested it 2 days ago.
If you had the Last Event Threshold set to 12 Hours, you’d end up receiving notifications because the only event the original check can see is the test from 2 days ago.
If you enable the new setting, it will detect that the battery changed within the last 12 hours so it will set the Last Event Time to 12 Hours and it won’t send the notification.
Warning:
Checking all of the device’s attributes for changes is time consuming so if you have a lot of devices that fall outside the threshold, it could end up exceeding the execution limit.
If that happens, you’ll see timeout exceptions in Live Logging and the Last Events screen probably won’t load so you’ll have to disable the feature.
The first post in this topic has the latest version of the SmartApp.
This is great! I previously had to exclude a lot of sensors that weren’t used much but now can add them as they should still report battery level. Do these now show up in the last event screen?
With the new feature enabled, devices that silently report things should show a Last Event Time within the threshold, but it won’t change which devices are shown on the last events screen.
You’re referring to the last 2, not the Nest devices, right?
What type of contact sensors are they?
One is a water sensor, the other is an open/close sensor. I was actually referring to also my Nest Protects as they do check in via @tonesto7’s Nest Manager, but I am not sure if you can rely on that capability. If you look at my Nest Protect’s logs, you will see in the IDE every few minutes activity:
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Last Parent Refresh time: (May 5, 2016 - 11:29:56 AM) | Previous Time: (May 5, 2016 - 11:26:51 AM)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Device Type Version is: (2.0.0(Current)) | Original State: (2.0.0(Current))
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Firmware Version: (3.0.3rc5) | Original State: (3.0.3rc5)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Testing State: (false) | Original State: (false)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug UI Color: (green) | Original State: (green)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: info alarmState: ok (Nest Smoke: Ok | Nest CarbonMonoxide: Ok)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Smoke State: (OK) | Original State: (OK)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug CO State: (ok) | Original State: (ok)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Battery State: (ok) | Original State: (ok)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Online Status is: (Online) | Original State: (Online)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug debugOn: (On) | Original State: (On)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug API Status is: (Ok) | Original State: (Ok)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Last Manual Test was: (Aug 19, 2015 - 5:31:22 PM) | Original State: (Aug 19, 2015 - 5:31:22 PM)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: debug Last Nest Check-in was: (May 5, 2016 - 11:19:58 AM) | Original State: (May 5, 2016 - 11:19:58 AM)
2df3aa5c-f756-447c-bb6d-830d17d37fd3 11:29:56 AM: warn -------------------------------------------------------------------
The nest protects don’t have the icon next to them so they are within the threshold and no notifications will be sent. The new check can see that there has been activity, but can’t see the time so it sets the last event time to the threshold time, which I’m assuming is 24 Hours.
If for some reason one of the nest devices drops off and there hasn’t been any activity within 24 hours, it will fall outside of the threshold like it’s supposed to.
If the Contact Sensor is a linear/gocontrol/monoprice sensor, I wrote a device handler that will make it check in regularly.
I also wrote/modified one for my Everspring Water Sensor, but since it prevents it from running locally, I’m not sure if it’s worth using.
Ok, makes sense now.
My water sensor and open/close sensor is a Ecolink Z-Wave Door/Window Sensor (DzWaveWZWAVE2-ECO) and the water sensor is Aeon Labs Aeotec Z-Wave Water Sensor (DSB45-ZWUS). I assume those won’t work and I should exclude them?
The battery and open/close reporting might work with my GoControl Contact Sensor DH, but the tamper alerting won’t…
I just found a bug that caused the last event time to show as N/A when it falls outside the threshold so you should upgrade to the latest version and see if those 2 still report N/A.
If you chose the device more than once on the “Choose Devices & Capabilities” screen and the device is outside the threshold, it will show up twice on the last events screen.
I’ll have it fixed in the next version.
I think the version I had was 1.5 and in my Smartapps it was called Things Viewer. After the last ST update that Smartapp will no longer open for me. I updated it to the latest version (I think) which I saw as 1.8. Since it will not open for me I cannot uninstall it from the ST app and when I go to the IDE to delete it that fails stating it is installed for a user. Any ideas how I can uninstall the old version SA? I update to the new version within the IDE and configured it and it is working fine but I still have the old ‘Things Viewer’ installed as well. I would like to delete the old version if possible.
If anyone has any thoughts I would appreciate it.
Sean