Feature Request: Expose LWT as Binary Sensor via MQTT Auto-Discovery

[MiguelAngelLV]

Describe the solution you'd like

lnxlink already publishes an MQTT LWT (Last Will and Testament) topic (ON / OFF) to indicate client availability. However, this is only used internally as an availability_topic and is not exposed as a standalone entity in Home Assistant.

To use the PC power state in automations, users must:

• Manually create an MQTT sensor/binary_sensor, or
• Rely on availability of other entities (less clear and harder to reuse)

Proposed Solution

Expose the LWT topic as a binary sensor via MQTT auto-discovery:

{
  "name": "PC Power State",
  "state_topic": "lnxlink/<hostname>/lwt",
  "payload_on": "ON",
  "payload_off": "OFF",
  "device_class": "running",
  "unique_id": "<hostname>_lwt"
}

Simpler automations (no manual config required)

• Clear ON/OFF representation of PC state
• More robust: MQTT LWT ensures it eventually switches to offline even after crashes
• Better UX, especially for new users
• Summary

Expose LWT as a binary sensor to provide a simple and reliable way to track PC power state in Home Assistant.

Additional context

No response

[bkbilly]

I've pushed an update which adds this functionality.
A new LWT binary sensor is created which ignores the availability topic, so it will only show the status ON or OFF.
Thank you for recommending this.

[MiguelAngelLV]

Thanks you.

When be release the next version?

[bkbilly]

In about a week, I'll have it ready

[balgerion]

Hey gents, this sensor is available in this release ?
I don’t have any new sensor do I need to change config to make it work ?

[bkbilly]

You will need to edit your config to enable the new lwt sensor.
There is a command that shows all the available modules and lets you enable/disable any of them:

lnxlink -m -c lnxlinkconfig.yaml