2024.11.0
Home ▸ Integrations ▸

RaspyRFM

The raspyrfm integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] adds support for cheap RC 433 MHz outlets via one of the supported gateways.

Initially, this integration was created to support the Simple Solutions ConnAir gateway which has been discontinued. There are custom alternatives that reimplemented the protocol used by the ConnAir gateway like this ConnAir emulator which can be used in conjunction with the RaspyRFM-II RC module for a Raspberry Pi.

Other vendors of 433 MHz RC outlets have also created gateways that use a very similar protocol and can also be used with this integration like the Intertechno ITGW-433 LAN Gateway.

Configuration

To use the RaspyRFM integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] in your installation, add it to your configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file. After changing the configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file, restart Home Assistant to apply the changes. The integration is now shown on the integrations page under Settings > Devices & services. Its entities are listed on the integration card itself and on the Entities tab.

# Example configuration.yaml entry
switch:
  platform: raspyrfm
  switches:
    - controlunit_manufacturer: Intertechno
      controlunit_model: CMR 1000
      channel_config:  # Note that keys used here vary between control units
        master: A
        slave: 1

Configuration Variables

Looking for your configuration file?
gateway_manufacturer string (Optional, default: Seegel Systeme)

Manufacturer of the gateway.

gateway_model string (Optional, default: RaspyRFM)

Model of the gateway.

host string (Optional, default: 127.0.0.1)

Host of the gateway.

port integer (Optional)

Port of the gateway.

Default:

Depends on the gateway model.

switches list Required

List of switches that can be controlled with this gateway.

name string (Optional, default: Unnamed Device)

Name for the device.

controlunit_manufacturer string Required

Manufacturer of the control unit.

controlunit_model string Required

Model of the control unit.

channel_config map Required

Channel configuration of the control unit. The exact keys needed depend on the control unit manufacturer and model.

Device support

Have a look at the underlying library raspyrfm-client to check what gateways and control units (outlets) are supported.

Channel configuration

Depending on the control unit the channel configuration can have varying formats. Have a look at the underlying library raspyrfm-client to find out about a specific model.

Switch state

Initially, the state of a switch is unknown. When the switch is turned on or off (via frontend) the state is known and will be shown in the frontend.

Note

Note that due to the way those cheap RC units work it is not possible to query their current state. Therefore the only way to preserve a consistent state within Home Assistant is to only use Home Assistant as the controller.

Full example 

switch:
  platform: raspyrfm
  gateway_manufacturer: Seegel Systeme
  gateway_model: RaspyRFM
  host: 127.0.0.1              # Optional
  port: 49880                  # Optional
  switches:
    - name: My Switch
      controlunit_manufacturer: Intertechno
      controlunit_model: CMR 1000
      channel_config:
        master: A
        slave: 1
    - name: My other Switch
      controlunit_manufacturer: Brennenstuhl
      controlunit_model: RCS 1000 N Comfort
      channel_config:
        1: 1
        2: 1
        3: 1
        4: 1
        5: 1
        CH: A

Related topics