Minew G1 (Bluetooth)

The G1 is Minew's Wi-Fi and Ethernet Bluetooth gateway. It is configured from a web page inside the gateway and publishes to Omaya over MQTT in Minew's own JSON, which Omaya reads directly — no script, no app.

It hears any Bluetooth tag, beacon or sensor, Minew's own (the MWC01 wristband, S1 sensors, E-series beacons) included.

What you do in Omaya

1. Create the connector and copy its host and topic — A
2. Register the gateway by its MAC — B
3. Place it on the floor plan and do the calibration walk — C
4. Register the tags and sensors it will hear — D
5. Check it end to end — E

Before you start

• Where it will hang — read gateway placement first.
• How it joins your network: an Ethernet cable (simplest, and the G1 can be powered over it), or the name and password of the Wi-Fi network it will use.
• A laptop or phone with Wi-Fi, the connector topic from step A, and the gateway's MAC, printed on the label (it starts AC233F).

On the gateway

1. Open its web page

1. Power the G1. It opens its own Wi-Fi network named GW- followed by its MAC, e.g. GW-AC233FC0A1B2.
2. Join that network from the laptop or phone and open http://192.168.99.1.
3. Sign in as admin with the password on the label or in the box (Minew ships some units with none set — set one before you leave).

2. Network

On the Network page, choose Ethernet or Wi-Fi. For Wi-Fi, pick your network from the list and enter its key. Leave the addressing on DHCP unless your network needs a fixed address. Save; the G1 restarts onto your network.

The G1 stamps every reading with its own clock, so it needs to reach the internet for time. A G1 whose clock is wrong has its readings ignored for positioning (anything more than 30 seconds old is), so if Step E shows tags but they never move, check the time first.

3. Service

On the Service page, choose MQTT and enter:

Setting	Enter	Why
Server / URL	tcp:// and the Omaya host you sign in to, e.g. tcp://omaya.example.com	ssl:// with port 8883 works too once tcp:// does
Port	1883
Topic	your connector's topic, character for character	see Your MQTT settings
Client ID	G1- followed by the MAC without colons, e.g. G1-AC233FC0A1B2	must differ on every gateway
Username / Password	blank
Upload interval	1 second	Positioning wants every gateway reporting at about the same pace
Data format	JSON-LONG	The long format carries the raw advertisement Omaya decodes; the short and binary formats do not

4. Filters

Leave the filters open:

• RSSI filter off (or the weakest value offered);
• no name or MAC filter, no whitelist;
• iBeacon, S1 and Unknown uploads all on;
• duplicates uploaded.

Positioning compares what every gateway hears, weak readings included, and a button press is a short burst that a duplicate filter can swallow. A gateway that filters is deciding on Omaya's behalf which readings matter. If you want fewer messages, register only the devices you care about in Omaya — anything not registered is dropped on arrival.

Save. The G1 starts publishing straight away.

Newer G1 firmware

Some G1s run Minew's newer firmware, whose Data format list offers MINEW-CONNECT, JSON-RAW and JSON-PREPARSED instead of JSON-LONG. Omaya has been checked against JSON-LONG, where the gateway names itself in every message. On the newer firmware choose JSON-RAW, then do step E before anything else: if the gateway never shows online, the format is not carrying its MAC — tell your Omaya provider which formats your G1 offers and its firmware version, shown on its status page.

Your MQTT settings

The G1's Topic is your connector's topic, character for character. It is built from two values Omaya generated for you:

• Organisation id — the second part. It never changes.
• Connector token — the third part: 16 characters, issued when the connector was created. It is the gateway's password, so treat the topic like one. Rotating it on the connector page stops the old topic at once, and every gateway on that connector then needs the new one.

One topic per connector. Every gateway a customer owns from you publishes to the same topic; the gateway is identified inside the payload, not in the topic.

Type your organisation id, token and the G1's MAC — or paste the whole topic from the connector page — to get the topic and Client ID to copy. It works in the page only: nothing you type is sent or saved. The G1 does not need the subscribe topic the box also shows.

Fill in your gateway's MQTT settings

Paste the topic from your connector page (optional — fills the next two)

Organisation idConnector tokenGateway MACOmaya host

Use SSL/TLS (port 8883)

Host	the Omaya host
Port	1883
SSL/TLS	off
Client Id	G1-<gateway-MAC>
Publish topic	omaya/<organisation>/<token>/minew/ble
Subscribe topic	omaya/<organisation>/<token>/minew/cmd/<gateway-MAC>
Username / Password	(blank)

Anything still in <angle brackets> needs your value. Nothing you type here leaves this page.

In Omaya

A. Create the connector

Connectors → IoT Gateway (MQTT) → add:

Field	Choose
Connector Name	e.g. Minew G1s — HQ
Vendor	Minew
Protocol	BLE (Bluetooth Low Energy)
Active	on

Save, and copy the host into Server / URL and the topic into Topic. The topic looks like omaya/<organisation>/<16-character token>/minew/ble; the vendor part must say minew, which is what tells Omaya to read Minew's format.

B. Register the gateway

Device → Gateway → add, with the MAC from the label, Device Model Minew, and its location, venue and zone. Messages from a gateway Omaya does not know are dropped, so do this before or straight after saving the Service page; one that publishes first is noted and can be registered afterwards.

C. Put it on the floor plan

Place it where it physically hangs, at its real height, and once every gateway on the floor is up, do the calibration walk. On a floor that mixes G1s with other makes, the walk is what lets Omaya allow for each one hearing a little differently.

D. Register what it will hear

Under Device → Sensor, add each tag, beacon or sensor with its MAC and Device Model — and a zone for anything fixed to a wall. Minew's own devices are in the model list by name. Device → Bulk Import takes a spreadsheet; New sensor types handles a model Omaya does not know yet.

E. Check it

Within a minute the gateway shows online on Device → Gateway — the G1 reports on itself in every message, so it shows online even in an empty room — and the tags it hears appear on the Live Monitor and on their own pages.

When it disappoints

The G1's web page is unreachable after saving the network. It has left its own Wi-Fi and joined yours. Find its new address in your router's list of connected devices, or hold the reset button to return it to its own network.

Connected, nothing in Omaya. The topic first, character by character — a wrong token is dropped silently, by design; paste it into the box above to check its shape. Then the vendor part of the topic (minew), and the MAC registered under Device → Gateway.

Online, but tags never move from room to room. The G1's clock. Readings more than 30 seconds old are not used for positioning, and a G1 that cannot reach a time server stamps them wrongly.

Two G1s keep going offline in turn. They share a Client ID. Give each its own, with its MAC in it.

Tags appear but sensor values or button presses do not. The data format is not JSON-LONG (the short format has no raw advertisement to decode), or a filter is on.