### 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 ``` -------------------------------- ### Complete SNMP Switch Examples Source: https://www.home-assistant.io/integrations/snmp Examples demonstrating configuration for SNMP v1, v3, and specific device implementations. ```yaml switch: - platform: snmp name: SNMP v1 switch host: 192.168.0.2 community: private baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0 payload_on: 1 payload_off: 0 - platform: snmp name: SNMP v3 switch host: 192.168.0.3 version: "3" username: "myusername" auth_key: "myauthkey" auth_protocol: "hmac-sha" priv_key: "myprivkey" priv_protocol: "aes-cfb-128" baseoid: 1.3.6.1.4.1.19865.1.2.1.4.0 payload_on: 1 payload_off: 0 - platform: snmp name: Enable PoE on NETGEAR switch port 2 using SNMP v3 host: 192.168.0.4 version: "3" username: "myusername" auth_key: "myauthkey" auth_protocol: "hmac-sha" priv_key: "myprivkey" priv_protocol: "des" baseoid: 1.3.6.1.4.1.4526.11.15.1.1.1.1.1.2 payload_on: 15400 payload_off: 3000 vartype: Gauge32 ``` -------------------------------- ### Emulated Hue Configuration Example Source: https://www.home-assistant.io/integrations/emulated_hue A full configuration example for the emulated_hue integration in configuration.yaml. ```yaml # Example configuration.yaml entry emulated_hue: host_ip: 192.168.1.186 listen_port: 8300 advertise_ip: 10.0.0.10 advertise_port: 8080 off_maps_to_on_domains: - script - scene expose_by_default: true exposed_domains: - light entities: light.bedroom_light: name: "Bedside Lamp" light.ceiling_lights: hidden: true ``` -------------------------------- ### 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 ``` -------------------------------- ### Systemd Unit Dependency Source: https://www.home-assistant.io/integrations/recorder Example configuration to ensure the database service starts before Home Assistant. ```text [Unit] Description=Home Assistant After=network.target postgresql.service ``` -------------------------------- ### Full Sensor Configuration Example Source: https://www.home-assistant.io/integrations/lacrosse Example showing how to configure multiple sensors (humidity, temperature, and battery) for a single device ID. ```yaml # Example configuration.yaml entry sensor: - platform: lacrosse device: /dev/ttyUSB0 baud: 57600 sensors: kitchen_humidity: name: Kitchen Humidity type: humidity id: 72 kitchen_temperature: name: Kitchen Temperature type: temperature id: 72 kitchen_lacrosse_battery: name: Kitchen Sensor Battery type: battery id: 72 ``` -------------------------------- ### Full NAD Configuration Example Source: https://www.home-assistant.io/integrations/nad A comprehensive example including serial port, custom name, volume limits, and source mappings. ```yaml # Example configuration.yaml entry media_player: - platform: nad serial_port: /dev/ttyUSB0 name: "NAD Receiver" min_volume: -60 max_volume: -20 sources: 1: "Kodi" 2: "TV" ``` -------------------------------- ### Install mysqlclient in Virtual Environment Source: https://www.home-assistant.io/integrations/recorder Commands to activate the virtual environment and install the mysqlclient package. ```bash pi@homeassistant:~ $ sudo -u homeassistant -H -s homeassistant@homeassistant:~$ source /srv/homeassistant/bin/activate (homeassistant) homeassistant@homeassistant:~$ pip3 install mysqlclient ``` -------------------------------- ### Play Media Script Example Source: https://www.home-assistant.io/integrations/yamaha Example script demonstrating how to turn on a zone, set volume, and play a specific Net Radio station. ```yaml # Example play_media script # # This is for an environment where Zone 2 of the receiver named # `Living Room Stereo` drives outdoor speakers on the porch. script: rp_porch: alias: "Radio Paradise Porch" sequence: - action: media_player.turn_on target: entity_id: media_player.living_room_stereo_zone_2 - action: media_player.volume_set target: entity_id: media_player.living_room_stereo_zone_2 data: volume_level: 0.48 - action: media_player.play_media target: entity_id: media_player.living_room_stereo_zone_2 data: media_content_type: "NET RADIO" media_content_id: "Bookmarks>Internet>Radio Paradise" ``` -------------------------------- ### Install python-broadlink library Source: https://www.home-assistant.io/integrations/broadlink Commands to clone and install the python-broadlink library from source. ```bash git clone https://github.com/mjg59/python-broadlink.git cd python-broadlink sudo python setup.py install ``` -------------------------------- ### Dialogflow Configuration Example Source: https://www.home-assistant.io/integrations/dialogflow This is an example of how to configure the Dialogflow integration in your Home Assistant `configuration.yaml` file. It sets up the basic integration. ```yaml dialogflow: ``` -------------------------------- ### Full De Lijn configuration example Source: https://www.home-assistant.io/integrations/delijn Example demonstrating multiple sensors with custom departure limits for specific stops. ```yaml # Example configuration.yaml entry sensor: # De Lijn public transport - platform: delijn api_key: "abcdefg" next_departure: - stop_id: '200018' - stop_id: '201169' number_of_departures: 20 ``` -------------------------------- ### Pilight Switch Configuration Example Source: https://www.home-assistant.io/integrations/pilight Example configuration for a Pilight switch, demonstrating 'on_code', 'off_code', 'on_code_receive', and 'off_code_receive' with different protocols. ```yaml switch: - platform: pilight switches: Bed light: on_code: protocol: intertechno_old unit: 3 id: 4 'on': 1 off_code: protocol: intertechno_old unit: 3 id: 4 'off': 1 on_code_receive: protocol: daycom systemcode: 14462 unit: 6 id: 34 state: "on" off_code_receive: protocol: daycom systemcode: 14462 unit: 6 id: 34 state: "off" ``` -------------------------------- ### Analytics Data Payload Example Source: https://www.home-assistant.io/integrations/analytics Example of the raw data structure stored on the server, including a unique identifier and installation metadata. ```text uuid:12a3456bc78d90123ef4567g789012h3 {‘version’: ‘2026.7.2’, ‘installation_type’: ‘Home Assistant OS’, ‘country’: ‘NO’} ``` -------------------------------- ### 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 ``` -------------------------------- ### Start Harmony Activity via Automation Source: https://www.home-assistant.io/integrations/harmony Example of using the remote.turn_on action to switch to a specific activity by name. ```yaml actions: - action: remote.turn_on target: entity_id: remote.bed_room_hub data: activity: "Watch TV" ``` -------------------------------- ### Configure Yi Home Camera with FFmpeg arguments Source: https://www.home-assistant.io/integrations/yi Advanced configuration example including custom path and FFmpeg video scaling arguments. ```yaml camera: - platform: yi name: My Camera host: "192.168.1.100" password: my_password_123 path: /home/camera/feed ffmpeg_arguments: "-vf scale=800:450" ``` -------------------------------- ### 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 /api/unifiprotect/video/{nvr_id}/{camera_id}/{start}/{end} Source: https://www.home-assistant.io/integrations/unifiprotect Proxies a MP4 video clip from UniFi Protect for a specific camera. ```APIDOC ## GET /api/unifiprotect/video/{nvr_id}/{camera_id}/{start}/{end} ### Description Proxies a MP4 video clip from UniFi Protect for a specific camera. ### Method GET ### Endpoint /api/unifiprotect/video/{nvr_id}/{camera_id}/{start}/{end} ### Parameters #### Path Parameters - **nvr_id** (string) - Required - The UniFi Protect ID of your NVR or the config entry ID. - **camera_id** (string) - Required - The UniFi Protect ID of your camera or an entity ID. - **start** (string) - Required - Start time in ISO 8601 format. - **end** (string) - Required - End time in ISO 8601 format. ``` -------------------------------- ### 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 }}" ``` -------------------------------- ### 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 ``` -------------------------------- ### 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 ``` -------------------------------- ### Configure Shelly Gen1 Device Update Source: https://www.home-assistant.io/integrations/update.mqtt Example configuration for a Shelly Gen1 device using MQTT topics for version tracking and firmware installation. ```yaml # Example configuration.yaml entry mqtt: - update: name: "Shelly Plug S Firmware Update" title: "Shelly Plug S Firmware" release_url: "https://shelly-api-docs.shelly.cloud/gen1/#changelog" entity_picture: "https://brands.home-assistant.io/_/shelly/icon.png" state_topic: "shellies/shellyplug-s-112233/info" value_template: "{{ value_json['update'].old_version }}" latest_version_topic: "shellies/shellyplug-s-112233/info" latest_version_template: "{% if value_json['update'].new_version %}{{ value_json['update'].new_version }}{% else %}{{ value_json['update'].old_version }}{% endif %}" device_class: "firmware" command_topic: "shellies/shellyplug-s-112233/command" payload_install: "update_fw" ``` -------------------------------- ### 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] ``` -------------------------------- ### 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 ``` -------------------------------- ### 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/" ``` -------------------------------- ### 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] ``` -------------------------------- ### Configure Push Camera with Buffering Source: https://www.home-assistant.io/integrations/push Example configuration for a Push camera named 'MotionEye Outdoor' that buffers 3 images and has a timeout of 5 seconds. This setup is useful for replaying motion-triggered events. ```yaml camera: - platform: push name: MotionEye Outdoor buffer: 3 timeout: 5 webhook_id: my_custom_webhook_id ``` -------------------------------- ### ComEd Hourly Pricing Configuration Source: https://www.home-assistant.io/integrations/comed_hourly_pricing Example configuration for the ComEd Hourly Pricing sensor in Home Assistant's configuration.yaml file. This setup monitors both the 5-minute price and the current hour average price feeds. ```yaml sensor: - platform: comed_hourly_pricing monitored_feeds: - type: five_minute - type: current_hour_average ``` -------------------------------- ### Device tracker example sketch for MySensors 2.x Source: https://www.home-assistant.io/integrations/mysensors A C++ sketch demonstrating how to implement a GPS sensor using the MySensors library. It includes the necessary setup for serial debugging, radio configuration, and the loop logic for sending position updates. ```cpp /** * Documentation: https://www.mysensors.org * Support Forum: https://forum.mysensors.org * * https://www.mysensors.org/build/gps */ // Enable debug prints to serial monitor #define MY_DEBUG #define MY_RADIO_NRF24 #include #define SN "GPS Sensor" #define SV "1.0" // GPS position send interval (in milliseconds) #define GPS_SEND_INTERVAL 30000 // The child id used for the gps sensor #define CHILD_ID_GPS 1 MyMessage msg(CHILD_ID_GPS, V_POSITION); // Last time GPS position was sent to controller unsigned long lastGPSSent = -31000; // Some buffers char latBuf[11]; char lngBuf[11]; char altBuf[6]; char payload[30]; // Dummy values. Implementation of real GPS device is not done. float gpsLocationLat = 40.741895; float gpsLocationLng = -73.989308; float gpsAltitudeMeters = 12.0; void setup() { } void presentation() { sendSketchInfo(SN, SV); present(CHILD_ID_GPS, S_GPS); } void loop() { unsigned long currentTime = millis(); // Evaluate if it is time to send a new position bool timeToSend = currentTime - lastGPSSent > GPS_SEND_INTERVAL; if (timeToSend) { // Send current gps location // Build position and altitude string to send dtostrf(gpsLocationLat, 1, 6, latBuf); dtostrf(gpsLocationLng, 1, 6, lngBuf); dtostrf(gpsAltitudeMeters, 1, 0, altBuf); sprintf(payload, "%s,%s,%s", latBuf, lngBuf, altBuf); Serial.print(F("Position: ")); Serial.println(payload); send(msg.set(payload)); lastGPSSent = currentTime; } } ``` -------------------------------- ### Automate Tare and Timer Start on Brew Source: https://www.home-assistant.io/integrations/acaia This automation triggers when a brew starts, then tares the scale, resets the timer, and starts the timer. Ensure the entity IDs match your scale model. ```yaml alias: "Start timer on scale" description: "When a brew starts on the machine, the following actions are started: tare, reset the timer, and start the timer on the scale." triggers: - trigger: state entity_id: - binary_sensor.lm001234_brewing_active to: "on" from: "off" actions: - action: button.press target: entity_id: button.lunar_tare - action: button.press target: entity_id: - button.lunar_reset_timer - action: button.press target: entity_id: - button.lunar_start_stop_timer ``` -------------------------------- ### 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 ``` -------------------------------- ### Example configuration.yaml entry for Unitymedia Horizon HD Recorder Source: https://www.home-assistant.io/integrations/horizon Add this to your configuration.yaml file to integrate the Unitymedia Horizon HD Recorder. Restart Home Assistant after making changes. ```yaml # Example configuration.yaml entry media_player: - platform: horizon host: 192.168.0.127 ``` -------------------------------- ### Install PostgreSQL Dependencies Source: https://www.home-assistant.io/integrations/recorder Required system packages and Python client installation for PostgreSQL. ```bash sudo apt-get install postgresql-server-dev-X.Y pip3 install psycopg2 ``` -------------------------------- ### Full Configuration Source: https://www.home-assistant.io/integrations/qld_bushfire Extended configuration example including custom radius, specific alert categories, and manual coordinates. ```yaml # Example configuration.yaml entry geo_location: - platform: qld_bushfire radius: 30 categories: - 'Emergency Warning' - 'Watch and Act' latitude: -24.85 longitude: 152.35 ``` -------------------------------- ### Install MySQL Dependencies Source: https://www.home-assistant.io/integrations/recorder Required system packages and Python client installation for MySQL. ```bash sudo apt-get install default-libmysqlclient-dev libssl-dev pip3 install mysqlclient ``` -------------------------------- ### Full Xeoma Configuration Example Source: https://www.home-assistant.io/integrations/xeoma An example of a comprehensive configuration.yaml entry for the Xeoma integration, including authentication and specific camera settings. Ensure the Xeoma Web Server module is enabled. ```yaml camera: - platform: xeoma host: http://localhost:10090 username: user password: secretpassword new_version: false cameras: - image_name: front_porch name: Front Porch - image_name: back_patio hide: true ``` -------------------------------- ### Install MariaDB Dependencies Source: https://www.home-assistant.io/integrations/recorder Required system packages and Python client installation for MariaDB. ```bash sudo apt-get install libmariadbclient-dev libssl-dev pip3 install mysqlclient ``` -------------------------------- ### Full Configuration Example Source: https://www.home-assistant.io/integrations/device_sun_light_trigger A complete example of the device_sun_light_trigger configuration in configuration.yaml, specifying light group, profile, device group, and disabling the turn-off feature. ```yaml device_sun_light_trigger: light_group: group.living_room light_profile: relax device_group: group.my_devices disable_turn_off: true ``` -------------------------------- ### Install luci-mod-rpc on OpenWrt Source: https://www.home-assistant.io/integrations/luci Commands to install the required RPC package on the OpenWrt router. ```bash apk update apk add luci-mod-rpc ``` -------------------------------- ### Add Demo Integration to configuration.yaml Source: https://www.home-assistant.io/integrations/demo To integrate a demo platform, add this section to your configuration.yaml file. Restart Home Assistant after making changes. ```yaml # Example configuration.yaml entry demo: ``` -------------------------------- ### Install cec-utils Source: https://www.home-assistant.io/integrations/hdmi_cec Command to install the necessary utilities for CEC interaction on Debian-based systems. ```bash sudo apt install cec-utils ``` -------------------------------- ### Install BlueZ on Debian Source: https://www.home-assistant.io/integrations/bluetooth Command to install the BlueZ package on Debian-based host systems. ```bash sudo apt-get -y install bluez ``` -------------------------------- ### FinTS Configuration Example Source: https://www.home-assistant.io/integrations/fints Add this configuration to your configuration.yaml file to enable the FinTS integration. Ensure you replace placeholder values with your bank's specific details. Restart Home Assistant after making changes. ```yaml sensor: - platform: fints bank_identification_number: ID_FOR_YOUR_BANK username: YOUR_FINTS_USERNAME pin: YOUR_PIN url: URL_FOR_YOUR_BANK ``` -------------------------------- ### Configure Plant Monitor in configuration.yaml Source: https://www.home-assistant.io/integrations/plant Add this entry to your `configuration.yaml` file to set up the Plant Monitor integration. Restart Home Assistant after making changes. This example configures sensors for moisture and battery, and sets a minimum moisture level. ```yaml plant: name_of_your_plant: sensors: moisture: sensor.my_sensor_moisture battery: sensor.my_sensor_battery temperature: sensor.my_sensor_temperature conductivity: sensor.my_sensor_conductivity brightness: sensor.my_sensor_brightness min_moisture: 20 ``` -------------------------------- ### Advanced Homematic Configuration with Multiple Protocols Source: https://www.home-assistant.io/integrations/homematic Comprehensive configuration example covering multiple interfaces, protocols, and authentication settings. ```yaml homematic: interfaces: rf: host: 127.0.0.1 resolvenames: "json" username: "Admin" password: "secret" wired: host: 127.0.0.1 port: 2000 resolvenames: "json" username: "Admin" password: "secret" ip: host: 127.0.0.1 port: 2010 groups: host: 127.0.0.1 port: 9292 resolvenames: "json" username: "Admin" password: "secret" path: /groups hosts: ccu2: host: 127.0.0.1 port: 2001 username: "Admin" password: "secret" ``` -------------------------------- ### RESTful Binary Sensor Configuration (GET) Source: https://www.home-assistant.io/integrations/binary_sensor.rest Add this to your configuration.yaml for a GET request to a RESTful endpoint. ```yaml binary_sensor: - platform: rest resource: http://IP_ADDRESS/ENDPOINT ``` -------------------------------- ### Apprise Configuration File Setup Source: https://www.home-assistant.io/integrations/apprise Use a separate configuration file to manage multiple notification services or implement tag-based routing. Reference the configuration file path in your `configuration.yaml`. ```yaml notify: - name: NOTIFIER_NAME platform: apprise config: /config/apprise.yml ``` -------------------------------- ### RFXtrx Event Data Examples Source: https://www.home-assistant.io/integrations/rfxtrx Examples of event data structures received from different RFXtrx devices. ```yaml packet_type: 22 sub_type: 0 type_string: "Byron SX" id_string: "00:90" data: "0716000100900970" values: Sound: 9 Battery numeric: 0 Rssi numeric: 7 ``` ```yaml packet_type: 16 sub_type: 1 type_string: 'ARC' id_string': 'C3' data: '0710010143030170' values': Command: "On" Rssi numeric': 7 ```