Not being an LSP user at all, I'm not sure what the conventions are. If a "controller" in LSP would map to a strand on an xLights model, that would be easy to supported. The LMS and HLS imports support that if it detects a CCR (LMS) or a pixel plane (HLS). I just don't know the conventions in LSP.
This is what I have been able to gather by trying to parse the data
I opened the xml file ‘1f4929bf-9a8e-4739-9bde-a1bc7b40720f’ and had a look
What is visible to the LSP user (ie the controller which is equivalent to a model) is the Controller name (eg Pipes 5)
Each controller name , then has a number of channel ids (eg 7361, 7364, 7367 etc) , which then has the channel name (Channel #1)
the green , red , blue channelids (7360,7361,7362)
So everything pertaining to the controller (‘Pipes 5’) ie each channel id within that should map to the corresponding model/node in xlights if mapping by strand and if they are aligned and exactly the same.
Not sure if this helps. I have attached screen prints in this thread above of my config and posted the files in another post today/
I also understand that Tom Langley who worked with Sean last year is the expert on getting data back and forwards.
ControllerGuid>1f4929bf-9a8e-4739-9bde-a1bc7b40720f</ControllerGuid>
<ControllerID>1</ControllerID>
<ControllerName>Pipes 5</ControllerName>
<ControllerOrdinal>0</ControllerOrdinal>
<ControllerProtocol>6</ControllerProtocol>
<ControllerType>3</ControllerType>
<ControllerZone>1</ControllerZone>
<EnableControllerOutput>true</EnableControllerOutput>
<GreenControllerID>1</GreenControllerID>
<GroupName>E1.31 Controllers</GroupName>