Naming Inputs
Learn how to name the inputs of your boneIO Black device.
Why should you name them?
Naming your inputs will make working with the controller much easier. It's a lot easier to remember "Bedroom Button1" than "IN_04", right?
Events – event entities
Let's start with event entities. Below is the default configuration from the file:
~/boneio/event.yaml- id: IN_04
boneio_input: IN_04
actions:
single:
- action: output
pin: OUT_04
- id: IN_05
boneio_input: IN_05
actions:
single:
- action: output
pin: OUT_05
- id: IN_06
boneio_input: IN_06
actions:
single:
- action: output
pin: OUT_06How do you name your input? It's very simple!
| Parameter | Description |
|---|---|
id | This part of the configuration is the input name, and you can change it freely. There are many naming approaches. For example, you can change the name to BedroomButton1 or IN_04_BedroomButton_1. |
boneio_input | This is the input number that your name refers to. For now, ignore actions: – we'll discuss them later. |
Our example looks like this:
- id: IN_04_BedroomButton_1
boneio_input: IN_04
actions:
single:
- action: output
pin: OUT_04Binary (Binary sensor)
Below is the default configuration from the file:
~/boneio/binary_sensor.yaml- id: IN_01
boneio_input: IN_01
actions:
pressed:
- action: output
pin: OUT_01
- id: IN_02
boneio_input: IN_02
actions:
pressed:
- action: output
pin: OUT_02| Parameter | Description |
|---|---|
id | This part of the configuration is the input name, and you can change it freely. There are many naming approaches. For example, you can change the name to MotionBedroom or IN_01_MotionBedroom. |
boneio_input | This is the input number that your name refers to. For now, ignore actions: – we'll discuss them later. |
Our example looks like this:
- id: IN_01_MotionBedroom
boneio_input: IN_01
actions:
pressed:
- action: output
pin: OUT_01