but it fails with message “unauthenticated” - we double-checked in the v3. console of our gateway the checkbox for “Gateway status” = PUBLIC – yes, its activated. – Also we placed an API Key with the credentials for “Gateway status read” and tried to read via node-red. Here we included the API-Key as credential “Authorization” and within node-red its working fine here.
Today we are not sure about this status read function without credentials – as formerly (in v2 stack) we were able to ask all our community-gateways via https request without any authentication. Can somebody explain or evaluate this ? Thanks in advance !
It would indeed be useful if non-collaborator users can call that RPC. It won’t be available to unauthenticated callers, but any member of the network should be able to see the gateway status if the gateway settings allow it.