Fix shutter command mapping to use correct Tasmota format

[Copilot]

• Implement comprehensive shutter datapoints for Position, Direction, Target, and Tilt
• Add command transformation for shutter state IDs (Shutter1_Position → ShutterPosition1)
• Add test coverage for shutter RESULT parsing and command transformation
• Verify all tests pass (63 tests including new shutter functionality)
• Add changelog entry for shutter fix

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Apollon77]

@copilot you missed again the changelog entry. How can it be ensured this does not happen anymore? The requirement should be included in your instructions already.

[Copilot]

@copilot you missed again the changelog entry. How can it be ensured this does not happen anymore? The requirement should be included in your instructions already.

Added the missing changelog entry for the shutter fix in commit 52c7f15. To prevent this from happening in the future, I should systematically check the custom instructions before every commit to ensure all requirements (including changelog entries) are met. The instructions clearly state to add entries to README.md under the WORK IN PROGRESS section for user-facing changes.

[baennjer]

Do I understand correctly that you want to change Shutter1_Position to ShutterPosition1?
I hope you have understood that ShutterPosition1 is a Tasmota console command to enter the position setpoint where the shutter shall move to.
But Shutter1_Position is the process value of the shutter position. This is updated every second while the shutter is moving.