I’m looking for something that reads the contents of a webpage and triggers a Vera action if specific content is found or not found. I’ve looked through all the plugin descriptions and it’s not clear to me if something already exists for this.
For those interested, I want to look at the device pages of my HD Homerun Primes and cycle power to the tuning adapters if they return status of anything other than “ready”. I have the power control handled. Just need something to read webpage content.
Awesome! That’s just what I needed. Seems to work great. I’ll know more when the first triggered failure occurs. One thing to note, I created two sensors. The first I started with a positive match, just to make sure it matched. The second I started as a negative match, and switched the first to negative match. On the one created as a negative match, the first run returned a status of “Valid response: no match”, but subsequent normal runs list status as “Valid response: matched!”. The one created as a positive and switched to negative always has returned “Valid response: matched!”. I’m pretty sure they aren’t triggered (green bars on icon), and shouldn’t be, so maybe it’s just a display issue?
Interesting. After moving mine to a 100 Mbps switch instead of a 1 Gbps, it is rock solid. (Along with a HDHomeRun Connect and an original HDHomerun OTA.)
I run a PING sensor, just in case, but I don’t see a need to monitor status…
Edit: Oh, I re-read your post, it is the Tuning Adapters you are worried about. I have one or two issues a year, but my TWC Tuning Adapter is reliable…
@strangely I don’t have UI5 to develop and test on at the moment. I bought new hardware (Plus), and plan to retire my Vera3 to my test bench for multiple versions including UI5, but with the uncertainty around 3015 I’m waiting to see how that shakes out. But, if it can be made to work on UI5, I will get it there.
If you are on Android, and use Tasker, you might be able to do this with some of the AutoApps plugins. I’m thinking that AutoWeb & AutoVera could get it done. I have no experience with AutoWeb so you might want to check the developer’s G+ page: https://plus.google.com/u/0/communities/110193399489813640793
Yeah, I have two Homeruns and two TAs from TWC (now Spectrum), so twice the problems. I usually end replacing one every couple of years, because it starts to fail almost weekly. It seems like one or the other goes into bad mode once every month or two. I don’t notice it immediately, because it’s round robin on which Homerun/TA gets selected to tune, and as long as it doesn’t require a signal switch, you can tune fine with a broken TA. The great part of getting this monitored in Vera is not only that I can control immediate reboots of the devices (before a recording failure), but also that I can have a persistent log of which unit failed, exactly when it failed, and what other correlating factors may have been occurred at the time (power failure, ambient temp or humidity change, UFO sighting, etc.).
Really happy to have this app. There are plenty of other pieces of internal web content that I’ll want to monitor and alert on. Even with the homeruns, I can now monitor and notify on them for things like available firmware updates. I can also make sure that other non-integrated but connected things with web interfaces, like water softener, are available online, and doing their thing. Sometimes a ping doesn’t tell the whole story which requires looking at the actual web interface. Not sure how I lived without the ability to monitor web content.
Appears to just be a cosmetic issue. Display is correct on initial check, but on recheck it appears to fall into a different logic branch and returns “Valid response; matched!” for a NOT monitor.
I have it set to check for NOT:
Tuning Resolverready
I simulated a failure by unplugging a Tuning Adapter, and it triggered and alerted, and recovered without a problem.
Actually, that’s correct (i.e. as designed). It is showing whether or not the pattern was found in the response. Whether the trigger happens on match or not match is separate issue. The state of the string match is displayed in the text, and the state of the trigger in response is shown in the trigger itself (and the device icon, which follows the trigger state).