Lovelace: Check Button Card

Share your Projects! Dashboards & Frontend
68

Yes you will need to add it to your resources

/hacsfiles/check-button-card/check-button-card.js
Type: Module
69

Silly of me, indeed
Now its working, i do know now what is meant with config mode.
I entered some check buttons, and it asked if i wanted it to create…
Good working.
However still some questions…

1)How do i use the dutch translations of months/days… etc etc
i entered & value in dutch but its showing in english
Should i add “text” in the code?
2) can someone explain how to use severity… i see value, hue, color… i understand value, but how do i see how it counts?

  1. should i use mqtt discovery prefix? cause i use mqtt for other stuff too

  2. having some desing issue too
    When using vertical-stack, i dont have the white background, which i dont like

When using custom:stack-in-card, i do have the white background, but i lose space between the check buttons.
How do i get both in one?

70

yes

text:
  days: dayz
  month: m0nth
  months: monthz

from the example

  • check button will start green, after 1 day it will change to blue, after 3 days it will change to red, after 5 days it will change to purple and after 10 days it will change to yellow.
color: Green
severity:
  - value: 5 days
    color: Purple
  - value: 3 days
    color: Red
  - value: 10 days
    color: Yellow
  - value: 1 day
    color: Blue

in “due mode”

  • will start green and display due in 5 days in green, at the 0 day mark it will change yellow, and 1 day after it was due it will be red
due: true
timeout: 5 days
color: Green
severity:
  - value: '-1 day'
    color: Red
  - value: 0 days
    color: Yellow

chances are you dont need to change this, if you for example use smart things, then your broker prefix will be set to something different and you will need to specify for each instance

use card-mod to manipulate and achieve what you want, i use the following inside an entities card

style: |
  ha-card {
    padding: 2px;
    --ha-card-box-shadow: 'none';
    --paper-card-background-color: rgba(0, 0, 0, 0);
  }
1 Like
71

Hi,

Ok layout and text is fixed.
Severity and due mode is clear too

Thx for the support !

72

Guys a small question, do i need to discovery MQTT stay all the time on enabled to work this custom intergration? Or is that only by need when installing or adding the config?

73

Can someone please help me?? I have installed Check Button card via HACS and it is added to the lovelace dashboard automatically. But what is next? Do i need to somehting in Configuration.yaml file?

Where do i need to put this?

{"timestamp":"**timestamp here**","timeout":"2 hours","unit_of_measurement":"timestamp"}
74

This has been working well for me for a long time but now on version 1.2.0 and i get Lovelace Error. Tried to re-install from HACS and it says it does not exist. Has this been removed from HACS or changed name to another project?

75

Yes. It got removed from HACS as it was no longer being maintained.

76

very sad. was really useful… any alternatives out there?

77

How is it no longer maintained when the most recent release was just six weeks ago?

1 Like
78

Because 6 weeks is a lot of time in the world of Home Assistant. The card doesn’t work anymore with the newest releases and the developer didn’t adjust his card accordingly. If he decides to adjust his card and make it work with the newest releases, it’ll probably come back to HACS.

79

I just installed this card from HACS a couple of days ago and set up a bunch of buttons last night. All are working as expected. I am running 0.115.6 of Home Assistant (Supervised) and 1.2.0 of Check Button Card. Is the problem with 0.116 of HASS?

1 Like
80

And now I know. The problem IS with 0.116 apparently. I had not heard how 0.116 was going to be breaking a number of custom cards unless they made some changes. While this particular card wouldn’t be a deal breaker for me, Custom Header certainly was, so I suppose I will be sticking with 0.115.6 for a while.

81

Anyone else having issues after updating to 2021.12?
All my sensors are unavailable allthough everything is there in my mqtt broker
Logs are saying :

  • nvalid state message ‘{“timestamp”:1629904884,“timestamp_friendly”:“8/25/2021, 5:21:24 PM”,“severity”:[{“value”:“3 months”,“color”:“Red”,“seconds”:7889238},{“value”:“2 months”,“color”:“Orange”,“seconds”:5259492}]}’ from ‘homeassistant/sensor/trimmen/state’
  • Invalid state message ‘{“timestamp”:1622303265,“timestamp_friendly”:“5/29/2021, 5:47:45 PM”,“severity”:[{“value”:“3 months”,“color”:“Red”,“seconds”:7889238},{“value”:“2 months”,“color”:“Orange”,“seconds”:5259492}]}’ from ‘homeassistant/sensor/vaccinaties/state’
  • Invalid state message ‘{“timestamp”:1612454233,“timestamp_friendly”:“2/4/2021, 4:57:13 PM”,“severity”:[{“value”:“9 months”,“color”:“Red”,“seconds”:23667714},{“value”:“6 months”,“color”:“Orange”,“seconds”:15778476}]}’ from ‘homeassistant/sensor/ventilatie/state’
  • Invalid state message ‘{“timestamp”:1603529937,“timestamp_friendly”:“10/24/2020, 10:58:57 AM”,“severity”:[{“value”:“24 months”,“color”:“Red”,“seconds”:63113904},{“value”:“20 months”,“color”:“Orange”,“seconds”:52594920}]}’ from ‘homeassistant/sensor/verwarmingsketel/state’
  • Invalid state message ‘{“timestamp”:1639223861,“timestamp_friendly”:“12/11/2021, 12:57:41 PM”,“severity”:[{“value”:“90 days”,“color”:“Red”,“seconds”:7776000},{“value”:“30 days”,“color”:“Orange”,“seconds”:2592000}]}’ from ‘homeassistant/sensor/vijver/state’
82

Same problem here

83

Could it be related to below on 2021.12?
“Timestamp/Date device class value changes
When using datetime and date device classes in sensors, the returned native value must (respectively) be a datetime or date Python object.”

84

Anyone got a fix for this?

85

unfortunatly not yet… also looking for a solution… the idea of the plugin is great; but it’s no longer maintained…

86

Fixed in v1.3.0. Details here.

1 Like
87

Thankyou!!!