Great, thanks for reporting that it is working without issues.
I consider each segment to be a new light. So 1 led strip can be split up to create multiple “light globes”, aka segments. The maserControls are the controls for a single light aka segment and will model how a normal light is normally handled and responds in openHAB. The future global controls will globally control the whole strip. Another way to globally change all segments is to use the normal openHAB group items as you would if you want to change multiple light globes as one from other bindings.
The brightness changing is important as the semantic model will display a list/count of ‘ON’ lights and also the icons will change to reflect the state of the light output. When a light is OFF, it should be black and any slider icons should go from yellow to gray. Any count of lights turned on should go back down by 1 when the light is turned off. This is the difference between the “primaryColor” channel and the “masterControls” channels.
You can choose to use it with only the primary colour linked to items if you wish, as there is a “segmentBrightness” channel that can be used to change brightness and turn the segment on and off. The choice to set it up in two very different ways can be made, however the masterControls IMHO makes your life much easier, especially if you link it to alexa/google and ask it to change the light to X colour when the light is running FX.
One thing I recommend that you try is to link up the new segmentBrightness channel to BOTH a Switch item and also a Dimmer item, or just a Dimmer if you prefer one less switch. These currently allow you to change the brightness without the HSB color changing if this is what you prefer. It sounds like this is what you were expecting and prefer? Tick the show advanced box to see this and other channels.
The other thing I will mention is that its possible to use openHABs ability to create your own Global controls by creating an item and setting it up to send either MQTT or the HTTP messages directly and not through the binding. There is a whole thread on how to setup openHAB and wled without the binding using MQTT, but it could easily be done without mqtt and by sending the older http API directly or the json api directly. The semantic model allow you to create equipment from multiple bindings and methods and display it as a single piece of equipment, so this is a real world example of how openHAB is flexible and why the equipment concept was introduced.
V0.13.x has only just introduced named segments into the firmware, so the goal for the next lot of changes would be to add auto discovery of multiple segments with auto naming ability and to add the global controls with a bridge/thing setup. So if you or anyone else is setting up segments, don’t forget to name them with the V0.13 firmware when creating your presets and playlists as this will make future upgrades smoother.