What’s New in IoT Spaces 3.0

Device configuration can be bundled into a profile and assigned to several devices at once. The configuration that actually applies is derived from the profile and the device-specific settings, so a change to the profile reaches every assigned device without overwriting the deviations of individual devices. Profiles can be exported and imported into another environment. Assignment and management happen in the device view.

The space wizard now asks for the type of the space in its first step, because the type determines which of the following steps apply at all. General and Infrastructure are offered here — both hold locations, devices and scenarios.

An application space, which obtains its infrastructure from another space, is not shown in IoT Spaces and is not created here either; that happens in Users & Permissions. As a consequence, switching from an application space to IoT Spaces selects its infrastructure space.

Until now the place search only displayed the outline of a hit. While editing a GPS location it can now be taken over as that location’s boundary and reshaped straight away — no more tracing it by hand. See Location > GPS.

There is now a general device type for devices that rtlscloud does not manage. Such a device only reports its events and measurements and can be registered under an IoT gateway or an Edge without a device profile of its own. See Devices.

Floor plans are no longer limited to 8192 x 8192 pixels. Larger plans are processed on upload without being held in memory in full. See Locations.

The dialogs for editing location maps and the device placement step in the wizard were moved to the new map component. GPS locations have a dedicated editing dialog. See Location, in particular GPS.