Ties de Kock

I added a `source_name` field containing the hostname of the station in the body of the pushed events in https://github.com/ties/openwrt_hass_devicetracker/commit/33923eba0f32a07bece8da3ef1b8b861b3c12a6d. Will try to normalise this data in an AppDaemon.

@SaturnusDJ the `source_name` field is definitely working. I have not created the AppDaemon (or, what I planned later, modified hass) yet. My notion for how device trackers track presence differs...

> Today I uninstalled v0.1.1 and installed v0.1.4 and then manually copied the files in that were affected by the last commits. Uncommented the `source_name` field and gave it a...

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...

In addition, using this pattern may cause another issue. I have a set-up with two access points (with 802.11R) and the order of connects and disconnects may differ from what...

> Ah got a situation now. > Phone switched to other access point without disassociating from the original ap this time. So after a few minutes the original ap timed...

> @ties, you mean a master? Maybe set up one access point as such and the others just report to it. I guess there must be some functionality like that...

> I guess the solution is to add authority/client type devicetracker instances to this code where the clients simply forward all state changes to the authority and only the authority...

> Time machine backups over Tailscale 🤤 To clarify: This is currently blocked because it seems to require mDNS.

> Sounds reasonable. Given that this is all public (published) information I see no reason to enforce authentication. > > Do you see specific requirements from your end regarding the...