Full Featured HCPBridge

[v1.1.0] - 2023-10-10

🚀 New Features

• Separation of HCP Features into Individual Components

  • The HCP features have been modularized into separate components for improved organization and ease of use. These components include Cover, Light, Sensor, Button, Switch, and more. Each feature now has its dedicated component to enhance readability and maintainability of configurations.

• Replaced Templates with Custom Components

  • Templates have been replaced by custom components for all HCP features. The main HCPBridge component remains a polling component, while all other components (e.g., Cover, Light, Switch) now subscribe to callback functions that are triggered when data changes. This reduces the load on the main component and allows for more efficient and event-driven updates.

  • Backward Compatibility: The Cover component continues to expose certain variables and methods to maintain backward compatibility, ensuring that existing configurations will continue to work with minimal changes.

⚠️ Breaking Changes

1. Binary Sensor is_connected No Longer Part of hcpbridge Component

   The binary_sensor named is_connected was previously defined as part of the hcpbridge component. Starting from version v1.1.0, this sensor must now be created separately using the standard binary_sensor configuration.

   Impact: Configurations that include the is_connected property directly within the hcpbridge component will no longer be recognized. Users must migrate to the new configuration format.

   Migration Path:

   • Update your YAML configuration file to define the is_connected sensor as a separate binary_sensor entity.

   Old Configuration:

   hcpbridge:
     id: hcpbridge_id
       is_connected: # Sensor to display the connection status to the motor
       name: "HCPBridge Connected"
     rx_pin: 18 # optional, default=18
     tx_pin: 17 # optional, default=17
     #rts_pin : 1 # optional RTS pin to use if hardware automatic control flow is not available.

   New Configuration:

   hcpbridge:
     id: hcpbridge_id
     rx_pin: 18 # optional, default=18
     tx_pin: 17 # optional, default=17
     #rts_pin : 1 # optional RTS pin to use if hardware automatic control flow is not available.
   
   binary_sensor:
     - platform: hcpbridge
       is_connected:
         name: "${connection_state}"
         id: sensor_connected