You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be handy to have the option to clock in automatically when a specific Bluetooth device is with range and clock out when it's out of range. Similar to the Wi-Fi feature, but for Bluetooth. Wi-Fi covers whole workspace so when I go to grab lunch or coffee, I am still within Wi-Fi range. If I could set up this to clock in when my work laptop is in range, it would be great.
Since our phones stay connected to smartwatches and Bluetooth earphones, keeping Bluetooth on might not be an issue. However, I think in order to check if the device is in range, the app might have to run Bluetooth discovery periodically. I'm not sure about the battery cost for this, and I'm also not sure if there are any alternative better ways.
The text was updated successfully, but these errors were encountered:
I am currently using Tasker to achieve this functionality, though it is not easy to setup and sometimes fails to trigger for an unknown reason. I would really welcome seeing this implemented directly in TWT.
What I would like to add to the request is functionality to detect Bluetooth beacons. Let me know if this idea fits in here or better into another issue.
It could be handy to have the option to clock in automatically when a specific Bluetooth device is with range and clock out when it's out of range. Similar to the Wi-Fi feature, but for Bluetooth. Wi-Fi covers whole workspace so when I go to grab lunch or coffee, I am still within Wi-Fi range. If I could set up this to clock in when my work laptop is in range, it would be great.
Since our phones stay connected to smartwatches and Bluetooth earphones, keeping Bluetooth on might not be an issue. However, I think in order to check if the device is in range, the app might have to run Bluetooth discovery periodically. I'm not sure about the battery cost for this, and I'm also not sure if there are any alternative better ways.
The text was updated successfully, but these errors were encountered: