Expose Next Game DateTime as Attribute

[databoy2k]

This adds a new attribute, "Next game datetime," which exposes the date and time of the next game in a single attribute. This is necessary if you want to have automations that rely on the start time.

Probably not being defined in the best place (I am a neophyte at Python); maybe there's a better place for it to be placed?

Sample automation.yaml:

• id: leafsgamestart alias: Leafs Game Start trigger:
  • platform: state entity_id: sensor.leafs_game to: "Pre-Game" condition:
  • condition: time before: '18:30:00' action:
  • wait_template: "{{ as_timestamp(states('sensor.date_time_iso')) == as_timestamp(state_attr('sensor.leafs_game', 'next_game_datetime') - timedelta(minutes=5)) }}"
  • condition: state entity_id: input_select.tam_status state: 'Home'
  • service: media_extractor.play_media entity_id: media_player.all_speakers data: media_content_id: "https://www.youtube.com/watch?v=jkG2dLl0Gso" media_content_type: "audio/youtube"
  • delay: 56
  • service: media_extractor.play_media entity_id: media_player.all_speakers data: media_content_id: "https://www.youtube.com/watch?v=dwpqiaWKPkQ" media_content_type: "audio/youtube"

[ctml91]

Sweet, was hoping to have access to this attribute!

[JayBlackedOut]

next_game_datetime is already a key-value pair provided by the pynhl API wrapper (also written by me) that's used by this component . There's a cleaner way to do this but you have the right idea. I'll work on this once I'm back in town in a week.

[databoy2k]

next_game_datetime is already a key-value pair provided by the pynhl API wrapper (also written by me) that's used by this component . There's a cleaner way to do this but you have the right idea. I'll work on this once I'm back in town in a week.

Thanks. I don't mind moving it, either. I just got tired of manually editing the component for each update (haha).

Thanks, Jay.

[JayBlackedOut]

Changes committed directly to master branch. Will release Version 0.10.1 that incorporates changes.