60001 Is not an valid ip address
Hah yes i know, i did not mention the ip adress just wrote âip addressâ. I put â192.168.1.120â at ip address. So I visit 192.168.1.1200:60001 in my browser to connect. But when I fill that in the homey app settings it is not working
Can you send an screenshot from the settings page?
you write that you acces your server at 192.168.1.120, but in your screen shot you have 192.168.2.160 is a big deference.
Standaard acces to you server is at port 443, did you change it to port 60003, I donât think so.network
Ok now I see (all so read your first part) you have your manager running in a docker on your NAS
If you acces your unifi manager at the NAS you use a internal nat rull.
And all so in this i see that you type other info then you use in the screen.
If I translate your info then you must use in unify config of homey the next info:
Host : 192.168.1.120 (you use above a other but use the same ip and port how you acces direct localy)
Port : 60001 (and not 60003 you use above)
Why you acces the
Is the user âHomeyâ a local user on your Server manager? No admin rightâs read acces is only needed.
Just some info to veryfy
anyboddy has the same probs?
after finaly getting it to work it crashes evry time
CPU Warning Limit Reached
help :s
Hey all,
So I appear to have a similar problem to Menno.
- Running UI Network 7.5.176 in a Docker container on my NAS. IP 172.17.35.72, port 8443
- Homey Pro (Early 2023, 10.1.4) IP 172.17.35.162, connected on wired Ethernet
After entering the details, and doing a âTest user dataâ it comes up with the same error message as Menno has. However, when ignoring that and just saving the info, it comes up with a different message if I visit the âSitesâ tab.
" Error: connect EHOSTUNREACH 172.17.35.72:8443 "
So looked like a network issue. I put my Mac in the same VLAN as Homey and was able to access the UI manager without issue from browser.
I then activated the SSH Sandbox on Homey to confirm connectivity from there; [also no issue, I can ping the host and telnet to the host on port 8443, everything comes up just fine so it seems that the app (or Homey?) is choking on something else.] â strike that I missed the fact that I dropped back to my Macâs console and wasnât testing from Homey 
homey@homey-pro-sandbox:~$ curl https://172.17.35.72:8443
curl: (7) Failed to connect to 172.17.35.72 port 8443: No route to host
So there is a network issue after all, now just to find a way to correct.
Thanks,
Matthieu
Hi @ObelixNL,
I have a small question, hopefully, you can help me with it. I use the âUbiquiti UniFi Networkâ app to set if someone is home or not. I also send a notification and log this. In the log card I use the TAG âverbindingstatusâ (connection status). As result it gives an true (v) or false (x). When I do not add the small delay of 1 second the value has still its old or previous status. It is not already updated or not fast enough. Is it possible to add a TAG âStatusâ directly to the trigger card which can than be used instead or is it possible to look into the app code if the TAG âconnectionstatusâ can be updated more quickly? It happens for both trigger cards (connected and connection disconnected).
Many thanks.
Best Regards, Hugo
Just for reference, I found the issue (I think). Homey has a very broad network route for docker which overlaps with my server VLAN and as such the packets never leave Homey.
homey@homey-pro-sandbox:~$ ip route show
default via 172.17.35.129 dev eth1 proto dhcp metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.17.35.128/25 dev eth1 proto kernel scope link src 172.17.35.162 metric 100
I have reconfigured my UI controller to be in a different VLAN and the app now works fine, Iâll raise a ticket with Homey to see if they can provide a way to sort this out. Simply adding a static route isnât allowed it seems 
Hello all,
I have been a Homey user for a long time and have always used Heimdall in the past as an âalarmâ in the house. The alarm went on and off with presence. I (still) use the Unifi app for presence in the house. The Unifi app registers my presence and absence perfectly, I can also see that in the app. But since the app changed (I think about a year ago, maybe longer), the âlast connection lostâ option as the IF option does not work in my opinion. At least it does not trigger a flow when the last connection is broken. I never took the time to fix it until now there have been a number of break-ins in the area. I know that a Heimdall alarm will of course not prevent this, but it gives a somewhat more reassuring feeling than having nothing at all 
.
So my question is, do Unifi users recognize themselves in the above? Or does it work for you?
With the âlast connection disconnectedâ I assume that it concerns the last connection of the devices that are linked to Homey, so not other devices that are connected to Unifi (outside Homey). That would also be strange, because WiFi and internet continue, of course.
p.s. I am sure that no device will remain secretly connected. All tiles are then inactive, so to speak.
In addition, I really prefer Unifi over other presence and absence functions. So hopefully we can get it working again. Below are the flows I use as an example.
Iâve translated this message with google translate, so maybe some sentences doesnât make sense. But i already asked the question on a Dutch facebook group, and was to lazy to type it again in English. So if something not clear, please let me know 
1 Like
Hello UA84, you are right. I have the same issues. First connected or last lost does not trigger a flow. Nothing happens. It is a pity, as I use this for switching on and off the lights. When this worked with the old app was more reliable than an PIR device. As if you sit still the PIR device thinks nobody is in the room.
1 Like
Hmm thatâs really a shame. Why does it give the option for these then? Because in my opinion they are the most important options.
Is this already known to the developer of the app? @ObelixNL
Or does someone has a work around flows, maybe with variables? I was thinking about it, but if it isnât triggering any flow, then variables is also not possible is it?
Thank you 
after reinstall 3 times it worked whit no problem, dont know what happend.
Exact same problem here except in my case I use the trigger First device connected and last device disconnected (all APs). I think something is not working. When I let it do a flow with specific devices connected/disconnected the flows do work. @ObelixNL can you take a look please?
I use variables so I can use these in variable flows as a starter or a check. I have a variable called âanybody homeâ which is a yes / no. If none of our phones are connected to the Unifi network, the variable is set to ânoâ. This also gives me the opportunity to overrule the setting when a guest (like a nanny) is in our home when weâre out.
1 Like
Yes, but I think you can not do this per separate accesspoint, only for the whole wifi network?
To be able to to this per accesspoint is the problem I face.
Thank you for your answer.
I thought about that one, but donât you need the same trigger function of the app (last connection) for the variable to work?
Can you maybe share your flows? Because i really want to use this app and not another app, like smartpresence. But this is for me the last try.
Thank you!
you can determine on which endpoint a device is connected , the option i use is :
when roams to AP
and
AP is not DeviceAP (created a variable in homey for each telephone)
then
Set DeviceAP to AP
in that way i can track where telephones (and thus people) are located in the house
it works very accurate here.
next step is to execute flows when noone is at a floor and the lights are on , for instance.
I have a Poe device that needs to be rebooted after every udm pro update, would it be possible to add support for detecting if a firmware update for the udm is done and add support to restart a wired device (if itâs using poe)
Can you implement the 2FA feature in the app?
This since Unifi is going to require us to enable 2FA as of july 2024.
