Was offline from 8:36 to 8:53
Try removing the "/login" from your endpoint URL and add the port number instead.
Thx, that fixed it
IMPORTANT UPDATE FOR ANYONE USING THIS DRIVER:
I have posted a stability update here:
This is a critical update for anyone using this driver. It puts a timeout on the http requests the driver makes. (Timeout was not a part of the Hubitat http api at the time I initially wrote this driver.)
So if I understand this correctly, in a round about manner, I could use this as a trigger to tell me when my home WiFi has dropped out.
I have a separate WiFi router that occasionally locks up and the WiFi dies. All wired devices are not affected. HE is not affected.
so.... If I use the "HTTP Presence Sensor" to constantly ping a SonOff device I have, then if it goes uncontactable it'd likely be because the WiFi is down and I could then power cycle the Zigbee power outlet that feeds power to the WiFi Router. Rebooted router = restored WiFi
That should work, right ?
It does exactly what I thought it would and I've now got a "recoverable WiFi" setup.
Big thanks @jwetzel1492
IMPORTANT UPDATE: HTTP Presence Sensor can now be installed from Hubitat Package Manager. This is the best way to make sure you keep up-to-date with bug fixes and new features.
In your code on line 63, your showing that wifi is checked every minute.
I'm not a programmer, but I'd like it to run every 5 minutes. Can I just change it to
runEvery5Minute(refresh) and do I have to change
Also, in the logs, is it showing when the Wi-Fi was pinged and if there wasn't a change you won't see (on) ?
Yes there is a command for running every 5 minutes. Note there is an ‘s’ in minutes.
For anyone using this HTTP Presence Sensor with my app Combined Presence, I have just release V2.0 of Combined Presence. The best way to get the update is to install via Hubitat Package Manager, but you can also install directly from GitHub.
It should be fully backwards compatible and not break any existing combiner instances.
The most important update is the new "Standard Combiner". This instance has the optimal logic for detecting presence of a person using multiple geofencing and wifi-based presence sensors. You don't have to think about the boolean operations involved. It just does it the best way based on the performance characteristics of the different sensor types.
Can i use this app in my android phone ?
if yes. How ?
thanks for help.
Try this driver instead:
Despite the name, it works for most android users as well.
The instructions for setup are in the first post (just like in this thread ).
Is there an analogous driver for HTTPS?
Devices that present a 'legacy' authentication prompt are not being detected correctly:
Happy to share information from Firefox's Web Developer feature but not sure what's needed to fix this.
My initial thought is that any endpoint with an auth prompt is not a good candidate for using this driver. That said, maybe it should be a good candidate? But I don't have any extra devices suitable for testing this. If you modify the code and can make it work, please send me a pull request and I'll incorporate it.
This Driver works great, but not on all devices.
I have been working on presence sensors so I can detect when power is down. The problem I´m facing is that it detects some devices, but it´s not detecting two Raspberry Pi´s on my network.
If I ping both of them, they are detected, but the driver does not detect them.
I am trying to use this for an avr I have that seems to drop offline. When it drops offline a power cycle fixes it. But the driver is reporting not present when it is online. The avr has a webpage at its IP i am pointing the driver to on port 80. Anything I could be doing wrong, or is this the wrong application for the driver?
Try web pinger. I think it might work for you, it's in HPM.
THANK YOU! That's exactly what I was looking for! Seems to be working as I was hoping
Just a note. I have an onkyo tx-nr575 and it doesn’t actually drop off line (in my case) but the telnet connection just gets screwed up for some reason.
I noticed it I hit “initialize” on the driver page it brings it back. I haven’t debugged further and frankly I don’t know if I am capable to do so. I tried automating the initialize to once a day and it wasn’t enough, so for now, every time my time of day mode changes, it hits the reinitiallize command. It’s kept it connected for the last 3 weeks or so.
This may sound really stupid, but how do I figure or what end point to use?