Take a property and wrap it inside a map with the priority and
property-array-index.

Make sure we have the extended information of every known
remote devices.

Can be used some time after the network discovery mechanism, as
some devices might take a while to answer the WhoIs.

Remote devices are queried in parallel.

Return the cached remote device extended information. Nil if we have nothing.

Send a 'create object request' to the remote device. Must be given
at least an :object-identifier OR an :object-type. If
an :object-identifier isn't given, the numbering of the new object
will be choosen by the remote device.

Will block until we receive a response back, success or failure.
If the request times out, an exception is thrown.

Send a 'delete object' request to a remote device.

 Will block until we receive a response back, success or failure.
If the request times out, an exception is thrown.

Find remote devices and their extended info. By default, will try
up to 5 time if not a single device answer. Return the list of
remote-devices.

Should be called in a future call to avoid `hanging' the program
while waiting for the remote devices to answer.

Return the device extended information that we have cached locally,
or request it directly to the remote device.

Send a WhoIs for a single device-id, effectively finding a single
device. Some devices seem to ignore a general WhoIs broadcast, but
will answer a WhoIs request specifically for their ID.

We find remote devices by sending a 'WhoIs' broadcast. Every device
that responds is added to the remote-devices field in the
local-device. WARNING: This won't ask the device if it supports
read-property-multiple. Thus, any property read based solely on this
remote device discovery might fail. The use of `discover-network' is
highly recommended, even if it might take a little longer to
execute.

Do a Who-Has and return the remote-device-ids of any remote devices that
respond. The Who-Has updates a cache that can be accessed at
bacure.events/cached-remote-objects, and that is the same cache we query
here.

Query our cached remote-objects to see which remote-devices have the
specified object (if any). Use `find-remote-devices-having-object`
to update the cache.

Listen to IAm and try to fetch extended-information.

Check if the remote device is still alive. This is the closest
thing to a 'ping' in the BACnet world.

Boot up local devices and return their IDs.
The devices are registered as foreign devices to each other.

Return a map with the networking info of the remote device. (The
network number, the IP address, the port...)

Get the remote device object by its device-id

Return the list of the current remote devices. These devices must
be in the local table. To scan a network, use `discover-network'.

Return a list of vector pair with the device-id and its name.
-->  ([1234 "SimpleServer"])

Retrieve the remote device extended information (name, segmentation,
property multiple, etc..) and update it locally.

Return the cached extended information.

Return the type of segmentatin supported.

Return a map of the services supported by the remote device.

Set the given remote object properties.

Will block until we receive a response back, success or failure.

'write-access-specifications' is a map of the form:
{[:analog-input 1] [[:present-value 10.0][:description "short description"]]}

If the remote device doesn't support 'write-property-multiple',
fallback to writing all properties individually.

Set the given remote object property.

 Will block until we receive a response back, success or failure.

Property-value can be the value directly OR a map resulting from
`advanced-property'