On "stop" from external remote MQTT only reports the target position, but not current position

[smumriak]

Hardware

ESP32

Firmware version

v2.4.7

Application version

v2.4.7

What happened? What did you expect to happen?

Inverted positioning! Sending shades down from external remote. Shade starts moving, it's target is set to 0, position gets updated. Sending shades stop from external remote. Last position update is at 89%, target position update is at 88%. This unfortunately breaks integration with homebridge, shades are in permanent "closing state" after stopping movement.

How to reproduce it (step by step)

1. Press down on external remote.
2. Press stop on external remote.
3. Observe MQTT logs.

Logs

espsomfy/shades/2/target 0
espsomfy/shades/2/cmdSource remote
espsomfy/shades/2/cmdAddress 15315477
espsomfy/shades/2/cmd Down
espsomfy/shades/2/direction 1
espsomfy/shades/2/position 99
espsomfy/shades/2/position 98
espsomfy/shades/2/position 97
espsomfy/shades/2/position 96
espsomfy/shades/2/position 95
espsomfy/shades/2/position 94
espsomfy/shades/2/position 93
espsomfy/shades/2/position 92
espsomfy/shades/2/position 91
espsomfy/shades/2/position 90
espsomfy/shades/2/position 89
espsomfy/shades/2/target 88
espsomfy/shades/2/cmdSource remote
espsomfy/shades/2/cmdAddress 15315477
espsomfy/shades/2/cmd My
espsomfy/shades/2/direction 0

[smumriak]

I expect that upon stopping the code would publish both position and then target at 88 in this example