Skip to content
This repository was archived by the owner on Mar 20, 2019. It is now read-only.

Commit 0e6a9fb

Browse files
authored
Update tutorial.markdown
1 parent 7cd587a commit 0e6a9fb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/_docs/ecosystem/appdaemon/tutorial.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ This is also fairly easy to achieve with Home Assistant automations, but we are
6969
Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changesd where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callack function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
7070

7171
```python
72-
import homeassistant.appapi as appapi
72+
import appdaemon.appapi as appapi
7373

7474
class FlashyMotionLights(appapi.AppDaemon):
7575

0 commit comments

Comments
 (0)