no. as I explained above, you save them in the /www folder.
that is part of my dashboard, and also posted more than a few times in this thread
since you’re new, my advise would be to take it 1 step at a time, and not try to create a rather complex card like this immediately. use the building blocks, (the image shown there is the markdown section ) and see if you can create that first. That particular section though is made with several non-afvalwijzer entities in my own config.
I used the following code (in configuration.yaml), after I downloaded afvalwijzer from HACS:
sensor:
- platform: afvalwijzer
provider: mijnafvalwijzer # (required, default = mijnafvalwijzer) either choose mijnafvalwijzer, afvalstoffendienstkalender or rova
postal_code: 1234AB # (required, default = '')
street_number: 5 # (required, default = '')
suffix: '' # (optional, default = '')
exclude_pickup_today: true # (optional, default = true) to take or not to take Today into account in the next pickup.
default_label: Geen # (optional, default = Geen) label if no date found
id: '' # (optional, default = '') use if you'd like to have multiple waste pickup locations in HASS
exclude_list: '' # (optional, default = '') comma separated list of wast types (case ignored). F.e. "papier, gft"
I see you are using the built-in UI for creating this card. I fear we have to stop there. you can not create the card you like in UI mode, and need YAML mode for that. Let alone all the many customizations needed for it.
You can ofc set pictures and entities, but not in the complexity of that card you posted
here’s 1 picture-entity card (already modded by card_mod), you could try in the UI editor:
Here is my automation for achieving that. You might think it is a little peculiar. That is because I want the TTS-announcement only when there is motion in the living room. To make sure someone definitely gets the message. This automation will try to make the announcement between 20 and 21 hours on motion. Feel free to just take out the parts you need
- alias: Reminder tomorrow trash day
trigger:
- platform: time_pattern
hours: '20'
minutes: '/1'
condition:
condition: and
conditions:
- condition: template
value_template: "{{ states('sensor.afvalwijzer_tomorrow') != 'Geen' and states('sensor.afvalwijzer_tomorrow') != 'unknown' }}"
- condition: time
after: '20:00:00'
before: '21:00:00'
- condition: template
value_template: "{{ ((as_timestamp(now()) - as_timestamp(states.binary_sensor.pir_woonkamer.last_changed)) /60 ) | int < 2 }}" #Less than two minutes ago there was motion in the livingroom
- condition: state
entity_id: input_boolean.trash_reminder_done
state: 'off'
action:
- service: script.announce_downstairs
data:
my_message: "Morgen is afvaldag voor {{states('sensor.afvalwijzer_tomorrow')}}."
sure, but what dont you get? does the automation not work?
as example for the conditions:
- alias: Afval vandaag
id: afval_vandaag
trigger:
platform: time
at: '07:00'
condition:
- >
{{states.sensor.afvalwijzer_today is not none}}
- not:
condition: state
entity_id: sensor.afvalwijzer_today
state: Geen
action:
- service: script.intercom_message
data:
message_nl: >
Het is {{now().strftime('%A %-d %B')}}: vandaag wordt {{states('sensor.afvalwijzer_today')}} opgehaald!
message_en: >
It is {{now().strftime('%A %-d %B')}}: today {{states('sensor.afvalwijzer_today')}} will be collected!
- service: script.persistent_trash_today
- service: script.trash_outside_today
tomorrow:
- alias: Afval morgen
id: afval_morgen
trigger:
platform: time
at: '21:00'
condition:
- >
{{states.sensor.afvalwijzer_tomorrow is not none}}
- not:
condition: state
entity_id: sensor.afvalwijzer_tomorrow
state: Geen
action:
- service: script.intercom_message
data:
message_nl: >
Het is {{now().strftime('%d %B')}}: Morgen wordt
{{states('sensor.afvalwijzer_tomorrow')|title}} opgehaald!
message_en: >
It is {{now().strftime('%d %B')}}: Tomorrow
{{states('sensor.afvalwijzer_tomorrow')|title}} will be picked up!
- service: script.persistent_trash_tomorrow
- service: script.trash_outside_tomorrow