NAME
Tinkerforge::BrickletRemoteSwitchV2 - Controls remote mains switches and receives signals from remotes
CONSTANTS
- DEVICE_IDENTIFIER
-
This constant is used to identify a Remote Switch Bricklet 2.0.
The get_identity() subroutine and the CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.
- DEVICE_DISPLAY_NAME
-
This constant represents the display name of a Remote Switch Bricklet 2.0.
- CALLBACK_SWITCHING_DONE
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_SWITCHING_DONE callback.
- CALLBACK_REMOTE_STATUS_A
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_REMOTE_STATUS_A callback.
- CALLBACK_REMOTE_STATUS_B
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_REMOTE_STATUS_B callback.
- CALLBACK_REMOTE_STATUS_C
-
This constant is used with the register_callback() subroutine to specify the CALLBACK_REMOTE_STATUS_C callback.
- FUNCTION_GET_SWITCHING_STATE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_REPEATS
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_REPEATS
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SWITCH_SOCKET_A
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SWITCH_SOCKET_B
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_DIM_SOCKET_B
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SWITCH_SOCKET_C
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_REMOTE_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_REMOTE_CONFIGURATION
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_REMOTE_STATUS_A
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_REMOTE_STATUS_B
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_REMOTE_STATUS_C
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_SPITFP_ERROR_COUNT
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_BOOTLOADER_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_BOOTLOADER_MODE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_WRITE_FIRMWARE_POINTER
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_WRITE_FIRMWARE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_SET_STATUS_LED_CONFIG
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_STATUS_LED_CONFIG
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_CHIP_TEMPERATURE
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_RESET
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_WRITE_UID
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_READ_UID
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
- FUNCTION_GET_IDENTITY
-
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
FUNCTIONS
- new()
-
Creates an object with the unique device ID *uid* and adds it to the IP Connection *ipcon*.
- get_switching_state()
-
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 :func:`Set Repeats`.
- set_repeats()
-
Sets the number of times the code is sent 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.
- get_repeats()
-
Returns the number of repeats as set by :func:`Set Repeats`.
- switch_socket_a()
-
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 :ref:`here <remote_switch_bricklet_type_a_house_and_receiver_code>`.
- switch_socket_b()
-
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 :ref:`here <remote_switch_bricklet_type_b_address_and_unit>`.
- dim_socket_b()
-
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 :ref:`here <remote_switch_bricklet_type_b_address_and_unit>`.
- switch_socket_c()
-
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 :ref:`here <remote_switch_bricklet_type_c_system_and_device_code>`.
- set_remote_configuration()
-
Sets the configuration for **receiving** data from a remote of type A, B or C.
* Remote Type: A, B or C depending on the type of remote you want to receive. * Minimum Repeats: The minimum number of repeated data packets until the callback is triggered (if enabled). * Callback Enabled: Enable or disable callback (see :cb:`Remote Status A` callback, :cb:`Remote Status B` callback and :cb:`Remote Status C` callback).
- get_remote_configuration()
-
Returns the remote configuration as set by :func:`Set Remote Configuration`
- get_remote_status_a()
-
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 :func:`Set Remote Configuration` and :cb:`Remote Status A` callback.
- get_remote_status_b()
-
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 :func:`Set Remote Configuration` and :cb:`Remote Status B` callback.
- get_remote_status_c()
-
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 :func:`Set Remote Configuration` and :cb:`Remote Status C` callback.
- get_spitfp_error_count()
-
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.
- set_bootloader_mode()
-
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.
- get_bootloader_mode()
-
Returns the current bootloader mode, see :func:`Set Bootloader Mode`.
- set_write_firmware_pointer()
-
Sets the firmware pointer for :func:`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.
- write_firmware()
-
Writes 64 Bytes of firmware at the position as written by :func:`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.
- set_status_led_config()
-
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.
- get_status_led_config()
-
Returns the configuration as set by :func:`Set Status LED Config`
- get_chip_temperature()
-
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.
- reset()
-
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!
- write_uid()
-
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.
- read_uid()
-
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
- get_identity()
-
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 :ref:`Isolator Bricklet <isolator_bricklet>` is always as position 'z'.
The device identifier numbers can be found :ref:`here <device_identifier>`. |device_identifier_constant|