Restart your UniFi doorbell
Helps for a day… After the restart it sends requests to 2 times… Log file in Unifi app only shows 1 hit
Hmmz i have same issue, i though this was the solution 
I have the Doorbell pro but cannot set the led on or off.
Changing the following card to “Ja” or “Nee” and test it, doenst change the led even tho it doesn’t report an error.
What are the rights of the user what your using for the integration? View Only ?
1 Like
Restart Protect and your Doorbell, I don’t have this?
What for ALARM do you have created?
Didn’t think about that, that was it … Thanks
It looks when protect has an update a restart of the app is useful… i have no issues at the moment 
I use the fingerprint scanner. It worked completely as expected until 3 days ago.
However, now the action is no longer recognized by Homey.
I have done the following things
Doorbell restarts
Unifi protect app on the homey restarts
Dreammachine pro restarts
Reinstalled the app on the homey.
Unfortunately, none of these things helped. Do any of you have any ideas?
Problem solved
Downgrade Protect software version from 5.2.39 back to 5.1.87
Fixed in latest test version
4 Likes
thnx.
I was locked out of my home after Protect updated itself.
Concerning Smart Detections and “when triggering” intensity
Protect 5.2.42 was released tonight(today) and it made an issue (re)appear:
- “[flowxxx] has been disabled because the Flow executed too many times.”
Spec:
- HP 2023
- Advanced Flow using when “[Specific Camera] An Object was detected” card.
- One or more of those when in same flow
- NVR PRO
- A mix of cameras in the system
Timeline:
- All flows using the when were disabled this morning when cameras detected.
- Proceeded to test only one specific flow with only one camera. Immediately flow disables.
History:
- I had this issue before when using the [any camera] Object was detected when card. Can understand lot’s of triggering then when many cameras are present with high traffic.
- Switched over to [specific camera] Object was detected when card and spread into multiple flow and the flows stopped being disabled.
Timeline example
Just this simple thing disables immy from one detection.
This is what i have been using successfully for a longer period.
Some cameras but not very big system.
Hi, It seams that 5.2.42 version break all integrations. Somthing has been change on the UNIFI side. If I go in to the user account in UNIFI the user password is blank and is not possible to save a new password it just returns blank ( I use a local account). In Homey it just says that the user credencials is wrong, and can not log in to the user account. So i think it is a UNIFI issue…?
Do you have the new test version installed already?
https://homey.app/nl-nl/app/com.ubnt.unifiprotect/Ubiquiti-UniFi-Protect/test/
1.7.6 - 20 jan 2025
Fixed Websocket problem because an change in latest Protect version.
Thanks, installing the beta version did the trick! A tip for other users, editing your account details from an browser instead from the app, at least if you using Android. I have issues to making it to save my settings. Could only be me, but if someone experience the same problem…
Unfortunately, it has stopped working for me as of today. I receive the message: “Credentials are invalid.”
I am using the Ubiquiti UniFi Protect app on my Homey, version v1.7.6, and the UniFi Protect app itself is on version 5.2.42.
Would you happen to know what could be causing this issue or how I can resolve it? I’ve double-checked my credentials, but the issue persists. Any guidance or troubleshooting steps would be greatly appreciated!
2 Likes
Hi ,
The app crashes after 2 Sec . If I do the credentials check it returns a success . Running latest bèta version of this app and up-to-date unify .
Please see App crashes after startup within 2 sec · Issue #23 · steffjenl/com-homey-unifiprotect · GitHub
Thanks
Hello, I’m seeing this error when trying to update Night Vision mode on one of my AI Pro’s:
Error setting Night Vision mode: Error: Failed to PATCH url: /proxy/protect/api/cameras/obfuscated(status code: 400, response: {“error”:“There was an error updating the camera.”,“validationErrors”:[{“instancePath”:“/speakerSettings/ringtoneId”,“schemaPath”:“#/properties/ringtoneId/type”,“keyword”:“type”,“params”:{“type”:“string”},“message”:“must be string”}]})
Could this be an issue from my side or is this something that they changed in their API?
