[Wiegand] Add 18-bit values

[Oggy512]

Component name

Wiegand

Link to component documentation on our website

https://esphome.io/components/wiegand/

Describe the enhancement

I'm using the Wiegand component together with a s-Touch Reader ( https://www.i-keys.de/de/sTouch-Leser-R-w.html ), which is working fine so far. However, the reader does have a Bell button, which sends a 18 bit value. I pressed the button three times, it always sends the same value "2e00d", it appread in the log as following:

[D][wiegand:116]: received unknown 18-bit value: 2e00d
[D][wiegand:116]: received unknown 18-bit value: 2e00d
[D][wiegand:116]: received unknown 18-bit value: 2e00d

I would love to get this tag in HA to trigger an automation for bell-ringing, but since 18 bit is not in the code, it logs it just in the debug log, but does not transfer/create a tag in HA.

Solutions might either be add 18-bit values as in the following example:

if (count == 18) {
char tag_buf[12];
buf_append_printf(tag_buf, sizeof(tag_buf), 0, "%" PRIu32, static_cast<uint32_t>((value >> 1) & 0xffffff));
ESP_LOGD(TAG, "received 18-bit tag: %s", tag_buf);
for (auto *trigger : this->tag_triggers_)
trigger->trigger(tag_buf);
}

OR, another idee might be an configurable option, so one can choose, if only "well-known" values should deliver tags to HA, or "all values" should deliver tags to HA.

Use cases

Trigger automations based on button press from i key reader, which ends up as 18-bit values/tag in HA.

Anything else?

No response

[github-actions[bot]]

🏷️ I've automatically added the component: wiegand label to help categorize this feature request.

[ssieb]

Do you have any documentation on 18-bit values?
You can still use the raw trigger to pick this up.

[Oggy512]

This can be closed. I was using this component for a long time, back then it was a own repository and either didn't had documentation regarding the raw values, or I did not recognize it.
Anyway, I found a solution to solve it: I created a variable and write the RAWID in, and with a text sensor I read those values. In HA I then have an automation which triggers, when the last RAW value is 2e00d.

wiegand:
  - id: reader
    d0: GPIO25
    d1: GPIO26
    on_tag:
      - lambda: |-
          ESP_LOGI("tagID", "received tag %s", x.c_str());
          id(tagID).publish_state(x);
      - homeassistant.tag_scanned: !lambda 'return x;'
    on_raw:
      - lambda: |-
          ESP_LOGI("RAWID", "received raw %d bits, value %llx", bits, value);
          char buf[20];
          sprintf(buf, "%llX", value);
          id(RAWID).publish_state(buf);

key_collector:
  - id: pin_reader
    source_id: reader
    min_length: 8
    max_length: 12
    end_keys: "#"
    end_key_required: true
    back_keys: "*"
    allowed_keys: "0123456789"
    timeout: 10s
    on_progress:
      - logger.log: 
          format: "input progress: '%s', started by '%c'"
          args: [ 'x.c_str()', "(start == 0 ? '~' : start)" ]
    on_result:
      - logger.log: 
          format: "input result: '%s', started by '%c', ended by '%c'"
          args: [ 'x.c_str()', "(start == 0 ? '~' : start)", "(end == 0 ? '~' : end)" ]
      - lambda: |-
          ESP_LOGI("pinID", "received pin %s", x.c_str());
          id(pinID).publish_state(x);
      - homeassistant.tag_scanned: !lambda 'return x;'
    on_timeout:
      - logger.log:
          format: "input timeout: '%s', started by '%c'"
          args: [ 'x.c_str()', "(start == 0 ? '~' : start)" ]

text_sensor:
  - platform: template
    name: "Last tag ID"
    id: tagID
    update_interval: never

  - platform: template
    name: "Last PIN"
    id: pinID
    update_interval: never

  - platform: template
    name: "Last RAW ID"
    id: RAWID
    update_interval: never

[ssieb]

If you do have any documentation on the values, it would still be good to add this variant to the component.