sam159/brotherql_grocylabels

Brother QL Grocy Label Printer Service

brotherql_grocylabels's Issues

Support for endless labels

Is it possible to add support for endless label rolls?

brother_ql returns label size as [x,0] for them
https://github.com/pklaus/brother_ql/blob/56cf4394ad750346c6b664821ccd7489ec140dae/brother_ql/labels.py#L89

So function

brotherql_grocylabels/app/imaging.py

Line 22 in 7d1c782

def createLabelImage(labelSize : tuple, text : str, textFont : ImageFont, textMaxLines : int, barcode : Image, dueDate : str, dueDateFont : ImageFont):

cannot create proper image.

I think of a workaround like set height of the label to NAME_FONT_SIZE multiplied by NAME_MAX_LINES plus feed_margin that can be received from ALL_LABELS.

Add support for `62red` endless labels

QL-820NWBc printers come with the 62mm endless tape which supports red. Without properly calling create_label within sendToPrinter in __init__.py, the printer will error due to an incorrect tape size. Remedy the issue by including the red parameter in the call. Review https://github.com/pklaus/brother_ql_web/blob/9e20b6dc/brother_ql_web.py#L201 for how the author of brother_ql implemented the red labels in their version of brother_ql_web

Error when setting LABEL_SIZE

I only have 62mm endless and 29x90 to go with. So I'm setting the label-size as environment variable.
My compose for grocylabels:

  grocylabels:
    image: sam159/brotherql_grocylabels:latest
    restart: unless-stopped
    environment:
      - PRINTER_MODEL=QL-720NW
      - PRINTER_PATH=tcp://10.16.0.20
      - LABEL_SIZE=29x90
    networks:
      - lab01
    ports:
      - 8000:8000

If I set any LABEL_SIZE, I get a CODE 400 due to timeout:

  "error_message": "cURL error 28: Operation timed out after 2001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://10.16.0.12:8000/print"

If I don't set LABEL_SIZE, the print is sent but the printer gives an error for wrong paper size.

Am I missing something?

The printer works fine, for example printing from the brother_ql_web-dashboard works flawless.