&cacheSeconds=15600&url=https://analytics.home-assistant.io/custom_integrations.json&query=$.wiser_by_feller.total){kind=icon}
Use your Wiser by Feller smart light switches, cover controls and scene buttons in Home Assistant. Note that this is an unofficial integration that is not affiliated with Feller AG. All brand and product names are courtesy of Feller AG.
Important
This integration implements Wiser by Feller and not Wiser by Schneider Electric, which is a competing Smart Home platform (and is not compatible). It es even more confusing, as Feller (the company) is a local subsidiary of Schneider Electric, catering only to the Swiss market.
Warning
This integration is not yet feature complete and still under active development. See below for supported features and roadmap.
Click the button above or perform the following steps:
- Ensure HACS is installed.
- Navigate to HACS on your Home Assistant
- Search for "Wiser by Feller"
- Click "Download" in the bottom right corner and follow the instructions.
Copy the directory custom_components/wiser_by_feller into your custom_components directory.
If it does not exist yet, you can create it in the home assistant installation directory.
Warning
Please make sure your Wiser setup has been fully configured by your electrition before adding it to Home Assistant. Otherwise naming and categorizing all the devices can be very time consuming and confusing.
Home Assistant should ✨automagically✨ discover your µGateway and suggest to set it up. If not, you can follow these steps to connect manually:
- Go to Settings → Devices & services and click "Add Integration".
- Search for Wiser by Feller
- Enter the IP address of your µGateway.
Important: If you have multiple home assistant installations or other applications that connect to your µGateway, make sure to use a unique username (e.g.homeassistantandha-testbench) for each installation. Connecting with the same username on a second installation leads to the first one being de-authorized. - Fill in the username you would like home assistant to claim with the Gateway.
- The buttons on your µGateway should start flashing purple and pink. Press one of them within 30 seconds
Tip
In the moment you connect your gateway, all your settings (room and device names, scenes, etc.) are copied over from the user you pick (for a normal install that's either the installer (installer, via Wiser eSetup app) or the end user (admin, via Wiser Home app).
If you add more scenes with the Wiser eSetup or Wiser Home app, you need to reconnect the user (Note: This is currently under development).
By default, the setup fails, if fields like fw_version or serial_nr are missing for devices in the API response. Enable this option for debug purposes to disable the check. See this Wiser API GitHub issue for more details.
Caution
Use with caution, this can affect entity IDs and functionality! You should always check the actual API output manually before checking this checkbox.
Wiser by Feller devices always consist of two parts: The control front and the base module. There are switching base modules (for light switches and cover controllers) and non-switching base modules (for scene buttons and secondary controls).
Learn more about Wiser devices on the official website and API documentation.
Here's what the integration currently supports:
After you've installed the integration, Home Assistant will autodetect your µGateway and suggest installing it. Based on your network it might be possible that you have to manually enter its hostname or IP address.
You can also give your installation a unique username and select from which user you want to copy scenes and settings from. Room assignments are automatically suggested on setup, as long as their names match between Home Assistant and Wiser.
Your Wiser setup will integrate into Home Assistant as devices and entities. What Wiser calls a load (e.g. a light or an awning) will be represented as a device. This means that light switches with two loads will be represented as two separate devices.
Wiser devices without any loads (e.g. "Nebenstellen" or secondary switches) are represented in Home Assistant as a single device. They only have the identify entity but are also selectable in the status LED service (see below).
You can ping (identify) any device, which makes their button illumination flash for a short amount of time.
Wiser scenes are integrated as native Home Assistant scenes, allowing to trigger them like any other scene as well as use them in automations.
The integration listens to state changes via a Websocket, leading to near-instant updates in Home Assistant
The integration also provides a status light service that allows you to control the status leds of a Wiser device. Each channel (load) of the device supports a brightness value for the logical "on" and "off" state. Secondary devices follow the main device. As there currently is no way in the Wiser ecosystem to determine wheter a scene is active, scene buttons do not have a logical "on" state. Two-channel devices (e.g. two dimmers in the same switch) allow for different configurations for each channel.
This feature can be used to indicate system status (e.g. turn a light switch to red to indicate that your washing machine has finished and wants to be emptied or detected motion in a different room).
- In the current implementation of the Wiser ecosystem it is not possible to configure different colors for the "on" and "off" state.
- Note that updating the configuration can take up to multiple seconds as there are multiple slow API calls involved.
The integration automatically prompts you to re-connect if there is any authentication error.
| Device | Support | Remarks |
|---|---|---|
| Light switches | ✅ | Full support, well tested |
| LED dimmers | ✅ | Full support, well tested |
| DALI dimmers | ✅ | Full support, well tested |
| DALI tunable white dimmers | ❌ | On the roadmap |
| DALI RGBW dimmers | ❌ | On the roadmap |
| Blind / awning controls | ✅ | Full support, well tested |
| Secondary controls (Nebenstellen) | ✅ | Support for status LED control |
| Heating controller 6K | ✅ | Full support, recently added |
| Temperature sensors | ✅ | Full support, recently added |
| Weather station + REG module | ✅ | Full support, recently added |
Here's a couple of things that are on the roadmap for future releases:
- Full support for all light types
- Template for Micro-Python script to trigger Home Assistant events. This way you could use Wiser scene buttons to trigger actions in Home Assistant.
This is a known bug in the Wiser µGateway firmware. Please refer to issue #48 and Feller-AG/wiser-api#43 to resolve the issue.
This happens, if your Wiser system has not been finalized by an electrician / installer. This includes naming all the loads, setting up rooms, assigning loads to rooms, etc. To resolve this, please ask your electrician / installer to finalize the setup using the Wiser eSetup app, or refer to Feller-AG/wiser-api#49 for more information on using the API to finalize the system.
- As of right now, the µGateway API only supports Rest and Websockets. MQTT is implemented, but only for the proprietary app.
- While Home Assistant supports updating the state of multiple devices at once, it does not support controlling multiple devices together. Home Assistant scenes will therefore always update one device after another, while Wiser native scenes will update all devices in parallel. For an optimal experience it is therefore recommended to maintain scenes in Wiser and trigger them with Home Assistant.
- By default, a heating controller is exposed to HA as a heating device. If your heating source also supports cooling, HA will dynamically update the supported modes from heating and off to cooling and off. This was decided because unlike a split system, a heating system like this will not be able to quickly switch between heating and cooling, thus the mode heating/cooling is not correct. Switching between modes currently requires you to reload the dashboard.
- The Wiser API allows for custom blink pattern, duration and color for load (e.g. light outputs) pinging. For load-less devices (sensor-only or secondary controls), the API currently only supports pinging by blinking once in yellow.
