redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 214916702 | Release Date | 2026/04/12 | List Price | $36.00 | Model Number | 214916702 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
This is Okin Bed Remote Model RF.27.19.33 Replacement, is only compatible with Lucid l600 Adjustable Bed and CANNOT replace other brands of adjustable beds. Please Check your Label Before Ordering! The remote used 2 AAA batteries, which need to be purchased separately. If your buttons and words on your old remote that you are replacing do not exactly match those on the new one shown here in either of the pictures then the chances are it will not work with your base. Please contact us if you have questions before ordering to ensure your remote will work.In the event that the remote is not paired with the foundation, follow the steps below:Step 1: Ensure the remote batteries are functioning. Replace if necessary. Confirm the power cord is connected to a powered source.Step 2: On the control box (underside of base), press the PAIR button twice. The LED light on the control box turns blue.Step 3: On the remote control, press and hold the PAIR button. The light on the remote flashes and starts the pairing process.If the pairing is successful, the LED light on the control box turns to green. If pairing fails, the LED light on the control box turns off. Repeat the steps until pairing is successful.
| Brand | Uetmulik |
|---|---|
| Color | white |
| Model Name | RF.27.19.33 |
| Item Weight | 0.1 Kilograms |
| Battery Type | AAA |
| Manufacturer | Uetmulik |
| Model Number | RF.27.19.33 |
| Maximum Range | 10 Meters |
| Controller Type | Button Control |
| Mfr Part Number | RF.27.19.33 |
| Compatible Devices | Lucid l600 Adjustable Bed |
| Additional Features | Ergonomic |
| Connectivity Technology | Radio Frequency |
| Maximum Number of Supported Devices | 1 |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form