Releases: idatum/unifi_tracker
v.0.1.2
v.0.1.1
v.0.1.0
v.0.0.9
Bug fix: Apply --sshTimeout arg value to timeout parameter of paramiko.client.SSHClient exec_command().
Optimization: Use local scope for Queue variable.
I recommend using the device_tracker.py --sshTimeout option to avoid potentially hanging on the SSH channel if the AP is rebooted (e.g. firmware update).
Also includes v.0.0.8:
Bug fix: Recreate paho.mqtt.client.Client to avoid ERROR:labtracker:SSL/TLS has already been configured. on MQTT disconnect/reconnect.
v.0.0.7
v.0.0.6
v.0.0.5
Added device_tracker.py options --homePayload
(default is "home") and --awayPayload
for MQTT message payload, corresponding to home and away presence. Starting with HA 2022.6, if you define your devices under HA's mqtt
platform instead of device_tracker
, you should use --awayPayload=not_home
.
v0.0.4
v0.0.3
-
Option
--sshTimeout
to explicitly set SSH connect timeout in seconds (float). -
Option
--maxIdleTime
to set AP client idle time threshold in seconds (int). Use--maxIdleTime
to check theidletime
field ofsta_table
and filter on clients that are below the given threshold. There are cases where I've seen a tracked client go out of range of the last connected AP yet still shows as connected for several minutes. I've been able to repro this case when a mobile phone goes out of range quickly (e.g. driving away in a car). If the mobile phone slowly goes out of range (e.g. walking away), it correctly shows as disconnected. Setting this threshold ensures the status changes in a more deterministic amount of time.