Clicking a Plug-In Window in Cubase 13

Hello, we are attempting to do some scripting with SoundFlow in Cubase 13 and I'm running into an issue. It's my understanding (because of my post here: Current State of Cubase Support #post-3) that SoundFlow doesn't fully support Cubase 13 at the moment. That said, some code appears to work while some doesn't, so I'm just trying to make sure I'm not doing anything wrong before I give up.

I'm currently using some coordinates to click and drag a knob on a plug-in UI. These coordinates are relative to the top left corner of the plug-in UI, NOT including the toolbar that Cubase the plug-in UI for bypassing, changing presets, etc. It looks like I'm able to use SoundFlow's Pick button to highlight and select this portion of the UI. This code looks like this: sf.ui.cubase.mainWindow.groups.whoseTitle.is("4020 Retro EQ").first.groups.first;

I then have this code to click a parameter on the UI:

sf.ui.cubase.mainWindow.groups.whoseTitle.is("4020 Retro EQ").first.groups.first.mouseClickElement({
    relativePosition: { "x": 100, "y": 100 },
    isRightClick: false,
});

However, when I run this code, I get this error

08.10.2024 13:27:48.21 <info> [Backend]: !! Command Error: Script [user:<insertIDHere>]:
MouseClickAction requires valid UIElement (01 retroEQ: Line 165) // Line 165 is the line with the mouseClickElement call
    Couldn't get item #0 as the array's parent node wasn't found - sf.ui.app('com.steinberg.cubase13').<unknown>.groups.whoseTitle.is('4020 Retro EQ').first (AxElementArrayIndexedItem)

This suggests to me that, although the Pick tool is able to select my desired portion of the UI, SoundFlow isn't able to successfully target it. This is strange to me because the following code DOES work and does not produce this error:

sf.ui.cubase.mainWindow.mouseClickElement({
    relativePosition: { "x": 100, "y": 100 },
    isRightClick: false,
});

While this does work, the main issue with this is that this would require us to alter all of our parameter coordinates to work from the top left corner of the Cubase window, as opposed to the top left corner of the plug-in UI. This would also require all of our plug-in UIs to be in a specific spot in Cubase before running the script. Of course, we'd prefer to avoid this approach, if possible.

So, could you please clarify if the behavior that I'm experiencing is expected due to the lack of support for Cubase? Or is there another way I should go about getting a reference to this portion of the plug-in UI so that our coordinates line up with our parameters as expected?

As always, thank you so much!