Device attributes not returned via API in The Things Stack Self-Hosted v3.33.0

[matiasAS]

Summary

I am using The Things Stack Self-Hosted v3.33.0, and I have noticed that device attributes are not returned via the API, even though the documentation suggests they should be accessible.

Steps to Reproduce

1. I have devices with attributes configured in the TTS Console.

2. I attempted to retrieve them using the following API call:

   curl -X GET "https://<my-tts-server>/api/v3/applications/<application_id>/devices/<device_id>" \
     -H "Authorization: Bearer <my-api-key>" \
     -H "Content-Type: application/json" \
     -d '{
       "field_mask": {
         "paths": ["attributes"]
       }
     }'
   

Current Result

The response does not include the attributes field.

Expected Result

The API should return the attributes field as per the documentation.

Relevant Logs

URL

No response

Deployment

The Things Stack Enterprise (self-hosted)

The Things Stack Version

3.33.0

Client Name and Version

Using the CLI: ttn-lw-cli 3.33.0 (run `ttn-lw-cli version`) on Ubuntu 22.04 (Intel)  
Using a web browser: Firefox 102.0 on Ubuntu 22.04 (Intel)  
Gateway: Milesight UG65 Semi-Industrial with the latest firmware  
TTS Deployment: Self-hosted using Docker (`thethingsnetwork/lorawan-stack:3.33.0`)

Other Information

TTS Version: v3.33.0 Self-Hosted
Database Check: The attributes do exist in the PostgreSQL database (attributes table).
API Key Permissions: The API key has full rights.
TTS Logs: No error messages related to attributes retrieval.

Proposed Fix

No response

Contributing

• I can help by doing more research.
• I can help by implementing a fix after the proposal above is approved.
• I can help by testing the fix before it's released.

Validation

• The fix is tested in a staging environment.
• The fix is documented in The Things Stack Documentation

Code of Conduct

• I agree to follow TTN's Community Code of Conduct.

[techminion940118]

Hello Matias, I can help you.

[matiasAS]

Ok @techminion940118 , do you know if it is possible? Can we talk here or another way (whatsapp, email, telegram...)?
I'm from Chile, I don't speak English, but with the translator I can!

[techminion940118]

Okay, no problem. Can you share your email, so that I can invite you in my slack workstation?

[matiasAS]

matialvarezs@gmail.com

[matiasAS]

@techminion940118 where you from?

[techminion940118]

I am from Canada, I have just sent invitation.
https://join.slack.com/t/docker-assistant/shared_invite/zt-30wkfan0k-62TYZOgnMuHXnoBP6OMTTA

[KrishnaIyer]

The field mask is a part of the request parameters and not in the body.

Please try something like this:

curl -X GET "https://<my-tts-server>/api/v3/applications/<application_id>/devices/<device_id>?field_mask=attributes" \
  -H "Authorization: Bearer <my-api-key>" \
  -H "Content-Type: application/json"

[matiasAS]

@KrishnaIyer thanks

Do you know the solution to that error? It is on a proxmox server, pfsense is my firewall on a virtual machine, I have ports 80/443 busy, I am using external letsencrypt ssl and I pass them to docker by volume, and it gives me that error.

[KrishnaIyer]

For this please check our troubleshooting: https://www.thethingsindustries.com/docs/enterprise/docker/troubleshooting/.

[matiasAS]

Hello @KrishnaIyer ,

I followed the troubleshooting guide (link) but ACME is not generating the +rsa certificate inside my Docker container.

Setup:
Proxmox VM with pfSense firewall
Ports 80 and 443 are forwarded to the TTS VM
TTS runs in Docker, listening on 80 and 443
ACME volume: ./acme:/var/lib/acme
Issue:
The TTS stack starts successfully, but Let's Encrypt challenges return 404 at http://tts1.sistemasmas.cl/.well-known/acme-challenge/test.
Port 80 is open and listening (netstat -tulnp).
No ACME logs in docker logs the-things-stack-2-stack-1 --tail=50 | grep acme.
The +rsa file is not generated in ./acme/.
I tried removing ./acme/ and restarting, but the issue persists.
Questions:
Why is ACME not generating the +rsa certificate?
How can I manually force TTS to request a new certificate?
Can I reach you via WhatsApp, Slack, Skype, or another channel for direct assistance?
Thanks in advance!

Best regards,
Matias