When initiating the OAuth authorization code flow, the FoxESS auth page does not redirect to the configured redirect_uri, so the application never receives an authorization code. In DevTools Network, only two XHR requests occur (/oauth2/login and /oauth2/getRedirectUri). No top-level navigation/302 to the callback URL is observed.
OAuth config / parameters
• client_id: f8f7900d6c7f47049413f482ce242d6d
• redirect_uri: https://wattion.app/api/foxess/oauth/callback
• scope: data_access device_control
• response_type: code
• state: (random string per attempt; example: X4bV3q1Htha_lXEOAELz8JdkexFUywEE)
URL looks like this
https://www.foxesscloud.com/h5/auth/fox ... dkexFUywEE
and I'm expecting a redirect like this
https://wattion.app/api/foxess/oauth/ca ... ate=<STATE>
1. What does code: 41825 indicate in /oauth2/getRedirectUri?
The response includes supportDevices but also msg: "Unrecognized msg:41825".
2. Should the page perform an additional request / step to trigger the redirect (e.g., device selection / consent)? If so, what is the expected endpoint / UX?
3. Is there any requirement that the redirect_uri be whitelisted exactly (including trailing slashes / https only / etc.) beyond what’s shown in the personal center settings?