Please advise on camera model and firmware. I have tested with a single command successfully. Testing with the two options in sequence failed.
I suggest a reasonable workaround is to run setOptions twice, once for just dateTimeZone with only that option set. The second time, set all your other options.
Test 1 - single command on Z1, firmware 1.60.1, dateTimeZone only
Result: success
Test Environment
"firmwareVersion": "1.60.1",
"manufacturer": "RICOH",
"model": "RICOH THETA Z1",
Command
{name: camera.setOptions, state: done}
{dateTimeZone: 2020:05:18 01:04:29+08:00}
Result
check options with getOptions
successful
"dateTimeZone": "2020:05:18 01:05:08+08:00",
Test 2 - Multiple options, including dateTimeZone
Result
Failure.
Failing with multiple commands is one of the commands is dateTimeZone. Will continue to test. In the meantime, suggest you break up the setOptions into two commands.
Test 3 - set multiple options, without dateTimeZone
Check to see if multiple options can be set in general.
Result
Success.
Payload
{
"exposureDelay" : 0,
"exposureCompensation": 0.7
}
Test 4 - set multiple options with dateTimeZone as last option
Checking if dateTimeZone takes longer to save to persistent storage.
Result
Fail
Option Payload
{
"exposureDelay" : 0,
"exposureCompensation": 0.7,
"dateTimeZone": "2020:05:18 01:04:29+08:00"
}
Test 5 - Set Options Individually in Script
Set options individually. No delay between options. Functionality should be comparable to setting
multiple commands.
Result
Success
Script Used for Testing
#!/usr/bin/bash
# set individual options one at a time
# set first option
./theta.exe setOption --name=dateTimeZone --value="2020:05:18 01:04:29+08:00"
# HTTP session is automatically closed
# next option is set with no delay
# set second option
./theta.exe setOption --name=exposureDelay --value=0