new states request for Hockey

[xenia-09A]

Hi for Hockey can you add the following states as an example(you can change as desired):
five minutes left in 3rd period : IN to FINAL5
end of game: FINAL5 to POST
end of third period but game in overtime FINAL5 to OT
end of game in OT: OT to POST
end of OT but game in shootout: OT to SO
end of game in SO: SO to POST

Lastly is it possible to send PRE 30 minutes prior to game time? and thanks for doing this integration! much appreciated!

[xenia-09A]

Hi sorry for one of these I see clock turns to 'Final' when game is over

[vasqued2]

The state is controled and returned by the ESPN API, not me. I just pass it along. What are you trying to do? There are probably other ways to accomplish it.

[xenia-09A]

It be nice to get PRE like 30 minutes before game start, For five minutes left in 3rd period I think I can code some solution with the clock data but maybe easier for others if you can also set something to trigger on. I like to also trigger on OT or game went to SO(shoot out).

thanks I love the card and this integration as avid hockey fans.

edit: I see IN starts at game time so I can trigger on that

[vasqued2]

You should be able to trigger everything you want to do off of existing sensor attributes.

Use kickoff_in or date to trigger something before the game starts.
Use clock and quarter to trigger something with 5 minutes left in the third period.
Use quarter to trigger your OT or shootout actions as it should increase to 4, 5, 6, etc. I've confirmed w/ soccer but hockey so rarely goes into OT/SO I haven't ever caught the json to confirm but it should behave the same.

Changing the behavior of something as basic as the sensor state in a non-backward compatible manner would impact many existing automations others have already set up.

[xenia-09A]

Hi yes as I mention one can, but my point was asking to make it easier for others with this being native instead of custom yaml to get all this!

thanks you can close this

[vasqued2]

The thing I learned is everyone wants something a little different based on a sport or their bias. You want a 5 minute warning for hockey. Soccer wants a two minute warning. You want an alert 30 minutes before gametime, someone else wants it 20 minutes or 10 minutes or an hour.

Even something as simple as a score change is different. Soccer and hockey want alerts, football on touchdowns, volleyball after a game is won.

Given all the variations, it either becomes a lot of sport-specific custom code or tons of extremely complex configurations.

In the end, I made the design decision to expose the attributes and let people use them in whatever way they want. It gave people more freedom to do what they wanted instead of my locking them in. Hope this helps you understand.

Thanks for the kind words.

[xenia-09A]

Thanks for all you do! Yes it makes sense from what you see from everyone. Thanks for the tips and I will track quarter to see if it changes to 4 when hockey goes to OT.