[Bug] rx_log_data is empty when a message is sent using a region scope

[RikoDEV]

I created a bot for my community using automation, and during testing we encountered an issue with region scope handling in this integration.

If a user sends a message with region scope, the data from trigger.event.data.rx_log_data is empty in the meshcore_message event with the channel message_type. When sending the same message without a region scope, I have access to path data and other information from rx_log_data.

Example automation to replay:

alias: "MeshCore Bot: Trace Route"
description: Responds to `es trace` on channel with hop/signal info
triggers:
  - trigger: event
    event_type: meshcore_message
    event_data:
      message_type: channel
      channel_idx: 2
conditions:
  - condition: template
    value_template: >-
      {{ (trigger.event.data.message | default('') | lower).startswith('es
      trace') }}
actions:
  - delay:
      seconds: 2
  - variables:
      d: "{{ trigger.event.data }}"
      rx0: >
        {{ d.rx_log_data[0] if (d.rx_log_data is defined and d.rx_log_data |
        length > 0) else {} }}
      rssi_val: "{{ rx0.rssi if rx0.rssi is defined else 'n/a' }}"
      snr_val: "{{ rx0.snr if rx0.snr is defined else 'n/a' }}"
      path_hex: "{{ rx0.path if rx0.path is defined else '' }}"
      path_len: "{{ rx0.path_len if rx0.path_len is defined else 0 }}"
      path_step: >
        {% set pl = path_len | int %} {% set hex_len = path_hex | length %} {{
        ((hex_len // pl) if pl > 0 else (6 if hex_len % 6 == 0 and hex_len > 0
        else (4 if hex_len % 4 == 0 and hex_len > 0 else 2))) }}
      path_nodes: |
        {% set step = path_step | int %}
        {% if path_hex | length >= 2 %}
          {% set ns = namespace(nodes=[]) %}
          {% for i in range(0, path_hex | length, step) %}
            {% set ns.nodes = ns.nodes + [path_hex[i:i+step]] %}
          {% endfor %}
          {{ ns.nodes | join(' → ') }}
        {% else %}
          ⚡ direct or empty
        {% endif %}
      reply_text: >
        📡 @[{{ d.sender_name }}] RSSI: {{ rssi_val }} dBm | SNR: {{ snr_val }} dB Hops: {{ path_len }} | Path: {{ path_nodes }}
  - data:
      channel_idx: 2
      message: "{{ reply_text | trim }}"
    action: meshcore.send_channel_message

[WJ4IoT]

May I comment I like the automation but dislike the use of it. Every simple soul can copy it, thinks it does not really work remove the condition and creates a ping-pong effect on RF.

There could be better solutions like letmesh or likewise see: https://mc-radar.woodwar.com/test-inspector/message/3783511 as an example. These do not show a single path (consuming air-time) but the complete distribution of the original message.

[RikoDEV]

May I comment I like the automation but dislike the use of it. Every simple soul can copy it, thinks it does not really work remove the condition and creates a ping-pong effect on RF.

There could be better solutions like letmesh or likewise see: https://mc-radar.woodwar.com/test-inspector/message/3783511 as an example. These do not show a single path (consuming air-time) but the complete distribution of the original message.

We use both (automation and corescope), for some reason our community also want diag via #bot channel. For them its easier to ask bot, than opening analyzer. I also know it wasting air time.