u/TEEorCoffee2025

Local setup:
Paperless-ngx

Paperless-GPT

Ollama on DGX Spark

MiniCPM-V for OCR/image processing

Paperless-AI for metadata afterward

I noticed a consistent issue with searchable PDFs (PDFs with embedded text).
I tested the same document as:

1. Searchable PDF with embedded text

2. Image-only PDF version (pdf-> screenshot-> converted back to pdf with an online img to pdf tool)

Results:

Searchable PDF

-Can take a very long time to process

-Repeats the same paragraphs 100+ times in content

Image-only PDF

- Processes quickly

- Works correctly

Has anyone else seen this with MiniCPM-V or Paperless-GPT? If you're using Ollama + local vision models, what are you doing to avoid this with searchable PDFs?

I’m running Paperless-ngx with Paperless-GPT and occasionally hit an issue where table-heavy or dense documents get analyzed for 30–60 minutes, and the output ends up containing long repeated text blocks over and over again.

Setup:

Paperless-ngx (Docker)

Paperless-GPT triggered automatically via workflow tag

Vision model: MiniCPM (latest)

Metadata model (Paperless-AI): Gemma 4

GPU: NVIDIA DGX Spark (local Ollama)

Page limit already set to 6 pages max

OCR handled before GPT stage

Problem:

Some documents (especially tables or structured layouts) trigger extremely long processing and produce repeated text loops instead of clean extraction.

Hi everyone,

I’m trying to connect a Mitsubishi indoor unit via the CN105 port using an ESP32 dev board, but I’m only getting one-way communication and Home Assistant always shows the unit as “off”, even when I send commands (mode/temp/etc.).

I’ll attach a log screenshot showing the unidirectional communication.

Details:

Board: ESP32 DevKit

Baud rate: 2400 (also tested 9600, no change)

Already tried swapping TX/RX, no difference

Not using the CN105 12V pin

Wiring currently:

Pin 2 → GND

Pin 3 → 5V

Pin 4 → TX

Pin 5 → RX

ESP32 powered separately during testing as well

Symptoms:

Commands can be sent from ESP32

No response from AC detected

In Home Assistant, the climate entity always shows “off”

Changing mode/temperature does not update state

Questions:

Has anyone successfully used a standard ESP32 dev board with CN105?

Does this setup only reliably work with Wemos D1 Mini / ESP8266 instead?

Is one-way communication usually a wiring issue, logic-level issue, or ESP32 UART compatibility problem?

Are pull-ups or level shifting required on the CN105 RX line when using ESP32?

Would really appreciate hearing from anyone who got bidirectional communication working with ESP32 on CN105.