Filter for sensor specifically remotes thresholds

[LordHepipud]

If you are using the plugin to collect all sensor data, you receive performance metrics for the sensors:

./check_akcp_sensorprobeXplus -h xx.xxx.xxx.xx -c community
[CRITICAL] - Device SPX+ Demo at location Hole (SPX+ F7 1.0.5233 May 12 2020 09:41:)
\_ [OK] Dual Humidity Port 1: 56.0%
\_ [OK] Dual Temperature Port 1: 23.5℃
\_ [OK] Temp Sensor Test: 23.7℃
\_ [CRITICAL] Motion Detector Port 4: Motion
\_ [OK] Icinga Demo: 0.0
|'Dual Humidity Port 1'=56%;32:66;23:69 'Dual Temperature Port 1'=23.5C;20.7:30;10.6:40 'Temp Sensor Test'=23.7C;20:30;10.5:40 'Motion Detector Port 4'=1 'Icinga Demo'=0

If you are filtering for specific sensors and ports, the thresholds are not added to the output:

./check_akcp_sensorprobeXplus -h xx.xxx.xxx.xx -c community --sensorPort 1 -m temperature
[OK] - Device SPX+ Demo at location Hole (SPX+ F7 1.0.5233 May 12 2020 09:41:)
\_ [OK] Temp Sensor Test: 23.7℃
|'Temp Sensor Test'=23.7C

While the plugin output is correct in case it is critical, the performance data thresholds are just missing.

[martialblog]

@RincewindsHat Can you have a look at this?

[RincewindsHat]

sure, if I remember correctly, the -m temperature part is not actually a filter, but queries an entirely different table on the device. I think the specialised tables do not include the threshold data.

Adding a real filter function for the main sensor table would remove this limitation