Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Supported features in blueprint imports are transformed to invalid values #103431

Closed
ludeeus opened this issue Nov 5, 2023 · 13 comments · May be fixed by #139852
Closed

Supported features in blueprint imports are transformed to invalid values #103431

ludeeus opened this issue Nov 5, 2023 · 13 comments · May be fixed by #139852
Labels
integration: blueprint

Comments

@ludeeus
Copy link
Member

ludeeus commented Nov 5, 2023

The problem

I have a blueprint with this input:

  input:
    update_entity:
      name: Update entities
      description: The update entities that should be controlled
      selector:
        entity:
          filter:
            domain: update
            supported_features: [update.UpdateEntityFeature.SPECIFIC_VERSION]

And this is working the way I expect it to work, I'm only able to select entities matching that filter.
But if someone is importing this blueprint from URL, the supported_features part is transformed into an invalid value.

This is the resulting input after using the import feature:

  input:
    update_entity:
      name: Update entities
      description: The update entities that should be controlled
      selector:
        entity:
          filter:
          - domain:
            - update
            supported_features:
            - 2
          multiple: true

The UI allows this and the selector is rendered with the expected filter, but when you save an automation that uses this you will get an error like this:

There is an error in this Blueprint: Invalid blueprint: expected str @ data['blueprint']['input']['update_entity']['selector']['filter'][0]['supported_features'][0][0]. Got None

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

Unknown if this has ever worked

What type of installation are you running?

Home Assistant OS

Integration causing the issue

blueprint

Link to integration documentation on our website

https://www.home-assistant.io/docs/automation/using_blueprints/

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
Copy link

home-assistant bot commented Nov 5, 2023

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (blueprint) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of blueprint 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 blueprint Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

blueprint documentation
blueprint source
(message by IssueLinks)

@issue-triage-workflows
Copy link

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.

@ludeeus
Copy link
Member Author

ludeeus commented Feb 3, 2024

Still a problem in current dev

@github-actions github-actions bot removed the stale label Feb 3, 2024
@issue-triage-workflows
Copy link

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.

@ludeeus
Copy link
Member Author

ludeeus commented May 6, 2024

Tested again now on dev (4fce99e) still a problem.

@issue-triage-workflows
Copy link

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.

@ludeeus
Copy link
Member Author

ludeeus commented Aug 4, 2024

I give up, just close it.

@github-actions github-actions bot removed the stale label Aug 4, 2024
@paperh8rrr
Copy link

The problem

I have a blueprint with this input:

  input:
    update_entity:
      name: Update entities
      description: The update entities that should be controlled
      selector:
        entity:
          filter:
            domain: update
            supported_features: [update.UpdateEntityFeature.Feature Homepage 



This is the resulting input after using the import feature:

```yaml
  input:
    update_entity:
      name: Update entities
      description: The update entities that should be controlled
      selector:
        entity:
          filter:
          - domain:
            - update
            supported_features:
            - 2

``

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

Unknown if this has ever worked
I have never set up homeassistant. io
Van Clad Hill Arnold Mo 63010

Link to integration documentation on our website

https://www.home-assistant.io/docs/automation/using_blueprints/

Diagnostics information

No response

Example YAML snippet

No7 response

Anything in the logs that might be useful for us?

No response

Additional information

#103431 (comment)

@paperh8rrr
Copy link

blueprint for
x:Westley House
8834 Van Clad Hill Arnold Mo 63010
botique@homeplan.com

@paperh8rrr
Copy link

x:Westley House

@paperh8rrr
Copy link

[Package: org-super-agenda
Fetcher: github
Source: https://github.com/alphapapa/org-super-agenda

Updating /mnt/store/melpa/working/org-super-agenda/
Checking out d0954b8e7780a4efe49ab32fc11941db21c22bfd
Copying files (->) and directories (=>)
from /mnt/store/melpa/working/org-super-agenda/
to /tmp/org-super-agendarT5JtR/org-super-agenda-20240916.1753
org-super-agenda.el -> org-super-agenda.el
org-super-agenda.info -> org-super-agenda.info
Created org-super-agenda-20240916.1753.tar containing:
org-super-agenda-20240916.1753/
org-super-agenda-20240916.1753/dir
org-super-agenda-20240916.1753/org-super-agenda-pkg.el
org-super-agenda-20240916.1753/org-super-agenda.el
org-super-agenda-20240916.1753/org-super-agenda.info
✓ Success:
2024-10-05T01:39:13+0000 org-super-agenda-20240916.1753.entry
2024-10-05T01:39:13+0000](url)

@paperh8rrr
Copy link

[ I give up, just close it.](x:Westley House)

@issue-triage-workflows
Copy link

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.

@joostlek joostlek removed the stale label Jan 3, 2025
@ludeeus ludeeus closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2025
@joostlek joostlek mentioned this issue Mar 5, 2025
Draft
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integration: blueprint
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make sure supported features work in Blueprints joostlek/core
3 participants
@joostlek @ludeeus @paperh8rrr