From d76d99c36a2d48d728695b2f316044f05925b212 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 16 Aug 2016 08:57:33 -0700 Subject: [PATCH] Update social image we have apps now --- source/_posts/2016-08-16-we-have-apps-now.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_posts/2016-08-16-we-have-apps-now.markdown b/source/_posts/2016-08-16-we-have-apps-now.markdown index a1c0eb8451a..cc6ed602fc9 100755 --- a/source/_posts/2016-08-16-we-have-apps-now.markdown +++ b/source/_posts/2016-08-16-we-have-apps-now.markdown @@ -7,7 +7,6 @@ date_formatted: "August 16, 2016" author: Andrew Cockburn comments: true categories: How-To -og_image: /images/blog/default-social.png --- I have been working on a new subsystem to complement Home Assistant's Automation and Scripting components. `AppDaemon` is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called "Apps". An App is a Python class that is instantiated possibly multiple times from `AppDaemon` and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.