-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WN17CM2 Support #8
Comments
Interesting, could you verify that the +5V and GND lines are on the correct positions? You can find the RJ45 pinout here. If they aren't in the correct place, you may need a special cable. |
Same for the WN17CM3, which I assume will have the same pinout. This is the controller for the Monoprice desks. |
https://www.kontive.com/products/lifting_table_part/17.html Maybe they can help. |
Honestly, I'm out of my depth here 😬 Providing power through USB-C was no problem, though. |
If anyone figures out the pin out for the controller, I can make a cable and test it out. |
Any instructions on how to test the pinouts so I can help move this along? |
@seanford I recommend getting an RJ45 breakout board like this one so you have somewhere to attach multimeter leads. Then follow this guide: https://github.com/tjhorner/wifi-desk-controller/wiki/Desk-Compatibility Basically, just use a multimeter to find the position of the +5V and GND pins. After that we can start figuring out which pins transfer which data, if it uses serial, etc. |
I have a desk with a WN17CM3 controller. The control pad is wired with an RJ45. I have found the following pinouts and color coding. Control panel wires
RJ45 pinout
Below are pictures of my evidence: |
With my just-arrived Upsy Desky, I see the same thing as @AnalogAyub.
I will double-check for the +5V and GND pins from the controller box. Once I've found that, will the device need a debug firmware installed? Or is there something I can change in the (very minimal) ESPHome config? |
I think RJ45 pin 2 is +5v and 3 is GND. I've also posted in the reverse engineering discussions area. |
i reverse enginieered the pinout and protocol some time ago, maybe this will help you: https://github.com/swoga/standingdesk |
@swoga Awesome. I’ve been wondering about this for years! Do you have any thoughts on how this could integrate into Upsy-Desky / ESPHome? |
@Jaharmi |
@swoga If this fit in with Upsy-Desky, I’d be a fan. :) That would give it things like the Upsy-Desky local Web interface. I already have an Upsy-Desky and just never figured out how to get from beyond the pinouts to do anything else. Looking at the related component, the C++ part is currently beyond me. |
@swoga Does this state diagram seem to handle what you found in the serial protocol for the WN17CM3? I am trying to understand the protocol and maybe do something with it. This is probably my first state diagram ever so I may have mixed it with a flow chart. stateDiagram
[*] --> CMDBEGIN
CMDBEGIN --> CMD: colon
CMD --> DISPLAY: D
CMD --> KEY: K
CMD --> REQUEST: R
CMD --> ACKNOWLEDGE: A
DISPLAY --> HEIGHT
HEIGHT --> HEIGHTCKSUM: decimal number as string
HEIGHTCKSUM --> CMDEND: semicolon
HEIGHT --> COMMAOPT: comma
COMMAOPT --> HEIGHTCKSUM
KEY --> DONTCARE
REQUEST --> DONTCARE
ACKNOWLEDGE --> DONTCARE
DONTCARE --> CMDEND: semicolon
CMDEND --> CHKSUM
|
hi @swoga could yo develop the custom component? I been trying for several weeks and nothing worked. |
Hi! I, too have this controller and have only been able ot get the UART messages to work with upsy desky. am I understanding correctly that more is still needed to make this unit work? Thanks - Bucket |
Unfortunately, I don't think it is going to happen. |
Is it safe to say that this control box will no be supported by Upsy Desky? Just wanted to know if I should continue to monitor this project for an update or just move on. |
Unless someone like @swoga can figure out a component that handles the communication, I don’t see it happening. Although I’m very interested in making it work, it’s beyond my current understanding. I’m still not sure why the Upsy-Desky doesn’t seem to get power from the WN17CM3 controller. It seems like that, at least, should be working, given the pinouts we’ve all found. I am not sure whether or not my Upsy-Desky’s RJ45 ports even work. I also don’t know if there’s a way to capture and decode the serial/UART communication. Maybe something could be done with the UART Bus component in ESPHome. 🤷 (It looks like this is what the Reverse Engineering Guide does.) |
Update: I set up the reverse engineering firmware with the UART settings from @swoga. Since I could not set a With this firmware, I was able to capture sequences that appear to correspond to the investigation by @swoga. I can confirm that the display on the connected keypad — which initially started out at I am attaching the following files:
Rough sequence of events from that test:
|
I refreshed the Upsy-Desky with similar firmware to what I used above, but changed back to the reverse engineering firmware’s Here is the log capturing in hex: upsy-desky-WN17CM3-uart-hex-logs-all-buttons.txt I followed the same rough sequence, trying to press each button at least twice. The display correctly showed the desk height when I connected the keypad and controller to the Upsy-Desky. It also updated as I raised and lowered the desk with the up/down buttons and presets. It also flashed when pressing the “M” button. |
I was able to set up the UpsyDesky easily, but the unit would not power on with just the RJ45 from the desk controller box. Once connecting a USB-C, the unit was detected by Home Assistant but would not control the desk or detect a height. Additionally, the desk keypad daisy-chained through the UpsyDesky would not control the desk.
Here's what the box looks like:

The text was updated successfully, but these errors were encountered: