Bug: undefined state: Actual_Position and actual_angle not called/used

[RobertWeit]

The interface of Position and tilt doesn't show the current position nor angle if it was set by another controller, e.g. Alexa, or onyx.click.

reproduce: open one onyx device, move it to pos50 and tilt 50. close the device, reopen it, you'll see pos100 and angle100, although it moved to 50 and 50

This bug blocks the usage of cover.terrasse current_position and current_tilt_position as they are always at 0 or 100. The overall target application: create a Close1StepAutomation for a Raffstore, by checking the current _tilt and increase/decrease the target with e.g. 10degrees/percent.

This might relate to he button behaviour: some device do not allow up or down button interaction:

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[muhlba91]

thanks for your report and the details! 😀

i'm currently on vacation but would like to request more logs from your side that will help troubleshooting this.

could you turn on debug logging and then use the clock devices and/or alexa to move the shutters, grab the logs from HA and post them here?

i'm relying on the API's streaming endpoint and would like to see how these actions are streamed by the ONYX device.

if you are able to identify the ID of the shutter, it would help to speed up identifying at which device i need to look at. 😄