Configuring devices from Omaya

Many sensors have settings: how sensitive a motion sensor is, how often a tag broadcasts, how strong its signal is, how often a LoRaWAN sensor reports. Omaya can change these for you, from the device's page, without anyone standing next to it with the maker's phone app — for the models whose maker publishes how.

Which devices

Device → Sensor settings lists every model Omaya supports, whether or not you have one: what can be changed, how the change reaches it, and what Omaya never sends. Filter it to You have or Configurable, none yet.

Devices	What you can change	How the change gets there
MOKO S01 motion sensor	Motion sensitivity, how long it stays occupied, how often it broadcasts, signal strength, name and beacon IDs, whether a long press can switch it off, its clock, its password	Bluetooth, through a gateway that can send commands
MOKO S02R distance sensor	Read only for now (how often it measures, range, signal strength)	Bluetooth, through a gateway
MOKO BeaconX Pro tags (H2–H5, M2, M3 mini, MK B5, BXP-C/D/DH)	Per broadcast slot: how often and how strong; the password	Bluetooth, through a gateway
MOKO buttons (B2, H8)	Per press (single, double, long): how often and how strong; the double-press window; the name	Bluetooth, through a gateway
MOKO PS101-M badge	Everything — see Badge settings and commands	Its own commands
Milesight LoRaWAN sensors	How often it reports; restart	A downlink through your LoRaWAN network server
Home Assistant and Aqara devices	Whatever Home Assistant offers as a setting for the device (an FP300's hold time, a bulb's power-on behaviour)	Home Assistant
Minew tags, beacons and buttons (MWC01, MWL01, MBS02, S1, E7, E8, i7, MBM01)	Per broadcast slot: how often and how strong; the password (exactly 8 letters or digits). On an MWC01, Button presses (see below). What a slot broadcasts and what triggers it are shown; anything else there is changed in Minew's BeaconSET+ app	Bluetooth, through a gateway
Minew radars (MSR01-A, MSR01-B)	Not yet: use Minew's MinewLink app next to the sensor	—
Kontakt, MikroTik, Dusun beacons	Not from Omaya: set by the maker's cloud, by a magnet, or not published	—

Today only Dusun gateways can connect to a Bluetooth sensor. A gateway carries commands only while its Accept commands switch is on (Device → Gateway → edit).

Changing a setting

1. Open Device → Sensor and open the device (double-click its row, or select it and press View), then its Control tab. The Configure card lists what can be changed and which gateway the change would go through, or says why it cannot be configured; when Omaya can change nothing on that model, the Control tab is greyed and says why.
2. Press Configure. The page shows only the settings this model has, each with Now — what the device last said it holds — and Change to.
3. For a Bluetooth sensor seen for the first time, press Read from the device first so Now is filled in. It takes a minute or two.
4. Change what you need. Each change is marked Waiting, and the panel on the right lists them. Nothing is sent until you press Apply to the device; Undo forgets them.
5. Apply. You can leave the page: the change runs on its own and ends in the History as Done, Failed (with the reason), No answer or Not sent.

With Manage devices permission you can tick Also apply to the other devices of this model: each one is changed in turn, a few minutes apart, so one gateway is never asked to do two at once.

After you apply, Apply to all under the Apply panel lists every one of those devices on its own line with where it stands — Done, Waiting, Sending, Not sent, Failed or No answer — and the reason for any that were not sent or failed. A line at the top adds them up (for example "12 done · 3 waiting · 2 not sent · 1 failed"). The list keeps itself up to date while any device is still waiting; long lists show the first 20 with Show all. Each device name opens that device's Configure page, so you can send it again from there.

Come back later and the Configure page of any device of that model shows the last apply to all of the past 7 days, folded to one line such as "Last apply to all: 2 hours ago — 12 done, 2 not sent". Press Show to see each device.

What "Done" means

Route	Done when
Bluetooth	The device accepted every value, and Omaya read each one back and it matches. If one reads back differently the change ends Failed and says which.
LoRaWAN	A sensor only listens for a moment after it reports, so the change waits on the network server for the next report. Most Milesight sensors do not say "done", so Omaya confirms it by watching the reports: two in a row at the new interval. Five reports without that, it ends Failed; you can send it again. Stop waiting gives up early.
Home Assistant	Home Assistant accepted it and shows the new value two seconds later.

Passwords

MOKO and Minew Bluetooth sensors ask for a password before they accept a change. Omaya keeps the passwords it signs in with, so nobody has to type one each time a setting is changed. LoRaWAN and Home Assistant devices need no password here.

Omaya tries, in order:

1. the sensor's own password, if one is saved for it;
2. the organisation's password for that maker;
3. the maker's factory default, which is published.

Passwords are stored encrypted and never shown again, only replaced or removed.

The Passwords page

Device → Sensor settings, then the Passwords tab. The tab appears only for a role that can open it (see Who can see and use passwords).

The first card has one row per maker, MOKO and Minew:

Column	What it shows
Maker	The maker, and how many of its sensors this organisation has
Organisation password	•••••••• saved, or Not saved (factory default is tried)
Last used	Worked and when, Refused and when (with the sensor that refused it), or Saved and by whom, when it has not been used yet
(buttons)	Add, or Replace and Remove once a password is saved

The second card, Sensors with their own password, or a recent sign-in, lists each sensor that has a password of its own or that Omaya has signed in to: Sensor, Password (Its own, or Organisation / factory), Last sign-in (Worked or Refused, and when) and a Configure link to that sensor's page.

Save the organisation's password

Do this once per maker, with the password your sensors use now.

1. On the Passwords tab, press Add (or Replace) on the maker's row. A box opens below the list.
2. Password the sensors use now: type it. MOKO and Minew passwords are exactly 8 characters; a Minew password is letters and digits only.
3. Leave Also change it on the sensors unticked.
4. Press Save. Cancel closes the box without saving.

Check it worked. The row shows •••••••• saved. After the next change to one of that maker's sensors, Last used shows Worked and when.

Errors you may see:

Message	What to do
Enter the password.	The box was empty. Type the password, or press Cancel
MOKO devices use passwords of exactly 8 characters. (or Minew devices …)	Check the length and type it again
Letters, digits and punctuation only, no spaces.	Remove spaces and other characters

Saving a new organisation password clears the row's Last used, so the next sign-in shows whether the new one is right.

Change the password on every sensor

Factory passwords are published, so anyone near a sensor with the maker's phone app could change it. Replace them with your own.

1. On the maker's row, press Add or Replace.
2. Password the sensors use now: type the current password if it is not saved yet. If it is already saved, you can leave this empty.
3. Tick Also change it on the sensors. The text under it says how many of this maker's sensors Omaya can change.
4. New password: type the new one, exactly 8 characters (for Minew, 8 letters or digits).
5. Press Save. Omaya asks Change the password on every MOKO sensor that supports it? (or Minew), and warns that anyone using the maker's app will need the new one. Press Change to go ahead.

The message says how many sensors will be changed, and names any it could not send the change to, with the reason; it stays on screen until you leave the page. Omaya changes the sensors one at a time, a few minutes apart, as a gateway reaches each one. Each sensor keeps its old password until it accepts the new one.

From then on the new password is the organisation's, so sensors you add later are tried with it. Sensors that have not taken it yet keep the old one as their own password, so they still sign in: those still waiting, those no gateway could reach, and models whose password Omaya cannot change. If no sensor could be sent the change, nothing changes, and the organisation keeps the old password.

Check it worked. In Sensors with their own password, or a recent sign-in, each sensor that accepted the new password shows Password Organisation / factory and Last sign-in Worked; one still on the old password shows Its own until it takes the change. Its Configure page shows the result in its History:

Result	What it means
The sensor accepted the new password; Omaya will use it from now on.	Done. The sensor now uses the organisation's password, which is the new one
The sensor did not answer the password change. Omaya will try both passwords next time and keep the one that works.	The answer was lost. Nothing to do: the next change sorts it out
The sensor did not accept the new password. Its password is unchanged.	Try again later, or change that sensor from its Configure page

A sensor that no command gateway can reach at that moment is not counted as changed and keeps its old password: the message and its History show Not sent with the reason, such as No gateway has heard it in the last hour. A sensor that already has a change under way is left out and named too. Change those from their Configure page once they can be reached. Only models whose password Omaya can change are included: MOKO S01 motion sensors, MOKO BeaconX Pro tags and Minew devices. MOKO S02R sensors and MOKO buttons are left alone; change those with the maker's app.

A sensor with a password of its own

For a sensor that does not use the organisation's password, such as one set up by a supplier:

1. Open the sensor on Device → Sensor, go to the Control tab and press Configure.
2. In the Device password card, type the password in the box (This device's own password) and press Save. The card says Saved for this sensor only.
3. To go back to the organisation's password, press Use the organisation's password instead. The card says This sensor now uses the organisation's password.

The card always says which password the sensor signs in with: This device's own password, The organisation's MOKO password (or Minew), or The factory default (no password saved), with Worked or Refused and when.

To change the password on this one sensor, open Change the password on the device in the same card, type the new password and press Change. Omaya asks Change the password on the device itself?; press Change. The button is greyed while another change to the sensor is waiting, or when no gateway can reach it. If the model's password cannot be changed from Omaya, the card has no such option.

Remove a saved password

1. On the maker's row, press Remove.
2. Omaya asks Remove the saved password?: sensors without their own are then tried with the factory default. Press Remove.

Sensors with their own password keep it. Removing the organisation's password does not change anything on the sensors.

Who can see and use passwords

The Passwords tab, the Device password card's boxes and every password change need the Bulk Import Devices permission on the role (System → Roles). Admin and Manager have it as shipped; Viewer does not. Without it, the tab is not shown, and the Configure page shows only which password the sensor signs in with. See Permissions.

Nobody can read a saved password back, including administrators. System → Activity Log records, with who did it and never the password:

• saving, replacing or removing the organisation's password for a maker, and starting a change on every sensor, with how many were sent and which were not;
• saving, replacing or removing one sensor's own password, also on that sensor's History;
• every change of a password on a sensor, and every change or read that signed in to one, under Device commands.

What Omaya never sends

Whatever the device, Omaya never sends: switch off, factory reset, firmware update, stop accepting connections, or rewriting its serial number, Bluetooth address or maker details. On LoRaWAN, never its network settings (join, data rate, channels, class), shutdown, clearing its stored history, or calibration. Each of these can leave a device nobody can reach without going to it; do them with the maker's app, on site.

These are blocked in the code that talks to the gateway, not only hidden on the page. Two more rules:

• A button's press is never switched off, and a tag's broadcast slot is shown but never changed: either could silently stop a panic alarm or the readings Omaya gets from it. The one exception is Button presses on a Minew tag, which only ever writes the press slot described below.
• One change at a time per device, and one device at a time per gateway.

Every read, change, password change and refusal is in System → Activity Log under Device commands, with who asked, the values (never a password) and the gateway that carried it.

Button presses on a Minew tag

A Minew MWC01 sends a press only if one of its broadcast slots is set up for it. Out of the box that slot is often empty, so a double press does nothing. Button presses sets it up from Omaya:

1. Open the tag on Device → Sensor, go to the Control tab and click Configure.
2. Under Button, set Button presses to Double press raises an alarm.
3. Click Apply to the device. Omaya connects through a gateway, writes the press slot and reads every slot back.
4. Check it worked: the result says the sensor confirmed it and reads back the new values, and the slot it used shows Broadcasts when: Double press. Double-press the tag; within a few seconds the press appears on Report → Button Press and fires any rule on button presses.

Omaya uses the first empty slot (never slot 1, which carries the tag's position). That slot broadcasts only for 20 seconds after a double press, so the tag's battery and the other slots are unaffected. Setting it back to Off switches that slot off again. If every slot is in use, the result says so and nothing is written; free one with Minew's BeaconSET+ app first.

LoRaWAN: let the network server take changes

Omaya sends a LoRaWAN change on the same MQTT broker your network server already publishes to, on a topic only that server listens on. Set it once:

• Milesight UG56 / UG65 built-in network server: in the application's MQTT settings, set Downlink data topic to omaya-downlink/{token}/$deveui, where {token} is your connector's token (the part after your organisation in the connector topic). See Milesight UG56 and UG65.
• ChirpStack: set command_topic as shown in MQTT gateways (it is in the example).

A network server that sends to Omaya over HTTP cannot take changes: HTTP is one way. Switch it to the MQTT integration.

Problems

What you see	Why, and what to do
"No gateway has heard it in the last hour"	The device is out of range of every gateway, or its battery is flat.
"None of the gateways that hear it can send commands"	Only Dusun gateways can connect to a Bluetooth sensor. Bring it near one.
"Every gateway near it … is set to listen only"	Turn Accept commands on for one of the gateways named.
"No gateway could connect to it"	It was heard but would not take a connection: too far (a weak signal drops the link), or a button that only accepts connections for a while after a press — press it, then apply.
"The sensor refused the password"	Save the right one under Sensor settings → Passwords, or on the device's Configure page. Nothing was written. See Passwords.
"Omaya cannot change this model's password; use the maker's app."	The model's password can only be changed with the maker's app.
"This tag did not answer as a MOKO BeaconX Pro"	The model is set wrong in Omaya, or it runs other firmware. Nothing was written.
"This device did not answer as a Minew BeaconSET+ device"	The model is set wrong in Omaya, or it is a Minew product configured with another app. Nothing was written.
"The gateway could not keep a connection to the device"	The signal is too weak for a steady link. Omaya tries the next gateway that hears it; if none can, bring the device closer to one. Nothing was written. Once a gateway has completed a change or a read with a device, Omaya tries that gateway first the next time, which the card shows as Through ….
A setting shows a lock and Read only	Omaya can read it but not yet change it; the reason is under the setting.
LoRaWAN: "Its network server sends to Omaya over HTTP"	Switch the network server to the MQTT integration.
LoRaWAN: Failed, "Its reports did not change"	The network server did not pass it on. Check its downlink topic, then send again.
Home Assistant: "offers no settings for this device"	Home Assistant has no configuration entities for it; nothing to change from here.