Configuration parameters at component level

bt_interface

(MAC accost or list of multiple MAC addresses)(Optional) This parameter is used to select the Bluetooth-interface of your Home Assistant host. When using YAML, a list of available Bluetooth-interfaces available on your system is given in the Home Assistant log during startup of the Integration, when you enable the Domicile Assistant logger at info-level. If you don’t specify a MAC address, past default the showtime interface of the list will be used. If you want to employ multiple interfaces, you can utilise the following configuration:

          
            ble_monitor
            :
            bt_interface
            :
            -
            '
            04:B1:38:2C:84:2B'
            -
            '
            34:DE:36:4F:23:2C'
          
        

Default value: First available MAC accost

hci_interface

(positive integer or list of positive integers)(Optional) Like the previous option
bt_interface, this parameter is also used to select the bt-interface of your Home Assistant host. It is however strongly advised to utilise the
bt_interface
option and not this
hci_interface
selection, as the hci number can change, e.g. when plugging in a dongle. However, due to backwards compatibility, this option is yet bachelor. Use 0 for hci0, 1 for hci1 and so on. On most systems, the interface is hci0. In add-on, if you need to collect information from several interfaces, yous tin specify a list of interfaces:

          
            ble_monitor
            :
            hci_interface
            :
            -
            0
            -
            1
          
        

Default value: No default value,
bt_interface
is used as default.

discovery

(boolean)(Optional) By default, the component creates entities for all discovered, supported sensors. However, situations may arise where you lot need to limit the list of sensors. For example, when you receive data from neighboring sensors, or when data from part of your sensors are received using other equipment, and yous don’t want to see entities you lot do not need. To resolve this issue, but add an entry of each MAC-address of the sensors you need under
devices, by using the
mac
option, and set the
discovery
option to False:

          
            ble_monitor
            :
            discovery
            :
            False
            devices
            :
            -
            mac
            :
            '
            58:C1:38:2F:86:6C'
            -
            mac
            :
            '
            C4:FA:64:D1:61:7D'
          
        

Data from sensors with other addresses will be ignored. Default value: True

active_scan

(boolean)(Optional) In agile mode browse requests will be sent, which is nigh ofttimes non required, simply slightly increases the sensor battery consumption. ‘Passive manner’ means that you lot are non sending whatever asking to the sensor just you are simply receiving the advertisements sent past the BLE devices. This parameter is a subject field for experiment. Default value: False

batt_entities [DEPRECATED]

(boolean)(Optional) This choice is deprecated, delight remove from your configuration.

decimals

(positive integer)(Optional) Number of decimal places to round. This setting can be overruled with for specific devices with settings at device level. Default value: i

period

(positive integer)(Optional) The period in seconds during which the sensor readings are collected and transmitted to Home Assistant after averaging. Default value: 60.

To analyze the departure between the sensor broadcast interval and the component measurement period: The LYWSDCGQ transmits 20-25 valuable BT LE messages (RSSI -75..-70 dBm). During the period = threescore (seconds), the component accumulates all these 20-25 messages, and later the threescore seconds expires, averages them and updates the sensor status in Abode Assistant. The period does not affect the consumption of the sensor. Information technology only affects the Dwelling Banana sensor update rate and the number of averaged values. We cannot modify the frequency with which sensor sends information.

log_spikes

(boolean)(Optional) Puts information most each erroneous fasten in the Home Assistant log. Default value: Faux

Baca juga:  Https Www.timesofisrael.com Topic Binary-options

In that location are reports (pretty rare) that some sensors tend to sometimes produce erroneous values that differ markedly from the bodily ones. Therefore, if you see inexplicable sharp peaks or dips on the temperature or humidity graph, I recommend that you enable this option so that y’all can run into in the log which values were qualified every bit erroneous. The component discards values that exceeds the sensor’s measurement capabilities. These discarded values are given in the log records when this choice is enabled. If erroneous values are within the measurement capabilities (-40..60°C and 0..100%H), there are no messages in the log. If your sensor is showing this, there is no other option only to calculate the average equally the median (next option).

use_median

(boolean)(Optional) Employ median as sensor output instead of mean (helps with “spiky” sensors). Please note that both the median and the mean values in any example are present as the sensor state attributes. This setting can be overruled with for specific devices with settings at device level. Default value: Imitation

The difference between the hateful and the median is that the median is
selected
from the sensor readings, and not calculated as the average. That is, the median resolution is equal to the resolution of the sensor (one tenth of a degree or per centum), while the mean allows y’all to slightly increment the resolution (the longer the measurement period, the larger the number of values will be averaged, and the higher the resolution can be accomplished, if necessary with disabled rounding).

restore_state

(boolean)(Optional) This option will, when set to
True, restore the country of the sensors. If your devices are configured with a mac address, they will restore immediately afterward a restart of Dwelling Assistant to the state right before the restart. If yous didn’t configure your devices, the land volition exist restored upon the first BLE advertisement being received. with
restore_state
set to
Faux, the integration needs some fourth dimension (run across catamenia option) after a restart before it shows the actual information in Home Assistant. During this fourth dimension, the integration receives data from your sensors and calculates the hateful or median values of these measurements. During this menses, the entity will take a land “unknown” or “unavailable” when
restore_state
is set to
False. Setting it to
Truthful
will prevent this, as it restores the old state, but could result in sensors having the incorrect state, e.thousand. if the state has changed during the restart. Past default, this pick is disabled, equally especially the binary sensors would rely on the right state. For measuring sensors similar temperature sensors, this option can be safely set to
True. It is also possible to overrule this setting for specific devices with settings at device level. Default value: False

report_unknown

(Xiaomi,
Qingping,
ATC,
Mi Scale,
Kegtron,
Thermoplus,
Brifit,
Govee,
Ruuvitag,
Other
or
False)(Optional) This option is needed primarily for those who want to request an implementation of device support that is not in the list of supported sensors. If you lot set this parameter to
Xiaomi,
Qingping,
ATC,
Mi Scale,
Kegtron,
Thermoplus,
Brifit,
Govee
or
Ruuvitag, then the component volition log all letters from unknown devices of the specified type to the Home Assitant log (logger
component must exist enabled at info level). When set to
Other, all BLE advertisements will be logged.
Attention!
Enabling this selection can lead to huge output to the Home Assistant log, especially when set to
Other, do non enable it if you do non need it! Details in the FAQ. Default value: False

Baca juga:  1 Minute Dynamic Momentum Binary Options System Download

Configuration parameters at device level

devices

(Optional) The devices option is used for setting options at the level of the device and/or if y’all want to whitelist certain sensors with the
discovery
option. For tracking devices, it is mandatory to specify your devices to be tracked. Annotation that if you utilise the
devices
selection, the
mac
option is also required.

Configuration in the User Interface

To add a device, open the options carte du jour of the integration and look for the
mac
of your device in the devices drop downwards carte du jour. Almost sensors are automatically added to the driblet down menu. If it isn’t shown or if you want to add together a device to be tracked, select
Add Device
in the device drop down bill of fare and click on Submit. You can modify existing configured devices in a similar way, by selecting your device in the aforementioned drop down bill of fare and clicking on Submit. Both will show the following form.

device setup

Configuraton in YAML

To add a device, add together the following to your
configuration.yaml

          
            ble_monitor
            :
            devices
            :
            # sensors
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            proper noun
            :
            '
            Livingroom'
            encryption_key
            :
            '
            217C568CF5D22808DA20181502D84C1B'
            temperature_unit
            :
            C
            decimals
            :
            two
            use_median
            :
            Imitation
            restore_state
            :
            default
            -
            mac
            :
            '
            C4:3C:4D:6B:4F:F3'
            reset_timer
            :
            35
            # device trackers
            -
            mac
            :
            '
            D4:3C:2D:4A:3C:D5'
            track_device
            :
            True
            tracker_scan_interval
            :
            xx
            consider_home
            :
            180
          
        

mac

(string)(Required) The
mac
option (MAC accost
in the UI) is used to identify your device based on its mac-address. This allows you to ascertain other additional options for this specific device, to rails information technology and/or to whitelist it with the
discovery
option. Yous tin find the MAC address in the attributes of your sensor (Developers Tools
–>
States). For deleting devices see the instructions in the FAQ.

proper noun

When using configuration in the User Interface, you tin modify the device name by opening your device, via configuration, integrations and clicking on devices on the BLE monitor tile. Select the device you want to change the name of and click on the cogwheel in the topright corner, where y’all can alter the name. You volition get a question wether you want to rename the individual entities of this device as well (normally, information technology is advised to do this).

(string)(Optional) When using YAML, you tin use the
name
pick to link a device name and sensor name to the mac-address of the device. Using this choice (or changing a name) will create new sensor/tracker entities. The quondam information won’t exist transfered to the new sensor/tracker. The old sensor/tracker entities tin exist safely deleted afterwards, only this has to be done manually at the moment, see the instructions in the FAQ. The sensors/trackers are named with the following convention:
sensor.ble_sensortype_device_name
(e.thou.
sensor.ble_temperature_livingroom) in stead of the default
ble_sensortype_mac
(eastward.g.
sensor.ble_temperature_A4C1382F86C). Yous will have to update your lovelace cards, automation and scripts later on each alter. Note that y’all can all the same override the entity_id from the UI. Default value: Empty

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            proper noun
            :
            '
            Livingroom'
          
        

encryption_key

(string, 24 or 32 characters)(Optional) This option is used for sensors broadcasting encrypted advertisements. The encryption cardinal should exist 32 characters (= 16 bytes) for near devices (LYWSD03MMC, CGD1, MCCGQ02HL, and MHO-C401 (original firmware but). Only Yeelight YLYK01YL (all types), YLYB01YL-BHFRC, YLKG07YL and YLKG08YL crave a 24 character (= 12 bytes) long key. The example of the characters does not matter. The keys beneath are an example, you need your ain key(s)! Data on how to become your key(s) can be plant here. Default value: Empty

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            encryption_key
            :
            '
            217C568CF5D22808DA20181502D84C1B'
          
        

temperature_unit

(C or F)(Optional) Most sensors are sending BLE advertisements with temperature data in Celsius (C), fifty-fifty when set to Fahrenheit (F) in the MiHome app. However, sensors with custom ATC firmware will get-go sending temperature information in Fahrenheit (F) after changing the display from Celsius to Fahrenheit. This means that you volition have to tell
ble_monitor
that it should expect Fahrenheit information for these specific sensors, by setting this choice to Fahrenheit (F). Note that Home Assistant is e’er converting measurements to C or F based on your Unit Organization setting in Configuration – Full general. Default value: C

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            temperature_unit
            :
            F
          
        

decimals (device level)

(positive integer or
default)(Optional) Number of decimal places to circular. Overrules the setting at integration level. Default value: default (which ways: employ setting at integration level)

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            decimals
            :
            ii
            -
            mac
            :
            '
            A4:C1:38:2F:86:6B'
            decimals
            :
            default
          
        

use_median (device level)

(boolean or
default)(Optional) Utilise median every bit sensor output instead of mean (helps with “spiky” sensors). Overrules the setting at integration level. Please note that both the median and the hateful values in whatever case are nowadays as the sensor land attributes. Default value: default (which means: utilise setting at integration level)

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            use_median
            :
            True
            -
            mac
            :
            '
            A4:C1:38:2F:86:6B'
            use_median
            :
            default
          
        

restore_state (device level)

(boolean or
default)(Optional) This option volition, when prepare to
Truthful, restore the state of the sensors immediately afterwards a restart of Home Banana to the state correct before the restart. Overrules the setting at integration level. Run into for a more than detailed caption the setting at integration level. Default value: default (which means: use setting at integration level)

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            restore_state
            :
            Truthful
            -
            mac
            :
            '
            A4:C1:38:2F:86:6B'
            restore_state
            :
            default
          
        

reset_timer

(possitive integer)(Optional) This option sets the fourth dimension (in seconds) after which a sensor is reset to
motion articulate
(motion sensors) or
no press
(push button and dimmer sensors). Subsequently each
motion detected
advertisement or
button/dimmer press, the timer starts counting downward once again. Setting this option to 0 seconds will turn this resetting behavior off.

Baca juga:  Social Media Trading In 2023: The New Way To Invest

Note that movement sensors also sends advertisements themselves that can overrule this setting. To our electric current knowledge, advertisements after 30 seconds of no move send by the sensor are
motility clear
messages, advertisements within thirty seconds are
movement detected
messages. For button and dimmer sensors, it is advised to gear up the
reset_timer
to 1 second. Default value: 35

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            reset_timer
            :
            35
          
        

track_device

(boolean)(Optional) Enabling this pick will create a device tracker in Home Assistant. The device tracker volition be
Dwelling
as long as information technology receives data and volition move to
Abroad
afterward no data is received anymore for more that the fix period with consider_home. Annotation that your device should accept a fixed MAC address to be able to rail. Default value: False

          
            ble_monitor
            :
            devices
            :
            -
            mac
            :
            '
            A4:C1:38:2F:86:6C'
            track_device
            :
            Truthful
            tracker_scan_interval
            :
            xx
            consider_home
            :
            180
          
        

tracker_scan_interval

(positive integer)(Optional) To reduce the state updates in Abode Assistant and non spam your Abode Banana, it is brash to set up a scan interval. Subsequently a BLE advertisement is received and the state has been updated, Dwelling Assistant Scan will not update the state during the set interval to safety resource. The setting is in seconds. Default value: 20

consider_home

(positive integer)(Optional) This option sets the period with no data later which the device tracker is considered to be abroad. The setting is in seconds. Default value: 180