Skip to content

Add more parameters to trigger event data#120

Open
GoaMind wants to merge 1 commit into
meshtastic:devfrom
GoaMind:trigger_event_more_params
Open

Add more parameters to trigger event data#120
GoaMind wants to merge 1 commit into
meshtastic:devfrom
GoaMind:trigger_event_more_params

Conversation

@GoaMind

@GoaMind GoaMind commented Nov 30, 2025

Copy link
Copy Markdown

Like SNR, RSSI, Hops, Sender name and id

Example payload for trigger event:

trigger:
  id: message_recieved_from_eg
  idx: '0'
  alias: null
  platform: device
  event:
    event_type: meshtastic_event
    data:
      device_id: xxx000
      type: message.received
      message: '!test' 
      sender_short_name: EG2 # NEW
      sender_long_name: Blue tit EG2 # NEW
      sender_id: '!abcdefg' # NEW
      rx_snr: 6 # NEW
      rx_rssi: -19 # NEW
      hop_count: 0 # NEW
      entity_id: meshtastic.gateway_eg6_channel_longfast
      channel_name: Channel LongFast

@CLAassistant

CLAassistant commented Nov 30, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@GoaMind

GoaMind commented Dec 2, 2025

Copy link
Copy Markdown
Author

Overlaps with PR #94
but adds more parameters

@GoaMind
GoaMind changed the base branch from main to dev December 2, 2025 11:58
@GoaMind
GoaMind force-pushed the trigger_event_more_params branch from 339b995 to a6a9fdf Compare December 2, 2025 14:39
Like SNR, RSSI, Hops, Sender name and id
@GoaMind
GoaMind force-pushed the trigger_event_more_params branch from a6a9fdf to 51248cf Compare December 2, 2025 14:48
@GoaMind

GoaMind commented Dec 8, 2025

Copy link
Copy Markdown
Author

Related #126

@megadimich

Copy link
Copy Markdown

sender_short_name: EG2 # NEW ???
sender_long_name: Blue tit EG2 # NEW ???
sender_id: '!abcdefg' # NEW ???

Thank you for your work. But I couldn't find these parameters here:

       {
            "from": packet.from_id,
            "to": {"node": to_node, "channel": to_channel},
            "gateway": self.get_own_node()["num"],
            "message": packet.app_payload,
            "rx_snr": packet.rx_snr,
            "rx_rssi": packet.rx_rssi,
            "hop_count": packet.hop_count,
        } 

@GoaMind

GoaMind commented Dec 12, 2025

Copy link
Copy Markdown
Author

@megadimich could you clarify how and where from you are taking this parameters, listed in your json object?

Implementation in this PR is mostly related to EVENTS data

@megadimich

Copy link
Copy Markdown

@megadimich could you clarify how and where from you are taking this parameters, listed in your json object?

Implementation in this PR is mostly related to EVENTS data

Now I understand everything. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants