Problem with node-red-contrib-senec-cloud has ERROR 302

without making any changes the senec cloud note has ERROR 302. Has anyone the same problem?

Welcome @nobs

without making any changes

The API that this node uses, is simple HTTP requests, and 302 in this area is a redirect.

You will need to address that with the Node author if it continues

Same here - seems that the Node-red node cannot handle the HTTP 302 Redirect

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.