[BUG] Error with max. value for Tilt Angle

[granturism0]

Hi @johannrichard
In my logs i see a lot of this errors: [homebridge-dingz] This plugin generated a warning from the characteristic 'Current Horizontal Tilt Angle': characteristic was supplied illegal value: number 100 exceeded maximum of 90. See https://git.io/JtMGR for more info.
I think something is wrong with the maximum value.
PS: I use the latest firmware (1.3.30)
Greetings,
Granturismo

[github-actions]

🎉 This issue has been resolved in version 3.2.0-alpha.5 🎉

The release is available on:

• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 3.2.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[johannrichard]

I know it's been a while since you reported the bug. In case you still use the plugin, I'd be grateful if you could check whether the beta indeed solves the issues here.

[johannrichard]

I know it's been a while since you reported the bug. In case you still use the plugin, I'd be grateful if you could check whether the beta indeed solves the issues here.

N.B.: I tried to test it as much as possible. What's irritating me: if I move the slider in the Dingz WebUI to 100%, HomeKit will indeed display the maximum tilt angle of 90°. However, the slider just above that will display a value less than the maximum. OTOH, if I move the HomeKit Slides to 100% while the value of the angle is less than 90°, everything moves as well, but if I move the slider to the max, it somehow stalls.

[github-actions]

🎉 This issue has been resolved in version 3.2.0-alpha.9 🎉

The release is available on:

• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[johannrichard]

Did some more tests (and tweaks to the code). The warnings are (mostly IMHO) gone now and the values set should now be all converted between ° and % (and vice-versa) at the right place.

[github-actions]

🎉 This issue has been resolved in version 3.2.0-beta.3 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀