Search FAQs
NetBotz sensors with custom names report incorrectly if swapped with a different sensor type.
Issue:
NetBotz sensors with custom names report incorrectly if swapped with a different sensor type.
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Botzware 5.3.5 (maybe others)
Cause:
If you plug a NetBotz sensor into a universal sensor port and give it a custom name them replace it with a different sensor type, you may see sensor name, alarm severity, connection status, sensor type from the original sensor when polling the NetBotz appliance via modbus.
For instance, if you install a temperature sensor, give it a custom name, they unplug that sensor and plug in a spot leak sensor, you may see an output something like "Temperature = No Leak"
Resolution:
The only way to correct this is to disconnect the sensor in that port and delete the sensor in the user interface.
Once deleted, plug the new sensor in and reconfigure it.
NetBotz sensors with custom names report incorrectly if swapped with a different sensor type.
Product Line:
NetBotz
Environment:
NBRK0750
NBWL0755
Botzware 5.3.5 (maybe others)
Cause:
If you plug a NetBotz sensor into a universal sensor port and give it a custom name them replace it with a different sensor type, you may see sensor name, alarm severity, connection status, sensor type from the original sensor when polling the NetBotz appliance via modbus.
For instance, if you install a temperature sensor, give it a custom name, they unplug that sensor and plug in a spot leak sensor, you may see an output something like "Temperature = No Leak"
Resolution:
The only way to correct this is to disconnect the sensor in that port and delete the sensor in the user interface.
Once deleted, plug the new sensor in and reconfigure it.
Released for:APC United Kingdom
Explore more
Range:
Explore more
Range:
