Hi there, I have not so much experince with HA but step by step I get this to work but there is one thing that i can’t figure out at the moment and I hope somebody can me explain hoe to solve this.
I get this Error in the Dashboard and I think there something missig but I have no idea.
After a lot of try and error and many readings I have it running with the modifications to my needs. I’ve integrated the German ‘1.Bundesliga’ and ‘2.Bundesliga’.
Now my Question is : Is it possible to colorize the fields that i marked in the above picture?
The first 4 cells are qualified for CL the next 2 cells are for EL and the last cells are going down to second league.
Guessing you could just do an if else else on that ‘#’ column - similar to the rankings up and down code. If ‘#’<=4 do this, if 5-6 do this and if =>16 do this. And the do this is something @kbrown01 worked on last year on the flex-table card here:https://community.home-assistant.io/t/flex-table-card/461173/53
Not sure if you were able to add lines to your template per @bburwell 's share? This is what I do. Add more lines, change them, change the color - your choice. I only define the top 4 (nth-child 4) and bottom 2 (nth-child 16).
@ehcah nice. Do you have a github page? I was going to start building out MLS and UEFA but it looks like you already have that built. Would love to copy those files, sensors, templates, etc. and pay you with heaps of Kudos
@bburwell No github or pastebin. I’m sure I could figure something out though. Happy to share anything I have.
One challenge I’ve run into. With 570 + various sensors for sports alone, my HA server has been slowing down. As a result, I’ve start hashing out some sensors that aren’t required today. As mentioned above, I did update all my multiscrape sensors to rest or template.
I actually pulled all sensors off my server and added them onto a fresh HA install on proxmox where I keep a few machines spun up for other purposes. I thought a dedicated HA Sports Dashboard machine would be the answer. This works well for a few days and then slows. My intention is to add it back as a webpage dashboard on my server.
Yeah I have been noticing the slowdown as well. That was why I asked the question earlier about splitting up the sensors and templates. I plan on streamlining the dashboards and looking to maybe create a seasonal rotation for sports I kind of follow and then keep the main ones year around. I am also going to play around at some point with polling.
Funny thing is that I originally started looking at this because I wanted to have a scrolling marquee that I send updates to a bunch of Hub75’s. Right now I’m just sending Padres updates to a couple WS2812B’s.
Because of @kbrown01 great work this has kind of turned into something akin to eating potato chips - you think you can stop after a couple but there is always another tempting option to chose
Figured I would ask here. I am trying to create a simple template like I use for conferences but for the top 25. My conferences that are almost identical work fine and when I put the code below in the template editor it returns exactly how I expect. But when the code is in the template.yaml I keep getting no entities found.
It looks like you are defining cteam as an array and then using join. Just use
{{ cteams.cteam }}
On output.
Note this one from my templates for red zone (no join):
{% set hteams = namespace(hteam=[]) %}
{% for team in state_attr('sensor.nhl_wildcard','children')[0]['standings']['entries'][2:] %}
{% for stat in team['stats'] | selectattr('name','eq','clincher') %}
{% else %}
{% set hteams.hteam = hteams.hteam + [team] %}
{% endfor %}
{% endfor %}
{{ hteams.hteam }}
Not sure what correctly means, but if those above are you only columns then maybe increase column two to maybe 59% and make the last three 10% each. Even though you have table set to 100%, it is not going to fill 100% because you are placing explicit width on all the columns.
You rules are >=4, >=3, <=2, >=1, anything 2 or less will always match the third if. You should flop that rule to >=2 and likely just use else and not elseif for the last rule.