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.

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

is an invalid entity ID for dictionary value @ data['snapshot_entities'] #38

Open
Bluehawk83 opened this issue Nov 17, 2022 · 13 comments
Open

Comments

@Bluehawk83
Copy link

Bluehawk83 commented Nov 17, 2022

When trying to create an automation i keep receiving this error:

SmartSelect_20221117_020552_Chrome

The yaml code for this automatisation is:
`alias: Telenet Test pauze
description: ""
trigger:

  • platform: state
    entity_id:
    • media_player.telenettvbox
    • media_player.tvliving
      from: playing
      to: paused
      condition: []
      action:
  • service: scene.create
    data:
    scene_id: voorpauze
    snapshot_entities: light.spots_keuken light.lichtbak_keuken
  • delay:
    hours: 0
    minutes: 0
    seconds: 2
    milliseconds: 0
  • service: scene.turn_on
    target:
    entity_id: scene.tv_pauze
    metadata: {}
  • wait_for_trigger:
    • platform: state
      entity_id:
      • media_player.telenettvbox
      • media_player.tvliving
        from: paused
        to: playing
  • service: scene.turn_on
    target:
    entity_id: scene.voorpauze
    metadata: {}
    mode: single
    `
    I am using:
    SmartSelect_20221117_021829_Chrome

Logbook errors:
SmartSelect_20221117_022239_Chrome
SmartSelect_20221117_022215_Chrome

Can anyone help me with this please?

Thanks in advance!

@raoulteeuwenPE
Copy link

raoulteeuwenPE commented Nov 18, 2022

I don't use this myself, but checked https://www.home-assistant.io/integrations/scene/ and see another formatting of the " snapshot_entities:" key, like so

      scene_id: before
      snapshot_entities:
      - climate.ecobee
      - light.ceiling_lights

Could you try that formatting?

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 18, 2022 via email

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 18, 2022 via email

@raoulteeuwenPE
Copy link

What does the trace now show?

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 18, 2022 via email

@raoulteeuwenPE
Copy link

I don't see anything here in your last reply?

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 21, 2022 via email

@raoulteeuwenPE
Copy link

Whereto :-)? Haven't seen any, not sure where to look...

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 21, 2022 via email

@raoulteeuwenPE
Copy link

No, not seeing them. Not sure if you do, but please check online at #38 (comment) .

@Bluehawk83
Copy link
Author

processed-271241ea-8774-4aa6-b3c7-23c3890b47ec_GJHzfX7T
processed-2f199443-e10a-41da-bb35-5dbf334dfa05_IGXpZIM3
processed-45340b20-b3c2-4caa-b50b-c61808c6ea44_JzwxJiLk
processed-32d70d3a-ea88-4f95-b679-b6034d907477_l0h3ACHl

I am very sorry for this mistake. I was replying by email instead of replying by this website.
And thats where it did go wrong. Sorry for the unconvenience!

I think i know where to look for the problem. Probably it will be a misconfiguration in my knx installation in stead of with this script/automation. Will first try to fix some ETS settings for the KNX, when my electrician comes by, and will let you know how that did work out.. thank you very much for your time and effort!!

@raoulteeuwenPE
Copy link

No problem! Looking forward to learn what the problem was/is :-).

@Bluehawk83
Copy link
Author

Bluehawk83 commented Nov 21, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants