šŸˆ AWTRIX Light - NFL Team Scorboard

Blueprints Exchange
,
1

Hello.
here is my first Bueprint for you folks.

awtrix

nfl_app
nfl_app800Ɨ673 76.5 KB

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.
More Info and Screenshots in the Blueprint

Before using this blueprint, ensure that you have HACS installed. You also need the ha-teamtracker integration

You need a Ulanzi TC001 Clock with Awtrix Light Firmware INFO
Special Thanks to RobG
This would not be possible without him

SCR-20231029-qhjq
SCR-20231029-qhjq2594Ɨ2096 330 KB

4 Likes
2

Great work with this blueprint! works very nice on my AWTRIX device!

1 Like
3

running great so far !

4

found a typo in the blueprint. Now it is up to date :wink:

5

Thanks for the blueprint. Try to use it for the german soccer Bundesliga. Is this possible?

How to change the colour of the score from white to black?

6

canā€™t get it to work not seeing it on my clock ive imported blueprint set everything am I missing something?

7

FYI: Initial impression is that this works out of the box for the NHL, it might be worth adding to the docs. Well, I still have to see an overtime to confirm 4th pip appears as overtime.

8

Great, Thnx. See Soccer score from Bundesliga ))

9

Can anyone share a screenshot of their working settings? I have this installed and configured but nothing ever gets displayed on my clock. I suspect it is the ā€œAwtrix Application nameā€ setting is maybe wrong but i do not know what to put here.

10

It looks like whatā€™s happening is the automation is creating a malformed JSON when it sends it to MQTT topic and it gets dropped by the board. I looked at the payload in my MQTT broker and there are a couple of lines where the color hex values donā€™t have a closing quote which breaks the json. I havenā€™t looked at the automaton yet to see what section is failing.

11

You have to edit the blueprint and look for the lines that contain #5F5F5F (lines 79 to 84) and make sure that they all have a closing quote.

Once I changed them to this:

first_quarter: '{"dp":[12,7,"#ffffff"]}, {"dp":[14,7,"#5F5F5F"]}, {"dp":[17,7,"#5F5F5F"]},
    {"dp":[19,7,"#5F5F5F"]},'
second_quarter: '{"dp":[12,7,"#ffffff"]}, {"dp":[14,7,"#ffffff"]}, {"dp":[17,7,"#5F5F5F"]},
    {"dp":[19,7,"#5F5F5F"]},'
third_quarter: '{"dp":[12,7,"#ffffff"]}, {"dp":[14,7,"#ffffff"]}, {"dp":[17,7,"#ffffff"]},
    {"dp":[19,7,"#5F5F5F"]},'

It started showing up on the board correctly.

12

Iā€™ve forked this and added the ability to trigger intermission timers - for my interest wrt NHL games. Eg regular intermissions are about 19:30 in duration but between broadcast lags and api latency I set 17:30 and it works out to when the coverage resumes. Iā€™ve also set overtime timer of 90s or so and that works out during the regular season (post-season would be the same time as the regular season but Iā€™ve not tackled this).

Without the forked blueprint the intermission timers can be installed using this gist (to be fair the fork is more recent): Team Tracker NHL Intermission Timers Ā· GitHub

Iā€™ve not packaged it yet but Iā€™ve also implemented Awtrix displays of intermission timers, as three automations to start, update and stop the app, but Iā€™ve not thought of an effective way to package it. eg, maybe youā€™d install the tracker, 3 blueprints, the timer and you need the awtrix integration of course. Ugh. (The intermission timer updates every second so you do not want that running all the time and that increases complexity).

awtrix
awtrix1052Ɨ260 1.86 KB

Here itā€™s just showing a hypothetical 5 minute timer. It updates per second and the bottom line is a progress bar, with a game on! message when complete. It uses the home team colours for the timer.

13

I get an invalid parameters message click the link to import the blueprint. Anyone else? Apparently, I get this error trying any import blueprint link. :smiling_face_with_tear:

14

If youā€™re trying my fork Iā€™ve been futzing with it so it may be my bad. I didnā€™t think anyone was using it or I would have worked off main.

Now Iā€™m seeing a blueprint/template variable issue and Iā€™m not sure why. Sometimes iterating on this can be irritatingly slow.

As to the templates maybe it never worked? but my non-blueprint automations made it look like it was working. The existing quarter change code works well enough for everything except (NHL) overtime so I may just revert to that.

Iā€™ve also added a countdown display for the next game when it enters the PRE state and which mostly works but I think was actually blocked by the above issue.

15

Nothing to do with your fork. It was an issue for me simply using the ā€˜Import Blueprintā€™ button. The import button started working at some point though I made no changes. Iā€™m trying to use the blueprint to create an automation to send score updates to my Awtrix when my Liverpool Premier League team scores. I already had team tracker working which flashes my living room lights when they score. That doesnā€™t need MQTT to do its work. So far had no luck with this one. I verified I have MQTT working but I never see a payload sent when either testing or an actual score happens this morning using the blueprint. Debug shows an error with ā€˜Tā€™ in trigger. Stumped at the moment.

16

Thinking about it, I may have come across the issue youā€™re having then! Let me do a diff with the originalā€¦

Oh what version of the firmware are you running? > 0.96? I have two and one was 0.94 and somewhere around there the device name changed from Awtrix Light to Awtrix 3.

Meanwhile Iā€™ll check the diffs. edit: Hmm, while I did update the blueprint to use some more modern templates that shouldnā€™t have fixed a broken issue. Everything else appears to be my additions.

17

The template changes were like this, but it shouldnā€™t be necessary:

image
image1328Ɨ222 31.3 KB

ie, platform to trigger, and I removed the list for entity_id.

18

Awtrix Light firmware is .98. Just received two days ago.

19

In case it helps, my debugging box here is a collection of things:

  • Logs - kind of irritating because the amalgamation makes seeing changes/attempts more difficult
    • raw is the workaround though.
  • Listen in the MQTT configure integration on topic awtrix_XXXXX/custom/sportsteamname
  • while debugging I keep the default app name sportsteamname for speed when re-configuring but from my tests this has been working fine when changed
  • Use the Developer > States to set the values to known trigger conditions (while listening in mqtt)
  • In the Automation > Traces carefully examine the rendered payloads on triggered actions
  • cut and paste the triggered values into the Awtrix push_app_data service and see if renders correctly then
    • with a `ā€œlifetimeā€: 10," prefix to remove it from the screen quickly once verified to help prevent confusing with working conditions
    • and verifying it disappears before another test.

You do have to have the Awtrix integration from 10der to use the last step. I donā€™t think it should be required since mqtt for everything else but maybe it is? GitHub - 10der/homeassistant-custom_components-awtrix: HASS awtrix

20

As far as the model name you should be good then with the latest. The symptoms for this were that no devices would appear in the blueprint when creating a new automation, eg even though Iā€™d already configured one previously. Version mismatch over time basically.