Open Jolanrensen opened 2 years ago
Definitely on the roadmap! Will need an adapter cable as noted in #5.
Awesome! So same connector, different pinout. That's a bit more tricky than expected, but at least it's the same connector :)
I ordered one! Order number #351096 If you already have access to an adapter for that desk for me to try, please let me know! Otherwise I'm also willing to wait for the upsy desky until you can ship it together with an adapter. That's fine by me :) let me know how I can be of help @tjhorner
Upsy desky in the house! Now I just need an adapter :) (or a small guide on how to rewire the cables and make an adapter cable)
I'll move my software findings here, so the adapter research (https://github.com/tjhorner/upsy-desky/issues/5) can happen in the right issue. Using the adapter described in that issue and my adapted version from LoctekMotion_Iot: https://github.com/Jolanrensen/LoctekMotion_IoT/tree/main
I now have the following working:
I did find that we probably cannot use the upsy desky templates atm, since those assume setting a pin on/off will control the desk, while LoctekMotion (and more) desks require uart streams instead. We could however maybe generalize that to a switch that should be turned on instead since that's how I got it to work. Also, the target height seems to work very accurately :), no +0.4 needed.
Now, getting the screen and buttons to work is next. I'm curious to see what I can do with those. Since the target height works so well from home assistant, I might connect the buttons directly to home assistant as well, allowing them to map to anything you'd like to happen... Don't know yet. The LocktekMotion_Iot project simply captures the signal from the buttons and activates a switch which then sends the signal to the desk again, but the preset buttons don't seem to do anything for me atm, so I'm not sure where those presets are physically saved.
@tjhorner btw, is there a reason you use "return id(desk_height)->get_last_read() > x;" instead of "return id(desk_height).state > x;"? Is that for performance or for something else?
@Jolanrensen It's so the automation is more responsive. The state is published less often than the height is read.
Additionally fixed in my branch (https://github.com/Jolanrensen/LoctekMotion_IoT/tree/main)
Need to decide what to do with M, A buttons. Maybe I'll recreate some sort of save-function.
Pressing M and then 1, 2, or 3 saves the current desk height to the respective preset. Press M again (or any of the other buttons) to cancel. Unfortunately, the screen doesn't display that you're saving something since the saving functionality of the desk itself doesn't seem to work for me in this setup. Also, I've made button A just simply turn on a virtual switch and then turn off after 500ms, so you can automate anything you like in home assistant.
What's the status of Flexispot support? There's some decent looking ones on Amazon
@r14n I've been using my adapter and esphome file successfully for a couple of months now. It's not perfect but it works.
@r14n I've been using my adapter and esphome file successfully for a couple of months now. It's not perfect but it works.
Do you think it would work with this one? Bit hard to tell if the controller is RJ-45.
https://www.amazon.com/gp/product/B0CHVQ5LCL/ref=ox_sc_act_title_1?smid=A3686AOLDPXXOD&th=1
Which desk model do you have btw?
@r14n I've been using my adapter and esphome file successfully for a couple of months now. It's not perfect but it works.
Do you think it would work with this one? Bit hard to tell if the controller is RJ-45.
https://www.amazon.com/gp/product/B0CHVQ5LCL/ref=ox_sc_act_title_1?smid=A3686AOLDPXXOD&th=1
Which desk model do you have btw?
That looks like a completely different controller. Probably RJ-45 since most desks are controlled using that, but we can't be 100% certain. Might also require a different adapter compared to mine. I've got a HS01B-1 controller.
Are we able to identify this controller? Searching for your HS01B-1 is not really turning up useful results (as far as desks I can purchase right now)
Keypad: E2 Pro: 4 Presets Buttons with USB Ports
@Jolanrensen also, are you selling your adapter or willing to? Wishing for an "off the shelf" solution, as I'm familiar with homeassistant, but my electrical/wiring skills are very minimal. Seems like the upsy-desky isn't currently totally plug n play with flexispot. I'm also trying to keep my desk budget < $300 including additional "smart" hardware.
@Jolanrensen also, are you selling your adapter or willing to? Wishing for an "off the shelf" solution, as I'm familiar with homeassistant, but my electrical/wiring skills are very minimal. Seems like the upsy-desky isn't currently totally plug n play with flexispot. I'm also trying to keep my desk budget < $300 including additional "smart" hardware.
Haha I'm flattered, but my electrical skills aren't sell-worthy, plus I can't test it with your desk to see if it would work. Besides, my skills were minimal too before starting. I opted for the upsy-desky over a general ESP board since it already had a case and RJ45 ports. There are many toolless connectors that allow you to more easily make an adapter like mine, but nonetheless it will require some effort on your side. AFAIK there's no off-the-shelf solution for Flexispot desks.
Hi To follow this thread. I just bought an E7 flexispot with this screen A chance to get it work with Upsy ? What kind of job we have to produce for flexipot compatibility ?
Looks like most of the work is already done: https://github.com/iMicknl/LoctekMotion_IoT I think it would be awesome to have some sort of merge between these projects so that a clean all-in-one (no soldering) solution might also exist for Loctek desks. I would want to test, but unfortunately they're out of stock ;)