LinknLink Smart Home
  • Welcome to LinknLink Support Center
  • SMART HOME DEVICES
    • 1️⃣Common
      • πŸ—’οΈAnnouncement
      • πŸ—’οΈPower / Wiring
        • Power Supply
      • πŸ—’οΈDevice Setup
      • πŸ—’οΈDevice Settings
        • Push Notifications
      • πŸ—’οΈUniversal Settings
    • 2️⃣eMotion Series
      • πŸ“˜Installation
      • πŸ“‘eMotion Comparison
      • πŸ“‘eMotion2MQTT (HA)
      • Radar Module
      • Firmware Update
      • FAQ
    • 3️⃣eRemote
      • πŸ“˜Set Up eRemote TV Kit
      • πŸ“˜Set Up eRemote HA
        • Update eRemote to eRemote HA
        • Sync IR Devices to HA via MQTT
        • Rollback eRemote HA to eRemote
        • Set Up eRemote HA AC
      • πŸ“„Infrared (IR)
      • πŸ“„Radio Frequency (RF)
        • Why My RF Device Can't be Controlled?
      • πŸ“„BLE sensor: modbus - HA
    • 4️⃣eHome HA
      • πŸ“˜Set Up eHome HA
      • πŸ“˜Update from eHome
    • 5️⃣eTHS / eSensor
      • πŸ“˜Installation
    • 6️⃣BLE Accessories
    • 7️⃣zigbee Accessories
    • 8️⃣Other Products
    • 9️⃣Updates
      • πŸ—’οΈLinknLink App Updates
      • πŸ—’οΈFirmware Updates
      • πŸ—’οΈLocal Upgrade
  • COMMERCIAL IOT SOLUTIONS
    • 1️⃣Digital Signage
    • 2️⃣Smart Energy
  • WORKS WITH 3RD-PARTIES
    • πŸ”΄Alexa & Google Home
    • πŸ”΄Modbus TCP
    • πŸ”΄Home Assistant
Powered by GitBook
On this page
  1. SMART HOME DEVICES
  2. eRemote

BLE sensor: modbus - HA

In this tutorial, I will show you how to connect the eRemote BLE door contact and temperature & humidity sensors to Home Assistant (HA) using Modbus.

1. Update firmware of eRemote Go to the device page, click on the "..." menu > "Settings" > "Firmware Update" > "URL", then paste the following URL: http://eufirmware.linklinkiot.com/firmware/eRemote-60868-8720-BL-3330.upd.bin

2. Configure configuration.yaml File in Home Assistant

  • Step 1: Configure the Main Modbus Integration Find eRemote IP in eRemote App page, select top right ..., choose modbus, then you can see the IP of eRemote, you need to provide the IP address and port of your eRemote:

    modbus:
      - name: "modbus_tcp"
        type: tcp
        host: 192.168.1.100  # Replace with your eRemote's IP address
        port: 502            # Default port for Modbus TCP
  • Step 2: Configure Sensors

    Under the modbus integration, define the sensors you wish to read. Each sensor needs to specify the register address, input type (e.g., holding or input), data type (e.g., int16, uint16, etc.), and optional settings such as unit of measurement, precision, and scale.

    Here’s tabel configuration for multiple sensors excel download url: https://docs.google.com/spreadsheets/d/1VPKUUr-IxFr8NOj_vTzm4ZTsAf2Hla2T/edit?usp=sharing&ouid=117827812234970938974&rtpof=true&sd=true

  • Here's an example configuration for multiple sensors:


modbus:
  - name: "modbus_tcp"
    type: tcp
    host: 192.168.115.122       # change to eRemote IP
    port: 502

    sensors:
 # First TH Sensor 
      - name: "Temp001"
        unique_id: modbus_sensor_temperature001
        device_class: temperature
        state_class: measurement
        slave: 1
        address: 3008
        input_type: holding
        data_type: int16
        scale: 0.01
        precision: 1
        unit_of_measurement: 'Β°C'
        scan_interval: 30

      - name: "humidity001"
        unique_id: modbus_sensor_humidity001
        device_class: humidity
        state_class: measurement
        slave: 1
        address: 3009
        input_type: holding
        data_type: int16
        scale: 0.01
        precision: 1
        unit_of_measurement: '%'
        scan_interval: 35

      - name: "th_battery001"
        unique_id: modbus_sensor_th_battery001
        device_class: power
        slave: 1
        address: 3010
        input_type: holding
        data_type: int16
        unit_of_measurement: '%'
        scan_interval: 40

      - name: "th_status001"
        unique_id: modbus_sensor_th_status001
        slave: 1
        address: 3012
        input_type: holding
        data_type: int16
        scan_interval: 60

 # Second TH Sensor
      - name: "Temp002"
        unique_id: "modbus_sensor_temperature002"
        device_class: temperature
        state_class: measurement
        slave: 1
        address: 3021
        input_type: holding
        data_type: int16
        scale: 0.01
        precision: 1
        unit_of_measurement: "Β°C"
        scan_interval: 30

      - name: "humidity002"
        unique_id: "modbus_sensor_humidity002"
        device_class: humidity
        state_class: measurement
        slave: 1
        address: 3022
        input_type: holding
        data_type: int16
        scale: 0.01
        precision: 1
        unit_of_measurement: "%"
        scan_interval: 35

      - name: "th_battery002"
        unique_id: "modbus_sensor_th_battery002"
        device_class: power
        slave: 1
        address: 3023
        input_type: holding
        data_type: int16
        unit_of_measurement: "%"
        scan_interval: 40

      - name: "th_status002"
        unique_id: "modbus_sensor_th_status002"
        slave: 1
        address: 3025
        input_type: holding
        data_type: int16
        scan_interval: 60

# First Door Sensor
      - name: "door_battery001"
        unique_id: "modbus_sensor_door_battery001"
        device_class: power
        slave: 1
        address: 3309
        input_type: holding
        data_type: int16
        unit_of_measurement: "%"
        scan_interval: 40

      - name: "door_status001"
        unique_id: "modbus_sensor_door_status001"
        slave: 1
        address: 3311
        input_type: holding
        data_type: int16
        scan_interval: 60

# Second Door Sensor
      - name: "door_battery002"
        unique_id: "modbus_sensor_door_battery002"
        device_class: power
        slave: 1
        address: 3321
        input_type: holding
        data_type: int16
        unit_of_measurement: "%"
        scan_interval: 40

      - name: "door_status002"
        unique_id: "modbus_sensor_door_status002"
        slave: 1
        address: 3323
        input_type: holding
        data_type: int16
        scan_interval: 60
        
    binary_sensors:
# First Door Sensor
      - name: "door001"
        unique_id: "modbus_sensor_door001"
        device_class: door
        slave: 1
        address: 3308
        input_type: holding
        scan_interval: 1

# Second Door Sensor
      - name: "door002"
        unique_id: "modbus_sensor_door002"
        device_class: door
        slave: 1
        address: 3320
        input_type: holding
        scan_interval: 1

3. Restart Home Assistant

After configuring the Modbus integration, save the configuration.yaml file and restart Home Assistant.

4. Use Sensor Data

Once the sensors are successfully reading data, you can use them for various purposes in Home Assistant, such as:

  • Displaying the data on a dashboard (Lovelace).

  • Triggering automations based on sensor values (e.g., turning on a fan if the temperature exceeds a certain value).

PreviousWhy My RF Device Can't be Controlled?NexteHome HA

Last updated 1 month ago

3️⃣
πŸ“„