Adding ‘dBm’ to the UOM does mean that the value is no longer ignored, but the calculation is wrong
2025-09-11 15:27:26.917 [DEBUG] [internal.profiles.StateFilterProfile] - Evaluating Condition('$DELTA_PERCENT' $DELTA_PERCENT GT '10' ) with input: -84 dBm (QuantityType). Link: 'OutdoorSensor2_rssi -> mqtt:topic:SwitchBotOutdoorMeter:rssi2'
2025-09-11 15:27:26.917 [DEBUG] [internal.profiles.StateFilterProfile] - Calculating function: $DELTA_PERCENT
2025-09-11 15:27:26.918 [DEBUG] [internal.profiles.StateFilterProfile] - Performing a comparison between '$DELTA_PERCENT' state '25.89254' (DecimalType) and value '10' (DecimalType)
2025-09-11 15:27:26.918 [DEBUG] [internal.profiles.StateFilterProfile] - Received state update from handler: -84 dBm, forwarded as -84 dBm
==> /var/log/openhab/events.log <==
2025-09-11 15:27:26.920 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'OutdoorSensor2_rssi' changed from -85 dBm to -84 dBm
2
I do remember, back in Dec 2024, that calculations on dBm were ‘difficult’, and that was why the suggestion to remove UOM from the channel worked.