jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Convert subpages to folders

Browse source
This commit is contained in:
Paulus Schoutsen 2015-10-26 23:24:55 -07:00
parent aaa837c3e7
commit e59252a39b
81 changed files with 184 additions and 184 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
View file

@ -20,4 +20,4 @@ To enable the discovery component, add the following to your `home-assistant.con
[discovery]
```
A new [discovery section]({{site_root}}/developers/add_new_platform.html#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.
A new [discovery section]({{site_root}}/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.

2
source/_posts/2015-02-24-streaming-updates.markdown
View file

@ -18,7 +18,7 @@ A new toggle has been added ot the sidebar to turn streaming updates on and off.
Streaming updates has been implemented using the HTML5 `EventSource` tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The [server-side code](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/api.py#L90) is 50 lines and the [client-side code](https://github.com/balloob/home-assistant-js/blob/master/src/actions/stream.js) is 80 lines of code.
All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning [slave instance](https://home-assistant.io/developers/architecture.html#multiple-connected-instances) of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side.
All events that happen on the server will now also be sent to the browser. This turns any browser running the UI into a fully functioning [slave instance](https://home-assistant.io/developers/architecture/#multiple-connected-instances) of Home Assistant. This opens up new possibilities for Home Assistant components that live completely client-side.
Implementing EventSource was not without challenges. Here are some of the issues that had to be solved:

2
source/_posts/2015-04-25-release-notes.markdown
View file

@ -21,7 +21,7 @@ __ISY994 hub support__<br>
<img src='/images/supported_brands/universal_devices.png' style='border:none; box-shadow: none; float: right;' height='50' />
[Ryan](https://github.com/rmkraus) has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
He has created an extensive getting started guide which can be found on [the ISY994 component page](/components/isy994.html).
He has created an extensive getting started guide which can be found on [the ISY994 component page](/components/isy994/).
```yaml
# Example configuration.yaml entry

2
source/_posts/2015-06-10-release-notes.markdown
View file

@ -145,7 +145,7 @@ notify:
__Swiss Public transport sensor__<br>
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport.html) for more information how to set it up.
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport/) for more information how to set it up.
__Transmission turtle mode switch__<br>

2
source/_posts/2015-07-11-ip-cameras-arduino-kodi-efergy-support.markdown
View file

@ -35,7 +35,7 @@ To update to the latest version, run <code>scripts/update</code>. Please report
__Arduino__<br>
<img src='/images/supported_brands/arduino.png' style='border:none; box-shadow: none; float: right;' height='50' />
Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino.html) for an extensive guide to get started.
Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at [the docs](/components/arduino/) for an extensive guide to get started.
```yaml
# Example configuration.yaml entry

4
source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown
View file

@ -15,8 +15,8 @@ __MQTT Support__<br>
The big new addition in this release is the support for the MQTT protocol by [@fabaff](https://github.com/fabaff) with some help from [@balloob](https://github.com/balloob). It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics ([see the example][mqtt-example]) and also support for the automation component [has been added][mqtt-automation]. For more information, see [the MQTT component page][mqtt-component].
[mqtt-example]: https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py
[mqtt-automation]: /components/automation.html#mqtt-based-automation
[mqtt-component]: /components/mqtt.html
[mqtt-automation]: /components/automation/#mqtt-based-automation
[mqtt-component]: /components/mqtt/
```yaml
# Example configuration.yaml entry

6
source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown
View file

@ -14,7 +14,7 @@ _This is a guest post by Home Assistant user and contributor [Nolan Gilley](http
In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a [Moteino](https://lowpowerlab.com/moteino/), an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don't have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the [MQTT component](/components/mqtt.html) to my Raspberry Pi.
As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a [Moteino](https://lowpowerlab.com/moteino/), an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don't have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the [MQTT component](/components/mqtt/) to my Raspberry Pi.
After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn't get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It's easy to see when the washing machine is in operation here. I used the same technique for the dryer's accelerometer.
@ -27,14 +27,14 @@ After taking some sample data from the accelerometers while each appliance was i
<!--more-->
Next it was just a matter of integrating everything with Home Assistant. I was able to use the [MQTT component](/components/mqtt.html) to read the washer and dryer states from the Moteino and display it in Home Assistant.
Next it was just a matter of integrating everything with Home Assistant. I was able to use the [MQTT component](/components/mqtt/) to read the washer and dryer states from the Moteino and display it in Home Assistant.
<p class='img'>
<img src='/images/blog/2015-08-laundry-automation/screenshot-ha.png' />
Status of the dryer and washer in Home Assistant
</p>
Next I wrote [scripts](/components/script.html) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/components/automation.html). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/notify.pushbullet.html). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
Next I wrote [scripts](/components/script/) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/components/automation/). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/notify.pushbullet/). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
<p class='img'>
<a href='/images/blog/2015-08-laundry-automation/moteino-and-sensors.jpg'>

4
source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown
View file

@ -73,8 +73,8 @@ __MQTT Sensors and Switches__<br>
integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the
MQTT component to be connected to a broker.
[mqtt-sensor]: /components/sensor.mqtt.html
[mqtt-switch]: /components/switch.mqtt.html
[mqtt-sensor]: /components/sensor.mqtt/
[mqtt-switch]: /components/switch.mqtt/
```yaml
# Example configuration.yml entr

4
source/_posts/2015-09-11-different-ways-to-use-mqtt-with-home-assistant.markdown
View file

@ -11,7 +11,7 @@ og_image: /images/blog/2015-09-mqtt/arduino.png
---
<img src='/images/supported_brands/mqtt.png' style='border:none; box-shadow: none; float: right;' height='80' />
The [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt.html) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device.
The [MQTT](https://en.wikipedia.org/wiki/MQTT) support was added to Home Assistant recently. The [MQTT component](https://home-assistant.io/components/mqtt/) will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn't care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn't matter if the data is coming from a human, a web service, or a device.
A great example is shown in a [Laundry Automation](https://home-assistant.io/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/) post in this blog.
@ -32,7 +32,7 @@ sensor:
state_topic: "home-assistant/fabian/mood"
```
After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](https://home-assistant.io/components/mqtt.html) or the [MQTT sensor](https://home-assistant.io/components/sensor.mqtt.html) documentation.
After a restart of Home Assistant the "Mood" sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the [MQTT component](https://home-assistant.io/components/mqtt/) or the [MQTT sensor](https://home-assistant.io/components/sensor.mqtt/) documentation.
Now we can set the mood. The commandline tool (`mosquitto_pub`) which is shipped with `mosquitto` is used to send an MQTT message.

2
source/_posts/2015-09-13-home-assistant-meets-ifttt.markdown
View file

@ -25,7 +25,7 @@ if your smoke alarm goes off.
<img src='/images/blog/2015-09-ifttt/splash.png'>
</p>
Head over to the [setup instructions](/components/ifttt.html) to get started with IFTTT. Click the
Head over to the [setup instructions](/components/ifttt/) to get started with IFTTT. Click the
read more button for some example recipes.
<!--more-->

6
source/_posts/2015-09-18-monitoring-with-glances-and-home-assistant.markdown
View file

@ -11,13 +11,13 @@ og_image: /images/supported_brands/glances.png
---
<img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' />
Inspried by a [feature requests](https://github.com/balloob/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor.html) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
Inspried by a [feature requests](https://github.com/balloob/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
<!--more-->
The basic problem is to get the data from the remote host. Starting with [psutil](https://pypi.python.org/pypi/psutil) that is used by the systemmonitor sensor, a possible solution is only a click away and named [Glances](https://github.com/nicolargo/glances). Glances has a nice curses-based interface and a [RESTful API](https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API).
The [Glances sensor](/components/sensor.glances.html) sensor uses that API to get all needed data.
The [Glances sensor](/components/sensor.glances/) sensor uses that API to get all needed data.
In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn't matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools.
@ -55,7 +55,7 @@ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
{"used": 203943936}
```
Add the [glances sensor](/components/sensor.glances.html) entry to your `configuration.yaml` file and restart Home Assistant then.
Add the [glances sensor](/components/sensor.glances/) entry to your `configuration.yaml` file and restart Home Assistant then.
```yaml
# Example configuration.yaml entry

2
source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown
View file

@ -42,7 +42,7 @@ media_player:
__Automation__<br>
Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of
triggers. The best to get started with it is to head over to the new
[getting started with automation](/getting-started/automation.html) page.
[getting started with automation](/getting-started/automation/) page.
```yaml
# Example of entry in configuration.yaml

18
source/_posts/2015-10-05-home-assistant-goes-geo-with-owntracks.markdown
View file

@ -20,10 +20,10 @@ The geo support consists of three different parts:
We have added a new [getting started section][start-presence] to get up and running.
[platform-owntracks]: /components/device_tracker.owntracks.html
[component-zone]: /components/zone.html
[zone-automation]: /components/automation.html#zone-trigger
[start-presence]: /getting-started/presence-detection.html
[platform-owntracks]: /components/device_tracker.owntracks/
[component-zone]: /components/zone/
[zone-automation]: /components/automation/#zone-trigger
[start-presence]: /getting-started/presence-detection/
<p class='img'>
<img src='/images/screenshots/map.png' />
@ -33,15 +33,15 @@ Map in Home Assistant showing two people and three zones (home, school, work)
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a
short summary of highlights:
<a href='/components/media_player.plex.html'>
<a href='/components/media_player.plex/'>
<img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' />
</a>
- Sensor: [rest platform](/components/sensor.rest.html) added ([@fabaff](https://github.com/fabaff))
- Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt.html) added ([@sfam](https://github.com/sfam))
- Media Player: [Plex platform](/components/media_player.plex.html) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
- Sensor: [rest platform](/components/sensor.rest/) added ([@fabaff](https://github.com/fabaff))
- Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt/) added ([@sfam](https://github.com/sfam))
- Media Player: [Plex platform](/components/media_player.plex/) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
- Dev Tools: services can now show description of fields ([@balloob](https://github.com/balloob))
- MQTT: Support for certificates and improved error reporting ([@balloob](https://github.com/balloob))
- Light: [limitlessled platform](/components/light.limitlessled.html) extended with white light support ([@auchter](https://github.com/auchter))
- Light: [limitlessled platform](/components/light.limitlessled/) extended with white light support ([@auchter](https://github.com/auchter))
- Fuzzy matching for scenes ([@pavoni](https://github.com/pavoni))
- Scene support for media player ([@maddox](https://github.com/maddox))

2
source/_posts/2015-10-11-measure-temperature-with-esp8266-and-report-to-mqtt.markdown
View file

@ -34,7 +34,7 @@ I've been using Adafruit for my shopping:
- [Adafruit HUZZAH ESP8266 Breakout](http://www.adafruit.com/product/2471) ([assembly instructions](https://learn.adafruit.com/adafruit-huzzah-esp8266-breakout/assembly))
- [Adafruit HDC1008 Temperature & Humidity Sensor Breakout Board](http://www.adafruit.com/product/2635) ([assembly instructions](https://learn.adafruit.com/adafruit-hdc1008-temperature-and-humidity-sensor-breakout/assembly))
- [MQTT server](/components/mqtt.html#picking-a-broker)
- [MQTT server](/components/mqtt/#picking-a-broker)
_Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires,
soldering iron + wire, Serial USB cable._

12
source/_posts/2015-10-11-rfxtrx-blinkstick-and-snmp-support.markdown
View file

@ -20,11 +20,11 @@ This release also includes some new platforms (because they keep coming!):
<img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
<img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
- Light: [blinkstick platform](/components/light.blinksticklight.html) added ([@alanbowman](https://github.com/alanbowman))
- Device Tracker: [SNMP platform](/components/device_tracker.snmp.html) added ([@tomduijf](https://github.com/tomduijf))
- Light: [rfxtrx platform](/components/light.rfxtrx.html) added ([@badele](https://github.com/badele))
- Switch: [rfxtrx platform](/components/switch.rfxtrx.html) added ([@badele](https://github.com/badele))
- Notify: [telegram platform](/components/notify.telegram.html) added ([@fabaff](https://github.com/fabaff))
- Light: [blinkstick platform](/components/light.blinksticklight/) added ([@alanbowman](https://github.com/alanbowman))
- Device Tracker: [SNMP platform](/components/device_tracker.snmp/) added ([@tomduijf](https://github.com/tomduijf))
- Light: [rfxtrx platform](/components/light.rfxtrx/) added ([@badele](https://github.com/badele))
- Switch: [rfxtrx platform](/components/switch.rfxtrx/) added ([@badele](https://github.com/badele))
- Notify: [telegram platform](/components/notify.telegram/) added ([@fabaff](https://github.com/fabaff))
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command.
This has been implemented for the [iTunes platform](/components/media_player.itunes.html).
This has been implemented for the [iTunes platform](/components/media_player.itunes/).

34
source/_posts/2015-10-26-firetv-and-radiotherm-now-supported.markdown
View file

@ -21,22 +21,22 @@ complete revamp.
<img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
<img src='/images/supported_brands/geofancy.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
- Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink.html) now supported ([@mKeRix](https://github.com/mKeRix))
- Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual.html) added ([@sfam](https://github.com/sfam))
- Thermostat: [Radiotherm](/components/thermostat.radiotherm.html) now supported ([@toddeye](https://github.com/toddeye))
- Media Player: [Amazon FireTV](/components/media_player.firetv.html) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc))
- Device Tracker: [Geofancy](/components/device_tracker.geofancy.html) now supported ([@wind-rider](https://github.com/wind-rider))
- New component [Shell Command](/components/shell_command.html) can expose shell commands as services ([@balloob](https://github.com/balloob))
- [Scripts](/components/script.html) can now be customized using `customize` key in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Light: [Hyperion](/components/light.hyperion.html) now supported ([@MakeMeASandwich](https://github.com/MakeMeASandwich))
- Sensor: [aRest](/components/sensor.arest.html) can now also read out pins ([@balloob](https://github.com/balloob))
- Sensor: [Forecast.io](/components/sensor.forecast.html) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Thermostat: [Heat Control](/components/thermostat.heat_control.html) has been completely rewritten ([@balloob](https://github.com/balloob))
- Switch: [Rest](/components/switch.rest.html) now supported ([@bachp](https://github.com/bachp))
- Media Player: [Plex](/components/media_player.plex.html) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf))
- [Downloader](/components/downloader.html) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf))
- Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink/) now supported ([@mKeRix](https://github.com/mKeRix))
- Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual/) added ([@sfam](https://github.com/sfam))
- Thermostat: [Radiotherm](/components/thermostat.radiotherm/) now supported ([@toddeye](https://github.com/toddeye))
- Media Player: [Amazon FireTV](/components/media_player.firetv/) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc))
- Device Tracker: [Geofancy](/components/device_tracker.geofancy/) now supported ([@wind-rider](https://github.com/wind-rider))
- New component [Shell Command](/components/shell_command/) can expose shell commands as services ([@balloob](https://github.com/balloob))
- [Scripts](/components/script/) can now be customized using `customize` key in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Light: [Hyperion](/components/light.hyperion/) now supported ([@MakeMeASandwich](https://github.com/MakeMeASandwich))
- Sensor: [aRest](/components/sensor.arest/) can now also read out pins ([@balloob](https://github.com/balloob))
- Sensor: [Forecast.io](/components/sensor.forecast/) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob))
- Thermostat: [Heat Control](/components/thermostat.heat_control/) has been completely rewritten ([@balloob](https://github.com/balloob))
- Switch: [Rest](/components/switch.rest/) now supported ([@bachp](https://github.com/bachp))
- Media Player: [Plex](/components/media_player.plex/) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf))
- [Downloader](/components/downloader/) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf))
- Line Charts will use interpolation for sensor data and show current and target temperature for thermostats ([@balloob](https://github.com/balloob))
- Device Tracker: [OpenWRT via ubus](/components/device_tracker.ubus.html) now supported ([@krzynio](https://github.com/krzynio))
- Device Tracker: [OpenWRT via ubus](/components/device_tracker.ubus/) now supported ([@krzynio](https://github.com/krzynio))
<!--more-->
@ -45,11 +45,11 @@ complete revamp.
As part of this release we did some cleanup which introduced backwards incompatible changes:
**Heat Control thermostat no longer includes scheduling features.**<br>
This feature has been removed completely. Use the [automation component](/components/automation.html)
This feature has been removed completely. Use the [automation component](/components/automation/)
instead to control target temperature.
**Config changed for calling a service from a script.**<br>
`execute_service:` has been replaced with `service:`. See [component page](/components/script.html)
`execute_service:` has been replaced with `service:`. See [component page](/components/script/)
for example. The old method will continue working for some time.
**Scenes can no longer be turned off.**<br>