I have a similar issue, getting 401 from the console for both Protect and Network apps. Verified credentials several times and they are fine. When I manually try to sign into the homey local account, I get this message from console:
You’ve reached the login attempt limit. Please wait a few minutes before trying again.
Is there some sort of limitation on how many login attempts you can do?
Also having problems with only receiving a fraction of the Smart Detection events. This worked a while ago, but stopped working some time ago.
I have created a test flow that logs all Smart Detection events and also another flow that logs some motion events on selected cameras. All motion events seem to work fine, but only very few Smart Detection events come through to Homey, even though they are all displayed correctly in Protect. It’s like 1 out of 10 that comes through.
Using a Homey-only user in Protect.
If it has any relevance, I’m running Protect v4.1.53 on an UNVR.
I don’t know if this problem has to do with some update in Protect or in the Homey Protect app, but it no longer works as expected.
Edit: On the device pages, I can see that smart detections has been triggered, but it did not trigger a Smart Detection Event flow. So I think the problem is in the app.
Same here. Unifi Protect updates to 5.0.34 and smart detections in Homey are broken again. Weird thing is in the camera I can see the smart detections date and time and the smart detection score, but it doesn’t trigger the flows with smart detection cards. Maybe unifi fixes something on their side because the 5.0.34 release notes say:
Bugfixes: Fixed the inability to enable Smart Detections.
And the workaround made in the homey app last months is broken now, while the old stable version of the homey app would work again now Unifi fixed their stuff?!
Hey,
it would be nice to have more values gathered by the camera in Homey available, e.g. current lux.
This avoids to install more sensors.
Thank you very much!
Since the flow triggers of smart detections don’t work anymore, I made a workaround with the smart detection score as a variable. Works as a charm and without any delay!