End devices attributes are missing in MQTT message

[bertrik]

I wondered about this in my post from february:

Pass device attributes into uplink JSON

I noted that in the v3 console, you can now define a set of attribute/values for each device. Would it be possible to forward these attributes in the JSON uplink messages sent over MQTT? In my use case this would be a very convenient feature. My application is receiving airborne particulate matter / temperature / humidity telemetry and passing it on to sensor.community and opensensemap.org to display it on their maps. For opensensemap, I need an id to correlate the measurement to a station d…

In short: device attributes are not passed in the uplink with TTN v3. Not sending them avoids an extra backend database access for every device uplink. You can use the end device API to fetch the attributes at some interval (and cache them locally).