WTH - Why are there no Output Helpers?

[noswanson1982]

Why are there no Output Helpers?

I want a Helper that can output state information from scripts / automations. These would function similarly to input helpers, with the caveat of not being editable in the dashboards. They would be used to output information only.

This is similar to how template sensors function, but with less limitations:

1. Their states can be changed and updated with scripts and automations.

2. Their state will be preserved (much like input helpers) during reloads (from power outage, etc).

3. A state change will not happen when a state change is not wanted.

But would also have advantages over using input_sensors in that you can’t modify the data from the dashboard, preventing errors in scripts / automations that depend on specific data from that helper.

[stevemann (Stephen Mann (YAML-challenged))]

I don’t get your question. I use helpers in my programs and I can set them or read them from Node Red or ESPHome.

[petro]

There’s already a WTH for this. Read only input helpers

[123 (Taras)]

All of the requirements you listed are already fulfilled by a Trigger-based Template Sensor.

1. State value set by a service call (in an automation or script).
2. State value survives a restart.
3. State value is read-only in the UI.

Here’s how to do it:

WTH can't input helpers be read only in UI

Yes. I you can use a trigger template sensor like this: template: - trigger: - platform: event event_type: set_my_sensor sensor: - name: My sensor state: "{{ trigger.event.data.state }}" And then you can change it in a script or automation like this: action: - alias: Update my sensor event: set_my_sensor event_data: state: new_value Can even add attributes if you want, just pass more data in the event and use it in attributes in the sensor config. Plus trigger template …