contains not working as expected

[markfree]

Here are the three OIDs I have listed in the Discovery for each of the types. I use -v1 because some of the Ubiquiti hardware is old, using only v1.
FOR UBIQUITI
snmpget -v1 -ctheword 10.10.10.10 1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.6.32.68 #1 Fri Jan 3 10:25:52 Europe 2025 mips
snmpget -v1 -ctheword 10.10.10.10 1.3.6.1.2.1.1.5.0
SNMPv2-MIB::sysName.0 = STRING: honeyS
snmpget -v1 -ctheword 10.10.10.10 1.3.6.1.2.1.1.9.1.3.5
SNMPv2-MIB::sysORDescr.5 = STRING: Ubiquiti Networks MIB module
FOR MIMOSA
snmpget -v1 -ctheword 10.10.10.20 1.3.6.1.2.1.1.9.1.3.5
SNMPv2-MIB::sysORDescr.5 = STRING: The MIB module for logging SNMP Notifications.
snmpget -v1 -ctheword 10.10.10.20 1.3.6.1.2.1.1.5.0
SNMPv2-MIB::sysName.0 = STRING: SplawnNewClark
snmpget -v1 -ctheword 10.10.10.20 1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = STRING: AIRSPAN-B5c
FOR MICROTIK
snmpget -v1 -ctheword 10.10.10.30 1.3.6.1.2.1.1.1.0
SNMPv2-MIB::sysDescr.0 = STRING: RouterOS RB750Gr3
snmpget -v1 -ctheword 10.10.10.30 1.3.6.1.2.1.1.5.0
SNMPv2-MIB::sysName.0 = STRING: honeybkrtr
snmpget -v1 -ctheword 10.10.10.30 1.3.6.1.2.1.1.9.1.3.5
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-MIB::sysORDescr.5

Based on the information you provided, your devices have data that differs from what Zabbix is configured to expect in the action condition.
You should revise your data. Again, check out how to properly set up a discovery rule and action.

[tlkhorses]

Yes, I read through all of that before coming here. It's interesting that the Ubiquiti equipment is correctly handled but none of the others are. Thats even though the info is showing in the current data when looking at the hosts. I guess Zabbix doesn't like the multiple OIDs in the discovery with the actions.

[tomecki10000]

or ASCII/UTF-8 encoding incompatibility??