Just started to get this same issue after starting to use the new version of the addon. Seems to have been resolved now after a full restart of the system and ensuring the original version of the addon does not restart to conflict with my new (multi) version