A Flexy 205 fleet stopped publishing data to MindSphere and returned HTTP 401 responses. Re-onboarding restored publishing for only 1–2 hours, so treat it as a temporary diagnostic rather than a confirmed repair. The available evidence points to authorization data or token renewal behavior, but it does not establish the final root cause or a permanent field fix.
Identify the HTTP 401 failure mode
| Gateway message | Confirmed meaning | Diagnostic direction |
|---|---|---|
no Authorization header found |
MindSphere received the request without an Authorization header. | Capture logs around token acquisition and the first failed upload. Determine whether the agent omitted the header after initially publishing successfully. |
jwt signature verification failed: 'exp' claim expired at Mon, 21 Feb 2022 16:10:20 GMT |
MindSphere rejected a JWT whose exp claim had passed. |
Check whether the Flexy obtained a replacement token before the expiration and whether subsequent requests used that replacement. |
These messages describe different request failures: one request has no authorization header, while the other carries an expired JWT. Do not collapse them into a generic network or time-series error without correlating each response to the preceding token activity.
Use re-onboarding only to reproduce the sequence
Resetting the configuration and onboarding again reportedly restored publishing for 1–2 hours before the HTTP 401 returned. That behavior supports an authorization-lifecycle investigation, but it does not prove whether the fault is token validity, renewal, storage, or construction of later requests.
- Record the device, onboarding time, first successful data publication, token-request entries, and first HTTP 401 response.
- Keep the real-time log running through the transition from successful publishing to failure. No more detailed Flexy log was identified in the evidence.
- Export the real-time information by generating a backup with support files or by using an EBD.
- Provide the correlated logs to the manufacturers' official support channels so the agent request and MindSphere rejection can be compared.
Separate confirmed evidence from open hypotheses
MindSphere support reported that its services were running and that the issue appeared associated with authorization data sent by the Flexy 205 agent. It also stated that the integration used a custom agent rather than a prebuilt agent development kit. The two development teams were being connected for investigation; the evidence does not contain their final diagnosis, a firmware correction, or a permanent workaround.
A MindSphere notice separately announced planned deprecation of the Time Series Aggregate V3 API by mid-April 2022 and requested migration to Aggregate V4. Nothing in the evidence confirms that the Flexy publishing path used Aggregate V3 or that this deprecation caused the February HTTP 401 responses. Verify the API used by the agent before treating migration as corrective action.
Define successful verification
Do not close the incident after a single successful upload or immediately after re-onboarding. Verify that the device continues publishing beyond the previously observed 1–2-hour failure window, obtains a new token when required, sends an Authorization header with later requests, and produces no expired-claim HTTP 401 response. If it fails again, preserve the complete log interval instead of repeatedly re-onboarding and losing the sequence.
FAQ
Why does Flexy 205 receive MindSphere HTTP 401?
The captured responses show either a missing Authorization header or an expired JWT exp claim. The evidence points to authorization data or token handling, but it does not establish the final implementation defect.
Does re-onboarding permanently fix Flexy 205 data publishing?
No. Re-onboarding restored publishing for only 1–2 hours in the reported case, so use it to reproduce and log the token lifecycle rather than as a permanent repair.
Did the MindSphere Aggregate V3 deprecation cause the 401 error?
The evidence does not confirm that connection. First verify whether the Flexy agent uses Aggregate V3; the observed errors specifically concern a missing Authorization header and an expired JWT.