Description
The app is very lightweight and simply pings an IP address or IP and Port on a regular basis. If there is a response it sets the device as online but if the request times out then it sets the device off-line.
Using the app
When you add a device you can choose the method of either just specifying the IP Address/hostname or the IP/hostname and a TCP port.
In the Advanced settings of the device you can change the interval between polling and the time it waits before deciding it’s offline.
Kudos and big thanks to previous developers, which are credited also on the app page in the Contributors, namely Terry Hendrix and later Adrian Rockall.
Smart Presence is mainly targeted at presence detection via a smart phone and is much more feature rich. This app is a simple ping aimed at determining if a network device is available.
I believe this app was the predecessor and initial root of Smart Presence, also initially created by Terry Hendrix.
The original app was never updated by Terry from SDK1 so will no longer work on SDK3 and I have heard from a few users that they are missing the app after updating Homey to version 5 or later.
So if you just want to see if your PC or XBox is switched on then this app is smaller and easier to setup.
When it gets accepted by Athom i will make sure to test it out. I have the Community store version now but that does not work correctly with my setup. I cannot give you a log now however, as far as i’m aware
Marantz has a fixed IP, so does my router.
Same errors after restarting the app.
Disabling/enabling the app has the same effect.
A diagnostic report option is unavailable.
Maybe this is of any help.
IP only works fine, 3 devices (receiver, router an NAS).
Adding a port ping device, causes the app to crash.
I removed everything, then added one port ping device (NAS port 80).
It causes the app to crash.
So, from what I see,
IP ping = ok
Port ping = crash
It works fine up til now, i made a phone ping flowset with on & offline status messages.
Laptop LAN & WiFi connection monitoringworks perfect. So I can have a reminder to turn it off (I hate it when things turn themselves off hehe).
I will update the app, Adrian! Thanks for the quick fix!
I have found the tile dim / highlight feature to be unreliable in as much as it doesn’t always update when the tile is on view. Support say that is because the ‘uiQuickAction’ option that makes that happen is not meant for read-only capabilities.
To work around the issue I am thinking of changing the capability to an alarm so that the tile gets a yellow dot to indicate an alarm condition. However, to make that look right I would need to change it to a “Device Offline” status. Therefore, the dot will appear when a device goes offline and the capability will show:
and
I can keep the flow card actions the same so none of the flows will need to be changed and I can automatically migrate to the new capability on existing devices.
Sounds like a good plan, Adrian.
Btw fyi, after reading the new update notification, I just discovered the app had crashed. I don’t know for how long this has been.
Yesterday evening it still worked, after I added 22 IP and a few TCP devices.
Now running the latest version.
I will make a crash notification flow, that may come in handy.
This sounds so silly. Is it so much work to enable it for r/w capabilities while writing code… the strange world of Athom sometimes
Would you be able to give any specific guidance or documentation on updating these SDK1 to the latest? As I use an app Heatmiser which is an Athom app which hasn’t been updated and I’m looking to update.
As this is a simple app it only took a few hours to get the bulk of it done. But then I spent a lot more time tweaking and improving it, adding new features, etc.
I have had a reply from Athom and they can’t transfer the App ID over to me due to technical reasons as it has been deleted but is still registered.
Terry has been involved and, again, as the app has been deleted it is not in his account to transfer.
So to publish it in the Athom store I have to change it and submit it as a new app.
The disadvantage is any existing installations won’t upgrade to the new app and that means devices and flows will have to be re-created.
I’m really sorry for the inconvenience but it is out of my control.
What a bummer, but this stuff can happen.
No problemo for me to start over🙃.
FYI, the app didn’t crash again, since I reported one the other day. But the ram & cpu graphs aren’t what you want to see. I’m not complaining, but I just want to inform you about what is going on.
In the graphs you see the app from the moment I installed it, the crash (90MB), and the app restart I did last night.
So to be clear, it didn’t crash, but I had to restart the app due to the excessive ram usage
I hope this is of any use!
