You can do this in SharpTools. When setting up a device command in a rule, tap the </> icon to the right of the argument and it lets you pick a variable to insert.
You can even use a Context Variable to pass the value from the device that triggered your rule as a parameter if you’d like. 
I would strongly encourage you to test this with your device. If you are triggering based on the level for the device changing and then setting the level of that same device, you run the risk of an infinite loop. If the device only reports the level upon change, you’re fine. But if the device reports a level event every time the setLevel() command is called, it will repeatedly trigger the rule in an infinite loop.
As others have mentioned, it seems like the device could use some love in the form of a special Edge Driver that takes care of this quirky behavior natively.
If one of Mariano’s zigbee drivers works with the device, I wonder if he would be willing to entertain adding an option/preference to send the command twice.