Desky Standing Desk (ESPHome) [Works with Desky, Uplift, Jiecang, Assmann & others]

BrianRich88 · May 10, 2024, 3:03pm

Yeah definitely. So, I am a big proponent of having a rigid benchtop and desktop, so I typically just bolt my desks to the wall with a big L bracket. Well, you obviously can’t do that with a standing desk, so I bought a piece of 6" x 30" steel and mounted it to the wall behind my desk and bought an electromagnet from amazon that is meant to hold doors shut. I printed a mount to hold the magnet to the desk and it has like a 350lb rating.

I’m currently using a zigbee plug with a 12v power supply plugged into it to control the electromagnet. Ideally, I’d like to control this zigbee plug with the “desk is moving” bit in home assistant, however there is too much delay between when I press the down button, and the zigbee plug turns off. It’s only like a second or two, but that’s enough to bind up the desk and cause the magnet to keep holding.

This is where my question came in. I plan on controlling the magnet with an output from the D1 to a relay that allows the 12v to go to the magnet instead. I think this will give a much more instant response than waiting for the zigbee plug. The magnet takes like 1-2 seconds to energize, however it de-energizes very quickly, allowing the desk to move.

Here are some pictures to get a better idea, and this is the electromagnet that I am using (I took it out of its case since that just added bulk).

Mahko_Mahko · May 10, 2024, 8:40pm

Ah I see. So it is an anti-wobble device?

BrianRich88 · May 11, 2024, 2:14am

Yep. Albeit, maybe a little over-engineered or overkill, but that’s kind of why we’re all here, right? haha

Mahko_Mahko · May 11, 2024, 4:14am

You might get a laugh out of one of my lockdown projects then. It was a bit of failure in the end but was fun to build.

BrianRich88 · May 12, 2024, 7:42pm

Oh my goodness, this is amazing! Yeah, not going to mention “overkill” again, I now know I’m in the right place haha.

hraschan · May 16, 2024, 12:57pm

Hello @jcastro. Do you have the big fully controller with display or only the small one?
Could you maybe DM me your ESPHome config? I cant get the logging working.
Also my display isnt working anymore on the fully controller when my passthrough is connected. @Mahko_Mahko do you maybe have an idea about this?

Controller and ESP32

The first one is my used controller. This is my used ESP32

Config

esphome:
  name: standing-desk
  friendly_name: Standing Desk
  on_boot:
    priority: -100.0
    then:
    #Request a desk height update after boot.
      - delay: 5s
      - switch.turn_on: wake_desk_and_get_height
esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:
  level: VERY_VERBOSE
# Enable Home Assistant API
api:
  encryption:
    key: "lBXwa0ZuqNLMwW4rHZC0PhX7yCSeXnKencdECSKA1wY="

ota:
  password: "359fa6d122acb1d2dabc5366276edc66"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Standing-Desk Fallback Hotspot"
    password: "gi4UyEI3xG5D"

captive_portal:


external_components:
#Fetch ssieb's custom component# https://github.com/ssieb/custom_components/tree/master/components/desky
  - source:
      type: git
      url: https://github.com/ssieb/custom_components
    components: [ desky ]

uart:
  - id: desk_uart
    baud_rate: 9600
    rx_pin: 1
    ##You can uncomment the debug section below to see UART messages.
    debug:
      direction: BOTH
      dummy_receiver: true
      after:
        bytes: 9
      sequence:     
        - lambda: UARTDebug::log_int(direction, bytes, ',');
 
desky:
  id: my_desky
  ####################################################################################
  ##Uncomment this block to use Ssieb's move_to componet function.
  # up:    
    # number: 4 #D2
    # inverted: true 
  # down:  
    # number: 5 #D1
    # inverted: true
  # stopping_distance: 15  # optional distance from target to turn off moving, default 15  
  ####################################################################################
  height:  # Sensor publishing the current height
    name: Desky Height
    id: desky_height
    accuracy_decimals: 1
    unit_of_measurement: cm
    #any other sensor options
    filters:
    - delta: 0.05 #Only send values to HA if they change
    - throttle: 200ms #Limit values sent to Ha to 5 per sec.
    - multiply: 0.1 #convert from mm to cm
    on_value:
      then:
          #If the value changes, then the desk is moving
        - binary_sensor.template.publish:
            id: desky_is_moving
            state: ON
        - delay: 300ms
          #Assume it's stopped moving if no height changes after a short time.
        - binary_sensor.template.publish:
            id: desky_is_moving
            state: Off
            
binary_sensor:
  - platform: template
    id: desky_is_moving
    name: "Desky Is Moving"
    filters:
      - delayed_off: 400ms
    #If the desk isn't moving for a bit we better turn off attempts at movement. It's like poor man's collision detection? 
    on_release:
      then:
        - button.press: desky_stop_desk

button: 
#Stop movement 
  - platform: template
    name: Stop Desk
    id: desky_stop_desk
    on_press:
      then:
        - switch.turn_off: raise_desk
        - switch.turn_off: lower_desk

#Move to function
  - platform: template
    name: Go To Desky Height x
    id: go_to_desky_preset_height_x
    on_press:
      then:
      ##Option 1: Uncomment to use Ssieb's move_to componet functions
        # - lambda: id(my_desky).move_to(id(desky_target_height).state*10);  

        
      ##Option 2: Uncomment to use Mahko's lambda alternative 
      #Check if we need to move desk up or down from current position      
        if:
          condition:
          #Current height is more than target height, then move desk down
            lambda: |-
              return id(desky_target_height).state < id(desky_height).state;
          then:
            - switch.turn_on: lower_desk
            - wait_until:
              #Run until the difference between current and target state is < stopping distance 
                condition:
                  lambda: return abs((id(desky_height).state - (id(desky_target_height).state)))<(id(stopping_distance_cm).state);
            - switch.turn_off: lower_desk
          else:
          #Current height is less than target height, move desk up
            - switch.turn_on: raise_desk
            - wait_until:
                condition:
                  lambda: return abs((id(desky_height).state - (id(desky_target_height).state)))<(id(stopping_distance_cm).state);
                  #Run until the difference between current and target state is <0.3cm
            - switch.turn_off: raise_desk


number:
#Target Height ("Move desk to height x").
    #You should probably limit the range you can move the desk to to within the limits you've set via the control panel, perhaps offset a little within the range.
    #Sending commands higher/lower than this may cause error messages and require desk reset (or worse).
  - platform: template
    id: desky_target_height
    name: "Desky Target Height"
    optimistic: true
    unit_of_measurement: cm
    min_value: 80
    max_value: 130.0
    step: 0.1
    
#Offset correction - Adjust until you get the best accuracy. 
#The desk keeps moving for a little while after the up/down pins are released and we try to account for this.
#1.5cm was about right on mine
  - platform: template
    name: "Desky Stopping Distance cm"
    id: stopping_distance_cm
    unit_of_measurement: cm
    optimistic: true
    min_value: 0
    max_value: 2
    step: 0.1
    restore_value: true
    initial_value: 1.5
    
###############################################
#Define some preset heights.
###############################################
#You can freely define as many adjustable presets as you like.
#These are all seperate/independant of what you've set via the control panel (we can't retrieve them currently).
 
#Standing Height #1 - Set a standing height. 
  - platform: template
    id: desky_standing_height_1
    name: "Desky Standing Height 1"
    optimistic: true
    unit_of_measurement: cm
    #Limit the range
    min_value: 120
    max_value: 130
    step: 0.1
    restore_value: true
    initial_value: 124
    
#Sitting Height #1 - Set a sitting height. This is independant of what you've set via the control panel.
  - platform: template
    id: desky_sitting_height_1
    name: "Desky Sitting Height 1"
    optimistic: true
    unit_of_measurement: cm
    #Limit the range
    min_value: 79.7
    max_value: 82
    step: 0.1
    restore_value: true
    initial_value: 79.9


      
switch:
#wake up ther desk and request it sends its height 
  - platform: gpio
    id: wake_desk_and_get_height
    name: "Request Desk Height"
    pin:
      number: GPIO18
      inverted: true
    on_turn_on:
    - delay: 100ms
    - switch.turn_off: wake_desk_and_get_height

#Raise the desk 
  - platform: gpio
    id: raise_desk
    name: "Raise Desk"
    pin:
      number: GPIO21
      # mode: INPUT_PULLUP
      inverted: true
    interlock: lower_desk
    on_turn_on:
    #Auto off after 15s just in case
    - delay: 15s
    - switch.turn_off: raise_desk
#Lower the desk 
  - platform: gpio
    id: lower_desk
    name: "Lower Desk" 
    pin:
      number: GPIO22
      # mode: INPUT_PULLUP
      inverted: true
    interlock: raise_desk
    on_turn_on:
   #Auto off after 15s just in case
    - delay: 15s
    - switch.turn_off: lower_desk

Logs so far - Cant’t get uart logs

[15:03:52][V][mdns:117]:   Services:
[15:03:52][V][mdns:119]:   - _esphomelib, _tcp, 6053
[15:03:52][V][mdns:121]:     TXT: friendly_name = Standing Desk
[15:03:52][V][mdns:121]:     TXT: version = 2024.4.2
[15:03:52][V][mdns:121]:     TXT: mac = 409151ab9734
[15:03:52][V][mdns:121]:     TXT: platform = ESP32
[15:03:52][V][mdns:121]:     TXT: board = esp32dev
[15:03:52][V][mdns:121]:     TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[15:03:52][VV][scheduler:226]: Running interval 'update' with interval=60000 last_execution=768395 (now=828396)
[15:03:54][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=772092 (now=832092)
[15:03:54][VV][scheduler:226]: Running interval 'update' with interval=60000 last_execution=772340 (now=832345)
[15:03:55][VV][api.service:602]: on_ping_request: PingRequest {}
[15:03:55][VV][api.service:043]: send_ping_response: PingResponse {}
[15:04:26][VV][api.service:690]: on_switch_command_request: SwitchCommandRequest {
  key: 529781321
  state: YES
}
[15:04:26][D][switch:012]: 'Raise Desk' Turning ON.
[15:04:26][D][switch:055]: 'Raise Desk': Sending state ON
[15:04:27][VV][scheduler:032]: set_timeout(name='', timeout=15000)
[15:04:27][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 529781321
  state: YES
}
[15:04:27][VV][api.service:690]: on_switch_command_request: SwitchCommandRequest {
  key: 529781321
  state: NO
}
[15:04:27][D][switch:016]: 'Raise Desk' Turning OFF.
[15:04:27][D][switch:055]: 'Raise Desk': Sending state OFF
[15:04:27][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 529781321
  state: NO
}
[15:04:31][VV][api.service:690]: on_switch_command_request: SwitchCommandRequest {
  key: 2153922382
  state: YES
}
[15:04:31][D][switch:012]: 'Request Desk Height' Turning ON.
[15:04:31][D][switch:055]: 'Request Desk Height': Sending state ON
[15:04:31][VV][scheduler:032]: set_timeout(name='', timeout=100)
[15:04:31][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 2153922382
  state: YES
}
[15:04:31][VV][scheduler:226]: Running timeout '' with interval=100 last_execution=869049 (now=869154)
[15:04:31][D][switch:016]: 'Request Desk Height' Turning OFF.
[15:04:31][D][switch:055]: 'Request Desk Height': Sending state OFF
[15:04:31][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 2153922382
  state: NO
}
[15:04:37][VV][scheduler:226]: Running interval 'update' with interval=60000 last_execution=814817 (now=874818)
[15:04:38][VV][scheduler:226]: Running interval 'update' with interval=60000 last_execution=816082 (now=876090)
[15:04:41][VV][scheduler:226]: Running timeout '' with interval=15000 last_execution=864543 (now=879544)
[15:04:41][D][switch:016]: 'Raise Desk' Turning OFF.

HA Details
Up and down is working.

One last thing i noticed:
The desk usually is showing the height in inch not cm or mm when the display is working.

I also opend my controller board and checked my RJ45 layout. It matched the config from #Option 1

UPDATE:

I had to solder the TX pin of the controller to GPIO17 instead of GPIO3. No I’m getting the uart logs. I still facing the same issue as @jcastro. When looking at my logs the 5th and the 6th byte caltulate my desk height. Therefore i still cant see the height in HA. I managed to switch from inch to cm in the controllers settings.

@Mahko_Mahko @ssieb do you have any further tips how to get the height to work?

LOGS:

[20:43:51][D][switch:012]: 'Request Desk Height' Turning ON.
[20:43:51][D][switch:055]: 'Request Desk Height': Sending state ON
[20:43:51][VV][scheduler:032]: set_timeout(name='', timeout=100)
[20:43:51][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 2153922382
  state: YES
}
[20:43:51][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:51][VV][scheduler:226]: Running timeout '' with interval=100 last_execution=12504 (now=12610)
[20:43:51][D][switch:016]: 'Request Desk Height' Turning OFF.
[20:43:51][D][switch:055]: 'Request Desk Height': Sending state OFF
[20:43:51][VV][api.service:156]: send_switch_state_response: SwitchStateResponse {
  key: 2153922382
  state: NO
}
[20:43:51][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:52][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:52][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:52][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:52][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:52][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:53][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:53][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:53][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:53][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:53][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126
[20:43:54][D][uart_debug:176]: <<< 242,242,1,3,2,232,15,253,126

CONFIG:

uart:
  - id: desk_uart
    baud_rate: 9600
    rx_pin: GPIO17
    ##You can uncomment the debug section below to see UART messages.
    debug:
      dummy_receiver: true
      after:
        bytes: 9
      sequence:     
        - lambda: UARTDebug::log_int(direction, bytes, ',');

jcastro · May 16, 2024, 7:17pm

hi! I removed it completely a long time ago because it was never implemented, as a function to control the desk, so I gave up

Mahko_Mahko · May 16, 2024, 8:40pm

Interesting. So you’re the second person in addition to @jcastro who has a desk that uses a slightly different protocol.

The feature request for supporting that has been open for some time.

What I’d encourage you both to do is make a comment on the issue to help flag to @ssieb that there is still demand for the enhancement.

github.com/ssieb/esphome_components

Feature Request: Desky | Support Height Decoder Variant

opened 07:20AM - 09 Nov 22 UTC

OkhammahkO

Pasted from our discord chat. Let me know if you need any more info. -- We’v…e come across a desk which appears to be slightly different in one area. In summary (and to refresh)... Most desks send: - This protocol over the RJ45 port. Bytes 3 and 4 (of 4) are used for height. We use this in your component. https://discord.com/channels/429907082951524364/952464939480645642/957101799528095774 - This protocol over the R12 port (for Bluetooth dongle port), and bytes 5 and 6 (of 9) are used for height. This is not used by the desky component. https://discord.com/channels/429907082951524364/952464939480645642/957107106492850246 But what we’ve found with some Jarvis desks is that they appear to actually send the second “9 byte message” over the RJ45 port. Everything else appears to be the same (including how the bytes are used to calculate height. https://community.home-assistant.io/t/desky-standing-desk-esphome-works-with-desky-uplift-jiecang-assmann-others/383790/105?u=mahko_mahko So I think the feature request is to be able to select/switch the protocol. My thought was the revised config might look a bit like below? Thank you! ``` desky: #uart_id: desk_uart (optional, unless multiple uarts are defined) id: my_desky height_protocol_variant: (optional, 4byte or 9byte, defaults to 4byte) height: # optional sensor publishing the current height name: Desk Height # any other sensor options ```

You could also take a look at the Upsy Desky project and try to figure out if your protocol is already supported.

If you are willing to tinker in cpp I suspect it would be relatively small adjustments to this code section to just read bytes in two different positions.

github.com

ssieb/esphome_components/blob/b922726dae9cbb0e7945446610ca7aab808559f2/components/desky/desky.cpp#L37-L66


      
            while (this->available()) {
              uint8_t c;
              int value;
              this->read_byte(&c);
              switch (state) {
               case 0:
                if (c == 1)
          	state = 1;
                break;
               case 1:
                if (c == 1)
          	state = 2;
                else
          	state = 0;
                break;
               case 2:
                high_byte = c;
                state = 3;
                break;
               case 3:

This file has been truncated. show original

hraschan · May 16, 2024, 10:44pm

Thanks for your response. I will make a comment tomorrow. I also will check the c++ config. Maybe I can figure it out by myself. Not really into c++ but we’ll see.

Mahko_Mahko · May 17, 2024, 10:34am

ssieb is active on the development of support for this alternative protocol now (beta has been released), so if you still have some interest and the hardware, more testers would be helpful.

github.com/ssieb/esphome_components

Feature Request: Desky | Support Height Decoder Variant

opened 07:20AM - 09 Nov 22 UTC

OkhammahkO

Pasted from our discord chat. Let me know if you need any more info. -- We’v…e come across a desk which appears to be slightly different in one area. In summary (and to refresh)... Most desks send: - This protocol over the RJ45 port. Bytes 3 and 4 (of 4) are used for height. We use this in your component. https://discord.com/channels/429907082951524364/952464939480645642/957101799528095774 - This protocol over the R12 port (for Bluetooth dongle port), and bytes 5 and 6 (of 9) are used for height. This is not used by the desky component. https://discord.com/channels/429907082951524364/952464939480645642/957107106492850246 But what we’ve found with some Jarvis desks is that they appear to actually send the second “9 byte message” over the RJ45 port. Everything else appears to be the same (including how the bytes are used to calculate height. https://community.home-assistant.io/t/desky-standing-desk-esphome-works-with-desky-uplift-jiecang-assmann-others/383790/105?u=mahko_mahko So I think the feature request is to be able to select/switch the protocol. My thought was the revised config might look a bit like below? Thank you! ``` desky: #uart_id: desk_uart (optional, unless multiple uarts are defined) id: my_desky height_protocol_variant: (optional, 4byte or 9byte, defaults to 4byte) height: # optional sensor publishing the current height name: Desk Height # any other sensor options ```

hraschan · May 18, 2024, 12:59pm

I can confirm @ssieb work. I tried his solution with my Fully Jarvis Desk.

Everything works like a charm. @jcastro you could also try it now. Should also work with your desk.

How to update the repository:

Clean the Build folder of your ESP32 and reinstall the yaml file. This way the repository should update. You also could change your config in the following way and reinstall:

external_components:
#Fetch ssieb's custom component# https://github.com/ssieb/custom_components/tree/master/components/desky
  - source:
      type: git
      url: https://github.com/ssieb/custom_components
    components: [ desky ]
    refresh: 0s

Thanks again to the nice work of @ssieb and @Mahko_Mahko.

jcastro · May 18, 2024, 2:37pm

@hraschan would you mind sharing your whole config? I don’t have mine anymore. I’m using ESP8266 so I will just change the pin numbers. Thanks

hraschan · May 18, 2024, 2:44pm

Please keep in mind that i also configured my 4 memory buttons. As i remember you got the small controller. Therefor you don’t need them. Also make sure your uart config is right. I also changed that. Because I needed a different pin there as well.

esphome:
  name: standing-desk
  friendly_name: Standing Desk
  on_boot:
    priority: -100.0
    then:
    #Request a desk height update after boot.
      - delay: 5s
      - switch.turn_on: wake_desk_and_get_height
esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:
  level: VERY_VERBOSE
  # baud_rate: 0 #disable logging over uart
# Enable Home Assistant API
api:
  encryption:
    key: "lBXwa0ZuqNLMwW4rHZC0PhX7yCSeXnKencdECSKA1wY="

ota:
  password: "359fa6d122acb1d2dabc5366276edc66"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

external_components:
#Fetch ssieb's custom component# https://github.com/ssieb/custom_components/tree/master/components/desky
  - source:
      type: git
      url: https://github.com/ssieb/custom_components
    components: [ desky ]

uart:
  - id: desk_uart
    baud_rate: 9600
    rx_pin: GPIO17
    ##You can uncomment the debug section below to see UART messages.
    debug:
      dummy_receiver: true
      after:
        bytes: 9
      sequence:     
        - lambda: UARTDebug::log_int(direction, bytes, ',');
 
desky:
  id: my_desky
  ####################################################################################
  ##Uncomment this block to use Ssieb's move_to componet function.
  # up:    
    # number: 4 #D2
    # inverted: true 
  # down:  
    # number: 5 #D1
    # inverted: true
  # stopping_distance: 15  # optional distance from target to turn off moving, default 15  
  ####################################################################################
  height:  # Sensor publishing the current height
    name: Desky Height
    id: desky_height
    accuracy_decimals: 1
    unit_of_measurement: cm
    #any other sensor options
    filters:
    - delta: 0.05 #Only send values to HA if they change
    - throttle: 200ms #Limit values sent to Ha to 5 per sec.
    - multiply: 0.1 #convert from mm to cm
    on_value:
      then:
          #If the value changes, then the desk is moving
        - binary_sensor.template.publish:
            id: desky_is_moving
            state: ON
        - delay: 300ms
          #Assume it's stopped moving if no height changes after a short time.
        - binary_sensor.template.publish:
            id: desky_is_moving
            state: Off
            
binary_sensor:
  - platform: template
    id: desky_is_moving
    name: "Desky Is Moving"
    filters:
      - delayed_off: 400ms
    #If the desk isn't moving for a bit we better turn off attempts at movement. It's like poor man's collision detection? 
    on_release:
      then:
        - button.press: desky_stop_desk
substitutions:
  #Use your own ESP pin values
  desky_request_height_pin: GPIO18 #Request desk height | white wire  
  desky_purple_pin: GPIO16 #purple wire  
  desky_down_pin: GPIO22 #Move desk down | yellow wire  
  desky_up_pin: GPIO21  #Move desk up | green wire  

output:
  - platform: gpio
    pin: ${desky_up_pin}
    id: up_green_wire
    inverted: true
  - platform: gpio
    pin: ${desky_down_pin}
    id: down_yellow_wire
    inverted: true
  - platform: gpio
    pin: ${desky_purple_pin}
    id: purple_wire
    inverted: true

switch:
#wake up ther desk and request it sends its height 
  - platform: gpio
    id: wake_desk_and_get_height
    name: "Request Desk Height"
    pin:
      number: ${desky_request_height_pin}
      inverted: true
    on_turn_on:
    - delay: 100ms
    - switch.turn_off: wake_desk_and_get_height

#Raise the desk 
  - platform: output
    output: up_green_wire
    id: raise_desk
    name: "Raise Desk"    
    on_turn_on:
    #Auto off after 15s just in case
    - delay: 15s
    - switch.turn_off: raise_desk
#Lower the desk 
  - platform: output
    output: down_yellow_wire
    id: lower_desk
    name: "Lower Desk" 
    on_turn_on:
   #Auto off after 15s just in case
    - delay: 15s
    - switch.turn_off: lower_desk

button:
  # Combination Buttons
  - platform: template
    name: "Memory 1"
    id: button_1
    on_press:
      then:
        - output.turn_on: up_green_wire
        - output.turn_on: down_yellow_wire
        - delay: 300ms
        - output.turn_off: down_yellow_wire
        - output.turn_off: up_green_wire
  - platform: output
    output: purple_wire
    name: "Memory 2"
    id: button_2
    duration: 300ms
  - platform: template
    name: "Memory 3"
    id: button_3
    on_press:
      then:
        - output.turn_on: purple_wire
        - output.turn_on: down_yellow_wire
        - delay: 300ms
        - output.turn_off: down_yellow_wire
        - output.turn_off: purple_wire
  - platform: template
    name: "Memory 4"
    id: button_4
    on_press:
      then:
        - output.turn_on: purple_wire
        - output.turn_on: up_green_wire
        - delay: 300ms
        - output.turn_off: up_green_wire
        - output.turn_off: purple_wire
#Stop movement 
  - platform: template
    name: Stop Desk
    id: desky_stop_desk
    on_press:
      then:
        - switch.turn_off: raise_desk
        - switch.turn_off: lower_desk

jcastro · May 18, 2024, 2:50pm

Thanks! No I actually have the bigger controller with 4 memories. Will give it a try now

AJolly · May 19, 2024, 5:27pm

I’ve got mine on casters so clearly I’m not the right target audience but I still find this totally awesome.

Maybe whenever I get around to putting my 77" TV on a standing desk frame I do the same.

Mahko_Mahko · May 19, 2024, 9:49pm

This guy does some good desk reviews and tests including wobble tests.

Mahko_Mahko · May 25, 2024, 8:24am

There is some very cool rj12 port protocol decoding happening here.

Not sure if it applies to all models.

github.com/phord/Jarvis

IKEA MITTZON not receiving commands

opened 07:03PM - 21 May 24 UTC

closed 10:03PM - 21 May 24 UTC

Pereira98

I bought a pair of IKEA MITTZON Desks and I'm testing this protocol. I can read …the desk position when I manually move it via the handset but when I send commands nothing happens. It's worth pointing out that I'm using the RJ-12 port not the RJ-45 port. Through the FCC files, I can see that Jiecang has a new BT adapter that uses 5 pins so I checked the 5'th wire and it reads 3.3V. This wire is labelled in the BT adapter as "BKG". I'm not sure how to proceed from here since I don't own a BT adapter myself other than use the RJ45 port, but if someone can provide help I would rather use the RJ12 port. Link for the BT adapter I'm talking about: https://fcc.report/FCC-ID/2ANKDJCP35NBLT1 (Not sure if this BKG pin is relevant to my problem)

pereira98 · May 25, 2024, 8:30pm

I’m posting my progress here

pereira98 · May 27, 2024, 8:04pm

@Mahko_Mahko the cmd you tested not all were the new ones I found, some I believe were already known. But great to see you are already testing and something works!

I would like for you guys to test out the new cmd I found ands I can start a compatibility table based on your feedback.

I believe you guys lacked the stop command and the GoToHeight(mm) cmd, this later one works in my desks perfectly with soft stop accurate to the millimeter. I also think I found out how to change the memory presets to a desired hight, independently of were the desk is.

From my findings there are 2 adapters and 2 apps, I could not find an APK for the original app, just for the current one, so not all desks will be compatible with all of the commands I suspect, or maybe not and all of them work, better even, you guys share your findings

There are parts of the code I don’t understand yet, and there are things that I haven’t documented yet, I’m also planning on writing some custom code because I own 2 desks that are side by side, so I want to sync them, maybe even do a script for a celebration mode Tesla like ahah so more is coming than what I have now in my git.

As for my desks they are new here in my country at least, they are from IKEA, the MITTZON series, I believe there are 2 models 60 and 80 cm deep, I own the 80mm deep ones so I can only confirm that these use Jiecang hardware and they support the protocol via the RJ-12 port with no issues, just make sure to use the desk’s provided ground and not just wtv power supply you have for testing. For future compatibility it’s worth pointing out that my desks were bought the current year of 2024, future desks might look the same but with different hardware, who knows?

For users following the IKEA assembly instructions just make sure to pass half of a telephone cable like you did with the controller through the desks cable holes and connect to the F connector, BEFORE YOU ASSEMBLE THE TOP!!!

pereira98 · May 27, 2024, 8:30pm

Now about the RJ-45 port. If your goal is to completely upgrade the standard controls of the desk or just to reverse engineer the desk as you did yeah this is the correct port to use. If you don’t and just want to add wireless remote control and status report I think this is not the best option and should be avoided if your desk has the RJ12 port and this one works with the cmd you want to use. I have several concerns with the RJ45 approach:

1st - Warranty: my desks come with 10 years of warranty, so causing damage to any part of the desk is not an option.

2nd - Safety: I haven’t read everything on this forum since at this time I am a little busy but from my understanding you guys managed to control the desk without soft-stop, if I understand this right this could mean that the handset has like a “Lower Level” access to the desk’s controls, for exemple I haven’t managed to move the desk via the RJ12 connect without soft stop, so I suspect the RJ12 port has some kind of user error protection or at least is already designed by the manufacturer for remote access, in order for you guys to fix this again if my understanding is correct, you would need to make some sort of controller that could move the desk to a desired height but the desk already provides this for you. And I hope that the RJ45 port doesn’t let you send the desk higher or lower than possible, from my limited testing the RJ12 port doesn’t let you do nothing of those sorts.

3rd - Practicality: if your desk already provides a connector that is not in use it’s just more practical to go to the store, get a telephone cable and cut it in half, than to make a RJ45 adapter sniffer and put it between desk components. All I used is a raspberry pi pico w ~7€ and a standard telephone cable ~1€ maybe, 10€ max for the setup, all standard stuff fast to connect and go.

4th - Service Reliability: well this is pretty easy to understand, if you keep the standard controls connected always, you don’t loose your desk’s functionality while tinkering with stuff, this is especially important if the desk in question is not used by you, but used by others, like your wife/husband/girlfriend/boyfriend.