Device Type ID Error in v2.14.+fall2025 Branch During Conformance Testing

[WangHunZi]

Describe the bug

Hi,

I am testing my device using the v2.14.+fall2025 branch, which includes a custom device type. Regardless of the device type ID I set (e.g., 0xFFF10001, 0x13801380, 0x13800000, 0x13800001, 0x1380), I consistently encounter the following error during test execution:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/dist-packages/mobly/base_test.py", line 801, in exec_one_test
    test_method()
  File "/root/python_testing/scripts/sdk/TC_DeviceConformance.py", line 129, in test_TC_DESC_2_3
    problems.extend(self.check_all_application_device_types_superset())
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/python_testing/scripts/sdk/test_testing/DeviceConformanceTests.py", line 475, in check_all_application_device_types_superset
    dt for dt in all_device_type_ids if self.xml_device_types[dt].classification_class == 'simple'}
                                        ~~~~~~~~~~~~~~~~~~~~~^^^^
KeyError: 4992
...

This appears to be a KeyError occurring when the test attempts to access self.xml_device_types[dt] with a device type ID that is not present in the dictionary.

Is this a known issue where the test suite does not properly handle custom device type IDs? If the test case does not currently support this scenario, UL has indicated they will perform manual verification.

Please let me know if you need further details or logs.

Best regards.
WangHunZi

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

DESC-2_3_2026_01_06_03_34_15.log
DESC-2_3_2026_01_06_02_45_59.log
DESC-2_3_2026_01_05_10_09_26.log
DESC-2_3_2026_01_05_09_43_33.log

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response