RS485 Frame Text Sensor

The rs485_frame text_sensor platform exposes a single hub diagnostic: the type of the most recently validated frame, as a 4-character hex string (e.g. "0083", no separator). It requires the RS485 Frame hub to be configured.

This tracks every validated frame on the bus, not only frames matched by an on_frame: trigger — so it reflects the last frame type seen on the wire, whatever it was.

This is useful for cataloging frame types on an unknown bus during the discovery workflow. For user payload decoding, use on_frame: on the hub — that handles every text-decoding case from a single ASCII frame through Hayward AquaLogic’s blink-bit-and-degree-symbol display encoding.

Configuration variables

• rs485_frame_id (Required, ID): The ID of the rs485_frame hub.

All other options from Text Sensor. The platform defaults entity_category: diagnostic so Home Assistant groups this with the device’s other diagnostic entities; override in YAML if you want to surface it elsewhere.

The sensor publishes only on change — a steady-state bus produces no API traffic.

Example

text_sensor:
  - platform: rs485_frame
    rs485_frame_id: pool
    name: "Last Frame Type"

When a frame with payload starting 0x01 0x03 ... is validated, the sensor publishes the state "0103". The first two payload bytes are shown; longer frame_type prefixes still match in your on_frame: handlers but the diagnostic shows only the leading two bytes (which is the conventional frame type width).