Unfortunately, an online decoder shows that this looks just just fine. (It’s just a LoRaWAN header for an unconfirmed uplink, the actual application payload, and the MIC. No MAC commands that could be troublesome.)
TTN should really not care about the application payload. You could copy the secret NwkSKey (and AppSKey) session keys from the device in TTN Console into that online decoder, to verify that the MIC is okay. (But bugs in your LoRaWAN stack aside, the MIC really should be valid, as the successful OTAA proves the keys are okay.) And check that there are no errors in the Trace part when clicking the uplink in the gateway’s Traffic page TTN Console. (Unfortunately, an invalid MIC is silently ignored.)
Did you already configure the Cayenne integration? Maybe remove that for a quick test?
Is the DevEUI really unique (not some easy to read value you created yourself)?
Is the application also registered to a handler in the us-west region, like your gateway is?
And any chance you can use an MQTT client (or ttnctl subscribe) to see if it the data is available even when it’s not shown in TTN Console?