CLI responses not working properlly

[dida886]

@drewmccal

Please chceck my comment in
#295 (comment)

[drewmccal]

Thanks @dida886 — I replied in detail on the PR: #295 (comment)

Short version: this is working as designed. The incrementing number is the sensor's state (a neutral command counter). The command/response text is deliberately kept out of the state and the recorder DB — the state is written to history, and commands like send_login <contact> <password> would otherwise leak secrets into the database.

The CLI output is in the sensor's attributes instead — render state_attr('sensor.meshcore_XXXXXX_cli_console', 'transcript') in a markdown card (see the PR reply for the exact YAML), or use last_response / history. The logbook won't show it; the meshcore_cli_response event is there for automations.

I think this can be closed as working-as-designed once you've confirmed the transcript card shows your output — but I'll also add a note to the docs so the "state is a count, output is in the transcript attribute" bit is spelled out and nobody hits this again.