[GH-ISSUE #405] Solum 5.85-inch Display Not Fully Utilizing Screen with Google Calendar Script #2455

New Issue

sascha_hemi · 2026-03-20T21:06:41+01:00

sascha_hemi commented

2026-03-20 21:06:41 +01:00

Originally created by @MagnusErler on GitHub (Dec 7, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/405

Describe the bug
The Solum 5.85-inch e-paper display does not fully utilize the screen area when running the Google Calendar script. Portions of the display remain blank instead of being filled with content.

To Reproduce
Steps to reproduce the behaviour:

Flash the tag with the firmware: SOL_M3_Uni_ota_0029.bin
Set up and deploy the Google Calendar script as per the instructions
Upload the script to the tag
Observe the rendered display on the 5.85-inch screen

Expected behaviour
The entire screen area of the Solum 5.85-inch display should be filled with the content provided by the Google Calendar script.

Actual Behavior
The content does not fully occupy the display area, leaving portions of the screen blank.

Picture

Originally created by @MagnusErler on GitHub (Dec 7, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/405 **Describe the bug** The Solum 5.85-inch e-paper display does not fully utilize the screen area when running the [Google Calendar script](https://github.com/OpenEPaperLink/OpenEPaperLink/wiki/Google-Apps-Scripts#google-calendar). Portions of the display remain blank instead of being filled with content. **To Reproduce** Steps to reproduce the behaviour: 1. Flash the tag with the firmware: [SOL_M3_Uni_ota_0029.bin](https://github.com/OpenEPaperLink/OpenEPaperLink/blob/master/binaries/Tag/SOL_M3_Uni_ota_0029.bin) 2. Set up and deploy the [Google Calendar script](https://github.com/OpenEPaperLink/OpenEPaperLink/wiki/Google-Apps-Scripts#google-calendar) as per the instructions 3. Upload the script to the tag 4. Observe the rendered display on the 5.85-inch screen **Expected behaviour** The entire screen area of the Solum 5.85-inch display should be filled with the content provided by the Google Calendar script. **Actual Behavior** The content does not fully occupy the display area, leaving portions of the screen blank. **Picture** ![IMG_20241207_125328](https://github.com/user-attachments/assets/d681f38c-dfb6-4f73-af1d-52461dc67927) ![image](https://github.com/user-attachments/assets/0373cb49-d430-49bd-91d1-e831d2c8ff8a)

sascha_hemi added the bug label 2026-03-20 21:06:41 +01:00

sascha_hemi closed this issue

2026-03-20 21:06:41 +01:00

sascha_hemi commented

2026-03-20 21:06:42 +01:00

@nlimper commented on GitHub (Dec 8, 2024):

The 5.85" currently doesn't have its own templates for the resolution, so the content is not optimal. I sadly don't own a 5.85", so I cannot work on it. To create the templates, you can edit the /tagtypes/41.json file, and add a "template": {} section with the right coordinates for the content types. It can be a bit fiddly to do, but you will get a nicer layout. (after you edit a tagtype json file, you may have to restart the AP for it to work).
Instead, you can also alter in the 41.json file: "usetemplate": 47, by doing that, it uses the 4.3" tag as a fallback, which is more fitting for a start.

@nlimper commented on GitHub (Dec 8, 2024): The 5.85" currently doesn't have its own templates for the resolution, so the content is not optimal. I sadly don't own a 5.85", so I cannot work on it. To create the templates, you can edit the /tagtypes/41.json file, and add a `"template": {}` section with the right coordinates for the content types. It can be a bit fiddly to do, but you will get a nicer layout. (after you edit a tagtype json file, you may have to restart the AP for it to work). Instead, you can also alter in the 41.json file: `"usetemplate": 47`, by doing that, it uses the 4.3" tag as a fallback, which is more fitting for a start.

sascha_hemi commented

2026-03-20 21:06:42 +01:00

@MagnusErler commented on GitHub (Dec 8, 2024):

Thanks for the guidance. I will try editing 41.json

@MagnusErler commented on GitHub (Dec 8, 2024): Thanks for the guidance. I will try editing 41.json

sascha_hemi commented

2026-03-20 21:06:42 +01:00

@nlimper commented on GitHub (Dec 17, 2024):

fixed in https://github.com/OpenEPaperLink/OpenEPaperLink/pull/406
Thanks for fixing!

@nlimper commented on GitHub (Dec 17, 2024): fixed in https://github.com/OpenEPaperLink/OpenEPaperLink/pull/406 Thanks for fixing!

sascha_hemi commented

2026-03-20 21:06:42 +01:00

@MaxwellJK commented on GitHub (Oct 2, 2025):

Hi @MagnusErler I have the same tag - may I ask you what procedure you followed to flash it?
Thanks

@MaxwellJK commented on GitHub (Oct 2, 2025): Hi @MagnusErler I have the same tag - may I ask you what procedure you followed to flash it? Thanks

sascha_hemi commented

2026-03-20 21:06:42 +01:00

@MagnusErler commented on GitHub (Oct 3, 2025):

@MaxwellJK Follow the instructions here and choose nRF. If you have any other questions, please open a new issue

@MagnusErler commented on GitHub (Oct 3, 2025): @MaxwellJK Follow the instructions [here](https://github.com/OpenEPaperLink/OpenEPaperLink/tree/master/Tag_Flasher) and choose nRF. If you have any other questions, please open a new issue

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2455