Telldus Live keeps sensors and devices in separate collections. The Tools Telldus page displays both without treating switches or dimmers as temperature sensors.
Temperature sensors are synchronized into Tools' stored readings. The Telldus dashboard shows the most recent recorded temperature and history. Administrators configure monitoring thresholds and polling from Admin > Sensors.
The Devices section on the Telldus dashboard shows devices returned by the linked Telldus Live account and their latest reported state. Device states are cached briefly to reduce requests to Telldus; refreshing can retrieve newer information. Sensors are not included in the device list.
Only Tools administrators can send an explicit On or Off device command, and only when Telldus advertises support for that action. Commands use a CSRF-protected form, require the integration to be enabled, and are logged with an actor, device ID, outcome, and correlation reference. Device-command audit history remains available after an administrator's account is deleted. Past commands retain their recorded actor reference, action, outcome and time, with no account credentials in the log. The UI does not automatically turn devices on or off. Unsupported actions are not offered. A successful command response means Telldus accepted the command; the physical state may update afterward.
An administrator configures the shared Telldus API credentials at Admin > Telldus, without displaying stored secrets. Ordinary authenticated users can see data when the administrator has enabled the integration, but cannot edit the credentials or command devices.
The Test Connection action checks access to both Telldus collections. An upstream failure or rate limit may temporarily prevent a fresh device list; sensor readings already stored in Tools remain available.
Telldus API usage may depend on the account's Telldus subscription and current provider availability.