I think you have captured a very messy signal and that is why you get the stop between multiple sends. The Broadlink just captures whatever your remote sends while you are holding down a button. It doesn’t understand what the command means, it just repeats the signal back that it captured.
Lets have a go at cleaning up your captured signal. Yes it is base64. Convert it to hex using this site https://base64.guru/converter/decode/hex
This gives
b1c0c803ba9e06000d2710250d260d270e27270d270d270e260d270d0d28270d0c27270e270d0c280d0001950c260e270d270d260f260d270d27270c0f260d270d270e260d27280c270e270d270d260e0d27270d0d27270d270d0d280c0001950c270d270d270e260e260d270e27270c0d270f260d260e260e27280c270d270d270e260e0c27270e0c28260d270e0c280c0001960b270d270e270d260e260f260d27270c0f260d270d270e260e26280c270e270d270c270e0d27270d0d28260d270d0d280c0001950b270e270d270d260f260e260d26280d0e260d270e270e260d26280d270d270d270e260d0d27270e0c28270c270e0d270c0001960c270d260e260e270d270d260e27280c0d270e260d270e260e26280c280c270e270d270d0d28260d0d27270e260e0c270e0001940c270e270d260d270e270d260e26280d0d270d260f260d270d27270d270d270d270d270e0c28260d0e27270d260d0e270d0001940d270d260e260e270e260d260f26280c0d270e260e260d270e26280d270c270e270d270d0d28260d0d27270d260f0c270d0001960b270d270e260d270e260e260e26280c0e270d260e260f0f04140d27270d270d280c270d270e0c28260e0d27270d270d0d270d0001940c270e260d270d270e270d260d27270e0d270c270f260d270d27270d280c270d270e270d0c27270e0d27270d260f0c270d0001950c270d260e270d270d270e260e26280c0d260f260e260d270e27270d270d260e270d270d0d27270d0d27270e270d0c270e0001940c270e270c270d270e270d260e26280d0d270d260f260d260e27270d280c270d270d260f0c27270d0d28260e260d0d280c0001950d260d270d270e270d260e260f26280c0d260f260d270d270e26280c280c270e270d260e0d27270d0c28270e260d0d270c0001960c260d270e270d270d260e270d27270d0e260d270d270e270d26280c270e270d270d260f0c27270d0d28260d270d0d280c0001950d250e270d270d260e270e260e26280c0d270d270e270d260d27280d270d270d270d270d0d27270e0c27270d270e0c280c0001960b270d270e270c270d270e270d26280c0e260e270d260e260e27270d270c270e270d270d0d28260e0c27270e270d0c270e0001940c260e270e260d260f260d270d27270d0e260d270e270d270d26270d280d270d270c270e0d27270d0d27270d270d0d280c000340202120211f21202111fe11841183123c123f11811183123c123f113b1184113d1185113b123c123c123f113a1283123c1285113b113d11831285113a133c123c123e1281123c123c12851181113d123c1285113a123c133c1283130005dc
Although this looks meaningless, by understanding a little about the Broadlink command file structure you can make some sense of it. It starts with a frequency indicator:
b1c0
Followed by a file length (in reverse byte order) of 03c8 hex which is 968 bytes:
c803
Then some bytes I don’t understand:
ba9e
0600
Then repeating cycles of a command coded as hi/lo transmit times such as 0d27 (high for 0d, low for 27). Note there is a bit of variance in the timings so 0d27 is the same as 0f26. These hi/lo timings represent 1’s and 0’s but you don’t need to decode them to clean things up. The file ends with a terminator of:
05dc
Here is a copy of your capture rearranged to make the cycles clear. Each cycle starts with a 0195 (or similar) lead-in which helps the device sync with the signal so it can decode it:
b1c0
c803
ba9e
0600
0d2710250d260d270e27270d270d270e260d270d0d28270d0c27270e270d0c280d00
01950c260e270d270d260f260d270d27270c0f260d270d270e260d27280c270e270d270d260e0d27270d0d27270d270d0d280c00
01950c270d270d270e260e260d270e27270c0d270f260d260e260e27280c270d270d270e260e0c27270e0c28260d270e0c280c00
01960b270d270e270d260e260f260d27270c0f260d270d270e260e26280c270e270d270c270e0d27270d0d28260d270d0d280c00
01950b270e270d270d260f260e260d26280d0e260d270e270e260d26280d270d270d270e260d0d27270e0c28270c270e0d270c00
01960c270d260e260e270d270d260e27280c0d270e260d270e260e26280c280c270e270d270d0d28260d0d27270e260e0c270e00
01940c270e270d260d270e270d260e26280d0d270d260f260d270d27270d270d270d270d270e0c28260d0e27270d260d0e270d00
01940d270d260e260e270e260d260f26280c0d270e260e260d270e26280d270c270e270d270d0d28260d0d27270d260f0c270d00
01960b270d270e260d270e260e260e26280c0e270d260e260f0f04140d27270d270d280c270d270e0c28260e0d27270d270d0d270d00
01940c270e260d270d270e270d260d27270e0d270c270f260d270d27270d280c270d270e270d0c27270e0d27270d260f0c270d00
01950c270d260e270d270d270e260e26280c0d260f260e260d270e27270d270d260e270d270d0d27270d0d27270e270d0c270e00
01940c270e270c270d270e270d260e26280d0d270d260f260d260e27270d280c270d270d260f0c27270d0d28260e260d0d280c00
01950d260d270d270e270d260e260f26280c0d260f260d270d270e26280c280c270e270d260e0d27270d0c28270e260d0d270c00
01960c260d270e270d270d260e270d27270d0e260d270d270e270d26280c270e270d270d260f0c27270d0d28260d270d0d280c00
01950d250e270d270d260e270e260e26280c0d270d270e270d260d27280d270d270d270d270d0d27270e0c27270d270e0c280c00
01960b270d270e270c270d270e270d26280c0e260e270d260e260e27270d270c270e270d270d0d28260e0c27270e270d0c270e00
01940c260e270e260d260f260d270d27270d0e260d270e270d270d26270d280d270d270c270e0d27270d0d27270d270d0d280c00
0340202120211f21202111fe11841183123c123f11811183123c123f113b1184113d1185113b123c123c123f113a1283123c1285
113b113d11831285113a133c123c123e1281123c123c12851181113d123c1285113a123c133c12831300
05dc
You can see that the first cycle is incomplete. This just means that the capture started mid-cycle. There is also one cycle in about the middle of the file that is slightly longer having some dubious extra bytes in there. I guess this was a glitch or interference. At the end though is a bunch of codes that don’t seem to have any structure. I think that is just noise that got captured and may be causing your stopping.
To clean it up just take a single good cycle and reencode it.
b1c0
c803
ba9e
0600
01950c260e270d270d260f260d270d27270c0f260d270d270e260d27280c270e270d270d260e0d27270d0d27270d270d0d280c00
05dc
The file length is everything from the ba9e through to and including the 05dc terminator. So that’s 116 characters or 58 bytes which is 3a in hex. Reversing the bytes for the length gives 3a00.
So altogether your cleaned command would be:
b1c03a00ba9e060001950c260e270d270d260f260d270d27270c0f260d270d270e260d27280c270e270d270d260e0d27270d0d27270d270d0d280c0005dc
Convert it back to base64 via https://base64.guru/converter/encode/hex and you get:
scA6ALqeBgABlQwmDicNJw0mDyYNJw0nJwwPJg0nDScOJg0nKAwnDicNJw0mDg0nJw0NJycNJw0NKAwABdw=
Cross your fingers and give that a try in your Home Assistant Broadlink command file. If it doesn’t work then try using two complete cycles for the data part and recalculate the length accordingly. Some devices need a bit of time to lock into the signal.
I’ve used this approach to clean up all my Broadlink 433MHz commands and have a very tidy command file in Home Assistant as a result.