### Full configuration with parameters Source: https://www.home-assistant.io/integrations/seven_segments Example configuration including camera setup and specific image processing parameters derived from testing. ```yaml camera: - platform: local_file file_path: /home/homeassistant/.homeassistant/seven-seg.png name: seven_segments image_processing: - platform: seven_segments x_position: 390 y_position: 250 height: 280 width: 490 threshold: 20 digits: 4 source: - entity_id: camera.seven_segments ``` -------------------------------- ### Systemd Service File Configuration Source: https://www.home-assistant.io/integrations/recorder Example of how to configure a Systemd service file to ensure the database starts before Home Assistant. This example shows PostgreSQL. ```bash sudo nano /etc/systemd/system/home-assistant@homeassistant.service ``` ```text [Unit] Description=Home Assistant After=network.target postgresql.service ``` ```bash sudo systemctl daemon-reload ``` -------------------------------- ### ser2net.conf Example Source: https://www.home-assistant.io/integrations/edl21 Example configuration for ser2net to establish a serial connection over TCP. This is useful for remote transceiver setups. ```ini 2001:raw:0:/dev/ttyUSB0:9600 8DATABITS NONE 1STOPBIT ``` -------------------------------- ### Example configuration.yaml entry Source: https://www.home-assistant.io/integrations/aquostv Add this to your configuration.yaml file to integrate a Sharp Aquos TV. Restart Home Assistant after changing the file. ```yaml media_player: - platform: aquostv host: 192.168.0.10 ``` -------------------------------- ### Example response for get items action Source: https://www.home-assistant.io/integrations/todo This is an example of the data structure returned when the `todo.get_items` action is executed, showing the items and their statuses. ```yaml todo.vacation_preparation: items: - summary: Water plants uid: 01244b28-e604-11ee-a0a4-e45f0197c057 status: needs_action - summary: turn down heating uid: ae993df4-e604-11ee-a0a4-e45f0197c057 status: needs_action ``` -------------------------------- ### Example configuration.yaml entry Source: https://www.home-assistant.io/integrations/browser Add this to your configuration.yaml file to load the browser integration. Restart Home Assistant after making changes. ```yaml browser: ``` -------------------------------- ### Get Lock Usercode Example Response Source: https://www.home-assistant.io/integrations/zwave_js Example response structure for the zwave_js.get_lock_usercode action, showing usercode and in-use status for different slots. ```yaml "1": usercode: "1234" in_use: true "2": usercode: "" in_use: false ``` -------------------------------- ### Example MQTT Scene Configuration Source: https://www.home-assistant.io/integrations/scene.mqtt Add this to your configuration.yaml file to set up an MQTT scene. Remember to restart Home Assistant after making changes. ```yaml mqtt: - scene: command_topic: zigbee2mqtt/living_room_group/set ``` -------------------------------- ### Calendar Event Notification Automation Source: https://www.home-assistant.io/integrations/calendar An example automation that sends a persistent notification when a calendar event starts, including the event's summary and start time. It allows multiple events starting simultaneously. ```yaml automation: - alias: "Calendar notification" triggers: - trigger: calendar event: start entity_id: calendar.personal actions: - action: persistent_notification.create data: message: >- Event {{ trigger.calendar_event.summary }} @ {{ trigger.calendar_event.start }} ``` -------------------------------- ### Example configuration.yaml Entry Source: https://www.home-assistant.io/integrations/familyhub Add this configuration to your configuration.yaml file to enable the Family Hub camera. Ensure you replace 'IP_ADDRESS' with your refrigerator's actual IP address. Restart Home Assistant after making changes. ```yaml camera: - platform: familyhub ip_address: "IP_ADDRESS" ``` -------------------------------- ### Get movies action Source: https://www.home-assistant.io/integrations/radarr Example YAML configuration for the radarr.get_movies action. ```yaml action: radarr.get_movies data: entry_id: "01234567890abcdef1234567890abcde" ``` -------------------------------- ### Full YAML configuration example Source: https://www.home-assistant.io/integrations/generic_hygrostat Example configuration for the generic_hygrostat integration to be added to the configuration.yaml file. ```yaml generic_hygrostat: - name: Bedroom humidifier: switch.humidifier_plug target_sensor: sensor.outside_humidity min_humidity: 30 max_humidity: 70 target_humidity: 50 dry_tolerance: 3 wet_tolerance: 0 device_class: "humidifier" min_cycle_duration: seconds: 5 keep_alive: minutes: 3 initial_state: true away_humidity: 35 away_fixed: True sensor_stale_duration: 00:15:00 ``` -------------------------------- ### Script Configuration Example Source: https://www.home-assistant.io/integrations/script An example of how to configure a script in Home Assistant's configuration.yaml file, including a sequence of actions. ```APIDOC ## Script Configuration Example ### Description This example demonstrates the basic structure for defining a script in your Home Assistant configuration file. ### Method YAML Configuration ### Endpoint N/A (Configuration file) ### Parameters #### Configuration Variables - **alias** (string) - Optional - Friendly name for the script. - **icon** (string) - Optional - Icon for the script. - **description** (string) - Optional - A description of the script. - **variables** (map) - Optional, default: {} - Variables available within templates. - **PARAMETER_NAME** (any) - The value of the variable. Any YAML is valid. Templates can also be used. - **fields** (map) - Optional, default: {} - Information about script field parameters. - **FIELD_NAME** (map) - A parameter field used by this script. - **name** (string) - The name of this script parameter field. - **description** (string) - A description of this script parameter. - **advanced** (boolean) - Marks this field as advanced (UI only). - **required** (boolean) - Marks this field as required (UI only). - **example** (string) - An example value. - **default** (any) - The default value for this field. - **selector** (selector) - Optional - The selector to use for this input (UI). - **mode** (string) - Optional, default: single - Controls script execution behavior when already running. - **max** (integer) - Optional, default: 10 - Maximum concurrent runs (for 'queued' and 'parallel' modes). - **max_exceeded** (string) - Optional, default: warning - Log level when max runs are exceeded. - **sequence** (list) - Required - The sequence of actions the script performs. ### Request Example ```yaml script: message_temperature: alias: 'Notify Temperature' description: 'Sends a notification with the current temperature.' variables: greeting: 'Hello' fields: target_device: name: 'Target Device' description: 'Device to send notification to.' example: 'mobile_app_myphone' selector: device: sequence: - service: notify.notify data: message: "{{ greeting }}, the current temperature is {{ states('sensor.temperature') }}" data: target: {{ target_device }} ``` ### Response N/A (Scripts are configured, not directly called via API in this context) ### Script Modes - **single**: Do not start a new run. Issue a warning. - **restart**: Start a new run after first stopping previous run. - **queued**: Start a new run after all previous runs complete. - **parallel**: Start a new, independent run in parallel with previous runs. ``` -------------------------------- ### Example Response for Get User Keyring Info Source: https://www.home-assistant.io/integrations/unifiprotect This is an example of the response structure when retrieving user keyring information, showing user details and their associated keys. ```yaml users: - full_name: User One user_status: ACTIVE ulp_id: d23e27e0-a32a-41e5-9424-be646330c2d5 keys: [] - full_name: User Two user_status: ACTIVE ulp_id: a243ffdb-3ab2-4186-b2fe-0b53ccb29f24 keys: - key_type: nfc nfc_id: ABCDEF12 - key_type: fingerprint fingerprint_id: "1" ``` -------------------------------- ### Full BeeWi SmartClim Configuration Example Source: https://www.home-assistant.io/integrations/beewi_smartclim This example shows a full configuration in `configuration.yaml`, including an optional `name` for your sensor. Restart Home Assistant to apply. ```yaml sensor: - platform: beewi_smartclim mac: "xx:xx:xx:xx:xx:xx" name: Garden ``` -------------------------------- ### Get movies response Source: https://www.home-assistant.io/integrations/radarr Example response structure returned by the radarr.get_movies action. ```yaml movies: The Amateur: id: 3 title: The Amateur year: 2025 tmdb_id: 1087891 imdb_id: tt0899043 status: released monitored: true has_file: true size_on_disk: 0 path: /data/media/movies/The Amateur (2025) {tmdb-1087891} movie_file_count: 0 images: poster: https://image.tmdb.org/t/p/original/SNEoUInCa5fAgwuEBMIMBGvkkh.jpg fanart: https://image.tmdb.org/t/p/original/aD7FXrm2GErTmzrIFBntPyhAqS9.jpg The Maze Runner: id: 4 title: The Maze Runner year: 2014 tmdb_id: 198663 imdb_id: tt1790864 status: released monitored: true has_file: true size_on_disk: 0 path: /data/media/movies/The Maze Runner (2014) {tmdb-198663} movie_file_count: 0 images: poster: https://image.tmdb.org/t/p/original/ode14q7WtDugFDp78fo9lCsmay9.jpg fanart: https://image.tmdb.org/t/p/original/eTlcNXGv32zkVI7ZDHhfeaKHXKQ.jpg ``` -------------------------------- ### Full Emulated Kasa Configuration Example Source: https://www.home-assistant.io/integrations/emulated_kasa A comprehensive example demonstrating various ways to configure entities, including using sensor states, static values, templates, and external power sensors. ```yaml emulated_kasa: entities: # uses the sensor state value sensor.power_meter: name: "Power Meter" # uses static value light.dining_room: name: "Dining Room Lights" power: 40.2 # uses template based on state of device fan.ceiling_fan: power: >- {% if is_state_attr('fan.ceiling_fan','speed', 'low') %} 2 {% elif is_state_attr('fan.ceiling_fan','speed', 'medium') %} 12 {% elif is_state_attr('fan.ceiling_fan','speed', 'high') %} 48 {% endif %} # uses value from 3rd party sensor light.wled: name: "Strip Lights" power_entity: sensor.light_power_w # uses template to convert device state into watts sensor.ups_kw: name: UPS Power power: "{{ float(states('sensor.ups_kw')) * 1000 }}" ``` -------------------------------- ### Symlinking libcec for Raspberry Pi Manual Install Source: https://www.home-assistant.io/integrations/hdmi_cec Example of symlinking libcec files for a default virtual environment on a Raspberry Pi manual installation. Ensure the paths correctly point to your libcec installation and Home Assistant virtual environment. ```bash ln -s /usr/local/lib/python*/dist-packages/cec.py /srv/homeassistant/lib/python*/site-packages ln -s /usr/local/lib/python*/dist-packages/_cec.so /srv/homeassistant/lib/python*/site-packages ``` -------------------------------- ### Get HEOS queue response Source: https://www.home-assistant.io/integrations/heos Example response structure returned by the heos.get_queue action. ```yaml media_player.office: queue: - queue_id: 1 song: Alone Again album: After Hours artist: The Weeknd image_url: >- http://resources.wimpmusic.com/images/22f72311/8e9e/461e/a100/d9cfd4ddc2fa/640x640.jpg media_id: "134788274" album_id: "134788273" - queue_id: 2 song: Too Late album: After Hours artist: The Weeknd image_url: >- http://resources.wimpmusic.com/images/22f72311/8e9e/461e/a100/d9cfd4ddc2fa/640x640.jpg media_id: "134788275" album_id: "134788273" ``` -------------------------------- ### iGlo Configuration Example Source: https://www.home-assistant.io/integrations/iglo Add this to your configuration.yaml file to integrate iGlo Lights. Restart Home Assistant after changing the configuration. ```yaml # Example configuration.yaml entry light: - platform: iglo host: 192.168.1.10 ``` -------------------------------- ### Example Compensation Configuration Source: https://www.home-assistant.io/integrations/compensation This example shows how to configure the compensation sensor in your configuration.yaml file. It demonstrates setting up compensation for media player volume levels, including defining source, attribute, unit of measurement, and data points. It also shows how to enable lower and upper limits for the compensated values. ```yaml # Example configuration.yaml entry compensation: media_player_db_volume: source: media_player.yamaha_receiver attribute: volume_level unit_of_measurement: dB data_points: - [0.2, -80.0] - [1.0, 0.0] media_player_zone_2_db_volume: source: media_player.yamaha_receiver_zone_2 attribute: volume_level unit_of_measurement: dB # Ensure that the sensor's value will not have a state lower than -80.0 # when the source sensors value is less than 0.2 lower_limit: true # Ensure that the sensor's value will not have a state greater than 0.0 # when the source sensors value is greater than 1.0 upper_limit: true data_points: - [0.2, -80.0] - [1.0, 0.0] ``` -------------------------------- ### Vacuum Current Position Response Source: https://www.home-assistant.io/integrations/roborock This is an example of the response received when getting the vacuum's current position. ```yaml vacuum.roborock_s7: x: 28081 y: 25168 ``` -------------------------------- ### Advanced KEF configuration example Source: https://www.home-assistant.io/integrations/kef Extended configuration example including optional parameters like custom name and volume limits. ```yaml # Example configuration.yaml entry media_player: - platform: kef host: IP_ADDRESS type: LS50 name: My KEF speakers maximum_volume: 0.6 volume_step: 0.05 ``` -------------------------------- ### Start Irrigation Automation Source: https://www.home-assistant.io/integrations/rainbird Example configuration for an automation that triggers the rainbird.start_irrigation action to run a specific zone for a set duration. ```yaml # Example configuration.yaml automation entry automation: - alias: "Turn irrigation on" triggers: - trigger: time at: "5:30:00" actions: - action: rainbird.start_irrigation data: entity_id: switch.rain_bird_sprinkler_1 duration: 5 ``` -------------------------------- ### Full MVG Live Configuration Example Source: https://www.home-assistant.io/integrations/mvglive Demonstrates advanced configuration options including custom names, destinations, products, time offsets, and multiple departures. Use 'state_attr' to access departure details. ```yaml sensor: - platform: mvglive nextdeparture: - station: Hauptbahnhof name: Hbf destinations: ['München Flughafen Terminal','Markt Schwaben'] products: "S-Bahn" timeoffset: 2 - station: Sendlinger Tor lines: ['U2','U8'] number: 5 - station: Scheidplatz products: ['U-Bahn'] directions: "1" ``` -------------------------------- ### Todoist Manual Configuration Example Source: https://www.home-assistant.io/integrations/todoist Example of how to configure the Todoist integration in your `configuration.yaml` file. Ensure you replace 'YOUR_API_TOKEN' with your actual Todoist API token. ```yaml calendar: - platform: todoist token: YOUR_API_TOKEN ``` -------------------------------- ### Example Error Log Output Source: https://www.home-assistant.io/integrations/ubus This log output indicates an error during the setup of the ubus platform for device_tracker, potentially due to incorrect configuration. ```txt 17-04-28 10:43:30 INFO (MainThread) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker 17-04-28 10:43:30 INFO (MainThread) [homeassistant.loader] Loaded device_tracker.ubus from homeassistant.components.device_tracker.ubus 17-04-28 10:43:30 INFO (MainThread) [homeassistant.setup] Setting up device_tracker 17-04-28 10:43:31 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.ubus 17-04-28 10:43:31 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform ubus File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/integrations/device_tracker/__init__.py", line 152, in async_setup_platform File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/integrations/device_tracker/ubus.py", line 36, in get_scanner File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/integrations/device_tracker/ubus.py", line 58, in __init__ File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/integrations/device_tracker/ubus.py", line 156, in _get_session_id File "/opt/homeassistant/venv/lib/python3.4/site-packages/homeassistant/integrations/device_tracker/ubus.py", line 147, in _req_json_rpc 17-04-28 10:43:31 INFO (MainThread) [homeassistant.core] Bus:Handling 17-04-28 10:43:31 INFO (MainThread) [homeassistant.core] Bus:Handling ``` -------------------------------- ### Example Automation: Cast FireServiceRota dashboard Source: https://www.home-assistant.io/integrations/fireservicerota This automation casts the 'fsr' Lovelace view to a Nest Hub media player when Home Assistant starts. ```yaml automation: - alias: "Cast FireServiceRota dashboard to Nest Hub" triggers: - trigger: homeassistant event: start actions: - action: cast.show_lovelace_view data: entity_id: media_player.nest_hub_bedroom view_path: fsr ``` -------------------------------- ### Full Netdata configuration example Source: https://www.home-assistant.io/integrations/netdata A comprehensive configuration example including host, port, and multiple resource definitions. ```yaml # Example configuration.yaml entry sensor: - platform: netdata host: "192.168.1.2" port: "19999" name: SomeHostName resources: system_load: data_group: system.load element: load15 core0_freq: data_group: "cpu.cpufreq" element: "cpu0" icon: mdi:chip ``` -------------------------------- ### Manual Configuration Example Source: https://www.home-assistant.io/integrations/izone Use this configuration in configuration.yaml if you have multiple iZone systems and need to exclude specific units. Restart Home Assistant after modifying the file. ```yaml izone: exclude: - "000013170" ``` -------------------------------- ### Server-side Data Storage Example Source: https://www.home-assistant.io/integrations/analytics This format illustrates how per-installation analytics data might be stored on the server, including a unique identifier and basic installation details. ```text uuid:12a3456bc78d90123ef4567g789012h3 {‘version’: ‘2026.5.4’, ‘installation_type’: ‘Home Assistant OS’, ‘country’: ‘NO’} ``` -------------------------------- ### Example Firmata Configuration Source: https://www.home-assistant.io/integrations/firmata This is a comprehensive example of a Firmata configuration entry for Home Assistant's configuration.yaml file. It demonstrates how to set up the serial port, baud rate, and various types of devices like switches, lights, binary sensors, and analog sensors with their specific pin modes and properties. ```yaml firmata: - serial_port: /dev/serial/by-id/usb-Teensyduino_USB_Serial_358320-if00 serial_baud_rate: 57600 switches: - name: my_light pin_mode: OUTPUT pin: 4 negate: true - name: my_other_output pin_mode: OUTPUT pin: 5 initial: true - name: my_light2 pin_mode: OUTPUT pin: A6 initial: true negate: true lights: - name: my_dimmable_light pin_mode: PWM pin: 6 - name: my_subset_light pin_mode: PWM pin: 10 initial: 0 minimum: 127 maximum: 200 - name: my_inverted_light pin_mode: PWM pin: 11 minimum: 255 maximum: 0 binary_sensors: - name: my_motion pin_mode: INPUT pin: 2 - name: my_door pin_mode: PULLUP pin: 3 negate: true - name: my_other_door pin_mode: INPUT pin: 16 # A2 negate: true sensors: - name: my_sensor pin: A0 pin_mode: ANALOG differential: 40 ``` -------------------------------- ### Get VIZIO App List Source: https://www.home-assistant.io/integrations/vizio Command to retrieve a list of valid apps for inclusion or exclusion in the VIZIO integration configuration. Requires pyvizio to be installed locally. ```bash pyvizio --ip=0 get-apps-list ``` -------------------------------- ### Get KVS Value and Create Sensor Source: https://www.home-assistant.io/integrations/shelly Example configuration to create a temperature sensor by retrieving a value from the device's Key-Value Storage at a regular interval. ```yaml # Example configuration.yaml entry template: - trigger: - platform: time_pattern minutes: /10 action: - action: shelly.get_kvs_value data: device_id: e4c0e031f68a8fbe08c50eda5e189a70 key: my_temperature_value response_variable: temperature_variable sensor: - name: My temperature state: "{{ temperature_variable.value }}" unit_of_measurement: "°C" device_class: temperature ``` -------------------------------- ### Full state configuration example Source: https://www.home-assistant.io/integrations/sensibo Example of the required data structure for the sensibo.full_state action. ```yaml on: true fanLevel: "high" temperatureUnit: "C" targetTemperature: 23 mode: "cool" swing: "fixedBottom" horizontalSwing: "fixedLeft" light: "on" ``` -------------------------------- ### Get Tibber Energy Prices Source: https://www.home-assistant.io/integrations/tibber The `tibber.get_prices` action fetches hourly energy prices. You can specify a `start` and `end` time; otherwise, it defaults to today and tomorrow. ```yaml start: 2024-01-01 00:00:00 end: 2024-01-01 00:00:00 ``` -------------------------------- ### Envisalink Configuration Example Source: https://www.home-assistant.io/integrations/envisalink This is an example of how to configure the Envisalink integration in your configuration.yaml file. Ensure you replace placeholder values with your actual Envisalink and alarm panel details. Restart Home Assistant after making changes. ```yaml envisalink: host: panel_type: HONEYWELL or DSC user_name: YOUR_USERNAME password: YOUR_PASSWORD code: "1234" port: 4025 evl_version: 3 keepalive_interval: 60 zonedump_interval: 30 timeout: 10 panic_type: Police zones: 1: name: "Back Door" type: "opening" 2: name: "First Floor Motion" type: "motion" partitions: 1: name: "Home Alarm" ``` -------------------------------- ### Basic REST Command Configuration Source: https://www.home-assistant.io/integrations/rest_command Example of a basic REST command configuration in `configuration.yaml`. This sets up a command named `example_request` that sends a GET request to a specified URL. ```yaml rest_command: example_request: url: "http://example.com/" ``` -------------------------------- ### Snooz Transition On Automation Example Source: https://www.home-assistant.io/integrations/snooz Use this automation to transition the Snooz device's volume to a specific level over a set duration. If the device is off, the transition starts from the lowest volume. ```yaml automation: - triggers: - trigger: time at: "04:20:00" actions: - action: snooz.transition_on target: entity_id: fan.snooz_abcd data: volume: 33 duration: 120 ``` -------------------------------- ### Configure Xiaomi Camera with FFmpeg Arguments Source: https://www.home-assistant.io/integrations/xiaomi Example showing how to resize video output using ffmpeg_arguments. ```yaml camera: - platform: xiaomi name: My Camera host: "192.168.1.100" model: "xiaofang" password: YOUR_PASSWORD path: /home/camera/feed ffmpeg_arguments: "-vf scale=800:450" ``` -------------------------------- ### EnOcean Binary Sensor Configuration Source: https://www.home-assistant.io/integrations/enocean Example configuration for an EnOcean binary sensor in Home Assistant's configuration.yaml file. This setup is typically used for batteryless wall switches. ```yaml binary_sensor: - platform: enocean id: [0x01,0x90,0x84,0x3C] ``` -------------------------------- ### Switch Platform Example Source: https://www.home-assistant.io/integrations/command_line Demonstrates controlling a switch with `command_on`, `command_off`, and `command_state`, and using `value_template` to set its state. ```yaml # Example configuration.yaml entry command_line: - switch: name: Driveway outside sensor command_on: > curl -X PUT -d '{"on":true}' "http://ip_address/api/sensors/27/config/" command_off: > curl -X PUT -d '{"on":false}' "http://ip_address/api/sensors/27/config/" command_state: curl http://ip_address/api/sensors/27/ value_template: > {{value_json.config.on}} icon: > {% if value_json.config.on == true %} mdi:toggle-switch {% else %} mdi:toggle-switch-off {% endif %} ``` -------------------------------- ### Configuration with Included Files Source: https://www.home-assistant.io/integrations/template Example of a Home Assistant configuration splitting sensors and templates into separate files. ```yaml # configuration.yaml sensor: !include sensors.yaml template: !include templates.yaml ``` -------------------------------- ### Start LIFX Colorloop Effect with lifx.effect_colorloop Source: https://www.home-assistant.io/integrations/lifx Use the dedicated `lifx.effect_colorloop` action for full control over the colorloop effect. This script example demonstrates setting brightness, period, spread, and change. ```yaml script: colorloop_start: alias: "Start colorloop" sequence: - action: lifx.effect_colorloop target: entity_id: group.livingroom data: brightness: 255 period: 10 spread: 30 change: 35 ``` -------------------------------- ### Full MQTT Fan Configuration with Percentage and Presets Source: https://www.home-assistant.io/integrations/fan.mqtt Use this example for a full configuration of an MQTT fan that supports percentage-based speeds and preset modes. Ensure your fan's speed range is correctly mapped to percentage_step. ```yaml mqtt: - fan: name: "Bedroom Fan" state_topic: "bedroom_fan/on/state" command_topic: "bedroom_fan/on/set" direction_state_topic: "bedroom_fan/direction/state" direction_command_topic: "bedroom_fan/direction/set" oscillation_state_topic: "bedroom_fan/oscillation/state" oscillation_command_topic: "bedroom_fan/oscillation/set" percentage_state_topic: "bedroom_fan/speed/percentage_state" percentage_command_topic: "bedroom_fan/speed/percentage" preset_mode_state_topic: "bedroom_fan/preset/preset_mode_state" preset_mode_command_topic: "bedroom_fan/preset/preset_mode" preset_modes: - "auto" - "smart" - "whoosh" - "eco" - "breeze" qos: 0 payload_on: "true" payload_off: "false" payload_oscillation_on: "true" payload_oscillation_off: "false" speed_range_min: 1 speed_range_max: 10 ``` -------------------------------- ### Example Analytics Payload Source: https://www.home-assistant.io/integrations/analytics This JSON payload represents the data collected for Home Assistant analytics, including counts of integrations, users, entities, automations, and installed apps if the Supervisor is present. ```json { "uuid": "12a3456bc78d90123ef4567g789012h3", "version": "{{current_version}}", "installation_type": "Home Assistant OS", "supervisor": { "healthy": true, "supported": true, "arch": "amd64" }, "operating_system": { "board": "odroid-n2", "version": "{{site.data.version_data.hassos['odroid-n2']}}" }, "state_count": 1, "automation_count": 2, "integration_count": 3, "addon_count": 4, "user_count": 5 } ``` -------------------------------- ### TwinCAT PLC ENUM Type Definition Source: https://www.home-assistant.io/integrations/ads Example of defining an ENUM type in TwinCAT PLC for use with the ADS select entity. It is recommended to use explicit values starting from 0. ```plc TYPE E_SampleA : ( e1 := 0, e2 := 1, e3 := 2, ); END_TYPE ``` -------------------------------- ### Clickatell Configuration Example Source: https://www.home-assistant.io/integrations/clickatell Add this to your configuration.yaml file to set up the Clickatell notifier. Ensure you replace placeholders with your actual details. ```yaml notify: - platform: clickatell name: USER_DEFINED_NAME api_key: CLICKATELL_API_KEY recipient: PHONE_NO ``` -------------------------------- ### Upload File Script Example Source: https://www.home-assistant.io/integrations/immich This script demonstrates how to take a camera snapshot and upload it to your Immich instance in a specific album. Ensure the `config_entry_id` and `album_id` are correctly set for your Immich setup. ```yaml sequence: - variables: file_name: camera.yourcamera_{{ now().strftime("%Y%m%d-%H%M%S") }}.jpg - action: camera.snapshot data: filename: "/media/{{ file_name }}" target: entity_id: camera.yourcamera - action: immich.upload_file data: config_entry_id: 01JVJ0RA387MWA938VE8HGXBMJ file: media_content_id: "media-source://media_source/local/{{ file_name }}" media_content_type: "image/jpeg" album_id: f2de0ede-d7d4-4db3-afe3-7288f4e65bb1 ``` -------------------------------- ### Gitter Configuration Example Source: https://www.home-assistant.io/integrations/gitter Add this to your configuration.yaml file to set up the Gitter integration. You need to replace YOUR_API_TOKEN with your actual Gitter API token. The room is optional and defaults to 'home-assistant/home-assistant'. ```yaml sensor: - platform: gitter api_key: YOUR_API_TOKEN ``` -------------------------------- ### Configure Bayesian Sensor in YAML Source: https://www.home-assistant.io/integrations/bayesian Example of how to configure a Bayesian binary sensor in your configuration.yaml file. This setup defines the prior probability, probability threshold, and specific observations with their conditional probabilities. ```yaml binary_sensor: - platform: bayesian name: "Kitchen Occupied by Humans" prior: 0.3 # The kitchen is occupied by humans about 30% of the time probability_threshold: 0.5 # I care about false positives and false negatives equally observations: - entity_id: "binary_sensor.kitchen_motion" prob_given_true: 0.95 # When humans are in the kitchen, the motion sensor detects them 95% of the time prob_given_false: 0.33 # When no humans are in the kitchen, the cats trigger the motion sensor 33% of the time platform: "state" to_state: "on" ```