core icon indicating copy to clipboard operation
core copied to clipboard

Velux reboot_gateway not possible anymore

Open mmoelli opened this issue 1 month ago • 3 comments

The problem

The automation to restart the gateway when restarting HA does not work any more. Obviously, the reboot_gateway command was deprecated. Therefore, the restart is not working anymore and also the integration failing often.

Image

What version of Home Assistant Core has the issue?

core-2025.12.1

What was the last working version of Home Assistant Core?

core-2025.10.1

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

Triggered manually at December 8, 2025 at 6:09:15 PM Error in describing action: Cannot read properties of undefined (reading 'reboot_gateway') Stopped because an error was encountered at December 8, 2025 at 6:09:15 PM (runtime: 0.00 seconds)

Action velux.reboot_gateway not found

Example YAML snippet

id: 'XXXXX'
alias: KLF reboot on hass stop event
description: Reboots the KLF200 in order to avoid SSL Handshake issue
trigger:
  - platform: homeassistant
    event: shutdown
condition: []
action:
  - data: {}
    action: velux.reboot_gateway
mode: single

Anything in the logs that might be useful for us?

There is a new reboot button introduced to the integration, but I don't know how to integrate this for the automation. Or is this not necessary anymore to have the automated reboot? Please advise. Unfortunately, I haven't found any information on this topic.

Additional information

No response

mmoelli avatar Dec 08 '25 17:12 mmoelli

Hey there @julius2342, @deermaximum, @pawlizio, @wollew, 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.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


velux documentation velux source (message by IssueLinks)

home-assistant[bot] avatar Dec 08 '25 17:12 home-assistant[bot]

Hm, a few comments on this:

  1. the action itself should still be available, it is deprecated (since 2025.12.0) but it should still exist and also be usable, so this is weird. Are you sure your Velux integration loaded successfully? Can you go to "Developer Tools -> Actions" and check if you can find the action there?
  2. Indeed, the reboot automation is not necessary anymore at all (actually for quite a while), HA should reboot the gateway automatically on restart even without the automation (this was introduced ~1 year ago)
  3. If you need the gateway reboot for other reasons, you would replace "velux.reboot_gateway" with a button press action and the KLF 200 gateway as the target entity. In YAML it would look something like this
action: button.press
target:
  entity_id: button.klf_200_gateway_restart
data: {}

wollew avatar Dec 08 '25 18:12 wollew

I use the automation too and it still works My YAML is a little bit different:

description: Reboots the KLF200 in order to avoid SSL Handshake issue
mode: single
triggers:
  - event: shutdown
    trigger: homeassistant
conditions: []
actions:
  - data: {}
    action: velux.reboot_gateway

frontside76 avatar Dec 10 '25 05:12 frontside76