There are times when a sensor on the account is currently not used and the administrator would like to remove the sensor from the hardware list. At some later time, the administrator may want to use this sensor for a different purpose, and restore the sensor to the hardware list. The Removed Sensor feature provides a way to do exactly that, so that unused sensors do not clutter up the hardware list but still retain their membership with the account.
Remove a Sensor: To remove a sensor, click the trash button on the edit sensor page and confirm your action. Removing a sensor is just like deleting a sensor (including the deletion of measurement history), except that the sensor remains attached to the account, and appears in a new Removed Sensors panel on the account summary page.
Restore a Sensor: To restore a sensor, click on the sensor in the Removed Sensors panel to go to the removed sensor details page. Then select “Restore” on the status toggle switch and save. In the Removed Sensors panel, the sensor will indicate that it is currently restoring until a bridge on the same account detects it and it shows up in the hardware list as a new sensor. Please note that if a sensor was in sleep mode to conserve battery, it could take up to 4 hours for the sensor to restore.
Stop a Sensor: To stop a sensor from restoring, click on the restoring sensor, select “Remove” on the status toggle switch and save. The sensor will stop trying to restore and will stay removed.
Delete a Sensor: In case the sensor needs to be deleted from the account permanently because it was destroyed or it will be used on another account, the removed sensor details page has a delete button that deletes the sensor completely. If the sensor is in working order, it may appear as a new sensor under the nearest bridge, possibly on a different account.
In complex environments where a sensor is in range of many bridges, a sensor may occasionally attach to a far-away bridge with a lower sensor load when a closer bridge with a higher sensor load is available. In this case, the sensor’s signal strength may dip into the two-bar yellow zone or the one-bar red zone. Bridges that offer signal strength with less than three bars should generally be avoided as this can lead to missed samples. The Parent Bridge panel on the sensor diagnostics page shows how a sensor’s signal strength changes relative to each bridge. Correlating the parent bridge with the signal strength will offer insight into exactly which bridges should be avoided.
Sensor blocking feature: The sensor blocking feature provides a way for administrators to fine-tune a sensor’s reliability by blocking sensors from connecting to bridges which offer poor signal strength. Sensor blocking can be done in two ways:
1. On any sensor details page, edit the Blocking Bridges panel and select bridges to which this sensor should never connect.
2. On any bridge details page, edit the Blocked Sensors panel and select sensors which should never connect to this bridge.
Sensor connect to at least one bridge: In either case, remember to allow each sensor to connect to at least one bridge in range on the account to transmit its data. If you accidentally block a sensor from all bridges on the account, a warning message will appear in the Blocking Bridges panel. Finally, be sure to re-evaluate your sensor blocking configuration anytime you relocate or deploy Swift Sensors hardware, as the optimal distribution for your environment may have changed.
To help with troubleshooting, this page shows historical signal strength and battery levels during the selected time range for a sensor. Users can see how a sensor’s signal strength is affected by its environment over time to help optimize the sensor’s location. Users can also gain a better understanding of a particular sensor’s battery performance which can vary based on signal strength, inspection rate and temperature. The Sensor Diagnostics page can be accessed using the Diagnostics button from any sensor details page.
Sensor Diagnostics: Parent Bridge
This panel shows all bridges that were designated as the parent bridge for this sensor for some time during the selected time range. Each number on the chart is mapped to a bridge, and the chart traces the lineage of parent bridges over time. Bridges that no longer exist on the account, because they have been moved to another account or deleted, are labeled as (Removed).
A sensor’s signal strength is determined by many factors including proximity, orientation, nearby sources of radio interference and physical obstacles between the sensor and a bridge. When the Parent Bridge panel data is correlated with the Signal Strength panel directly beneath, administrators can better understand how all of these factors contribute to a sensor’s signal strength relative to each bridge. This correlation allows administrators to make better informed decisions about the optimal placement and number of bridges in their environment.
Bridge Connection Preference
Bridge Advanced Settings
Users have the option to configure a bridge to operate with a static IP address when connected over Ethernet. On the bridge edit page, users will find the Advanced Settings section that allows the bridge to be configured with a bridge static IP address and the router IP address.
Learn how Swift Sensors can protect your facility.
- Role-Based Access Control
- Migrate Bridge
- Add Parent Account
- Nested Sub Accounts
- Migrate Account
- Hardware Diagnostics
- L2 Support Bridge Commands for Resellers
- Brand Support for Resellers
- Hardware Overview