As far as I can see, only version 1.9.6 is marked as a test version — the others don’t have this label.
However, in reality, my app is not updating from 1.8.17. I’ve already restarted the app, rebooted Homey, and even tried downloading it manually from the non-test page, but no luck.
Also, in the changelog (even in the background of the screenshot), the latest visible version is still the same.
Could you possibly help me with this?
Thanks a lot for your support so far!
You need to install it from this page:
Ok, so just to clarify — there isn’t any 1.9.x version publicly released yet? For me, 1.9.5 would already be perfectly fine.
Thanks!
No, when a test version is updated, the test badge in the changelog gets removed from the older versions (even if they were never promoted to Stable)
There seems to be an exception for apps that have not had a live version and only test versions. Then the test badge is displayed next to each test version, e.g. the Universal Tuya app:
Yes, correct. Apps with no stable version show a test badge for all versions.
I moved to the 1.9.4 version of the Unifi app, and everything was working perfectly. But now it seems 1.9.6 just came out, and that seems to have broken the Chimes
Long-press on a chime and we see this
I saw the changelog for 1.9.5 was
Fix endless loop driver search and broken sendTestTone to chime.
But that was working fine - for me at least. I have flows that were sending test tones and they were working.
This week I get new UniFi Chime POE devices, after that I will test it out and make a fix.
Also will it possible again to set the volume. Also for the doorbell it self.
Tomorrow I will look at the new G6 Entry Pro with NFC and Pincode.
The problem with the G6 Entry Pro is that UniFi does not send the user id anymore and sends now every scanned NFC card as websocket message.
Has anyone tried the G6 Entry (not the pro) already with the app. Thinking of buying one to replace my Homekit doorbell but I want to make sure that at least I can send doorbell alerts to the rest of the house.
I tested today V1.9.7 and can confirm that the chime volume is now updated correctly based on a flow.
Thank you for your support.
My Homey Pro 2023 is connected to my Unifi NVR.
I have three cameras.
If i right-click on a camera in the Homey device overview, open the livestream (to the right in the browser) Right-click on the livestream, then “open in a new tab”. I can see the live direct in a tab. With the latest picture if I refresh.
If I copy that URL and open with another browser, Then I am able to see the livestream.
So thats means that the livepicture is possible to view without any credentials? Yes it would be hard to match the URL. But still?
I have tested the URL in multiple browsers, and I am not logged inn to my Athom Account.
My app was automatically updated to v1.9.8.
Unfortunately it broke my camera view on the dashboard. The widget shows : “camera not available” for my G4 Doorbell Pro. It has always been shown before in the dashboard.
I’ve tried a rebooted Unifi and homey, no results.
When I edit the camera widget I can see all my other cameras to pick from, but the G4 Doorbell is no longer listed as an option in the widget 
Can you send me the status tab screenshot to me DM?
Hi there,
I have a Unifi Doorbell Pro G4 and my Nuki Smart Lock Pro connected to Homey Pro.
I have a simple advanced flow using the flow cards “A fingerprint was identified” and “Open Smart Lock”, so that people with registered fingerprints in the Unifi protect app can open the door.
Over the last weeks I realized, that even if a fingerprint is not identified and my G4 Doorbell Pro displays “unidentified fingerprint”, the smart lock still opens the door!
This is quite new! I used this flow over the last 1,5 years without any issue so far.
I already restarted the Doorbell Pro G4, the Homey Pro as well as the CloudKey+ that is used. Furthermore I re-did the flow but nothing changed. Any fingerprint can open the door via smart lock even if not registered in the Unifi Protect app.
Maybe someone has an idea what I could try?
Kind Regards
Matthias
Can you try the test version?
Hi @ObelixNL ,
I’m really curious, did you already find out something that might help solving it with the NFC cards on the G6 Entry Pro?
Kr. Arlon
Not yet, for now you can use the ‘unknown nfc card’ because protect is not sending the user id anymore with the websocket on the G6 Entry
