openclaw - 💡(How to fix) Fix Dreaming config rejects `timezone` property despite docs showing it as valid [1 comments, 1 participants]

However, adding timezone causes a config validation error: 4. Gateway fails to start with validation error

TL;DR

The timezone property in the dreaming config should be accepted without causing a config validation error, suggesting a potential fix involves updating the validation rules to include this property.

Guidance

• Review the config validation logic to ensure it accounts for the timezone property in the dreaming config.
• Verify that the dreaming docs are accurate and up-to-date, reflecting any changes made to the validation rules.
• Consider adding the timezone property to the list of accepted properties in the config validation schema.
• Test the updated config validation with the timezone property to ensure it no longer causes an error.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a potential update to the config validation rules.

Notes

The provided information suggests a discrepancy between the documented config properties and the actual validation rules. Resolving this issue may require updates to the validation logic or the documentation.

Recommendation

Apply a workaround by manually calculating the UTC offset for the frequency cron, as described in the current workaround, until the config validation issue is resolved. This is because the issue implies a potential bug in the validation rules rather than a version-specific problem that could be fixed by upgrading.