This ValueID, if present, should be prefered over the existing Level ValueID, as the level valueID reports "instant" levels, rather than a final level. This causes users issues on devices such as dimmers, where the Value ramps up/down over a period of time, but the level value does not represent what the final value will be.
Just need to confirm no changes are necessary here. If there are, we still need to handle the old 1.4 way (with just a level valueID) as not all devices support the Target ValueID.
As per the OZW 1.6 Release Notes - The SwitchMultiLevel CommandClass now exports a Target Level ValueID
This ValueID, if present, should be prefered over the existing Level ValueID, as the level valueID reports "instant" levels, rather than a final level. This causes users issues on devices such as dimmers, where the Value ramps up/down over a period of time, but the level value does not represent what the final value will be.
Just need to confirm no changes are necessary here. If there are, we still need to handle the old 1.4 way (with just a level valueID) as not all devices support the Target ValueID.