esphome-docs/custom/custom_component.rst

107 lines
3.1 KiB
ReStructuredText
Raw Normal View History

2018-11-27 23:45:05 +01:00
Generic Custom Component
========================
2019-02-16 23:25:23 +01:00
This integration can be used to create generic custom components in ESPHome
2018-11-27 23:45:05 +01:00
using the C++ (Arduino) API. This integration should be used in cases where
2019-02-16 23:25:23 +01:00
none of ESPHome's abstraction layers (for example the "sensor", "binary sensor",
2018-11-27 23:45:05 +01:00
"switch", etc concepts) work well for your integration.
Please first read :doc:`/components/sensor/custom` guide, the same principles apply here.
2018-11-27 23:45:05 +01:00
The example below is an example of a custom component that can do anything you want really.
.. code-block:: cpp
2019-02-16 23:25:23 +01:00
#include "esphome.h"
2018-11-27 23:45:05 +01:00
class MyCustomComponent : public Component {
public:
void setup() override {
// This will be called once to set up the component
// think of it as the setup() call in Arduino
pinMode(5, INPUT);
pinMode(6, OUTPUT);
}
void loop() override {
2018-12-01 09:46:37 +01:00
// This will be called very often after setup time.
// think of it as the loop() call in Arduino
2018-11-27 23:45:05 +01:00
if (digitalRead(5)) {
digitalWrite(6, HIGH);
// You can also log messages
ESP_LOGD("custom", "The GPIO pin 5 is HIGH!");
}
}
};
In many cases however components should communicate with other appliances using the network.
2019-05-12 22:44:59 +02:00
That's why there is :apiclass:`mqtt::CustomMQTTDevice`. It is a helper class to create
2018-11-27 23:45:05 +01:00
custom components that communicate using MQTT.
.. code-block:: cpp
2019-02-16 23:25:23 +01:00
#include "esphome.h"
2018-11-27 23:45:05 +01:00
2019-05-12 22:44:59 +02:00
class MyCustomComponent : public Component, public CustomMQTTDevice {
2018-11-27 23:45:05 +01:00
public:
void setup() override {
// This will be called once to set up the component
// think of it as the setup() call in Arduino
pinMode(6, OUTPUT);
subscribe("the/topic", &MyCustomComponent::on_message);
// also supports JSON messages
subscribe_json("the/json/topic", &MyCustomComponent::on_json_message);
}
void on_message(const std::string &payload) {
if (payload == "ON") {
digitalWrite(6, HIGH);
publish("the/other/topic", "Hello World!");
} else {
digitalWrite(6, LOW);
publish("the/other/topic", 42);
}
}
void on_json_message(JsonObject &root) {
if (!root.containsKey("key"))
return;
int value = root["key"];
// do something with Json Object
// publish JSON using lambda syntax
publish_json("the/other/json/topic", [=](JsonObject &root2) {
root2["key"] = "Hello World";
});
}
};
(Store this file in your configuration directory, for example ``my_custom_component.h``)
And in YAML:
.. code-block:: yaml
# Example configuration entry
2019-02-16 23:25:23 +01:00
esphome:
2018-11-27 23:45:05 +01:00
includes:
- my_custom_component.h
custom_component:
- lambda: |-
auto my_custom = new MyCustomComponent();
return {my_custom};
Configuration variables:
- **lambda** (**Required**, :ref:`lambda <config-lambda>`): The lambda to run for instantiating the
binary sensor(s).
2019-05-12 22:44:59 +02:00
See :apiclass:`Component` and :apiclass:`mqtt::CustomMQTTDevice`.
2018-11-27 23:45:05 +01:00
See Also
--------
- :ghedit:`Edit`