Place devices and configure controls
Device placement answers where a device is located. A control defines what can be operated for a unit. Configure these separately.
Before you start
Your provider is connected, devices have been imported and you can manage the location. A control also needs an active unit and a suitable supported device function.
Place a device
- Open the location and its device view.
- Find the device under Unplaced or mobile. Open its three-dot menu and choose Place device.
- Assign it to the location, an area or a room and confirm.
- Check its current placement.
A room name reported by the provider is only a suggestion. It does not automatically create your octopancy structure. You can change or clear placement; an unplaced device remains identifiable.
Configure a unit's control
- Open Units at the location and select the unit.
- Use its actions to create a control with a clear name and the required function.
- Open the control's technical assignment and choose a compatible device function.
- Save and check assignment status. Activation and assignment are separate states; a name alone does not make a control operational.
Holiday rentals: A heating control belongs to the Villa Aurora unit. Coworking: The control for A101 belongs to the A101 room unit.
Before changing an assignment
A new assignment can send future commands to a different device. Review the displayed effects on reservations, access and pending executions before confirming.
Not every function available from a provider is supported by octopancy. Use the compatible functions actually offered.
Next: Room comfort and personal access.
Check state in Controls
Open Locations, select the location and its Controls tab. Devices appear immediately, with Checking state … while the check runs. Nuki state is retrieved when opening the page and when its live connection is restored. Provider reports shows the response and retrieval time. Nuki does not supply a measurement time; this is not a guarantee of the current physical state. Unlocked does not mean the door is open.
If the state cannot be checked, Current state unknown appears. Any previous report remains visible below it with its timestamp. Homematic target temperatures are checked when opening or reconnecting; subsequent changes arrive through provider reports. An accepted command does not confirm its physical execution.
When Nuki callbacks are configured, incoming state and action reports also trigger a state check. The open page receives the reconciled state automatically through its live connection.
Lock or unlock Nuki
The button follows the reconciled state: Locked offers Unlock, while Unlocked or Unlatched offers Lock. During checking, movement or an unknown state, Control lock remains disabled. A disconnected live connection or an effective personal access also disables control.
Clicking sends exactly the displayed action. A later state update does not change that command. Command accepted only confirms provider acceptance; check the subsequent report and inspect the physical lock if uncertain. Commands with an uncertain outcome are never automatically repeated.
Set the temperature
Open the desired Location, select its Controls tab and choose the target temperature using the slider or the plus/minus buttons in 0.5 °C steps. The last reported target temperature is used as the starting value when available. The state display still distinguishes a reconciled report from a historical one. After releasing the slider or the last plus/minus click, the temperature is applied automatically after 800 milliseconds without further changes. Rapid changes are combined into one command with the final value. Leaving the page or losing the connection cancels any change still waiting to be sent. New state reports do not overwrite your selection. The chooser remains disabled when the connection is interrupted or control is blocked.
When Controls opens or reconnects, the room target temperature reported by Homematic is retrieved again. During the initial check, cached values are not presented as current state. Subsequent changes arrive through device reports. If the check fails, the last reported value remains identifiable as historical state.