Having an issue with my protect / hubitat setup. Hoping someone can point me in the right direction.
I install the drivers, do the setup, and everything connects fine and talks to the protect API without issue. I setup a very simple motion test rule, pictured below. The first time it detects motion, I get an alert. However after the first alert, I never get alerted again. Nothing in the logs, nothing happens at all. It's as if it triggers and then goes into a permanent sleep. Any idea what might be going on? I've tried removing and reinstalling the drivers, its the same thing, the motions works the first time but never again.
Look at the Doorbell Events on the device page. Look in the "Triggered apps" column. Any time there is an active event you should see your rule in that column.
You can get rid of that delay too. The rule can run more than once at a time, so the delay won't do anything to stop being notified. If you are trying to debounce you'll need to use the private boolean or local variable to stop multiple notifications. The Notifications app can stop the excessive messages too.
Thanks for the reply. The issue is that there are active events up to a few mins ago in the protect side of things, but nothing is triggering on the hubitat side of things. Everything has been stale since 01/02 (when I installed the driver).
Are you saying that those events are the most recent? They're over a week old. If that's true then your issue is with the integration not the rule, possibly some sort of login issue. You should make sure you use a UniFi local user with no 2 factor authentication for the integration. And you should take further discussion to the main thread for better support:
Thanks. I did some more digging and I think I've isolated the issue. The way I have my devices setup is as follows - dream machine on ip x.x.x.1, and nvr on x.x.x.2. I do not have the protect installed on the dream machine, it's installed on the unvr directly. So in the integration, if I select dream machine and login, that would be wrong (I can login but it can't auth any protect stuff because it doesn't know about that stuff). So I pick other unifi controller...
With other unifi controller selected, i put in the ip for unvr, and the port. The login doesn't work right. I get an error about 403 auth key not found. I looked at the driver code and it looks like when you select other it goes to an endpoint without auth i.e. api/login vs api/auth/login. If I try curl to my unvr, with the ip and port I am using in the integration, I am able to auth without issue. I got the 403 by modifying the driver code and updating the endpoint. If I leave it as is, I get a 401 which makes no sense since I can login with the same creds and endpoint via curl.
Anyways, I'll do some more debugging and post in the other thread when I have some more info. Thanks for your help.
