Thanks for the clarification.
This is a known problem and I can even provide you with the fix, but it won’t be included in the next versions. Unfortunately, this issue requires a significant rework of the current add-on architecture and will be done at a later date. For those who are experiencing this problem and need a solution, please apply the attached .diff file.
13608.diff (2.4 KB)