Looks like you can easily change the name of the entity!
Anything with a unique_id in yaml can be edited in the Ui.
Thatās why there are no names in the yaml I shared (sometimes only for first addition)
Do we getting somewhere? 
Still one thing, what does the āsaver_offlineā mean/do?
that notifies if there is an issue with the integration connecting to the resource
and before you ask, I have move this to the UI helpers too:
# in UI Helpers Template
# - binary_sensor:
#
# - unique_id: afval_notificatie
# state: >
# {{is_state('input_boolean.afvalwijzer_vandaag_notificatie','on') or
# is_state('input_boolean.afvalwijzer_morgen_notificatie','on')}}
#
# - unique_id: saver_offline
# state: >
# {{not has_value('sensor.afvalwijzer_vandaag')}}
# device_class: problem
Slowly but surely, everything is falling into place, and Iām getting more and more things working. Now, Iām struggling with the notifications. Could it be that Iām missing the āscript.intercom_messageā script? I canāt seem to find this script anywhere.
Cheers H.
A yes, that is in another packageā¦ I hope you understand what itās doing. Completely copying someone elseās config isnāt the best way to start understanding how it all works, but here you go:
intercom_message:
mode: restart
sequence:
- condition: state
entity_id: input_boolean.announce_intercom
state: 'on'
- condition: >
{{has_value(states('sensor.intercom'))}}
- <<: *intercom_volume
- service: tts.cloud_say #tts.google_say
data:
<<: *main_tts
message: >
{% set language = states('input_select.intercom_language') %}
{{message_nl if language == 'Nl' else message_en}}
nevermind the comments, they are take out of production, (but uncommenting them immediately kicks them to life againā¦)
Ive taken out the commented bits, to make it a bit clearer
the yaml anchors are inserted from another script, which is declared above this script.
and goes like:
intercom_text_message:
mode: queued
sequence:
- condition: state
entity_id: input_boolean.announce_intercom
state: 'on'
- condition: >
{{has_value(states('sensor.intercom'))}}
- <<: &intercom_volume
service: media_player.volume_set
data:
entity_id: >
{{states('sensor.intercom')}}
volume_level: >
{{states('input_number.intercom_volume')}}
- service: tts.cloud_say #tts.google_say
data:
<<: &main_tts
cache: false
language: >
{{states('sensor.tts_language')}}
options:
gender: >
{{states('input_select.tts_gender')|lower}}
entity_id: >
{{states('sensor.intercom')}}
message: >
{{states('input_select.intercom_message')}}
ofc and like before, you need all of the entities in those scripts, and some are in the UI (the helpers). Important thing here is that entity_id in the cloud_say service resolves to a factual (list of ) entity_idās. I have that setup elsewhere, but please start with a single entity_id that your hard code in this service.
In fact, you should not copy this at all, and start figuring out the tts services yourself, using your own hardware and conditions (if any), and not copy all of my templated fields, as that is probably beyond your requirements currently.
Again, please open another topic, because this has now way passed the off-topic boundaries for this thread repeatedly. Besides, there are many many related posts on scripts/tts and passing variable to scripts (thatās what this does)
Thanks, @Mariusthvdb. I will give it a try. I hope this is not out of my league! Thanks anyway!
Herman F.
Did you find a solution?
@efleming Hi I know this post is old but I would like to use the bin images if you have a link for them please
Hi, struggling with this for months now. How did you get the rest/gft image split up like this?
Looking forward to hear you!
Herman F.
Hi @19roland70 ,
Did you get the two garbage pick-ups in one day working?
Look forward to hear from you,
Cheers Herman.
No I canāt realize this
Hi Frank,
I think I canāt avoid creating custom images for the collection of multiple types of waste on the same day. However, I canāt seem to split the different images as nicely as you did. For example this one;
Could you please let me know how I can easily do it myself? Or may I provide you with the images for you to split them for us? For now, it appears that I only need two variations, namely āRestafval/Papierā and āGFT/Papier.ā
Looking forward to your response.
Best regards,
Herman
@Mariusthvdb asked me to do some modifications to the afvalwijzer component Iām maintaining.However, I`m not sure what to do, so he asked met to reach out to you. Could you have a look and perhaps point me in the right direction? Thanks!
Hmm, somehow I donāt receive anything for this topic since a long time (I just noticed 
). Iāve updated my profile so I can actively help out again when I receive a notification 
1 Like
Hi @xirixiz,
I replied on GitHub. Just not sure if my comment belongs there. Apologies if it doesnāt.
Best wishes for 2024!
1 Like
@hermanf72 Donāt worry, you posted it at the right place! I`ll have a look later today or tomorrow.
I just noticed that you re-used an open issue. But since this is a ānewā topic, it was better to create a new issue:
Issues Ā· xirixiz/homeassistant-afvalwijzer Ā· GitHub ā Top right āNew issueā.
For now itās fine, but keep this in mind for the future.
Best wishes for 2024.
2 Likes
