I noticed this also. Six iPhones here report Not Home while Connected is true.
There is an issue with the new approach to caculate whether device is at home or not, working on that
1 Like
I have exactly the same problem.
Does this require EdgeOS 2.0? I keep getting an invalid credentials error and after checking with Postman I don’t get a beaker.session.id cookie. Just PHPSESSID and X-CSRF-TOKEN. I’m running 1.9.1.1.
Thank you.
I have only v2, if you would like, I can send you list of URLs to provide me response for comparison,
Maybe I’ll be able to support your version that way
2020-05-01
Fixed bugs:
- Fix device_tracker didn’t work correctly. It is always displayed not home (reported by @doors.sl @doubleUS @robfish )
Implemented enhancements:
- More enhancements to options, ability to change setup details
- Support new translation format of HA 0.109.0
- Added main.py to root directory for debugging
1 Like
Hi bar! Thanks for you great job!
Works like a charm!
Bar,
Do you know how long it takes for the device to appear offline or not home?
Because I notice that it takes a long time for the device to be identified as offline after being disconnected.
Is there any way to improve this recognition with some configuration on the router itself?
Basically it suppose to work according to what you see in web UI of EdgeOS
It’s about 30 minutes from the router, to improve it I need a full day to monitor behavior of multiple devices or reverse engineer the code of EdgeOS,
I will get to that in 1-2 weeks
From Ubiquiti support center:
Note that by default, the DPI engine recycles data after 30 minutes of inactivity. However, the DPI engine still retains data for any combination of host and application that passes traffic again within 30 minutes of inactivity.
If it’s by defualt, there must be a way to change that default…
1 Like
If you cannot overcome this problem it will render the device tracker useless which is a real pity because it was looking like a really good custom component.
We appreciate you work on this.
1 Like
I can return the previous functionality (with adjustments) that measures the traffic (tx/rx rate above 0 bps) and based on that decides if it is online or offline, WDYT?
If it works that would be great.
Just updated the custom component and all old eneities binary_sensor.edgeos_device_xxx became unavailable and new ones binary_sensor.edge_router_device_xxx were created. Was it intended?
Done it, I will release it later, need to test few hours
1 Like
it’s based on the name you’ve set, is that the name you entered (should be the same as the title)?
After some digging through the changelogs it looks like they moved to a python based UI in 1.9.7, so I upgraded to latest (1.10) and it all works now. So I would suggest adding 1.9.7 or so as a minimum required EdgeOS version.
Great, will add that to the validation checks when adding the integraion with proper error message
Thanks
2020-05-02
Implemented enhancements:
- Improved device tracker is home logic to consider traffic instead of just DPI report
- Version validation upon adding new integration (Required at least v1.10)
I updated this custom component (and restarted HA) but my device tracker still shows true (and activity) even with the phone off.
Do I need to uninstall the EdgeOS component and reinstall it?