Appearance
Dusun Bluetooth gateways
Dusun's DSGW gateways (the DSGW090 and its siblings) are the Bluetooth gateways Omaya is run on day to day. Each one listens for tags, beacons and Bluetooth sensors and publishes what it hears to Omaya over MQTT every few seconds. This page takes one from the box to tags on the floor plan: the gateway's own settings first, then the steps in Omaya.
Units supplied pre-configured for your organisation already carry the settings in steps 3 and 4 — for those, check them and go straight to the steps in Omaya.
What you do in Omaya
Before you start
- Where it will hang — read gateway placement first. Where a gateway is decides what positioning can do, far more than any setting.
- A network port with internet access (DHCP), or a SIM with its APN on models with LTE.
- In Omaya, an administrator login and the venue and floor plan the gateway serves.
Step 1 — Power and network
- Plug the Ethernet cable into the WAN port and power the gateway from its adapter. It takes about a minute to boot.
- Find the address it was given: your router's or DHCP server's client list shows it as DSGW090 (or the model you have), with a MAC address beginning
30:AE:7B. - Browse to that address from a computer on the same network. You get the gateway's Authorization Required page.
- Sign in as
root. The factory password isroot; units supplied by us may have one of their own, given with the delivery.
The Home page shows the model, the firmware version, the local time and the network. Keep the MAC address it shows — Omaya identifies the gateway by it.
On a site without a network port, use Interface → LTE instead: fill in the Apn (and Username / Password if your carrier needs them), choose the SIM Slot, then Save & Apply. Interface → WAN Setting is where a fixed address goes if the network team gives you one — set Ip address Get Type to static and fill in the address, netmask, gateway and DNS.
Step 2 — Password and clock
- Advance → Administration: set a new Password and Confirmation, then Save. Record it where the site team can find it.
- Advance → System → Time Synchronization: keep Enable NTP client on, and add a server near you to NTP server candidates —
pool.ntp.org, or your network's own. The factory list holds a single server in China, which corporate networks often block. Save & Apply.
The clock matters more than it looks: Omaya ignores readings more than thirty seconds old when it works out where a tag is, so a gateway whose clock drifts is a gateway whose tags stop moving on the map. The Timezone on the General Settings tab can stay at UTC — the gateway reports time in a form that carries no timezone.
Step 3 — Point it at Omaya
You need the connector's host and topic from Omaya first — see step A below.
On the gateway, open IOT Services → Cloud Config:
| Field | Enter |
|---|---|
| Mqtt Server | the Omaya host, e.g. omaya4.synchroweb.com |
| Mqtt Server Port | 1883 |
| Mqtt Login ClientId | leave as the gateway fills it (its own MAC) |
| Mqtt Login User / Mqtt Login Password | leave as they are — Omaya does not use them |
| Mqtt HeartBeat | 60 |
| Mqtt Sub Topic | leave empty — the gateway then listens on its own reply topic, which is where Omaya answers it |
| Mqtt Pub Topic | the connector topic, exactly — omaya/<organisation>/<token>/dusun/ble |
| Mqtt Will Topic / Msg / Qos / Retain | leave empty |
| Qos | 0 |
| Retain | 0 |
| SSL Option | no ssl |
Save. The topic's token is the gateway's credential: a single wrong character and Omaya drops everything it sends, without an error on either side.
Encryption
Port 1883 is not encrypted. The gateway offers ssl encrypt, with certificate files stored on the gateway itself; that has not been tested with Omaya yet. Until it has, keep Dusun gateways on a network you control, or behind the site's VPN (the gateway has Interface → OpenVPN).
Step 4 — What it listens for
On IOT Services → Bluetooth, under Bluetooth filter and config:
| Setting | Choose | Why |
|---|---|---|
| Data Type | Format Data | carries each device's raw advertisement, which Omaya decodes itself |
| Scan Type | 1M and Code PHY | hears both ordinary and long-range Bluetooth devices |
| Report interval | 1 | positioning wants every hearing, not a summary |
| Rssi (filter) | -110 | effectively off — let Omaya decide what is too weak |
| Device mac, Model String, Raw Data, Dev Name | empty | a filter here hides devices before Omaya can see them |
Press Config beside the group you changed. The Bluetooth devices table underneath lists what the gateway hears right now — a quick way to check a tag is in range before blaming anything else. Leave its Connect buttons alone: Omaya listens to advertisements and never needs the gateway to connect to a device.
In Omaya
A. Create the connector
Connectors → IoT Gateway (MQTT) → add:
| Field | Choose |
|---|---|
| Connector Name | e.g. Dusun gateways — HQ |
| Vendor | Dusun |
| Protocol | BLE (Bluetooth Low Energy) |
| Active | on |
Save, and copy the host and the topic it shows into step 3. One connector serves every Dusun gateway in the organisation.
B. Register the gateway
Device → Gateway → add:
| Field | Enter |
|---|---|
| Name | where it hangs, e.g. L3 east corridor |
| MAC address | the gateway's MAC, from its Home page or label, e.g. 30:AE:7B:EB:47:45 |
| Device Model | Dusun |
| Location, venue, zone | where it is |
A gateway Omaya does not know is dropped, so register it before or as soon as it is connected. (One that publishes first is noted, and can be registered afterwards.)
C. Put it on the floor plan
Place it on the venue's floor plan where it physically hangs. Once all the gateways on a floor are up, do the calibration walk: placing by eye gets a tag onto the right floor; the walk gets it into the right room.
D. Register what it will hear
Under Device → Sensor, add each tag, beacon or Bluetooth sensor with its MAC and Device Model, and — for anything fixed to a wall — its zone. Carried tags need no zone: Omaya works out where they are. Device → Bulk Import takes a spreadsheet for a delivery of tags, and New sensor types is for a sensor Omaya has no model for yet. What each model reports is listed under devices and decoders.
E. Check it
- Device → Gateway: the gateway turns online within a minute of step 3. It announces itself every few seconds until Omaya answers, then reports what it hears every few seconds.
- The Live Monitor: registered tags appear on the floor plan.
- A tag's own page: last seen, the gateways that heard it, and at what signal strength.
Good to know
A tag lingers for about two minutes after it leaves. A Dusun gateway keeps re-sending the last thing it heard from a device for roughly two minutes after losing it. Omaya recognises those repeats and does not count them as a hearing, so positions move on; the gateway's own Bluetooth devices table still shows the device until the gateway gives up on it.
It can change sensors' settings for you. A Dusun gateway can connect to a MOKO sensor, tag or button it hears and change its settings when you press Apply on the device's Configure page. Only gateways with Accept commands switched on (Device → Gateway → edit) are used for this; turn it off on a gateway you want to keep listening only. See Configuring devices from Omaya.
Frame counts are cadence, not reception. The gateway reports its whole device table every few seconds, whether or not anything changed. Frame counts per gateway are therefore reporting cadence, not a measure of how well it hears.
When it disappoints
The gateway never turns online. In order: Mqtt Pub Topic against the connector, character by character; the MAC registered under Device → Gateway; Mqtt Server and port; then whether the network lets the gateway out on 1883 — a guest or corporate network often does not.
Online, but no tags. The tags are not registered (Device → Sensor), or a filter on the Bluetooth page is set. Check the gateway's own Bluetooth devices table first: if the tag is not there, the gateway is not hearing it.
Tags on the wrong floor or in the wrong room. Placement and the calibration walk, not settings — see gateway placement and floor plans and positioning.
Tags freeze in place, then jump. The gateway's clock — step 2.