Handle 'trailing' disconnect when station roams in 802.11r setup #22
Comments
|
I added a |
|
@ties Did you get this working? |
|
@SaturnusDJ the I have not created the AppDaemon (or, what I planned later, modified hass) yet. My notion for how device trackers track presence differs from how it is implemented in hass and likely conflicts with how people would be implemented. I need to merge states at the device level, not at the person level. And I need a complex state machine (since the disconnect on AP1 can come after the join on AP2). I decided to wait for the person component to evolve. "Merging" presence states was moved to the person component. This will work for my use case if hass/the API got a way of expressing presence per MAC x per source instead of per type x per MAC. |
|
Coming back to the |
That is strange. Are you sure it is running the correct code? I do see the following in syslog: I do also see the |
|
Outputs: Nothing for me. |
|
Seems like the source name is not actually being sent. Maybe I introduced a
bug in the configurable source name.
…On Thu, 5 Dec 2019, 08:11 SaturnusDJ, ***@***.***> wrote:
Outputs:
Thu Dec 5 00:33:53 2019 user.debug /usr/lib/hass-tracker/push_even: build_payload 00:11:22:33:44:55 Mi_Hub.lan 99:00
Thu Dec 5 00:33:53 2019 user.debug /usr/lib/hass-tracker/push_even: post {"mac":"00:11:22:33:44:55","host_name":"Mi_Hub.lan","consider_home":"99:00","source_type":"router","attributes":{"source_name":""}}
Thu Dec 5 00:33:53 2019 user.debug /usr/lib/hass-tracker/push_even: post response [{"attributes": {"friendly_name": "Mi Hub", "icon": "mdi:home-plus", "source_name": "", "source_type": "router"}, "context": {"id": "09ff2f10c86d4cbc83f6bf7f3baba10f", "parent_id": null, "user_id": null}, "entity_id": "device_tracker.mi_hub", "last_changed": "2019-12-04T23:33:53.246467+00:00", "last_updated": "2019-12-04T23:33:53.246467+00:00", "state": "home"}]
~# cat /etc/config/hass-tracker
config hass-tracker 'global'
option host 'ip:port'
option source_name 'Nicerouter1'
option token 'token12345678'
option timeout_conn '99:00'
option timeout_disc '00:00:01'
...
Nothing for me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#22?email_source=notifications&email_token=AAGO7B7NDLVRZJAS75TQMUTQXBBJPA5CNFSM4GM27P72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF67XXA#issuecomment-561904604>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGO7BZCU3PIKSSKNJ47VBDQXBBJPANCNFSM4GM27P7Q>
.
|
|
Oops, a quick glance over the code shows me that I did miss renaming a variable. @SaturnusDJ let me know if 23fa712 fixes it for you. |
|
@mueslo that works! Via config and via commented out variant also. Great. Hope the multi router setup issue can be solved soon too. |
|
Good to hear that it worked! It has been a while since I worked on this. It definitely needs changes on the side of Home Assistant, right now MAC addresses are seen as unique while in fact the combination of |
|
hey Would it be possible to create a package and publish it? thanks a lot |
|
@andre-pt I was thinking to only use mobile app (iOS) now but it seems that app is also not reliable as sometimes it does not come up after restart of phone, etc. It is a painful fact that in some cases presence detection in Home Assistant is extremely hard to get reliable. Can still try https://github.com/gcobb321/icloud3 (Of course these two possible solutions would likely not work to detect if a device is on a specific floor or near/connected to a certain access point.) |
One way to implement this would be to send not the mac address but explicitly the device id made up of access point id plus MAC address. Then you would get N*M devices if you have N real devices and M access points. You would then be able to merge them in the Person component. However, this seems like a very unelegant, dirty way to do this. |
[As a user] when a station (mobile phone) roams between accesspoints, I expect the station to be 'connected' while it is connected to any of the access points.
At the moment the script sets the status to disconnected when the connection to the previous access-point times out (see logs below).
I consider a station to be disconnected when it is not connected to one of the access points. I will try setting "disconnect on low ack" again (but this causes problems with Archer C7 V2) to reduce the duration of this period.
I log to a remote machine. In these logs the following lines appear:
related to #16, #17.
The text was updated successfully, but these errors were encountered: