This behavior is expected if the clock doesn't have "Unicast Discovery" enabled.
In the configuration in question, the device with only "Unicast Negotiation" enabled, is a grantor only and thus will not have the unicast bit set.