Routes
A route decides which data goes to a destination. It says “this destination receives these tags”: for example “MES receives every energy tag of site A”. You choose the tags by site or another label, by source or one by one, where you are: on the destination, or with Send to destination on a source or tag. A route belongs to the organisation, not to one connection, so one route can feed a destination from many sources.
A route also covers tags that do not exist yet. Add a Modbus meter at site A next month, and its tags go to MES as soon as they match.
Choose what a destination receives
Open the destination. In the Routes card, click Choose what it receives, or Routes and then New route when it already has routes. The window asks What should this destination receive?
- Sites and other labels: choose a label, for example
site, and one or more of its values. A tag matches when it has one of the values. - Sources: only the tags read by these connections.
- Tags: only these tags.
Everything you fill in must match; leave a field empty to not filter on it. While you choose, the list shows the tags that match now. To change a route, open Routes and click Edit beside it.
Send a source or a tag to a destination
On a source or a tag page:
Pick the destination. UpBlue says what will happen, for example that the tag is already sent, or that it is added to a route of that destination, and creates the route when there is none yet.
Start a route
The route page saves your changes as you make them, but that changes nothing yet. A new route, and an edit of a started route, runs only after you click Start route or Update route on the route page.
Start and stop one route
The top card of the route page names the destination, with Online beside it while the route runs (Stopped after you stop it) and the time of the last push to the Collectors below it. On the right are Start route (on a new or stopped route), Update route (on a started route with edits that are not deployed) and Stop route (on a started route). Each asks you to confirm.
They act on that route alone: Start route and Update route send the route as you saved it, Stop route stops sending its tags. Edits of other routes stay as they are. The route list shows each route as Started, Stopped or Not started, like the sources and destinations lists, with Changes not deployed when a started route has edits that are not deployed.
The routes go to every Collector of the organisation (devices run no routes) and to the UpBlue cloud, and a window shows per Collector whether it received them. A Collector that is offline, or did not receive them, is marked Behind on the collector page and catches up by itself when it connects again.
Deleting a started route stops it at once and removes it. To keep a route without sending, stop it instead.
Warnings
Start route on a route, and Start source or Start destination on a connection, tell you when a linked item is not started, so you know why nothing is sent yet:
| Warning | What to do |
|---|---|
| A route that matches this source is stopped | Start the route |
| The destination of this route is stopped | Start the destination |
| No started route sends to this destination | Start a route to it, or create one |
Each warning links to the item. Nothing is blocked: the source still stores its data, and the route starts sending as soon as the other item is started.
Problems
A route that cannot work, for example with a tag name pattern that is not a valid regular expression or a destination that was deleted, shows the problem on the route and Invalid in the list, before you click anything. Start route is disabled until you fix it. A started route that became invalid keeps running as it was until you fix it.
All routes of the organisation
Routes under Data Collection in the menu lists every route, with what it sends and to which destination. Here you also find the settings the panels above do not show:
- Tag name pattern: a regular expression the whole tag name must match, for example
energy_.*. - Send data sends the values of the matching tags; Send events sends the start and stop of the events their rules create.
To keep a route without sending, stop it.
A route with nothing filled in sends every tag of the organisation. Check the list of matching tags before you save.
Which data a destination can receive
A route sends to a destination the matching tags of every Collector that delivers it (see Delivered by). A destination delivered by all collectors receives the tags of every Collector; one delivered by one Collector receives only that Collector’s tags, and the Flow view of a tag on another Collector shows that hop as not delivered by this collector. The values of cloud connections only reach an HTTP destination that sends via the UpBlue proxy, never MQTT out. The tags of a device are not delivered to a destination that a Collector delivers.
Events
Events arrive on the same address or topic as the data, so your system tells them apart by "type": "activity":
{"type": "activity", "rule": "…", "tag": "line_speed", "state": "started", "time": "2026-10-22T14:03:11Z", "label": [{"key": "site", "value": "plant1"}]}state is started or stopped. After a Collector restart it sends the current state of every rule again, so treat each event message as “this is the state now”. Messages can arrive out of order and, after a retry, twice: sort on time and drop duplicates on the message id.
Revisions
Every start that changes a route is kept as a revision of that route. Click Revisions on the route page to see when it changed, by whom and what it sent.
Restore makes an older revision the saved route again. Nothing changes in what is sent until you start or update the route.
Is it arriving?
The Flow card on a tag page, and Flow on a source or destination page, show the way the data takes, with the routes that send it, and how much went to each destination. A destination a route names but cannot reach is red with the reason, for example not delivered by this collector for a tag on a Collector that does not deliver that destination, or a route or destination that is stopped. Such a route is also listed under Needs attention on the home page, and the route, the source and the destination show Can’t deliver with the reason.