I'm having an error show up whenever the system tries to refresh the status of the phone.
dev:6422020-04-21 10:54:51.038 am errorgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Integer#div. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] on line 98 (refresh)
I reloaded from the github to ensure I have the latest code (was doing that all last night), but could have missed one.
Edit: Just saw above you mentioned the need to hit "save preference" on each device I have.
I just did that and will monitor.
I'm seeing this same error:
2020-04-21 08:42:39.086 am [error](http://192.168.0.51/device/edit/54)groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Integer#div. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] on line 98 (refresh)
Goes without saying, but Thank you so much for this app.
My Presence on HE has been 1000x more reliable thanks to this add-in as a factor in my combined presence.
Same here. It's an excellent app and now my Combined Presence routines are bullet proof. But the first thing I did was rename it to remove the annoying and unnecessary reference to Apple products lol
This driver has some customizations that are specifically for how smartphones behave. However, I also have a more general purpose HTTP sensor. You might give it a try.
LOL I did the same!! Mine says "Android Presence Sensor". I was doing some troubleshooting with support a while back and he says "I've never heard of that Android Presence Sensor app, but it threw an error in your logs". I had forgotten to hit "Save Preferences" after the last update.
Thanks
I am testing whether a Raspberry Pi is still on the network.
I dont think it has HTTP active and I was trying to encapsulate whether a ping responded or timeout...
I don't believe you can send true pings from Hubitat. At least I couldn't figure out how. However, if your pi is running anything at all that opens an http port, my http presence sensor has a good chance of working with it.
I've been running into an issue after updating to the most recent release of HE.
In particular the two drivers I have for this for my wife and me are getting stuck in either "present" or away.
I'm not sure how I'm getting stuck in away as I didn't have logs set when that happened. And I had to manually "refresh" to get into present.
It seems as if the device just stops checking after an HE upgrade, but I'm having a hard time proving this besides looking at the "last event" and how it aligns to my last HE update.
I figure out what the issue is, which isn't unique to this driver, but I do think it might be solvable in your driver.
In particular, this seems to happen everytime I upgrade my Hubitat to a new version. What I suspect is happening is if your 'scheduled' check overlaps with any of the downtown for Hubitat, a new scheduled check never happens, so the driver is stuck from that moment on.
That, or something about hubitat upgrades are nuking driver schedules in general.
Ok, I examined my code. If that is what's happening, it would be a Hubitat scheduler bug, and unfortunately I don't know of an event I could key off of to reset the schedule. I haven't verified the behavior you're describing though. I can try, the next time an HE update releases.