iPhone and iPad
Download from Apple
Get the Home Ecosystems app for iPhone or iPad.
Getting Started
Follow a clear path from first setup to your first connected device, automation and natural daily pattern.
Illustrative ecosystem concept
Home Ecosystems app
The same app account can be used across supported platforms. Core controller setup and local automation do not require a paid subscription.
Choose your controller
Mini and Controller are available now. Controller Pro is in development, so its product story is available while production setup guidance is still being prepared.
Set up the compact controller and connect qualified Wi-Fi and Bluetooth equipment.
Start Mini setupSet up the controller, connect smart equipment and configure its eight onboard 24 V channels.
Start Controller setupExplore the planned platform for larger installations and multiple ecosystems.
Explore Controller ProFirst setup
Work in small steps. Confirm each connection and output before adding more devices or leaving an automation unattended.
Find the model, revision, power requirements and details to keep close during onboarding.
Get the live app for iPhone, Android or Windows and prepare your account.
Start with the correct supply and find your controller from the app.
Choose the intended local network and confirm the controller is reachable.
Check the exact model, add one compatible device and confirm its reading or output.
Check live readings and manual control before relying on automation.
After first setup
Start with a single safe action. Then shape the environment through the day, connect a relevant weather location and add limits and alerts.
Get Started video series
Follow the tutorials in order, or open the written instructions for the task you need. Start locally; cloud setup is a separate choice.
Install the app, create an optional account, confirm your email and sign in.
Read the cloud service terms and check acceptance before controller cloud linking.
Add the eight-channel Smart Controller, configure a lighting channel and create a timed automation.
Review device access and controller Wi-Fi credentials, then reconnect after a password change.
Review manual override behaviour, network and remote permissions, cloud linking, backups and firmware checks.
Learn Home Ecosystems
Choose a task, follow a guide where available, then return as your ecosystem grows. Guides still in preparation are clearly marked.
Follow the first setup sequence for a compact, smart-device ecosystem.
Prepare the Controller and its direct 24 V outputs before adding equipment.
Choose the intended local network and confirm the controller is reachable.
Learn how local discovery and controller network access fit into setup.
Find release information and prepare a safe update with your configuration preserved.
Check the exact sensor and confirm a fresh reading after connection.
Use exact-model compatibility and verify LAN binding and control.
Match a suitable supply and load, then verify one direct output safely.
Choose the correct output profile before assigning lighting channels.
Understand its four separate outlets and one Wi-Fi device connection.
Read model, functions, limits and status before choosing equipment.
Start with one measured condition and one safe output action.
Bring several compatible actions together for one moment or mode.
Define gradual changes in light or environmental targets over a day.
Use compatible dimming equipment to shape a smooth lighting curve.
Combine a qualified reading, a suitable load and safe limits.
Use a humidity reading and suitable misting equipment with safeguards.
Choose a place relevant to your ecosystem and check the incoming data.
Let day length and environmental targets vary gradually across the year.
Use weather context alongside your configured environmental curves.
Set a sensible boundary around sensor-driven control.
Prevent a pump, heater or other load from running longer than intended.
Choose useful notifications and verify how you will receive them.
Check triggers, output response and failure behavior before unattended use.
Understand the difference between local automation and remote services.
Get Started manual
Read one chapter at a time. Each guide includes prerequisites, the setup steps, the expected result and help when a step needs attention.
Install the app, create an optional account, confirm your email and sign in.
Install the Home Ecosystems app, create an optional account, confirm your email address and sign in. Local controller setup and control are available without signing in. An account is used for account-linked features and services.
You need a Windows, iOS or Android device, an internet connection to download the app and register, and an email address whose inbox you can access. If you already have a Home Ecosystems account, use Log in rather than creating another account.
Download Home Ecosystems from the store for your device:
Install the app and open Home Ecosystems. Use the official download links in the Getting Started guide at https://home-ecosystems.com/pages/getting-started.
Select Account in the app's navigation. The page explains that an account is optional for local control. Select Create to show the account creation form.
Complete each field:
Select Create account. If the app identifies an incomplete or invalid field, correct it before submitting again.
Open the confirmation email sent to the address you entered and follow its confirmation link. After confirming the address, return to the Home Ecosystems app.
On the Account page, select Log in. Enter the email address and password for the account you created, then select Log in.
After your email is confirmed and you have successfully signed in, your account is ready for account-linked features. Controller onboarding and automation setup are separate tasks.
No confirmation email: check your spam or junk folder and verify the email address you entered. If the message still does not arrive, contact Home Ecosystems support at support@home-ecosystems.com.
Passwords do not match: enter the same password in Password and Confirm password, using at least eight characters.
You cannot sign in: confirm your email address first and check the email and password you are using. If you have forgotten the password, use Reset password on the login form and follow the instructions provided.
You do not want to create an account: continue using local controller features without signing in. Account-linked services may require a confirmed account and sign-in.
Further help: https://home-ecosystems.com/pages/getting-started
Welcome to Home Ecosystems. Let's get started.
In this video, we'll cover app setup, account creation, and email confirmation.
Start by downloading the Home Ecosystems app. Use the Microsoft Store for Windows, the Apple App Store for iOS, or Google Play for Android.
Open the app and select Account.
An account is optional for local controller setup and control. Create one when you want to use account-linked features.
Select Create to begin.
Enter your display name and email address. Choose a password of at least eight characters, then repeat it in Confirm password.
Check your details, then select Create account.
Follow the link in your confirmation email. Then return to the app.
Select Log in and enter your account details.
Thank you for watching. Confirm your email, then sign in.
The audio is in English. Use the timed caption file for your language.
Read the cloud service terms and check acceptance before controller cloud linking.
Review acceptance of the cloud service terms before continuing with account-linked controller features.
Sign in to the intended Home Ecosystems account. Acceptance of cloud terms and controller cloud linking are separate steps. Local control remains independent of the cloud service terms.
The terms section should show acceptance for the applicable published version. That status does not by itself confirm that a particular controller is linked to the cloud.
No accepted status: confirm you are signed in to the intended account and review the available terms and acceptance instructions.
Already accepted: review the status rather than assuming you must repeat acceptance. The demonstration account already shows accepted terms.
Cloud feature still unavailable: review the controller's cloud-link and connection status and the account's available services separately.
Welcome to Home Ecosystems. Let’s get started.
In this video, find the cloud service terms and check your acceptance status.
After signing in, open Account. Scroll down to Cloud service terms.
Expand the section and read the terms. This account already shows acceptance for the current published version.
Cloud terms apply to account-linked services. Local control remains independent. Check acceptance before linking the controller.
Thank you for watching. Check acceptance before linking your controller to the cloud.
The audio is in English. Use the timed caption file for your language.
Add the eight-channel Smart Controller, configure a lighting channel and create a timed automation.
Add an eight-channel Smart Controller to the app, configure an internal lighting channel, and create a timed scene. Controller Mini and other models may show different channel options.
Have the Home Ecosystems app ready and the controller powered and nearby. Keep the device password you choose available for later access. If you intend to add home Wi-Fi, have the network name and password ready. Use an appropriate lighting device already connected to the intended output; this guide covers app configuration, not electrical installation.
Home Wi-Fi is optional during onboarding. For direct local access without it, connect the phone or computer to the controller's own wireless network using its actual network details. The device password and controller Wi-Fi password are separate credentials. Review Controller security to protect the controller's wireless network.
The demonstration uses approximately 70% output, a 09:00-21:00 time window, and 30-minute ramps. Treat these as examples, not recommended settings for all lights, plants, or animals. Select values appropriate to the ecosystem and connected equipment.
A configured channel should appear in the channel overview, and the saved scene should be available in Automation. A local connection does not by itself confirm cloud linking or complete security setup.
Changing a channel to manual control interrupts automation that depends on it. Read the warning identifying the affected channel. Review the return policy under Controller settings > Manual control override. Restore Auto when you finish testing and confirm the channel and scene state.
Controller not found: check that it is powered and nearby, and that the app can use Bluetooth for the scan.
Controller not reachable after setup: check the connection result and network details. Use the controller's own network for direct local access when appropriate.
Channel not yet visible: allow the app to refresh, confirm the channel configuration was saved, and check local connectivity.
Scene interrupted: check whether an actuator channel is in manual mode. Review its return-to-Auto policy and restore Auto when appropriate.
Welcome to Home Ecosystems. Let’s get started.
In this video, add a controller, configure a lighting channel, and create an automation.
Open Home to see your controllers. A new installation may have an empty list. Scroll to Add a new controller and start the onboarding process. Keep the controller powered and nearby.
The app scans for nearby controllers using Bluetooth. Wait for the device to appear, then check that you have selected the controller you intend to set up. The detected device in this example is the eight-channel Smart Controller.
Select the controller and start onboarding. The app connects to it before showing the setup form. This guide uses the standard Smart Controller with internal output channels; other controller models may show different configuration options.
Give the controller a recognisable name. Use something that identifies the ecosystem or installation it belongs to, especially if you manage several devices. You can review the name later in Controller settings.
Enter a Device password, then enter the same value in Confirm device password. This protects access to the controller. Keep the credential private and available for future connections. The password entry is hidden in the demonstration.
Home Wi-Fi is optional during onboarding. If you want to add it now, enter your network name or use Scan Wi-Fi to find a network. Use the connection details for the network where this controller will operate.
Enter the Home Wi-Fi password. Remember this Wi-Fi for next time is optional. Then choose Finish setup.
The app sends the configuration to the controller over Bluetooth and waits for it to become reachable. Keep the controller powered while this completes. Adding home Wi-Fi and establishing a local connection are distinct steps.
If you chose not to add home Wi-Fi, connect your phone or computer to the controller's own wireless network for direct local access. Use the actual network name shown for your controller. The controller Wi-Fi can be secured separately in Controller security. Do not assume that the device password also secures this wireless network.
In this example, the setup confirmation says the controller joined home Wi-Fi and will reconnect automatically. Return to Home and find the new controller. Connected locally confirms local reachability. Security incomplete indicates that further configuration tasks remain; it does not mean the controller has failed to onboard.
Open the controller's Overview. It contains the general status and ecosystem information, plus Channels and Sensors views. The channels view will show the outputs you configure, including their operating mode and available controls.
Automation is where you manage scenes. Configuration is where you set up the controller, its devices, and the ecosystem. Keeping these areas separate helps you distinguish daily operation from changes to the underlying setup.
The Configuration page groups Device settings, Channels and devices, and Ecosystems and automation. Device settings includes security, controller settings, device time, firmware update, and alerts. Review the configuration checklist to see which setup tasks remain.
Internal channels configures the Smart Controller's own outputs. External devices is for compatible separate actuators and sensors. Available controls depend on your controller model. For this demonstration, we will use an internal channel and configure it as a dimmable light.
Before creating a scene, configure the channel it will control. A channel name helps you select the correct output later. Its type identifies how it is used, and its mode determines whether it follows automation or stays under manual control. We will keep this lighting channel in Auto.
Open Internal channels and choose Channel one. Enter a useful name, such as Light. Set the Type to Light so the output is clearly identified when you select it in a scene.
Keep Mode set to Auto. For the dimmable lighting setup shown here, use the PWM option. This allows the scene to request an output level instead of only switching the channel on or off.
Review the Output range. This example uses zero to one hundred percent. Choose values for your setup, then select Save.
Return to Overview and open Channels. Allow the app to refresh and show the configured channel. Next, open Automation to create its scene.
Add a new scene and name it Light. Choose the lighting scene type. The scene uses the channel configuration you saved, so a clear channel name and type make the selection easier.
Select Channel one, Light, as the scene’s actuator. It is dimmable. This example uses one channel; select additional compatible channels only when they should behave together.
Review Automation mode. Always on keeps an output active. Time lets you specify a start and end. Select Time for this lighting schedule, then review the ramp settings.
The time window defines when the scene applies. Ramps make lighting rise and fall gradually. Choose times and levels appropriate to your ecosystem.
Interval mode suits devices that run periodically, such as a misting or rain system. It combines an interval and an on duration with a time window. Choose values for the device and ecosystem; they are not a universal lighting recipe.
Other available modes use targets, a weather-station profile, or a daily cycle. Those modes need the corresponding ecosystem configuration. They are shown here as alternatives, but this tutorial will finish with a simple timed lighting scene.
Return to the timed scene. Set the ramp-up and ramp-down durations for gradual lighting transitions. This example uses thirty minutes for both.
Set the light’s output level. This example uses approximately seventy percent. The appropriate level depends on the light, its position, and the ecosystem’s needs.
Check the start and end times: nine in the morning to nine in the evening here. Review applicable safety limits, then choose Save.
Return to Overview and open Channels. Light appears with its Auto setting and output control. You can review it or make a temporary manual adjustment.
Manual control interrupts the automation that depends on this channel. The app warns which channel is affected. A temporary manual adjustment differs from changing the scene’s normal schedule.
Review the manual return policy in Controller settings. It determines when a temporary change returns to automation. Restore Auto after testing and check the scene and channel state. You now have the basic channel and scene setup workflow.
Thank you for watching. Check your lighting schedule and restore automatic control.
The audio is in English. Use the timed caption file for your language.
Review device access and controller Wi-Fi credentials, then reconnect after a password change.
Review controller protection, set the appropriate credentials, and restore connectivity after a controller Wi-Fi password change.
The controller must already be onboarded and locally reachable. Keep its existing device-access and network credentials available. Identify devices that connect directly to the controller's own Wi-Fi before changing that network's password.
The device password protects access to the controller. The Controller Wi-Fi password protects joining the controller's own wireless network. These are separate from your home router's Wi-Fi password and from your Home Ecosystems account password.
The security settings should reflect the changes you intentionally saved. Confirm both the protection status and a working local connection. A saved form alone does not prove that all connected devices have rejoined the network.
Controller did not answer in time: check power and that the phone or computer can reach the controller on the appropriate network. Reconnect using the updated Wi-Fi password, then reopen the controller and retry.
Directly connected device stops responding: update that device's controller-network credentials. It does not automatically learn the new password.
Uncertain which password changed: distinguish account sign-in, device access, controller Wi-Fi, and home Wi-Fi. Review the corresponding settings rather than changing all credentials at once.
Welcome to Home Ecosystems. Let’s get started.
In this video, protect your controller, secure its Wi-Fi, and reconnect after changes.
After onboarding, open Configuration and expand Configuration progress. This checklist shows the remaining setup tasks, so you can see what is ready and what needs attention.
The example has a channel and an automation. Other tasks include security, devices, and the ecosystem profile. This tutorial focuses on protection.
Open Controller security. The device password protects controller access. The controller also has its own Wi-Fi network. Compatible devices can join it directly, without relying on your home router.
Local automation runs on the controller. Suitable directly connected devices reduce dependence on the home network. Cloud features still need their own connection. Protect the controller’s Wi-Fi separately from the device password.
There are two separate credentials: the device password, and the Controller Wi-Fi password. Protecting one does not automatically protect the other. Review the status before making changes.
To set device access, enter a New device password and repeat it in Confirm new device password. Use matching entries. If you are keeping an already configured device password, leave the replacement fields empty.
The device password is entered and confirmed here. Next, enter a Controller Wi-Fi password. Devices joining the controller’s own wireless network will need this separate credential.
Show passwords reveals the entries. Keep it off when sharing your screen. When you are ready, choose Save security settings.
Read the confirmation. Changing the controller Wi-Fi password can disconnect the app and connected devices. They do not automatically learn the new password.
Reconnect devices that use the controller’s Wi-Fi with the new password. Some may need configuration again. Check the requirements of each directly connected device.
After confirmation, the form returns to the security page. Keep the new credentials available and check reconnection.
Return to Configuration and open Controller settings. The app may temporarily lose contact during the change. Wait until the controller is reachable before continuing.
Here, the controller did not answer in time. Check its power and the Wi-Fi connection. Reconnect with the updated password, then reopen the controller and retry. This clip does not show a successful reconnection.
Thank you for watching. Reconnect, then check that your controller responds.
The audio is in English. Use the timed caption file for your language.
Review manual override behaviour, network and remote permissions, cloud linking, backups and firmware checks.
Review the controller's identity, manual return policy, network and remote permissions, cloud-link status, backup controls, and firmware-update availability.
The controller should be onboarded, secured as appropriate, and locally reachable. For account-linked cloud features, sign in to the intended account and review the applicable cloud service terms. Keep network credentials private. Available services depend on the controller, app, account, and connection status.
Enabling a permission does not, by itself, establish a cloud link or prove that a service is available to the account. Confirm the account services and actual controller status separately.
Use Backup and restore to locate Export backup and Restore backup. Keep a local copy before major configuration or firmware changes. Reset options and the controls for forgetting a device are separate actions; they are not ordinary connection checks. Review the action and its effect before proceeding.
Finding an update, saving it in the app, and installing it are separate stages. This guide covers the availability check; it does not provide a firmware installation procedure.
The intended settings should be saved, the controller should remain reachable, and the cloud-link status should accurately reflect whether account-linked services are ready.
Pending cloud link: keep the connection available, allow processing time, and recheck the status. Do not assume a button press proves completion.
Firmware check blocked by linking: verify the cloud link and retry when the status is ready.
Unexpected manual channel behaviour: review Return to Auto after and the channel's current Auto/manual state.
Connection problem: verify power, network reachability, and the correct credentials before changing unrelated settings or using reset controls.
Welcome to Home Ecosystems. Let’s get started.
In this video, review overrides, connection permissions, cloud linking, backups, and firmware checks.
After reconnecting and reopening the app, the controller is accessible again. Return to Configuration. The checklist now reflects the security settings from the previous tutorial.
This example shows three of six tasks complete. Open Controller settings to review device behaviour, network connections, and permissions for account-linked services.
Identity lets you review or change the name set during onboarding. Choose a name that makes the controller easy to recognise in the app.
Expand Manual control override. This determines when a channel changed by hand returns to scene or program automation. Open Return to Auto after to see the durations, including the recommended thirty minutes.
Until switched back manually keeps the channel in manual control until you restore Auto yourself. A timed return helps a temporary adjustment avoid becoming a permanent interruption to the schedule.
Keep the recommended thirty-minute return here. Choose a duration that suits your ecosystem.
Expand Controller Wi-Fi. This is the controller’s own network for onboarding, recovery, and compatible direct connections. Its network name and password are hidden for privacy.
Home Wi-Fi profiles are separate. They hold the home network details used for normal network access and internet-backed functions. Review the enabled profile. Its private credentials are hidden here too.
API security concerns the local device token used by the app. Keep device access, controller Wi-Fi, and home Wi-Fi credentials separate.
Open Cloud and remote permissions. Enabling a permission does not prove the controller is linked or that a service is available to your account.
Allow Wi-Fi network access permits connection to configured home networks. Consider which functions need that connection before disabling it. Local operation and cloud connectivity are different parts of the setup.
Allow global time sync permits internet-based clock synchronisation. Accurate time matters for schedules and history timestamps. Review this permission together with the network connection needed for synchronisation.
Allow remote monitoring concerns viewing sensor and channel status remotely. Allow remote control concerns requesting output changes. Choose the permissions appropriate to your installation and available account services.
As the page explains, remote control also requires remote monitoring. Check both if you intend to use remote control. Then review Cloud link and local record to see whether the controller is linked to your account.
The status reads Not linked, with the claim pending. Choose Link to cloud now to request linking, and keep the controller connected.
The request can take time. This clip still shows a pending state, so completion is not demonstrated. Return to the status and verify the link before relying on remote services.
Backup and restore provides Export backup and Restore backup. Keep a local copy before major changes. Reset options are separate; do not use them simply to check a connection or a pending cloud link.
Choose Save settings for changes you intend to keep, then return to Configuration. Check the controller status before continuing.
Open Firmware update. The page separates installed firmware, the latest available update, and saved updates. Check for updates looks for a release through the app’s available update connection.
Update needs attention says this device is not linked to the cloud, so releases cannot be checked. Complete and verify linking, then retry. No firmware update is installed in this demonstration.
Return to Configuration after reviewing the settings. The next area is the ecosystem profile: weather-station settings or a user-set daily cycle. Those profiles are a separate task.
Thank you for watching. Verify your connection and cloud status before continuing.
The audio is in English. Use the timed caption file for your language.
Practical guides
These guides cover the current Mini and Controller onboarding flow. Check the exact product and device requirements before connecting any load.
Troubleshooting
Keep the phone close, enable Bluetooth and Local Network access, and confirm that no VPN or guest-network isolation is blocking local discovery. Wait a little longer after the controller starts before scanning again.
Confirm the phone and controller can reach the same local network. Give the controller time to reconnect after Wi-Fi or password changes, then retry once. Avoid repeated rapid taps while a request is still completing.
Re-enter the current device password in the controller connection prompt. Changing the controller password invalidates the old saved credential on other phones and computers.
Check the exact model and supported feature list. A device being visible on Bluetooth, Wi-Fi or the controller access point does not automatically mean every function is supported.
Do not erase or factory-reset a configured controller as the first recovery step. Record its model and symptoms, preserve a configuration backup where available, and contact support for the safest next action.
Important safety information
Help and product information
Use the model and hardware revision from the product label when contacting support.
Company and legal information
REA: CO - 434793
VAT / Partita IVA: 04302350139
Codice Fiscale: 04302350139
General and legal contact:
info@home-ecosystems.com
Telephone: +41 79 742 65 73
Product and app support: support@home-ecosystems.com
The product type, model, hardware revision and unique identifier are shown on the product or accompanying label. Retain that information and your proof of purchase.
Regulatory markings, declarations, instructions and disposal information apply to the exact model and market. Refer to the product label and the model-specific documents supplied with your product. Electrical and electronic equipment must not be discarded as unsorted household waste.