Android端MoveSense DataLogger激活报403错误排查求助

Hey there, let's dig into why you're hitting that 403 Forbidden error when trying to activate the DataLogger on your MoveSense device. Based on your description, here are the most likely issues and fixes:

1. You're Using an Invalid State Code #

The biggest red flag here is the newState: 5 value in your activation request. From MoveSense's official DataLogger API specs, valid state codes follow this standard:

• 0: IDLE (default, unconfigured state)
• 1: CONFIGURED (after successful setup of logging parameters)
• 2: LOGGING (active data recording)
• 3: STOPPED (recording paused/ended)

Sending 5 is an unrecognized state, which is almost certainly triggering the 403 error. You need to follow the proper state transition flow instead of jumping straight to an invalid state.

2. Verify Configuration Completion Before Activating #

Before trying to start logging, confirm your initial configuration actually took effect:

1. Run a GET request to check the current DataLogger state:

   Mds get() uri: suunto://<SERIAL>/Mem/DataLogger/State
   

2. Confirm the response returns state 1 (CONFIGURED). If it stays at 0 (IDLE), your config might be missing a required parameter—add the storageType field to your config contract (this is often mandatory for specifying where data is stored):

   {"config": { 
     "storageType": "INTERNAL",
     "dataEntries": {"dataEntry": [{"path": "/Meas/Gyro/13"}]}
   }}
   

3. Double-Check Module Compatibility & Dependencies #

Even though you've flashed the DataLogger and Logbook modules, ensure:

• The module versions match your MoveSense device's firmware version (mismatches can cause silent permission failures)
• The required underlying modules (like Storage, which handles memory write operations) are enabled on the device

Step-by-Step Valid Workflow #

Here's the full, tested flow to get logging up and running:

1. Configure DataLogger (with storage type specified):

   Mds put() uri: suunto://<SERIAL>/Mem/DataLogger/Config 
   contract: {"config": { "storageType": "INTERNAL", "dataEntries": {"dataEntry": [{"path": "/Meas/Gyro/13"}]}}}
   

2. Confirm Configuration State:

   Mds get() uri: suunto://<SERIAL>/Mem/DataLogger/State
   

   Wait for a response showing state 1.
3. Start Logging:

   Mds put() uri: suunto://<SERIAL>/Mem/DataLogger/State 
   contract: {"newState": 2}
   

4. Stop Logging when needed:

   Mds put() uri: suunto://<SERIAL>/Mem/DataLogger/State 
   contract: {"newState": 3}
   

If you still run into issues after this, use the MoveSense Debug tool to pull device system logs—they often reveal specific permission or module loading details that aren't visible in the basic 403 response.

内容的提问来源于stack exchange，提问作者Jeroen Bogers