End devices attributes are missing in MQTT message

[wotan]

v2 used to include “attributes” in MQTT messages. See actual example (with december warning by the way):
“attributes”:
{
“deepness”:“6.7”,
“dev_id_knd”:"",
“warning”:“The Things Network V2 is shutting down in December 2021. Migrate to V3 NOW!”
}

V3 doesn’t (tried with the ‘#’ topic)

Is this intentional or forgotten in the implementation?

[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).

[wotan]

@bertrik

You can use the end device API to fetch the attributes at some interval (and cache them locally).

Yes, as a work around.
Until now I only used MQTT with v3 an don’t know the new api.

V2 knew about attributes in MQTT. (There had been silent attributes in v2 you could use via api.)