C/C++ - Remote Switch Bricklet 2.0

This is the description of the C/C++ API bindings for the Remote Switch Bricklet 2.0. General information and technical specifications for the Remote Switch Bricklet 2.0 are summarized in its hardware description.

An installation guide for the C/C++ API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Switch Socket

Download (example_switch_socket.c)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
#include <stdio.h>

#include "ip_connection.h"
#include "bricklet_remote_switch_v2.h"

#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Remote Switch Bricklet 2.0

int main(void) {
    // Create IP connection
    IPConnection ipcon;
    ipcon_create(&ipcon);

    // Create device object
    RemoteSwitchV2 rs;
    remote_switch_v2_create(&rs, UID, &ipcon);

    // Connect to brickd
    if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
        fprintf(stderr, "Could not connect\n");
        return 1;
    }
    // Don't use device before ipcon is connected

    // Switch on a type A socket with house code 17 and receiver code 1.
    // House code 17 is 10001 in binary (least-significant bit first)
    // and means that the DIP switches 1 and 5 are on and 2-4 are off.
    // Receiver code 1 is 10000 in binary (least-significant bit first)
    // and means that the DIP switch A is on and B-E are off.
    remote_switch_v2_switch_socket_a(&rs, 17, 1, REMOTE_SWITCH_V2_SWITCH_TO_ON);

    printf("Press key to exit\n");
    getchar();
    remote_switch_v2_destroy(&rs);
    ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
    return 0;
}

Remote Callback

Download (example_remote_callback.c)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
#include <stdio.h>

#include "ip_connection.h"
#include "bricklet_remote_switch_v2.h"

#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Remote Switch Bricklet 2.0

// Callback function for remote status a callback
void cb_remote_status_a(uint8_t house_code, uint8_t receiver_code, uint8_t switch_to,
                        uint16_t repeats, void *user_data) {
    (void)user_data; // avoid unused parameter warning

    printf("House Code: %u\n", house_code);
    printf("Receiver Code: %u\n", receiver_code);

    if(switch_to == REMOTE_SWITCH_V2_SWITCH_TO_OFF) {
        printf("Switch To: Off\n");
    } else if(switch_to == REMOTE_SWITCH_V2_SWITCH_TO_ON) {
        printf("Switch To: On\n");
    }

    printf("Repeats: %u\n", repeats);
    printf("\n");
}

int main(void) {
    // Create IP connection
    IPConnection ipcon;
    ipcon_create(&ipcon);

    // Create device object
    RemoteSwitchV2 rs;
    remote_switch_v2_create(&rs, UID, &ipcon);

    // Connect to brickd
    if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
        fprintf(stderr, "Could not connect\n");
        return 1;
    }
    // Don't use device before ipcon is connected

    // Configure to receive from remote type A with minimum repeats set to 1 and enable callback
    remote_switch_v2_set_remote_configuration(&rs, REMOTE_SWITCH_V2_REMOTE_TYPE_A, 1,
                                              true);

    // Register remote status a callback to function cb_remote_status_a
    remote_switch_v2_register_callback(&rs,
                                       REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_A,
                                       (void (*)(void))cb_remote_status_a,
                                       NULL);

    printf("Press key to exit\n");
    getchar();
    remote_switch_v2_destroy(&rs);
    ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
    return 0;
}

API

Every function of the C/C++ bindings returns an integer which describes an error code. Data returned from the device, when a getter is called, is handled via output parameters. These parameters are labeled with the ret_ prefix.

Possible error codes are:

  • E_OK = 0
  • E_TIMEOUT = -1
  • E_NO_STREAM_SOCKET = -2
  • E_HOSTNAME_INVALID = -3
  • E_NO_CONNECT = -4
  • E_NO_THREAD = -5
  • E_NOT_ADDED = -6 (unused since C/C++ bindings version 2.0.0)
  • E_ALREADY_CONNECTED = -7
  • E_NOT_CONNECTED = -8
  • E_INVALID_PARAMETER = -9
  • E_NOT_SUPPORTED = -10
  • E_UNKNOWN_ERROR_CODE = -11
  • E_STREAM_OUT_OF_SYNC = -12
  • E_INVALID_UID = -13
  • E_NON_ASCII_CHAR_IN_SECRET = -14

as defined in ip_connection.h.

All functions listed below are thread-safe.

Basic Functions

void remote_switch_v2_create(RemoteSwitchV2 *remote_switch_v2, const char *uid, IPConnection *ipcon)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • uid – Type: const char *
  • ipcon – Type: IPConnection *

Creates the device object remote_switch_v2 with the unique device ID uid and adds it to the IPConnection ipcon:

RemoteSwitchV2 remote_switch_v2;
remote_switch_v2_create(&remote_switch_v2, "YOUR_DEVICE_UID", &ipcon);

This device object can be used after the IP connection has been connected (see examples above).

void remote_switch_v2_destroy(RemoteSwitchV2 *remote_switch_v2)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *

Removes the device object remote_switch_v2 from its IPConnection and destroys it. The device object cannot be used anymore afterwards.

int remote_switch_v2_get_switching_state(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_state)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_state – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

Returns the current switching state. If the current state is busy, the Bricklet is currently sending a code to switch a socket. It will not accept any calls of switch socket functions until the state changes to ready.

How long the switching takes is dependent on the number of repeats, see remote_switch_v2_set_repeats().

The following constants are available for this function:

For ret_state:

  • REMOTE_SWITCH_V2_SWITCHING_STATE_READY = 0
  • REMOTE_SWITCH_V2_SWITCHING_STATE_BUSY = 1
int remote_switch_v2_switch_socket_a(RemoteSwitchV2 *remote_switch_v2, uint8_t house_code, uint8_t receiver_code, uint8_t switch_to)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • house_code – Type: uint8_t, Range: [0 to 31]
  • receiver_code – Type: uint8_t, Range: [0 to 31]
  • switch_to – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

To switch a type A socket you have to give the house code, receiver code and the state (on or off) you want to switch to.

A detailed description on how you can figure out the house and receiver code can be found here.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
int remote_switch_v2_switch_socket_b(RemoteSwitchV2 *remote_switch_v2, uint32_t address, uint8_t unit, uint8_t switch_to)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • address – Type: uint32_t, Range: [0 to 67108863]
  • unit – Type: uint8_t, Range: [0 to 15, 255]
  • switch_to – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

To switch a type B socket you have to give the address, unit and the state (on or off) you want to switch to.

To switch all devices with the same address use 255 for the unit.

A detailed description on how you can teach a socket the address and unit can be found here.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
int remote_switch_v2_dim_socket_b(RemoteSwitchV2 *remote_switch_v2, uint32_t address, uint8_t unit, uint8_t dim_value)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • address – Type: uint32_t, Range: [0 to 67108863]
  • unit – Type: uint8_t, Range: [0 to 15, 255]
  • dim_value – Type: uint8_t, Range: [0 to 255]
Returns:
  • error_code – Type: int

To control a type B dimmer you have to give the address, unit and the dim value you want to set the dimmer to.

A detailed description on how you can teach a dimmer the address and unit can be found here.

int remote_switch_v2_switch_socket_c(RemoteSwitchV2 *remote_switch_v2, char system_code, uint8_t device_code, uint8_t switch_to)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • system_code – Type: char, Range: ['A' to 'P']
  • device_code – Type: uint8_t, Range: [1 to 16]
  • switch_to – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

To switch a type C socket you have to give the system code, device code and the state (on or off) you want to switch to.

A detailed description on how you can figure out the system and device code can be found here.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
int remote_switch_v2_set_remote_configuration(RemoteSwitchV2 *remote_switch_v2, uint8_t remote_type, uint16_t minimum_repeats, bool callback_enabled)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • remote_type – Type: uint8_t, Range: See constants, Default: A
  • minimum_repeats – Type: uint16_t, Range: [0 to 216 - 1], Default: 2
  • callback_enabled – Type: bool, Default: false
Returns:
  • error_code – Type: int

Sets the configuration for receiving data from a remote of type A, B or C.

The following constants are available for this function:

For remote_type:

  • REMOTE_SWITCH_V2_REMOTE_TYPE_A = 0
  • REMOTE_SWITCH_V2_REMOTE_TYPE_B = 1
  • REMOTE_SWITCH_V2_REMOTE_TYPE_C = 2
int remote_switch_v2_get_remote_configuration(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_remote_type, uint16_t *ret_minimum_repeats, bool *ret_callback_enabled)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_remote_type – Type: uint8_t, Range: See constants, Default: A
  • ret_minimum_repeats – Type: uint16_t, Range: [0 to 216 - 1], Default: 2
  • ret_callback_enabled – Type: bool, Default: false
Returns:
  • error_code – Type: int

Returns the remote configuration as set by remote_switch_v2_set_remote_configuration()

The following constants are available for this function:

For ret_remote_type:

  • REMOTE_SWITCH_V2_REMOTE_TYPE_A = 0
  • REMOTE_SWITCH_V2_REMOTE_TYPE_B = 1
  • REMOTE_SWITCH_V2_REMOTE_TYPE_C = 2
int remote_switch_v2_get_remote_status_a(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_house_code, uint8_t *ret_receiver_code, uint8_t *ret_switch_to, uint16_t *ret_repeats)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_house_code – Type: uint8_t, Range: [0 to 31]
  • ret_receiver_code – Type: uint8_t, Range: [0 to 31]
  • ret_switch_to – Type: uint8_t, Range: See constants
  • ret_repeats – Type: uint16_t, Range: [0 to 216 - 1]
Returns:
  • error_code – Type: int

Returns the house code, receiver code, switch state (on/off) and number of repeats for remote type A.

Repeats == 0 means there was no button press. Repeats >= 1 means there was a button press with the specified house/receiver code. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.

Use the callback to get this data automatically when a button is pressed, see remote_switch_v2_set_remote_configuration() and REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_A callback.

The following constants are available for this function:

For ret_switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
int remote_switch_v2_get_remote_status_b(RemoteSwitchV2 *remote_switch_v2, uint32_t *ret_address, uint8_t *ret_unit, uint8_t *ret_switch_to, uint8_t *ret_dim_value, uint16_t *ret_repeats)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_address – Type: uint32_t, Range: [0 to 67108863]
  • ret_unit – Type: uint8_t, Range: [0 to 15]
  • ret_switch_to – Type: uint8_t, Range: See constants
  • ret_dim_value – Type: uint8_t, Range: [0 to 255]
  • ret_repeats – Type: uint16_t, Range: [0 to 216 - 1]
Returns:
  • error_code – Type: int

Returns the address (unique per remote), unit (button number), switch state (on/off) and number of repeats for remote type B.

If the remote supports dimming the dim value is used instead of the switch state.

If repeats=0 there was no button press. If repeats >= 1 there was a button press with the specified address/unit. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.

Use the callback to get this data automatically when a button is pressed, see remote_switch_v2_set_remote_configuration() and REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_B callback.

The following constants are available for this function:

For ret_switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
int remote_switch_v2_get_remote_status_c(RemoteSwitchV2 *remote_switch_v2, char *ret_system_code, uint8_t *ret_device_code, uint8_t *ret_switch_to, uint16_t *ret_repeats)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_system_code – Type: char, Range: ['A' to 'P']
  • ret_device_code – Type: uint8_t, Range: [1 to 16]
  • ret_switch_to – Type: uint8_t, Range: See constants
  • ret_repeats – Type: uint16_t, Range: [0 to 216 - 1]
Returns:
  • error_code – Type: int

Returns the system code, device code, switch state (on/off) and number of repeats for remote type C.

If repeats=0 there was no button press. If repeats >= 1 there was a button press with the specified system/device code. The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number.

Use the callback to get this data automatically when a button is pressed, see remote_switch_v2_set_remote_configuration() and REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_C callback.

The following constants are available for this function:

For ret_switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1

Advanced Functions

int remote_switch_v2_set_repeats(RemoteSwitchV2 *remote_switch_v2, uint8_t repeats)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • repeats – Type: uint8_t, Range: [0 to 255], Default: 5
Returns:
  • error_code – Type: int

Sets the number of times the code is send when one of the Switch Socket functions is called. The repeats basically correspond to the amount of time that a button of the remote is pressed.

Some dimmers are controlled by the length of a button pressed, this can be simulated by increasing the repeats.

int remote_switch_v2_get_repeats(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_repeats)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_repeats – Type: uint8_t, Range: [0 to 255], Default: 5
Returns:
  • error_code – Type: int

Returns the number of repeats as set by remote_switch_v2_set_repeats().

int remote_switch_v2_get_spitfp_error_count(RemoteSwitchV2 *remote_switch_v2, uint32_t *ret_error_count_ack_checksum, uint32_t *ret_error_count_message_checksum, uint32_t *ret_error_count_frame, uint32_t *ret_error_count_overflow)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_error_count_ack_checksum – Type: uint32_t, Range: [0 to 232 - 1]
  • ret_error_count_message_checksum – Type: uint32_t, Range: [0 to 232 - 1]
  • ret_error_count_frame – Type: uint32_t, Range: [0 to 232 - 1]
  • ret_error_count_overflow – Type: uint32_t, Range: [0 to 232 - 1]
Returns:
  • error_code – Type: int

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

int remote_switch_v2_set_bootloader_mode(RemoteSwitchV2 *remote_switch_v2, uint8_t mode, uint8_t *ret_status)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • mode – Type: uint8_t, Range: See constants
Output Parameters:
  • ret_status – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

Sets the bootloader mode and returns the status after the requested mode change was instigated.

You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

The following constants are available for this function:

For mode:

  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_BOOTLOADER = 0
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE = 1
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For ret_status:

  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_OK = 0
  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_INVALID_MODE = 1
  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_NO_CHANGE = 2
  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • REMOTE_SWITCH_V2_BOOTLOADER_STATUS_CRC_MISMATCH = 5
int remote_switch_v2_get_bootloader_mode(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_mode)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_mode – Type: uint8_t, Range: See constants
Returns:
  • error_code – Type: int

Returns the current bootloader mode, see remote_switch_v2_set_bootloader_mode().

The following constants are available for this function:

For ret_mode:

  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_BOOTLOADER = 0
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE = 1
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • REMOTE_SWITCH_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
int remote_switch_v2_set_write_firmware_pointer(RemoteSwitchV2 *remote_switch_v2, uint32_t pointer)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • pointer – Type: uint32_t, Unit: 1 B, Range: [0 to 232 - 1]
Returns:
  • error_code – Type: int

Sets the firmware pointer for remote_switch_v2_write_firmware(). The pointer has to be increased by chunks of size 64. The data is written to flash every 4 chunks (which equals to one page of size 256).

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

int remote_switch_v2_write_firmware(RemoteSwitchV2 *remote_switch_v2, uint8_t data[64], uint8_t *ret_status)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • data – Type: uint8_t[64], Range: [0 to 255]
Output Parameters:
  • ret_status – Type: uint8_t, Range: [0 to 255]
Returns:
  • error_code – Type: int

Writes 64 Bytes of firmware at the position as written by remote_switch_v2_set_write_firmware_pointer() before. The firmware is written to flash every 4 chunks.

You can only write firmware in bootloader mode.

This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.

int remote_switch_v2_set_status_led_config(RemoteSwitchV2 *remote_switch_v2, uint8_t config)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • config – Type: uint8_t, Range: See constants, Default: 3
Returns:
  • error_code – Type: int

Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.

The following constants are available for this function:

For config:

  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_OFF = 0
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_ON = 1
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
int remote_switch_v2_get_status_led_config(RemoteSwitchV2 *remote_switch_v2, uint8_t *ret_config)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_config – Type: uint8_t, Range: See constants, Default: 3
Returns:
  • error_code – Type: int

Returns the configuration as set by remote_switch_v2_set_status_led_config()

The following constants are available for this function:

For ret_config:

  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_OFF = 0
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_ON = 1
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • REMOTE_SWITCH_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
int remote_switch_v2_get_chip_temperature(RemoteSwitchV2 *remote_switch_v2, int16_t *ret_temperature)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_temperature – Type: int16_t, Unit: 1 °C, Range: [-215 to 215 - 1]
Returns:
  • error_code – Type: int

Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!

The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.

int remote_switch_v2_reset(RemoteSwitchV2 *remote_switch_v2)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Returns:
  • error_code – Type: int

Calling this function will reset the Bricklet. All configurations will be lost.

After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!

int remote_switch_v2_write_uid(RemoteSwitchV2 *remote_switch_v2, uint32_t uid)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • uid – Type: uint32_t, Range: [0 to 232 - 1]
Returns:
  • error_code – Type: int

Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.

We recommend that you use Brick Viewer to change the UID.

int remote_switch_v2_read_uid(RemoteSwitchV2 *remote_switch_v2, uint32_t *ret_uid)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_uid – Type: uint32_t, Range: [0 to 232 - 1]
Returns:
  • error_code – Type: int

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

int remote_switch_v2_get_identity(RemoteSwitchV2 *remote_switch_v2, char ret_uid[8], char ret_connected_uid[8], char *ret_position, uint8_t ret_hardware_version[3], uint8_t ret_firmware_version[3], uint16_t *ret_device_identifier)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_uid – Type: char[8]
  • ret_connected_uid – Type: char[8]
  • ret_position – Type: char, Range: ['a' to 'h', 'i', 'z']
  • ret_hardware_version – Type: uint8_t[3]
    • 0: major – Type: uint8_t, Range: [0 to 255]
    • 1: minor – Type: uint8_t, Range: [0 to 255]
    • 2: revision – Type: uint8_t, Range: [0 to 255]
  • ret_firmware_version – Type: uint8_t[3]
    • 0: major – Type: uint8_t, Range: [0 to 255]
    • 1: minor – Type: uint8_t, Range: [0 to 255]
    • 2: revision – Type: uint8_t, Range: [0 to 255]
  • ret_device_identifier – Type: uint16_t, Range: [0 to 216 - 1]
Returns:
  • error_code – Type: int

Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.

The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). The Raspberry Pi HAT (Zero) Brick is always at position 'i' and the Bricklet connected to an Isolator Bricklet is always as position 'z'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions

void remote_switch_v2_register_callback(RemoteSwitchV2 *remote_switch_v2, int16_t callback_id, void (*function)(void), void *user_data)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • callback_id – Type: int16_t
  • function – Type: void (*)(void)
  • user_data – Type: void *

Registers the given function with the given callback_id. The user_data will be passed as the last parameter to the function.

The available callback IDs with corresponding function signatures are listed below.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the remote_switch_v2_register_callback() function:

void my_callback(int value, void *user_data) {
    printf("Value: %d\n", value);
}

remote_switch_v2_register_callback(&remote_switch_v2,
                                   REMOTE_SWITCH_V2_CALLBACK_EXAMPLE,
                                   (void (*)(void))my_callback,
                                   NULL);

The available constants with corresponding function signatures are described below.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

REMOTE_SWITCH_V2_CALLBACK_SWITCHING_DONE
void callback(void *user_data)
Callback Parameters:
  • user_data – Type: void *

This callback is triggered whenever the switching state changes from busy to ready, see remote_switch_v2_get_switching_state().

REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_A
void callback(uint8_t house_code, uint8_t receiver_code, uint8_t switch_to, uint16_t repeats, void *user_data)
Callback Parameters:
  • house_code – Type: uint8_t, Range: [0 to 31]
  • receiver_code – Type: uint8_t, Range: [0 to 31]
  • switch_to – Type: uint8_t, Range: See constants
  • repeats – Type: uint16_t, Range: [0 to 216 - 1]
  • user_data – Type: void *

Returns the house code, receiver code, switch state (on/off) and number of repeats for remote type A.

The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.

You have to enable the callback with remote_switch_v2_set_remote_configuration(). The number of repeats that you can set in the configuration is the minimum number of repeats that have to be seen before the callback is triggered for the first time.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_B
void callback(uint32_t address, uint8_t unit, uint8_t switch_to, uint8_t dim_value, uint16_t repeats, void *user_data)
Callback Parameters:
  • address – Type: uint32_t, Range: [0 to 67108863]
  • unit – Type: uint8_t, Range: [0 to 15, 255]
  • switch_to – Type: uint8_t, Range: See constants
  • dim_value – Type: uint8_t, Range: [0 to 255]
  • repeats – Type: uint16_t, Range: [0 to 216 - 1]
  • user_data – Type: void *

Returns the address (unique per remote), unit (button number), switch state (on/off) and number of repeats for remote type B.

If the remote supports dimming the dim value is used instead of the switch state.

The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.

You have to enable the callback with remote_switch_v2_set_remote_configuration(). The number of repeats that you can set in the configuration is the minimum number of repeats that have to be seen before the callback is triggered for the first time.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1
REMOTE_SWITCH_V2_CALLBACK_REMOTE_STATUS_C
void callback(char system_code, uint8_t device_code, uint8_t switch_to, uint16_t repeats, void *user_data)
Callback Parameters:
  • system_code – Type: char, Range: ['A' to 'P']
  • device_code – Type: uint8_t, Range: [1 to 16]
  • switch_to – Type: uint8_t, Range: See constants
  • repeats – Type: uint16_t, Range: [0 to 216 - 1]
  • user_data – Type: void *

Returns the system code, device code, switch state (on/off) and number of repeats for remote type C.

The repeats are the number of received identical data packets. The longer the button is pressed, the higher the repeat number. The callback is triggered with every repeat.

You have to enable the callback with remote_switch_v2_set_remote_configuration(). The number of repeats that you can set in the configuration is the minimum number of repeats that have to be seen before the callback is triggered for the first time.

The following constants are available for this function:

For switch_to:

  • REMOTE_SWITCH_V2_SWITCH_TO_OFF = 0
  • REMOTE_SWITCH_V2_SWITCH_TO_ON = 1

Virtual Functions

Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.

int remote_switch_v2_get_api_version(RemoteSwitchV2 *remote_switch_v2, uint8_t ret_api_version[3])
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
Output Parameters:
  • ret_api_version – Type: uint8_t[3]
    • 0: major – Type: uint8_t, Range: [0 to 255]
    • 1: minor – Type: uint8_t, Range: [0 to 255]
    • 2: revision – Type: uint8_t, Range: [0 to 255]
Returns:
  • error_code – Type: int

Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.

int remote_switch_v2_get_response_expected(RemoteSwitchV2 *remote_switch_v2, uint8_t function_id, bool *ret_response_expected)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • function_id – Type: uint8_t, Range: See constants
Output Parameters:
  • ret_response_expected – Type: bool
Returns:
  • error_code – Type: int

Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.

For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by remote_switch_v2_set_response_expected(). For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For function_id:

  • REMOTE_SWITCH_V2_FUNCTION_SET_REPEATS = 3
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_A = 5
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_B = 6
  • REMOTE_SWITCH_V2_FUNCTION_DIM_SOCKET_B = 7
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_C = 8
  • REMOTE_SWITCH_V2_FUNCTION_SET_REMOTE_CONFIGURATION = 9
  • REMOTE_SWITCH_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • REMOTE_SWITCH_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • REMOTE_SWITCH_V2_FUNCTION_RESET = 243
  • REMOTE_SWITCH_V2_FUNCTION_WRITE_UID = 248
int remote_switch_v2_set_response_expected(RemoteSwitchV2 *remote_switch_v2, uint8_t function_id, bool response_expected)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • function_id – Type: uint8_t, Range: See constants
  • response_expected – Type: bool
Returns:
  • error_code – Type: int

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For function_id:

  • REMOTE_SWITCH_V2_FUNCTION_SET_REPEATS = 3
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_A = 5
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_B = 6
  • REMOTE_SWITCH_V2_FUNCTION_DIM_SOCKET_B = 7
  • REMOTE_SWITCH_V2_FUNCTION_SWITCH_SOCKET_C = 8
  • REMOTE_SWITCH_V2_FUNCTION_SET_REMOTE_CONFIGURATION = 9
  • REMOTE_SWITCH_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • REMOTE_SWITCH_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • REMOTE_SWITCH_V2_FUNCTION_RESET = 243
  • REMOTE_SWITCH_V2_FUNCTION_WRITE_UID = 248
int remote_switch_v2_set_response_expected_all(RemoteSwitchV2 *remote_switch_v2, bool response_expected)
Parameters:
  • remote_switch_v2 – Type: RemoteSwitchV2 *
  • response_expected – Type: bool
Returns:
  • error_code – Type: int

Changes the response expected flag for all setter and callback configuration functions of this device at once.

Constants

REMOTE_SWITCH_V2_DEVICE_IDENTIFIER

This constant is used to identify a Remote Switch Bricklet 2.0.

The remote_switch_v2_get_identity() function and the IPCON_CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.

REMOTE_SWITCH_V2_DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Remote Switch Bricklet 2.0.