Velux core velocity over-written

[PhillyGilly]

The problem

I have a number of Velux devices (tilting windows and blinds) which I have recently added to HA via the Velux integration and the KLF200 unit. When set up and controlled locally, these devices operate in "silent" mode. This is essential for use in bedrooms. When the devices are copied over into HA the velocity setting is overwritten with "fast" which is basically unusable in bedrooms and generally undesirable. The vlxpy.py contains the relevant velocity classes

    """Enum class for velocity."""
    DEFAULT = 0
    SILENT = 1
    FAST = 2
    NOT_AVAILABLE = 255

It appears that HA is using the default. If the KLF isn't actually holding the downloaded velocity values in an accessible form then it should be possible for HA to pass the velocity as data to the KLF e.g.

- service: cover.open_cover
      data:
           velocity:
              silent
         target:
            entity_id: cover.blind_bedroom_2

What version of Home Assistant Core has the issue?

core-2023.6.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Velux

Link to integration documentation on our website

https://www.home-assistant.io/integrations/velux/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @julius2342, mind taking a look at this issue as it has been labeled with an integration (velux) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `velux` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign velux` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

velux documentation velux source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[PhillyGilly]

It looks like this is an omission in the underlying VELUX.py . So we can suspend this request until we can get that updated. Thanks.

On Thu, 28 Sept 2023, 10:05 issue-triage-workflows[bot], < @.***> wrote:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95604#issuecomment-1738757925, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANNKV75LKB2GP67L4QROR7LX4U4W7ANCNFSM6AAAAAAZZRESME . You are receiving this because you authored the thread.Message ID: @.***>

[Freggle1981]

Hi, Are there any News about silent Mode for devices Connect es to a KLF200? I am running on Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 11.1 Frontend 20231005.0 - latest And silent Mode seems to be still "ignored"

[PhillyGilly]

I now think this is a problem in the pyVLX interface to the Velux API https://pypi.org/project/pyvlx/ rather than with the HA integration itself. So I have raised an issue on that https://github.com/Julius2342/pyvlx/issues/342. No response yet.

[PhillyGilly]

It looks like we have some progress here https://github.com/Julius2342/pyvlx/issues/342. Thanks @Julius2342

[Julius2342]

Yes, we merged a large MR by @pawlizio into main branch of pyvlx library today and will bump a version asap.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.