It looks like you’re encountering an issue with the latest version (5.0.2), and the error seems to be linked to a specific event type. The developer mentioned that this bug should be fixed in version 5.0.3. I would recommend updating to that version and checking if the issue persists.