Benoit Anastay

> And is the entry in the secrets.yaml correct? There is no brackets Its like this ```yaml # Use this file to store secrets like usernames and passwords. # Learn...

Since your account is an administrator account there shouldn't be any restrictions to API usage. For security best practices it's still better to create a read-only user for API usage.

If you do use Docker internal hostname you don't need to expose the port, all container can communicate with each others

@CR6-SE as long as you use internal network it should work even if you cloud flare

Are you all using the hostname displayed in the addon panel ? I'll maybe try to replicate this setup to check if everythings work as intended

So I was able to make my sensor working by changing the request, my configuration is this one. ``` - platform: rest unique_id: 5dade7bc-ddb7-442e-bb17-0d379dbf01fb resource: http://44849f5f-paperless-ngx/api/documents/?tags__id=3 headers: Authorization: !secret paperless_auth_header...

@CR6-SE you can enable debug on rest api intégration to check what's wrong. Personally I used tag id instead of tag name, I think it's more reliable, the tag IDs...

@CR6-SE if you are using stable repository the URL differ from mine in your case this configuration should work (replace `?tags__id=3` by the one you need) ``` - platform: rest...

You need to delete you addon_config folder conten̂t to force it to create a new super user

Only paperless