A I see.
I do have couple of these and they ‘store’ all notifications . And some others.
When I get back to my system I’ll check exactly.
filed_daylight _settings.txt: 86kb
18 Jun 04:55:08: Daylight: off - Elevation: -4.0 - Light level: 3242
18 Jun 22:34:43: Daylight: on - Elevation: -4.35 - Light level: 3242
19 Jun 04:55:11: Daylight: off - Elevation: -4.0 - Light level: 3242
19 Jun 22:35:03: Daylight: on - Elevation: -4.35 - Light level: 3242
20 Jun 04:59:17: Daylight: off - Elevation: -3.57 - Light level: 231
20 Jun 22:35:19: Daylight: on - Elevation: -4.35 - Light level: 3242
21 Jun 04:55:28: Daylight: off - Elevation: -4.0 - Light level: 3242
21 Jun 22:35:32: Daylight: on - Elevation: -4.35 - Light level: 231
22 Jun 04:59:41: Daylight: off - Elevation: -3.57 - Light level: 6252
22 Jun 22:35:42: Daylight: on - Elevation: -4.35 - Light level: 3242
23 Jun 04:55:59: Daylight: off - Elevation: -4.0 - Light level: 3242
23 Jun 22:35:49: Daylight: on - Elevation: -4.36 - Light level: 0
24 Jun 04:56:20: Daylight: off - Elevation: -4.0 - Light level: 231
24 Jun 22:35:53: Daylight: on - Elevation: -4.36 - Light level: 231
25 Jun 04:56:45: Daylight: off - Elevation: -4.0 - Light level: 231
using these type of sensors to understand when and why and to be able to adjust settings.
filed_intercom_messages.txt 258 kb
filed_notifications.txt 1.4 Mb
and 2 older ones, no longer daly updated (automation == off) but still exist:
filed_automations.txt: 16.6 MB
filed_ios_messages.txt 6kb
the all use templates ofc, so maybe that counts twice as heavy ? I mean, templates and the file sensor behavior?
especially maybe because there’s also a template in the service itself:
sensor:
- platform: file
file_path: /config/logging/filed_notifications.txt
name: Filed notifications
value_template: >
{% if value is not none %}
{% if value|length < 255 %} {{value}}
{% else %} Truncated: {{value|truncate(240,True, '')}}
{% endif %}
{% endif %}
automation:
- alias: Forward notifications to filed notifications
id: forward_notifications_to_filed_notifications
mode: queued
trigger:
platform: event
event_type: call_service
event_data:
domain: notify
condition:
>
{{trigger.event.data.service not in
['filed_notifications','filed_automations','filed_intercom_messages']}}
action:
service: notify.filed_notifications
data:
message: >
{% set message = trigger.event.data.service_data.message %}
{% set service = trigger.event.data.service %}
{{now().timestamp()|timestamp_custom('%d %b: %X')}} - {{service}}: {{message}}
or eg:
- alias: Person forward intercom messages to filed intercom messages
id: person_forward_intercom_messages_to_filed_intercom_messages
mode: queued
trigger:
platform: state
entity_id: script.intercom_text_message
condition:
>
{{trigger.to_state is not none}}
action:
- condition: >
{{trigger.to_state.context.user_id is not none}}
- service: notify.filed_intercom_messages
data:
message: >
{% set message = states('input_select.intercom_message') %}
{% set device = states('input_select.intercom') %}
{% set language = states('input_select.intercom_language') %}
{% set id = trigger.to_state.context.user_id %}
{% set time = now().timestamp()|timestamp_custom('%d %b: %X') %}
{% set user = states.person|selectattr('attributes.user_id','eq',id)|first %}
{% set user = user.name %}
{{time}}: {{user}} played "{{message}}" on {{device}} in {{language}}
let me know if you need more
I make the py-spy recordings outside of the instance…
