Cannot make my state topic work

Configuration
1

I have the latest home assistant os on rpi3, with its own mqtt broker. Also I have an inels 204, which sends state of switches like this:
topic: inels/status/2C6A6F10C28E/02/04EBB6
payload is either “02\n00\n” or “02\n01\n” (if I understand well).
It is a manually configured device/entity, all the others (set and availability) looks working, but I cannot find a working solution for the status, it remains continuously unknown.
There is no syntax error, there is no anything in the log of hoas, but also there is no change.

configuration.yaml contains the include:
mqtt: !include elko_devices.yaml
and it contains:

  switch:
  - name: ELKO RFSA-66M 04EBB6
    unique_id: elko_02_04EBB6
    state_topic: inels/status/2C6A6F10C28E/02/04EBB6
    command_topic: inels/set/2C6A6F10C28E/02/04EBB6
    payload_on: "01\n00\n00\n"
    payload_off: "02\n00\n00\n"
    state: "{{ value[4:5] }}"
    state_on: "1"
    state_off: "0"
    availability:
    - topic: inels/connected/2C6A6F10C28E/02/04EBB6
      payload_available: "on\n"
      payload_not_available: "off\n"
    device:
      identifiers:
      - inels_rfsa6x_04EBB6
      name: "Szivatty\xFA"
      manufacturer: INELS
      model: RFSA-66M

(no, it is not about the inels integration, which doesn’t work either, that would be another question)

2

Use this to trigger it manually and see what’s happening:
Troubleshooting MQTT? MQTT-Explorer can help you be successful!
If you have Apps available, try adding this App repository to your Apps list. GitHub - GollumDom/addon-repository · GitHub.
With this you can see that the broker sees and likely find the bug.

3

Are you sure these are correct?

4

Is this the inels elan 204? If so is the yellow led showing it connected to mqtt lit?

5

in MQTT explorer I see that the state is "02 00 " or "02 01 " but I don’t know if those are spaces, newlines or anything else, and also I don’t know what is received by home assistant. I see (sometimes) the event is there, that means the topic is fine, but still no action, so the payload does not match.
Yes, inels switches have this weird payloads, for setting the device (command topic) I need to send “01\n00\n00\n” or “02\n00\n00\n” and that part works. Also availability is really “on\n” and “'off\n” that works too.
MQTT is really connected and working, the other direction works, just I have no idea what is the real payload and how to tell hoas to accept it.
Even in MQTT explorer I could not set/send anything, that do something.

7

So yes, in command topic 3 byte is sent (converted to string)

payload_on: "01\n00\n00\n"
payload_off: "02\n00\n00\n"

in status only 2 bytes are received (in hexadecimal)

30320A30300A
30320A30310A

, and yes, they are not even the same. Availability is different again.

      payload_available: "on\n"
      payload_not_available: "off\n"

I have no idea why. But that is what I have.

$ mosquitto_sub -h <host> -u <user> -P <pass> -t inels/status/2C6A6F10C28E/02/04EBB6 -F %X
30320A30300A

And what I need now how can I teach hoas to understand and work with that status payloads. The other two looks ok.