is the configuration only possible with the config.js or is a ui-editor (WYSIWYG) for
this dashboard available?
Only config.js for now.
I’m new to TileBoard and to behonest my JS is rather rusty (last used in the 00’s), but I haven’t been able to figure out why my climate tile does nothing to change the temperature on my Netatmo radiator valves. As I gathered upwards in this forum others are able to use the ‘+’ and ‘-’ to set the temperature, but has anyone an idea as to why I don’t seem to be able to get this done?
{
position: [0, 0],
width: 1,
id: 'climate.netatmo_woonkamer',
type: TYPES.CLIMATE,
unit: 'C',
state: function (item, entity)
{
return 'Current ' + entity.attributes.current_temperature + 'C';
}
},
Can you please post state dump of your climate.netatmo_woonkamer from HA?
It turns out that the climate tile does change the settings. The annoying thing is that it takes the tile half a minute to actually change the setting and update itself. So it looks like it is the same issue that @miszi had.
Any suggestions on this? @miszi did you ever sort this out?
This morning my climate-tiles suddenly increment with 0.1 degrees…
They don’t in lovelace.
Can’t find anytning in the docks, but before I go nuts having to press buttons like 20 times, anyone knows it it is possible to set the stepping?
climate.netatmo_woonkamer
auto hvac_modes: auto, heat, off min_temp: 7 max_temp: 35 target_temp_step: 0.5 preset_modes: away, boost, Frost Guard, Schedule current_temperature: 20.8 temperature: 19.5 hvac_action: idle preset_mode: manual battery_level: 100 friendly_name: Woonkamer icon: mdi:home-thermometer-outline supported_features: 17
If climate entity ha target_temp_step attribute it uses it or 1if attribute is not set.
Your thermostat has min/max temperature values, I’m afraid this is not something TileBoard supports at the moment.
Please post an issue on GitHub explaining what exactly is happens and someone will try to look into it.
Will do, thank you for helping out.
1 Like
Projects like this one typically attract more developers than end users. People will take this as a framework and start modifying it to suit their own very specific needs. Many of those modifications are not pushed back as PRs simply because they are too specific and typically take the project into a different direction altogether.
TB is far from dead. For me it was the reason I switched to HA (I don’t like Lovelace). Every single device that accesses HA in my house, from tablets to my mobile phone, uses an individually adjusted version of TB. I added a lot of functionality over time. The problem with contributing anything back is that I modified the TB backend so heavily that nothing would work with the code in the official repo anymore. I’ve talked to at least three other people who are in a similar situation and I suspect there are many more. So the apparent lack of PRs doesn’t mean that TB is dead at all. It’s just that this isn’t your typical one-size-fits-all addon thingy.
So thanks a lot to Alexey and Rafal for this awesome little piece of code 
2 Likes
HELP PLEASE
I have installed TileBoard as per the instruction but when i go the URL in Chrome i get a blank screen with the default background colour.
Is this normal from the default files ?
Please open browser console and see what error message is being displayed.
Good pointer @resoai … when i looked at that turned out i had to change the ws connection to wss
Thanks
Hi there! I’ve been using Tileboard on an older version of Home-Assistant (0.93 I think) for a few years now and loved it.
This week, I redid my whole system from scratch using the latest home-assistant (2021.2.1) and redid my setup with Tileboard version 2 as well.
Everything works great and I find the new version of Tileboard easier to navigate in the code. Good job on this!
However, I’m just having an issue with TEXT_LIST. I used to have a TEXT_LIST of all my windows and door showing with the appropriate icon (ex. icon of an open window when it’s open and a close window when it’s close)
With my new setup, I’m struggling with this as the icons doesn’t show up.
In my old setup, i created a template to convert my Binary sensors of my windows/door contact to a regular sensor in my configuration.yaml file.
- platform: template
sensors:
sensor_ariane_et_salle_de_bain:
value_template: >-
{% if is_state('binary_sensor.ariane_et_salle_de_bain', 'on') %}
OUVERT
{% else %}
fermée
{% endif %}
icon_template: >-
{% if is_state('binary_sensor.ariane_et_salle_de_bain', 'on') %}
mdi:window-open
{% else %}
mdi:window-closed
{% endif %}
I know the template works as the icons shows up in Lovelace.
Then I created my TEXT_LIST using this new sensor in the config. js file.
position: [0, 0],
width: 2,
height: 2,
title: null,
id: {},
type: TYPES.TEXT_LIST,
state: false,
list: [
{
title: 'Fenêtre chambre Ariane et salle de bain',
icon: '&sensor.sensor_ariane_et_salle_de_bain.attributes.icon',
value: '&sensor.sensor_ariane_et_salle_de_bain.state'
},
]
But with the new update, the icons doesn’t show up.
I’m wondering if it’s because the value ***.attributes.icon is not valid anymore in Home-Assistant 2021.2.1?
Thanks for the help! 
You can check in HA states which attributes are available for this entity. You could also define icon as a function and return whatever icon you want based on the state of that entity by doing something like this:
icon: function() {
return this.parseFieldValue('&binary_sensor.ariane_et_salle_de_bain.state') == 'on' ? 'mdi:XXX' : 'mdi:YYY';
}
Thanks a lot! I couldn’t make it work with the attributes but the fonction code works great. I also used this to change the value of my sensor from ‘on’ to ‘ouvert’. Way simpler than creating templates.
Thanks again!
1 Like
I have an other question. I’m trying to change the background color of the alarm button depending if it’s disarmed or armed.
I’m using this code in the CSS. Works when the alarm is off but not when it’s on. It used to work with version 1.
.item.-th-alarm
{background-color:rgba(0, 0, 0, 0.2);
border:1px solid hsla(0,0%,0%,.8)
}
.item.-th-alarm.-armed
{background-color:rgba(200, 0, 0, 1);
border:1px solid hsla(0,0%,0%,1)
}
This is likely because of a change in HA itself. Previously the alarm probably only had an armed state and now it can have various different armed states: armed_custom_bypass, armed_home, armed_night, and armed_away. So use those in your selector to override their color.