You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The raw payloads in the event list all use the same type, which makes it hard to filter for specific payloads. Maybe include the first byte of the message in the event type? To still allow finding all unprocessed payloads, introduce a separate field for these?
The text was updated successfully, but these errors were encountered:
Taking as example this event from the TH NKE device
Time 28 May 2021 14:36:18
Server creation time 28 May 2021 14:36:19
Type LoRaPayload
Processed true
Payload "3207c046a96e0267b877a08b76121b0113061080ac006405202b005901c82249252649122104"
Port 125
The raw payloads in the event list all use the same type, which makes it hard to filter for specific payloads. Maybe include the first byte of the message in the event type? To still allow finding all unprocessed payloads, introduce a separate field for these?
The text was updated successfully, but these errors were encountered: