Desk height and all other entities always eventually become unknown in Home Assistant about upsy-desky HOT 27 OPEN

Unfortunately my workaround did not work. Even if provided with an extra source of power via the USB-C port, it still goes completely unresponsive where the only fix is to unplug/replug the RJ-45 connector. I'm going to try the debug firmware again and hopefully something will show up in the log.

from upsy-desky.

Thanks, I installed that firmware

from upsy-desky.

I'm seeing this too with 1.0.0 but in my case re-plugging the Upsy Desky doesn't bring the entities back. HA can't see any entities from it anymore besides Status LED and Re-Detect Encoder. I've also done a factory firmware flash and its made no difference.

I can still operate the Upsy Desky from its web UI. I've got this connected to a Fully Jarvis desk.

from upsy-desky.

I'm seeing this too with 1.0.0 but in my case re-plugging the Upsy Desky doesn't bring the entities back. HA can't see any entities from it anymore besides Status LED and Re-Detect Encoder. I've also done a factory firmware flash and its made no difference.

I can still operate the Upsy Desky from its web UI. I've got this connected to a Fully Jarvis desk.

I ended up completely removing my upsy desky from HA to get it working again.

from upsy-desky.

HA can't see any entities from it anymore besides Status LED and Re-Detect Encoder

That's strange, were the old entities "unknown" or "unavailable"?

from upsy-desky.

@grahamwetzler In the history of the entities which become "unknown", do they become "unavailable" for a brief time beforehand?

from upsy-desky.

I'm not sure. Earlier today I moved away from the ESPHome configuration method and flashed 0.4.1 from the Github releases and it's been fine.

from upsy-desky.

It took a week of but it just happened to me on version 0.4.1. The entities all became unavailable then unknown. I guess I'll try version 1.0 again and see if it happens there.

from upsy-desky.

Unfortunately this is still happening on the version 1.0 file I downloaded from the Github release. Even using the reboot from the web ui does not bring back the entities in Home Assistant. The only way to temporarily get it to work is to replug the RJ45 connector.

from upsy-desky.

Sorry to leave you hanging here. If you're still experiencing this issue, I would suggest powering the device with an external USB power supply. Since the entities first become unavailable (indicates the device is totally unreachable) this suggests to me that your desk's control box may not be able to provide enough current to keep the Upsy Desky powered. Providing the additional power supply via USB-C will resolve this.

Let me know how it goes. If you still experience this after plugging in a USB-C power cable, try installing the debug firmware from the releases. Grab debug-firmware.bin and flash that via OTA. It will provide additional information in the logs, such as why the device was reset. Once the issue occurs again, grab the logs and provide them here.

from upsy-desky.

I believe I've come up with a workaround. I added an automation where any time the desk height becomes unavailable, I trigger a button press on the re-detect decoder button.

from upsy-desky.

I do see an issue right away. When first started, Decoder detection complete. Correct decoder variant: uplift showed up in the log. A few hours later I saw the height go unavailable in Home Assistant. I pressed a preset on my desk and I saw Decoder detection complete. Correct decoder variant: omnidesk pop up in the log

from upsy-desky.

Can you provide the information that appears in the "Device Info" sensor? I'm interested in the reset reason. It sounds like it might be restarting in the middle of the control box sending messages, and fail to detect the correct protocol. If you are familiar with ESPHome, you can also customize the configuration of the height sensor to always use the uplift decoder.

Also, what is the model number for your keypad?

from upsy-desky.

This info?

Firmware: 2023.2.4 (Mar 12 2023, 21:54:19)
Hardware: 1.0.0

I have this keypad

from upsy-desky.

There should be a sensor called "Device Info" under "Diagnostics" in Home Assistant (though, it looks like it's truncated to just "D..." because the value is so long lol):

from upsy-desky.

Oh I see,

2023.5.3|Flash: 4096kB Speed:40MHz Mode:DIO|Chip: ESP32 Features:WIFI_BGN,BLE,BT, Cores:2 Revision:3|ESP-IDF: v4.4.2|EFuse MAC: 3C:E9:0E:8B:49:D0|Reset: Software Reset CPU|Wakeup: Unknown

from upsy-desky.

Thanks for that. I'm not seeing any abnormal reset reason, which is strange. Can you try out this firmware? It bypasses detection and forces it to use the uplift decoder.

firmware.bin.zip

If possible, please keep the web UI open until the issue occurs, this way we have the full logs from start to finish as well.

If it doesn't work, then I suspect this may be a hardware fault of some kind; I can send you out another unit in that case. It could also be some difference in how the control box talks to your specific keypad — I have the same control box as you, but a very slightly different model of keypad. So I could purchase the one you have and do some testing myself.

from upsy-desky.

Unfortunately the current height and other entities are still going unknown after a few days. Once I press a key on the desk, the height does come right back at least.

from upsy-desky.

Coming here to report that this problem is still occurring on Version 2.0.0 of the firmware. I have a Fully Jarvis desk setup and I can control the desk for a while, and then the Upsy goes offline. No explanation why.

from upsy-desky.