Seems adding the dhcp options causes CleaarPass not to categorise the device ... however . this does work - note the commented out bits
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TipsContents xmlns="http://www.avendasys.com/tipsapiDefs/1.0">
<TipsHeader exportTime="Tue Jul 24 12:38:04 BST 2018" version="6.7"/>
<!—
Date: 27/07/18
Name: Amazon-echo-fingerprint.xml
Function; Create a locally defined fingerprint category="Home Audio/Video Equipment" family="Amazon" name="UoY Amazon Echo”. Take the standard ClarPass definition and add the OUI of the device on my desk to the list of known ones.
Gotchas: Seems that every though the dhcp options specified are what’s associated with a device, if you include them in the fingerprint, for a new device upon boot up it doesn’t get classified, so just here for information
—>
<DeviceFingerprints>
<DeviceFingerprint category="Home Audio/Video Equipment" family="Amazon" name="UoY Amazon Echo">
<FingerprintRules>
<FingerprintRule match-conditions="ALL">
<RuleCondition name="mac_vendor" operator="contains" value="Amazon"/>
<RuleCondition name="device.family" operator="contains" value="Android"/>
<!-- OUI prefixes for the default ClearPass Amazon Echo fingerprint and addition of the one on my desk -->
<RuleCondition name="mac" operator="contains" >
<valueList>[34d270 40b4cd fca667 4cefc0 8871e5]</valueList>
</RuleCondition>
<!-- Even though these are the options associated with the Amazon Echo on my desk, including them causes clearpass NOT to recognise the device u[on 1st boot up-->
<!--
<RuleCondition name="dhcp.option60" operator="contains" >
<valueList>["dhcpcd-5.5.6"]</valueList>
</RuleCondition>
<RuleCondition name="dhcp.option55" operator="contains" >
<valueList>["1,33,3,6,15,28,51,58,59"]</valueList>
</RuleCondition>
<RuleCondition name="dhcp.options" operator="contains" >
<valueList>["53,50,57,60,12,55"]</valueList>
</RuleCondition>
-->
</FingerprintRule>
</FingerprintRules>
</DeviceFingerprint>
</DeviceFingerprints>
</TipsContents>