Recurring connection errors #55
Comments
|
Are these errors being manifested through any symptoms like unavailable or unknown sensors? |
|
Yes, I believe so. The sensors go unavailable around the same time and then unknown a few minutes later. |
|
OK ... just confirmed... when this error occurs in the logs, all sensors in the UI go unavailable. A few minutes later, some sensors go to unknown (e.g. preset_1) and others go to their actual values (e.g. max_target_height). |
|
Thanks for confirming. I'm interested to know the following:
|
|
It seems to happen a handful of times per day. I'll try to keep better track over the next few days and let you know. I have an Uplift v2. I've had all this going for several months now but don't think I was getting this error until the past 30 days or so. Currently powering the board directly from the desk but have tried a separate USB-C power supply over the past few days. At first I thought that had fixed it, but after some time the errors resumed so I'm not sure it had any effect (hard to say, since it's inconsistent.) I currently have USB-C disconnected (and also haven't seen the error since my message ~5 hours ago ... but I'm sure it will be back!) |
|
OK - the answer is that this is happening quite often. Here are some times from error to sensor recovery from just 10 hours today: 6:36:43 -> 6:36:57 And here are the actual log messages: And here is my config: |
|
Hi @tjhorner, I'm going to go ahead and say this must be a power issue after all. Right after I sent you the update yesterday I plugged the USB-C power back in and the errors have been gone for over 24 hours. Still seems strange that it started to be an issue all of a sudden after using it without the external power for many months. |
|
Ugh - just kidding. I am continuing to see various errors like the ones above even with the USB power plugged in. Can't seem to find any pattern to why and when they pop up. However, I get no errors from my Bluetooth proxy, so it seems unique to this device for some reason. Any ideas? |
|
Something I'd like to try is collecting logs via USB - this will let us know if it's a true connection issue or if it's crashing for some reason. The easiest way to get logs via USB is through this page: https://upsy-desky.tjhorner.dev/docs/troubleshooting/#collecting-logs Keep that open until the device disconnects again, then you can save the logs for inspection. |
|
So I'm not positive I am doing this right... but for the past 24 hours, the only error showing up in the USB log is
And in the HA log, I see
This is the only error I've been seeing now... not the ones mentioned above. |
|
FYI ... this stopped for the past 3 weeks then restarted again yesterday. Super strange, and I'm not really sure if there's anything you can do about it since we don't know what causes it. Here's the most recent message:
|
|
Hey @tjhorner - these errors are continuing. Has anyone else reported something like this? Do you have any idea (or even a guess) as to whether the issue is with my device or with my Home Assistant? Here are the unique errors I've seen in just the past couple hours, and this is with USB-C power connected: |
|
After much experimentation, I'm happy to report I seem to have found a fix! Adding |
|
@jhemak Glad to hear that solved it! I'll see if this would be a reasonable addition to the stock firmware. Definitely will add it to the troubleshooting section as well. |
Troubleshooting Guide
Description
Hello, over the past couple weeks I have started to see errors like this in my log. Any idea what may cause or fix it?
Logs
No response
Which version of the Upsy Desky firmware config are you running?
4.0.0
How do you manage your Upsy Desky's updates?
OTA Updates
If you're using an ESPHome YAML config, which version of ESPHome are you running?
No response
ESPHome Config
No response
The text was updated successfully, but these errors were encountered: