--- title: "Selve NG" description: "Selve NG is a Marketplace integration for Home Assistant. It has 55 installs sharing analytics, works locally and was last updated October 13, 2026." canonical: "https://vulpo.app/integrations/marketplace/kannix2005-homeassistant-selve" url: "https://vulpo.app/integrations/marketplace/kannix2005-homeassistant-selve.md" last-updated: "2026-10-22" version: "1.4" --- # Selve NG > Selve NG is a Marketplace integration for Home Assistant. It has 55 installs sharing analytics, works locally and was last updated October 13, 2026. Selve NG is a Home Assistant integration for local control of Selve USB-RF gateways and the covers attached to them. It exposes shutters, blinds and awnings as cover entities, including groups, positions and tilt for Commeo devices. Devices and serial ports can be found automatically, or the port can be chosen manually during setup in the UI. An option clamps positions near the limits, so values of 0 to 1 percent show as closed and 99 to 100 percent show as open. Many actions cover the gateway itself, such as ping, state, firmware version, LED control, reset, event settings, radio usage and device scanning. Iveo devices are controlled by command only, so their state reporting is limited. Automatic summary of the README and code of Kannix2005/homeassistant-selve. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=Kannix2005&repository=homeassistant-selve&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=Kannix2005&repository=homeassistant-selve&category=integration) ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Selve NG Integration Setup - **Port**: Serial port (e.g. /dev/ttyUSB0) or socket URL (e.g. socket://192.168.1.10:6638) ### After setup - **Port**: Serial port (e.g. /dev/ttyUSB0) or socket URL (e.g. socket://192.168.1.10:6638) - **Open/Close Fix**: Clamp cover positions near boundaries: values 0-1% are reported as fully closed (0%) and 99-100% as fully open (100%). Useful when covers report 99 instead of 100 when fully open, or 1 instead of 0 when fully closed. Texts from the code of [Kannix2005/homeassistant-selve](https://github.com/Kannix2005/homeassistant-selve). ## Actions - **Ping GW**: Pings the gateway - The 'selve.GW.service.ping' method is used to address the SELVE USB-RF gateway in a simple way. This command is correspondingly short without parameters so that the method can be used to find the gateway quickly and automatically. As an initialization command, the application can, for example, locate the gateway as quickly as possible if several COM ports are available, without the user having to predefine a COM port. - **GW State**: Get the status of the gateway - The current status of the gateway is read using the “selve.GW.service.getState” method. If the USB stick is in the bootloader, for example, only limited methods are available - see the corresponding section below. To ensure that the application functions properly, an application should always wait until the “Ready” status is reached. During the “StartUp” phase, the gateway automatically synchronizes the internal information of taught-in actuators so that all available data is updated at the end. The following status information is communicated to the application: Bootloader The USB stick is in the bootloader. This area is active for two seconds after the restart. If no firmware update is carried out by the application and the status does not change, this indicates that the firmware may be faulty. In this case, a new firmware update must be started. Update The USB stick is in the bootloader and a firmware update is actively being carried out. An update must be carried out completely by the application before the actual firmware can be run again. However, an aborted or interrupted firmware update can be restarted from the bootloader at any time. StartUp The actual firmware is started and the StartUp phase is running. During this time, the gateway retrieves all the current statuses of the taught-in actuators. Depending on the size of the system, the start-up phase can vary. - **GW Firmware Version**: Get the FW version of the gateway - Using the “selve.GW.service.getVersion” method, the current version information of the currently installed firmware of the gateway can be read. The firmware version of the USB stick is made up of 4 digits, which are to be interpreted as follows: Part1.Part2.Part3.Revision (e.g. 16.02.03.01) The version of the SELVE XML specification used in the stick is also displayed: Part1.Part2 (e.g. 2.0) NOTE The individual integer values are available in the gateway as HEX values, which should be converted for a uniform, correct display. - **GW Serial**: Retrieves the serial number of the gateway. - **GW Spec**: Retrieves the spec number of the gateway. - **Reset GW**: Resets the gateway. - A software reset can be carried out using the “selve.GW.service.reset” method. When the method is received, the corresponding response from the application is sent and then rebooted. This method is used, for example, to carry out a firmware update. After a reset, the application should always wait for the desired readiness using the corresponding methods “selve.GW.service.ping” and/or “selve.GW.service.getState”. - **Werksreset GW**: ATTENTION - Resets the gateway to the factory settings. The SELVE USB-RF Gateway can be reset to the factory settings using the “selve.GW.service.factoryReset” method. If this command is executed, all user-specific settings, programmed transmitters, actuators, etc. are deleted. - **LED GW**: Turns the status LED on or off - **Get LED GW**: Get the state of the status LED - **Update All**: Update all known devices - **Set Forward**: Set commeo forwarding - The “selve.GW.param.setForward” method can be used to activate or deactivate commeo forwarding in the gateway. If forwarding is activated, this means that the gateway acts as an additional routing element in a commeo system. Depending on the system situation, this function can be switched off in the gateway, e.g. because the installation location of the gateway is against it. This function is always switched on in the factory settings. - **Get Forward**: Get Commeo Forwarding - **Set Events**: Change event manager config - The gateway's event manager can be set individually using the “selve.GW.param.setEvent” method. Activated events ensure that the gateway automatically notifies the application of changes so that the application does not have to poll for status information. EventDevice If the setting is activated, the gateway automatically sends all status changes of the taught-in actuators. EventSensor If the setting is activated, the gateway automatically informs the application of any changes in sensor data. EventSender If the setting is activated, the gateway automatically reports incoming actuations of taught-in transmitters to the application. Logging If the setting is activated, the gateway sends possible logs from the external application. The gateway itself has no memory for logs, so this must be done by the application at this point. EventDuty If the setting is activated, the gateway automatically sends changes in radio resource usage. - **Get Events**: Get Eventmanager Config - **Get Duty**: Read radio resource usage - The current radio resource usage of the gateway can be read using the “selve.GW.param.getDuty” method. Due to the 868 MHz ISM band used, the gateway automatically ensures that the required guidelines are adhered to. The utilization read here is reported as a percentage. This value indicates how high the current utilization is in relation to the permitted limit value. A 100 % utilization means that the limit value of the permitted radio utilization according to the guideline has been reached. - **Get RF**: Get RF info - **Scan devices Start**: Start scanning for devices - **Scan devices Stop**: Stop scanning for devices - **Scan devices Status**: Get scan results - **Save device**: Save found device(s) in gateway ## From the README > Local control of Selve USB-RF gateways and covers (Commeo/Iveo/Groups) via python-selve-new. From the README of [Kannix2005/homeassistant-selve](https://github.com/Kannix2005/homeassistant-selve#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Blinds and curtains](https://vulpo.app/integrations/category/blinds-and-curtains.md) - Number: 55 installs sharing analytics; 22 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v3.3.19, last updated October 13, 2026 - Domain: `selve` - Source: - Issues: In Vulpo: Cover card, Chart card, Apple Watch, Control Center Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/kannix2005-homeassistant-selve --- - HTML version of this page: https://vulpo.app/integrations/marketplace/kannix2005-homeassistant-selve - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml