Skip to content

Settings

Flags

A set of flags are used to toggle certain functionality:

Flag Description Default
Duty Cycle If flag is set, duty cycle requirements as per ETSI regulations are enforced by the device firmware. On
Confirmed uplinks If flag is set, event messages will be sent as confirmed messages On
Transport mode If flag is set, device will enter transport mode after a reset by magnet. This flag will be cleared every time device joins a network On

Configuration Options

The miro Logibutton offers the following options to adapt the functionality according to the use case requirements. See Payload on how to configure the devices using downlink messages

Name Description Default Unit
Mode Event configuration (see Event Configuration) 0x99
Nb of retransmissions Number of retransmissions for confirmed messages 8
Text transport mode Display text in transport mode «TRANSPORT» Text
Text idle mode Display text in idle mode «IDLE» Text
Text idle mode Display text in idle mode «ACTIVE» Text
Text action idle short Display text on short press in idle state «IDL S» text
Text action idle long Display text on long press in idle state «IDL L» text
Text action active short Display text on short press in active state «ACT S» text
Text action active long Display text on long press in active state «ACT L» text
Text Joining Display text while joining «JOINING» text
Text success idle short Display text on successful transition from idle by short press «SUCCESS IS» text
Text success idle long Display text on successful transition from idle by long press «SUCCESS IL» text
Text success active short Display text on successful transition from active by short press «SUCCESS AS» text
Text success active long Display text on successful transition from active by long press «SUCCESS AL» text
Text Joined Display text on join success «JOINED» text
Text fail idle short Display text on failed transition from idle by short press «FAIL IS» text
Text fail idle long Display text on failed transition from idle by long press «FAIL IL» text
Text fail active short Display text on failed transition from active by short pres «FAIL AS» text
Text fail active long Display text on failed transition from active by long press «FAIL AL» text
Text Join failed Display text on join failed «JOIN FAIL» text
duration_magnet Time to apply magnet to activate device in transport mode 20 100 ms
duration_magnet reset Time to apply magnet to reset device 80 100 ms
duration_short_min Minimum button press time for short press 10 100 ms
duration_short_max Maximum button press time for short press 20 100 ms
duration_long_min Minimum button press time for long press 30 100 ms
duration_long_max Maximum button press time for long press 40 100 ms
duration_idle_timeout Time to show message in idle mode (set to 0 for allways on) 50 100 ms
duration_active_timeout Time to show message in active mode (set to 0 for allways on) 0 100 ms
duration_result_is Time to show transition result (success/fail) on idle short press 20 100 ms
duration_result_il Time to show transition result (success/fail) on idle long press 20 100 ms
duration_result_as Time to show transition result (success/fail) on active short press 20 100 ms
duration_result_al Time to show transition result (success/fail) on active long press 20 100 ms
duration_joined_timeout Time to show join result (success/fail) 20 100 ms
interval_status Status message interval 1440 minute
interval_temperature Temperature measurement interval 300 second

Event Configuration

For each action (short or long press) in both of the two states (idle and active) the state transition can be configured or disabled. For each state/action combination, there are the following settings available:

  • Disable (0)
  • Transition to idle (1)
  • Transition to active (2)

If a transition is disabled it will not be offered to the user. If, for example, short press from active to idle is disabled, the user can only use long press. Obviously, there needs to be at least one active transition for idle state.

Warning

When configuring events, it is important to make sure there are no "dead states" (e.g. transition from idle to active with no transition back). The device will reject such configurations, which will possibly lead to unexpeced device misconfiguration.