You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Change docref to standard markdown link
- Improve wording for clarity
- Fix sensor.in_range parameter (sensor_id → id)
- Use proper note callout syntax
- Wrap lines to stay under 120 chars
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: content/components/binary_sensor/analog_threshold.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,20 +34,24 @@ binary_sensor:
34
34
threshold: 0.5
35
35
```
36
36
37
-
As an alternative to using this component you may use {{< docref "components/binary_sensor/template" >}} with [condition expressions](/automations/actions/#all-conditions):
37
+
Alternatively, you can achieve similar functionality using a
38
+
[Template Binary Sensor](/components/binary_sensor/template) with the `condition` option:
38
39
39
40
```yaml
40
-
#Example configuration entry
41
+
# Alternative using template binary sensor
41
42
binary_sensor:
42
43
- platform: template
43
-
id: engine_running
44
44
name: "Engine Running"
45
45
condition:
46
46
sensor.in_range:
47
-
sensor_id: motor_current_sensor
47
+
id: motor_current_sensor
48
48
above: 0.5
49
49
```
50
50
51
+
> [!NOTE]
52
+
> The template approach does not support hysteresis. Use `analog_threshold` if you need
53
+
> different upper and lower thresholds to reduce noise.
54
+
51
55
## Configuration variables
52
56
53
57
- **sensor_id** (**Required**, [ID](/guides/configuration-types#id)): The ID of the source sensor.
0 commit comments