Settings

Bridge settings

Registering hardware Raven cannot discover, and why there is nothing to configure.

A bridge has the fewest settings of any device type, because Raven does not interpret what is on the other end. It needs to know where the device is, and that is all.

Registering the hardware

Bridges are added by hand, not discovered. A generic HTTP device does not announce what it is, and hardware that cannot be identified is left out of discovery results rather than guessed at. The technician registers it instead:

Add hardware

Le Comptoir

Device

Device type
Bridge
Connection type
Network
Name (optional)
Card terminal

Address

Host
192.168.1.80
Port
8080
CancelSave
Registering bridge hardware. The name is the operator's, because nothing else can supply one.
SettingWhat it does
Device typeBridge. This is what makes it proxyable rather than printable.
Connection typeHow the connector reaches it. Network, for anything with an HTTP interface.
Name The operator's name for it. Manual registration exists precisely for hardware that cannot identify itself, so a person is the only source of a name. Leave it blank and it stays unnamed; there is nothing to fall back to.
Host and PortWhere the device answers on the venue network.

The virtual device

Then create a bridge-type logical device and bind it to that hardware. Its id is what your requests address, with the same stability every other device type gets. See The four nouns.

Card terminal

Virtual bridge · Le Comptoir

Identity

Name
Card terminal
Description (optional)
Counter A

Hardware

Physical device
Bridge · 192.168.1.80:8080
CancelSave
A bridge's own settings: a name, and the hardware it points at.

There is no protocol setting

No character set, no command language, no driver. A bridge call is passed through untouched, so there is nothing for Raven to configure: the contract is the device's own, and your integration is written against the device's documentation.

That is also why a bridge has no idempotency mechanism of Raven's. See Bridging any device.

If the device's address changes

The address lives on the physical device record, so a device that moves to a new IP is a rename of the hardware, not a change to your integration. Reserve its address on the venue router if you can; a bridge that silently points at a DHCP address someone else now holds is an unpleasant way to spend an afternoon.