Smart Home

The KDT smart home (the Iridium family) is built from a central console, wall and desktop touch panels, and relay modules. From this one system you can control lighting, curtains, fan coil, ducted split and evaporative cooler thermostats, music on IP speakers, the door intercom and the Rhenium alarm panel. Scenarios, schedules and home modes such as presence, away and night are set up in the same place. Everything runs on your local network, and the KDT cloud web app adds control from outside the building.

Yes. Lighting, curtains, thermostats, scenarios and schedules, home modes, music, the door intercom, paging and the prayer-time announcements all run on your local network inside the console, so they carry on without internet as long as the building's own network (the switch and the router or access point) is powered. You can control everything from the wall console and from any phone or laptop on your Wi-Fi through the console's web page. Internet is needed only for features that reach outside the building: remote access with the KDT cloud app, phone notifications while the app is closed, internet radio, weather and automatic updates.

The console, either the KD-SC10-PW 10-inch wall unit or the KDT console software on a Windows or Linux PC, is the brain of the system: it runs scenarios, schedules, thermostats and home modes and serves the web interface. The 4-inch touch panels, the KD-CC04-R03 for the wall and the KD-CC04-D for the desk, are control points for lights, thermostat, music and modes. The relay modules KD-R004, KD-R008, KD-R016 and KD-R032, with 4, 8, 16 and 32 channels, do the actual switching of lights, curtain motors and fan coils in the electrical cabinet. The KD-CC04-R03 also has 3 built-in 10 A relays of its own.

Count 1 channel per lighting circuit, 2 per curtain motor (open and close) and up to 3 per fan coil (low, medium and high speed), plus 1 more if you also switch its water valve, then add about 20 percent for future changes. For example, 14 lighting circuits, 3 curtains and 3 fan coils (without valves) need 14 + 3 × 2 + 3 × 3 = 29 channels, and with 20 percent spare about 35. That is covered by one KD-R032 (32 channels) plus one KD-R004 (4 channels). Each module also has as many digital inputs as it has relay channels.

Yes. The KDT console software can also be installed on Windows and Linux computers, where it acts as the system's central console. The PC must run around the clock, so put it on a UPS, disable sleep mode and, on Windows, turn on automatic sign-in so that the console starts again by itself after a power cut. Functions that rely on the operating system or hardware, such as Bluetooth phone audio, may differ between a wall console and a PC. Other devices on the network keep using the console through its web page as before.

There are 3 ways: the touch screen of the wall console or a panel, the console's web page opened by its IP address from any browser on your Wi-Fi, and the KDT cloud web app for use from outside. No app store download is required, because the cloud app is a web app that you can add to your phone's home screen (on an iPhone: open the Share menu, then choose Add to Home Screen). The interface is available in Persian, English and Arabic. Each user sees only the pages and functions the administrator has allowed.

No. When "Enable cloud connection" is switched on in the console's Cloud settings, the console opens an outgoing encrypted connection to KDT's cloud service, and your phone reaches the console through that service. Nothing has to be opened on your router, so it also works when your internet provider gives you a changing or shared IP address. You sign in to the cloud app with your own account and see only the consoles linked to it.

The link between the console and the cloud is encrypted, and each cloud account can reach only the consoles linked to it. Signing in needs a password of at least 8 characters with letters and digits, or a 6-digit code sent by SMS to your mobile number, and repeated wrong attempts lock the account for a while. At home, the administrator gives each user a personal login, can hide pages such as Settings or the door opener, and the console screen can be locked with a 4 to 6 digit PIN. Set your own strong passwords at commissioning, keep the software updated, and switch the cloud connection off if you never use it.

The console keeps working locally, and the cloud app shows it as offline until the connection returns. When the internet is back, the console reconnects by itself and shows as online again without any action from you. Do not rely on commands sent while it shows offline, since they cannot be carried out. At home nothing changes, because the wall console and the local web page keep working.

In the administrator's user settings you create a user for each person, set a password (and a PIN if needed) and untick anything that person must not see or use. Permissions cover whole pages such as smart home, music, calls, alarm and settings, and items inside them such as a single thermostat, a custom home mode or the door-opener button. Everything is allowed by default, and hiding a page also hides everything inside it. The same rules apply to accounts that use the cloud app, and you can disable a user without deleting them.

Wire what you can: put the console and the relay modules on Ethernet, where one cable run may be up to 100 m, and power the KD-SC10-PW over PoE (the IEEE 802.3at standard, on a unit with the PoE option) or from its 12 V supply. The 4-inch panels, the KD-CC04-R03 and the KD-CC04-D, connect over 2.4 GHz Wi-Fi, so every panel location needs a good signal. Control messages are tiny, so Wi-Fi is fine for them, but a weak signal or a crowded channel is the most common reason a panel looks slow or offline. Aim for a signal of about -70 dBm or better at each panel, use channel 1, 6 or 11, and add an access point per floor where needed.

Use one reliable router or switch and keep the console, relay modules, panels and speakers in the same subnet. Give the console and other fixed devices fixed IP addresses or DHCP reservations, because after a power cut a router may hand out different addresses and break the links between devices. Traffic is light: control messages are tiny, a music stream needs about 192 kbps (typical) and a door-phone video stream typically 2 to 4 Mbps, so an ordinary 100 Mbps network is enough. Music is sent as multicast, so enable IGMP snooping on managed switches to keep it from flooding every port. If you put the smart home on its own VLAN or Wi-Fi network, phones that send audio by AirPlay or DLNA must be in the same subnet as the console.

Because panels connect over 2.4 GHz Wi-Fi, the cause is almost always the signal: coverage weaker than about -70 dBm, a crowded channel, or a router that changed its channel or the console's address. Check the signal at the panel with a phone, move or add an access point, fix the Wi-Fi channel to 1, 6 or 11, and reserve a fixed address for the console. After a power cut, start the router first and the console after it, because the panels join the system through the console. If only one panel is affected, restart that panel before changing anything else.

When power returns, the console, relay modules and panels restart by themselves and your settings, scenarios and users are kept on the console. During an outage nothing can be controlled unless the console, the network switch and the router are on a UPS; with one, local control and remote access carry on. Estimate the runtime as battery watt-hours × 0.7 ÷ load in watts: a 12 V 7 Ah battery holds 84 Wh, so a load of 32 W (console up to 12 W, switch and router about 10 W each, typical values) runs for roughly 84 × 0.7 ÷ 32 ≈ 1.8 hours. Which state each circuit takes when power returns depends on the module's own setting, so cut the power once during commissioning and check it, especially for heaters and pumps.

Not through the touch screen, the panels, the web page or the cloud app, because all of them work through the console; scenarios, schedules, home modes, thermostat control, music and the intercom also stop until it is back. The relay modules, however, keep their last state while powered, and they have an input-to-output link function (Input Mutual Control) that lets a push button or switch wired to a module's inputs switch its relays without the console, so set it up and test it at commissioning. For essential circuits such as a corridor light, also keep a manual way, such as a conventional switch or a breaker. On a site with several consoles, scenarios and thermostats run only on the main console, so its failure stops them too.

The relays switch lighting (LED and halogen), curtain motors and fan coil motors; the KD-CC04-R03 offers 10 A per channel, and for the KD-R004 to KD-R032 modules you should read the contact rating in the datasheet of that model. A rating like this normally refers to a resistive load: at 220 V, 10 A is 220 × 10 = 2200 W, provided the relay's voltage rating covers your supply. Motors, transformers and LED drivers draw several times their running current at switch-on, so load them to no more than about half of the rating, or use an intermediate contactor. Heavy loads such as heaters, pumps and compressors should be switched through a contactor rated for the load, with the relay driving only the contactor coil.

The KDT interface offers a brightness slider for dimmable lights and a colour picker for RGB lights, provided a compatible dimmer or RGB controller is part of the installation. The relay modules, that is the KD-R004 to KD-R032 and the built-in relays of the KD-CC04-R03 panel, only switch on and off, so do not put a relay in the supply of a dimmable lamp or a colour LED to try to dim it, because it will only switch it on and off. The colours you choose for groups and keys in the interface are a separate thing: they are only labels on the screen that make rooms and buttons easy to recognise. Before designing the installation, confirm the exact dimmer or RGB controller model with KDT support.

In many cases yes. A KD-CC04-R03 wall panel is powered from the mains (110 to 220 V), connects by Wi-Fi so it needs no data cable, and switches up to 3 circuits of 10 A each, so it can take the place of a conventional switch in a box that has phase and neutral. Add the KD-SC10-PW console and make sure the Wi-Fi signal reaches every panel location. Circuits that have no suitable box, or more than 3 per location, are better served by relay modules in the electrical cabinet. Check the wiring at each position before you order panels.

A group usually stands for a room or a wall panel, and it holds keys, the buttons that switch relay outputs; each group and key has its own name and colour. A virtual key is a key with no wire of its own: pressing it runs several real keys or commands together, so you can build keys such as "all lights off". Groups and keys look the same on the console, in its web page and in the cloud app. Organise groups by room or floor so that the names make sense to every user.

Each curtain uses 2 relay channels, one for opening and one for closing, and you enter the motor's full travel time in each direction (for example 12 seconds). The console switches the opposite direction off before it energises the chosen one, then turns the relay off when the travel time ends, and you can stop the curtain at any moment; several curtains can also move together as a group. A half position is available too: the console closes the curtain fully and then opens it for the configured half time, because position is worked out from running time, not from a position sensor. Use motors with built-in limit switches, and run a full open or close now and then if a curtain was moved by hand or by a wall switch and its position seems off.

It controls fan coil units, ducted split systems and evaporative (water) coolers through relays, using a temperature sensor on the network, with cooling, heating, fan-only and, where the unit allows it, automatic modes. The control loop runs on the console with, by default, a 0.5 °C hysteresis and a setpoint range of 16 to 40 °C. Protections are built in: a compressor waits about 5 minutes before restarting, an evaporative pump wets the pads for about 2 minutes before the fan starts, and if the sensor stops reporting for about 2 minutes the thermostat's relays are switched off. Thermostat settings can also be part of home modes and weekly schedules.

Mount it on an interior wall, typically 1.2 to 1.5 m above the floor, in the area where people actually spend time, away from direct sun, supply air from the air conditioner, kitchens, radiators and exterior doors. A sensor next to a heat source or in the airflow reads too high or too low, so the equipment cycles too often or never reaches the setpoint. Use 1 sensor for each thermostat. Compare its reading with a reference thermometer once and correct the difference in the thermostat's calibration setting if it is more than about 0.5 °C.

There are 4 kinds. Weekly schedules switch a relay on and off at set times on chosen weekdays, including windows that run past midnight, and timed schedules switch it on at a set time for a set number of minutes. Sensor scenarios switch a relay when a reading such as temperature, humidity or CO2 crosses a threshold, or between two thresholds to avoid chattering, and relay-to-relay scenarios switch one output when another changes, optionally for a fixed time. Because they all run on the console they work without internet, and each can be enabled or disabled separately.

A weekly schedule keeps enforcing its own window: by default its "Refresh interval" checks the relay and corrects it every 60 seconds, so a light you turn off inside the on-window comes back on, and one you turn on outside the window goes off again. To change this, set the schedule's Refresh interval to Disabled so that it acts only at the on and off times, or set "Outside time duration" so that a light you switched on by hand stays on for the time you choose, from 10 seconds up to 24 hours. Sensor scenarios refresh too: while their condition is true they re-apply the output every 30 seconds by default. Also check that no other scenario or home mode switches the same output.

A home mode is a scene you apply with one tap from the console, a panel or the app. The system has 3 built-in modes, presence, away and night, which cannot be deleted, and at most 10 modes in total, so you can add up to 7 custom modes such as guests or cinema. Each mode can switch chosen relays on or off, open, close or half-open curtains, set thermostats, and start or stop music on selected speakers. The limit of 10 modes applies to the whole system, and a 4-inch panel shows the first 9 modes on its screen.

A home mode is a scene you start yourself: one tap applies a fixed set of actions across relays, curtains, thermostats and music, for example when you leave home or go to bed. A scenario is an automatic rule that runs by itself, at set times or when a sensor reading or a relay changes. Applying a mode does not lock anything and does not undo the previous mode; afterwards you can still change any light or thermostat. Use modes for moments you decide and scenarios for things that should happen without you.

Yes. New relay modules, panels and sensors that join the network announce themselves to the console and show up in its list of discovered devices by serial number, and you then assign their channels to groups, keys, curtains or thermostats without changing what already works. Leave about 20 percent of relay channels free when you choose modules, and leave spare network points and space in the electrical cabinet. Several modules work together in one system, for example a KD-R032 next to a KD-R016.

Yes. Every speaker or speaker group can play its own source: start a separate player for each room, pick its playlist or track, and set the volume of each speaker, while a master volume controls them all. A speaker plays one source at a time, and a new source replaces the previous one on that speaker. You can upload files in common formats such as MP3, WAV, AAC, OGG and FLAC, a playlist holds up to 50 tracks, and each music stream uses about 192 kbps of network capacity.

Yes. On a Linux console such as the KD-SC10-PW there are 4 ways: Bluetooth (Android phones and iPhones pair with the console like a speaker), AirPlay (iPhone, iPad and Mac), DLNA (Android apps that can cast to a DLNA renderer, after you start the DLNA receiver on the console) and browser casting from a secure page in any modern browser. AirPlay and DLNA need the phone and the console on the same subnet. Bluetooth and browser casting typically add well under half a second of delay and AirPlay about 2 seconds, so they suit music better than video. Google Cast, the Chromecast list on Android, is not supported.

The console calculates the 5 daily prayer times itself from your city's coordinates and the calculation method you choose, for example the Tehran method or Jafari, so it needs no internet. For each prayer you can turn the azan on or off and choose the speaker or speaker group, the volume and the muezzin recording. The azan takes priority over music on those speakers and stops what is playing there. Set the city, method, date, time and time zone correctly, because a wrong location or clock shifts every time.

Authorities use different sun angles below the horizon for dawn and nightfall, so calculation methods can differ by a few minutes; the Tehran method, for example, uses 17.7° for Fajr and 14° for Isha. In the azan settings check the calculation method first, then the city's latitude and longitude, then the console's date, time and time zone. A wrong city or a wrong clock, for example when the console's clock has drifted on a site without internet, moves all 5 times together. To match a specific authority, choose the method that authority uses.

Yes, with a SIP video door station. When the station calls, the console rings, shows the door camera image, lets you talk, and opens the door from its Open Door button; depending on the station, the door is released by a DTMF tone during the call or by an HTTP command. The console can also call the station directly by IP address, so no SIP server is required. For live video the camera should send H.264, because H.265 cannot be played live in a browser and the console then falls back to still snapshots. You can hide the door-opener button from users who should not have it.

Yes. Extra consoles, for example one per floor, join the same system, show and control the same devices, and each can be used for music, paging and answering the door. One console is set as the main (server) console and runs the shared tasks such as scenarios, schedules, thermostat control and time and weather updates, while the others act as clients so that commands are not repeated. To ring every console for the door, enter each console's IP address in the door station: each one rings independently and the others stop ringing when one answers. A cloud account can also be linked to several consoles, and you pick one after signing in.

Yes. The console, the touch panels and the cloud app can arm, disarm or stay-arm (Stay) an alarm area and show its status. Arming and disarming need the user's PIN, which the alarm panel itself checks exactly as at its keypad, so the console never decides who is allowed. Notifications can tell you about alarm triggers, tamper (Tamper), arming and disarming, mains power loss and low sensor batteries. Home modes do not arm the alarm, so use the alarm page or the panel for that (the alarm itself is covered under burglar alarms).

The console can notify you about group and key changes, thermostat and curtain activity, scenarios and home modes, air-sensor alarms, alarm-panel events, the doorbell and system connect or disconnect, and each category can be switched on or off in Settings. Inside your home network you get in-app banners without internet. Phone notifications while the app is closed travel through the phone maker's push service, so they need internet on the phone and the cloud connection on the console. Enable only the categories you need to avoid a flood of messages.

Switch on "Automatic cloud update" in the console's Cloud settings and the console checks KDT's update server by itself and downloads only the files that changed, so updates are small; each file is verified with a checksum before it is applied. The application restarts once when an update is installed, and your settings, users and scenarios are kept. You can also check and apply an update yourself in Settings under Maintenance. On a site without internet, an update package can be applied manually from the same place.

Yes. The relay modules speak MQTT, Modbus (RTU, TCP, UDP and ASCII), HTTP GET, CoAP, TCP and UDP, have RS485 and CAN interfaces, and work with platforms such as Home Assistant, openHAB, Domoticz and Node-RED; for a PLC, Modbus is the usual link. List the exact models involved before you plan an integration, because supported functions depend on the model. If one relay is commanded both by console scenarios and by another system, decide which system owns each output so that their commands do not conflict.

The DC supply of the KD-SC10-PW console is 12 V 1 A, so at most 12 W, and the relay modules KD-R004, KD-R008, KD-R016 and KD-R032 are rated at 3, 5, 9 and 16 W. For example a console (12 W), one KD-R032 (16 W) and one KD-R004 (3 W) add up to 31 W, and 31 W × 24 h × 365 days = 271.6 kWh per year. The panels and the network equipment add to this, and a UPS has losses of its own. These are rated maximums, so real consumption is normally somewhat lower.

Yes. The console automatically backs up its settings, such as groups, keys, curtains and scenarios, every day and keeps about the last 30 days on itself; when the cloud connection is on, the latest 7 copies are also stored on KDT's cloud server. In Settings under Maintenance you can make a backup at any moment or restore one of the copies, and it is best to restart the application after a restore. If the console's own storage fails, the local backups are lost with it, so keep the cloud connection on for that case. A backup contains settings only, not your music and azan files.