Not convinced fast / partial refresh is working properly

[PaulOckenden]

I have a Seeed E1001.

With the GUI I'm only given the option of Full or Fast refresh, but in both cases the display flicker seems to be the same. I also tried adding 'partial' in the YAML, but again no effect.

I know that the display does do partial refresh because the option on https://opendisplay.org/firmware/toolbox/index.html works fine.

I'm running HA integration 3.0.0-beta.6 and the display is running OD 2.10

Anyone else seeing similar?

Thanks.

[jonasniesner]

I tested partial refresh and it worked properly in the latest beta

[PaulOckenden]

I'm not totally convinced that partial is working properly.

Latest beta and device firmware.

If I write "hello world" in full and then "hello world123" in partial the display shows " 123" (the initial 'hello world' has gone).

Unless I'm doing something incredibly stupid....

[jonasniesner]

Oh, that is a different error thank you for noticing. I pushed an update to the website and partial should work properly after you updated the display and configure it again(make sure to clear your browser cache before)

[jonasniesner]

Please let me know if that resolved it or did not resolve it

[PaulOckenden]

Thanks, I've updated both the display and the HACS files although I didn't notice any new versions.

But I've obviously got something wrong here because I keep getting:

Failed to upload to the display: PIPE_WRITE aborted: no ACK progress after 3 PTO probes

That's with the latest HACS integration and OD driver.

I'll try having another play later, because I can't see any other reports of this error so it must just be me!

But the E1001 seems to be talking to HA fine - if I press the buttons, for example, they are reported instantly.

P.

[jonasniesner]

That is not suposed to happen. does your display refresh at boot and does it work with the web tool?

[PaulOckenden]

Yes, the boot display is fine (displays correct version) and I can interact with the screen just fine using the OD web tool.

Later (when I have time) I’m going to try removing OD from HACS completely and then reinstalling it again.

I’m sure it’s just something gore wrong here else others would be reporting the same problem.

Thanks,

P.

[PaulOckenden]

Reinstalling the integration from HACS didn’t help.

When I try a simple drawcustom the script trace shows it properly waiting until the device next checks in, but when it does I get the error above.

Is anyone else here running an E1001 with ha HACS integration 3.0.0-beta.10 and the device itself running 2.26.1 ?

[davelee98]

the error you are getting above sounds like a BLE error. In the latest ESPHome there have been some bugs introduced that break BLE proxies. You may need to revert a couple versions (prior to 8.0) for proxies to work again.