esphome/esphome/components/mqtt/mqtt_component.h
Otto Winter 6682c43dfa
🏗 Merge C++ into python codebase (#504)
## Description:

Move esphome-core codebase into esphome (and a bunch of other refactors). See https://github.com/esphome/feature-requests/issues/97

Yes this is a shit ton of work and no there's no way to automate it :( But it will be worth it 👍

Progress:
- Core support (file copy etc): 80%
- Base Abstractions (light, switch): ~50%
- Integrations: ~10%
- Working? Yes, (but only with ported components).

Other refactors:
- Moves all codegen related stuff into a single class: `esphome.codegen` (imported as `cg`)
- Rework coroutine syntax
- Move from `component/platform.py` to `domain/component.py` structure as with HA
- Move all defaults out of C++ and into config validation.
- Remove `make_...` helpers from Application class. Reason: Merge conflicts with every single new integration.
- Pointer Variables are stored globally instead of locally in setup(). Reason: stack size limit.

Future work:
- Rework const.py - Move all `CONF_...` into a conf class (usage `conf.UPDATE_INTERVAL` vs `CONF_UPDATE_INTERVAL`). Reason: Less convoluted import block
- Enable loading from `custom_components` folder.

**Related issue (if applicable):** https://github.com/esphome/feature-requests/issues/97

**Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** esphome/esphome-docs#<esphome-docs PR number goes here>

## Checklist:
  - [ ] The code change is tested and works locally.
  - [ ] Tests have been added to verify that the new code works (under `tests/` folder).

If user exposed functionality or configuration variables are added/changed:
  - [ ] Documentation added/updated in [esphomedocs](https://github.com/OttoWinter/esphomedocs).
2019-04-17 12:06:00 +02:00

179 lines
6.6 KiB
C++

#pragma once
#include "esphome/core/component.h"
#include "mqtt_client.h"
namespace esphome {
namespace mqtt {
/// Simple Helper struct used for Home Assistant MQTT send_discovery().
struct SendDiscoveryConfig {
bool state_topic{true}; ///< If the state topic should be included. Defaults to true.
bool command_topic{true}; ///< If the command topic should be included. Default to true.
};
#define LOG_MQTT_COMPONENT(state_topic, command_topic) \
if (state_topic) { \
ESP_LOGCONFIG(TAG, " State Topic: '%s'", this->get_state_topic_().c_str()); \
} \
if (command_topic) { \
ESP_LOGCONFIG(TAG, " Command Topic: '%s'", this->get_command_topic_().c_str()); \
}
#define MQTT_COMPONENT_CUSTOM_TOPIC_(name, type) \
protected: \
std::string custom_##name##_##type##_topic_{}; \
\
public: \
void set_custom_##name##_##type##_topic(const std::string &topic) { this->custom_##name##_##type##_topic_ = topic; } \
const std::string get_##name##_##type##_topic() const { \
if (this->custom_##name##_##type##_topic_.empty()) \
return this->get_default_topic_for_(#name "/" #type); \
return this->custom_##name##_##type##_topic_; \
}
#define MQTT_COMPONENT_CUSTOM_TOPIC(name, type) MQTT_COMPONENT_CUSTOM_TOPIC_(name, type)
/** MQTTComponent is the base class for all components that interact with MQTT to expose
* certain functionality or data from actuators or sensors to clients.
*
* Although this class should work with all MQTT solutions, it has been specifically designed for use
* with Home Assistant. For example, this class supports Home Assistant MQTT discovery out of the box.
*
* In order to implement automatic Home Assistant discovery, all sub-classes should:
*
* 1. Implement send_discovery that creates a Home Assistant discovery payload.
* 2. Override component_type() to return the appropriate component type such as "light" or "sensor".
* 3. Subscribe to command topics using subscribe() or subscribe_json() during setup().
*
* In order to best separate the front- and back-end of ESPHome, all sub-classes should
* only parse/send MQTT messages and interact with back-end components via callbacks to ensure
* a clean separation.
*/
class MQTTComponent : public Component {
public:
/// Constructs a MQTTComponent.
explicit MQTTComponent();
/// Override setup_ so that we can call send_discovery() when needed.
void call_setup() override;
void call_loop() override;
/// Send discovery info the Home Assistant, override this.
virtual void send_discovery(JsonObject &root, SendDiscoveryConfig &config) = 0;
virtual bool send_initial_state() = 0;
virtual bool is_internal() = 0;
/// Set whether state message should be retained.
void set_retain(bool retain);
bool get_retain() const;
/// Disable discovery. Sets friendly name to "".
void disable_discovery();
bool is_discovery_enabled() const;
/// Override this method to return the component type (e.g. "light", "sensor", ...)
virtual std::string component_type() const = 0;
/// Set a custom state topic. Set to "" for default behavior.
void set_custom_state_topic(const std::string &custom_state_topic);
/// Set a custom command topic. Set to "" for default behavior.
void set_custom_command_topic(const std::string &custom_command_topic);
/// MQTT_COMPONENT setup priority.
float get_setup_priority() const override;
/** Set the Home Assistant availability data.
*
* See See <a href="https://www.home-assistant.io/components/binary_sensor.mqtt/">Home Assistant</a> for more info.
*/
void set_availability(std::string topic, std::string payload_available, std::string payload_not_available);
void disable_availability();
/// Internal method for the MQTT client base to schedule a resend of the state on reconnect.
void schedule_resend_state();
/** Send a MQTT message.
*
* @param topic The topic.
* @param payload The payload.
*/
bool publish(const std::string &topic, const std::string &payload);
/** Construct and send a JSON MQTT message.
*
* @param topic The topic.
* @param f The Json Message builder.
*/
bool publish_json(const std::string &topic, const json::json_build_t &f);
/** Subscribe to a MQTT topic.
*
* @param topic The topic. Wildcards are currently not supported.
* @param callback The callback that will be called when a message with matching topic is received.
* @param qos The MQTT quality of service. Defaults to 0.
*/
void subscribe(const std::string &topic, mqtt_callback_t callback, uint8_t qos = 0);
/** Subscribe to a MQTT topic and automatically parse JSON payload.
*
* If an invalid JSON payload is received, the callback will not be called.
*
* @param topic The topic. Wildcards are currently not supported.
* @param callback The callback with a parsed JsonObject that will be called when a message with matching topic is
* received.
* @param qos The MQTT quality of service. Defaults to 0.
*/
void subscribe_json(const std::string &topic, mqtt_json_callback_t callback, uint8_t qos = 0);
protected:
/// Helper method to get the discovery topic for this component.
std::string get_discovery_topic_(const MQTTDiscoveryInfo &discovery_info) const;
/** Get this components state/command/... topic.
*
* @param suffix The suffix/key such as "state" or "command".
* @return The full topic.
*/
std::string get_default_topic_for_(const std::string &suffix) const;
/// Get the friendly name of this MQTT component.
virtual std::string friendly_name() const = 0;
/** A unique ID for this MQTT component, empty for no unique id. See unique ID requirements:
* https://developers.home-assistant.io/docs/en/entity_registry_index.html#unique-id-requirements
*
* @return The unique id as a string.
*/
virtual std::string unique_id();
/// Get the MQTT topic that new states will be shared to.
const std::string get_state_topic_() const;
/// Get the MQTT topic for listening to commands.
const std::string get_command_topic_() const;
bool is_connected_() const;
/// Internal method to start sending discovery info, this will call send_discovery().
bool send_discovery_();
// ========== INTERNAL METHODS ==========
// (In most use cases you won't need these)
/// Generate the Home Assistant MQTT discovery object id by automatically transforming the friendly name.
std::string get_default_object_id_() const;
protected:
std::string custom_state_topic_{};
std::string custom_command_topic_{};
bool retain_{true};
bool discovery_enabled_{true};
Availability *availability_{nullptr};
bool resend_state_{false};
};
} // namespace mqtt
} // namespace esphome