From 5f6ee08b8e6666c796858c9ebad29f113ffdf782 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 28 Mar 2017 09:19:02 +0200 Subject: [PATCH] Add social image --- source/_posts/2017-03-28-http-to-mqtt-bridge.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown index e2b41bab218..8c2f705d398 100644 --- a/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown +++ b/source/_posts/2017-03-28-http-to-mqtt-bridge.markdown @@ -7,6 +7,7 @@ date_formatted: "March 28, 2017" author: petkov comments: true categories: How-To +og_image: /images/blog/2017-03-bridge/social.png --- The idea of creating [HTTP to MQTT bridge](https://github.com/petkov/http_to_mqtt) appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up. @@ -15,7 +16,7 @@ The HTTP to MQTT bridge should fill that gap. The idea is to receive messages us -The app could be hosted on any Node.js hosting. I prefer [Heroku: Cloud Application Platform](https://www.heroku.com/home) for its simplicity. +The app could be hosted on any Node.js hosting. I prefer [Heroku: Cloud Application Platform](https://www.heroku.com/home) for its simplicity. ### {% linkable_title Bringing pieces together %}