Open mhilbush opened 7 years ago
Thanks Mark!
Hi Mark, was this considered a bug, user error, or problem with the documentation?
I would view it as an enhancement to the existing functionality. Currently, presence simulation expects just a command in the calendar description. This is because the presence simulation commands are added by the gcal persistence service when an item in the presence simulation group executes a command.
The user had manually entered calendar descriptions tagged with [Presence Simulation] that contained start and stop stanzas. These failed to execute because the code expects a command without start/stop stanzas.
If this is a valid use case (which I gather you are saying it is), then I will leave this marked as such. Thanks for the clarification.
[PresenceSimulation] calendar events whose description contains start & stop stanzas are not properly handled. These should be handled similarly to other gcal calendar events with start and stop stanzas (i.e. the start command should be executed at the calendar event start time, and the stop command should be executed at the calendar event stop time).