Hey @gregory337, a couple things about your post.
First, the way our max and min settings work is similar to how Fibaro does it. When you set a max or min, the firmware changes the scale internally to apply these settings. Externally you still send 0-99 to the switch, but internally it makes an adjustment based on the config settings. I believe this is the correct way to do it as z-wave is very vocal about the fact that a "dimming device" needs to allow the value to be set to 0-99.
Internally the calculation of (x/(max-min) = value) + min.
So if you change the min to 15 and the max to 75 then try to set the level to 85 the equation would be (x/(75-15) = .85) + 15. The result would be 66 (internally applied).
In the same scenario if you set level to 99 then the equation would be (x/(75-15) = .99) + 15. the result would be ~75 (the maximum value).
Lastly, if you set it to 1 the equation would be (x/(75-15) = .01) + 15. The result would be 15 (the minimum value).
So even though the switch still looks like it is being set to something higher than the maximum, internally it is not.
As for the problem you are seeing, we are actually investigating a few cases of people seeing this issue. It seems to be only with certain loads, but we are still looking into it. If you could post your experience in the following thread, that would help us get to the bottom of it. Also, I know it isn't ideal, but can you try setting the maximum a little lower as a workaround?