Overview
Users will be able to ring the Tag paired to an Asset from a few different places in the UI.
Actions Menu
The users can access the Ring Tag action by selecting an Asset in the table and clicking the Actions Menu (⁝) at the top of the page
List Cards
When the table is minimized and the list cards displayed, there is a Find Asset button that will initiate the Tag ringing command. Note this is only available for Assets that have been paired to Tags.
Map Cards
When the users select an Asset on the map by clicking on the map icon, its map card will appear in the upper righthand corner. Within the map card, there is a Find Asset button that initiate the tag ringing command. Note this is only available for Assets that have been paired to tags.
Item Screen Dashboard Cards
When the users drill into a specific Asset, they are in that Asset’s item screen dashboard. Within that dashboard, they fill find the Find Asset button that initiate the Tag ringing command. Note this is only available for Assets that have been paired to Tags.
Find Asset Technical Implementation
Action Enablement
The Find Asset action becomes active when a paired Tag is within the proximity of a Gateway.
If the Tag is out of range, no button is displayed, and a notification informs the user that the Tag is not within range.
If the Asset is not paired with a Tag, no button is displayed, and the user is prompted to pair a Tag with the Asset.
Find Asset Action
When the Find Asset action is enabled, users can initiate it by clicking the Find Asset button.
Gateway Selection Logic
Once a Tag ring command has been initiated, the system checks for pending Tag ring commands any time a Gateway checks in. The ring command is sent or re-queued based on the following logic:
Within the first 15 seconds after the ring command has been initiated: Send to any Gateway that reports the Tag with an RSSI equal to, or greater than, -75
After 15 seconds: Fall back to any Gateway that reports the Tag with an RSSI equal to, or greater than, -95
The system waits for up to two minutes to check if a Gateway reports the Tag in its detection list. The users have the option to cancel the request during this time.
If no Gateway reports the Tag after two minutes, an error toast message is displayed, and the process returns to the initial state.
Gateway Sends Command to Tag
Upon receiving a report from a Gateway that contains the Tag, a command is sent to the Gateway to ring the Tag. The users are notified that the request has been sent and can start looking for the ringing Tag.
The Gateway should provide a confirmation of the command. If the command fails, an error toast message is shown, and the process returns to the beginning.
If 90 seconds pass and the Gateway has not sent a confirmation, the system provides a toast before returning to the start of the flow.
Gateway Confirms Tag Got Command
When the Gateway confirms that the Tag received the command, it is indicated that the Tag is now ringing.
After a 35-second delay (accounting for the time it takes for the Tag to stop ringing, plus a 5-second buffer), the process returns to the initial state.