Show your dashboard

[dmellok]

Post the dashboards you're running on your panels. Photos welcome — the more the better. If it's bespoke, share the layout / widget list so other people can replicate.

A few prompts:

• What panel + client are you running?
• What widgets are on it?
• What's the room context? (where it lives, what it's for)

This thread is pinned so it stays near the top. Reply with whatever you've built.

[vkawai]

Still a WIP, but got the dash running!

[dmellok]

Fantastic! :D

[JosemyDuarte]

Really well done! I tried Inker and I had to hack my own HAOs installation and even then the plugins got me disappointed so didn't continue using it.

I'm still having troubles with the auto refresh not working reliably, but that's probably on the TRMNL plugin not waking up my Kindle.

Great job!

Widgets: Calendar + Weather + HAOs Temp + HAOs CO2

[dmellok]

Looks great! How are you running it on the Kindle, KOReader?

[JosemyDuarte]

Yes, Koreader with TRMNL plugin. But neither the server-side refresh nor the client-side refresh seems to do the work. Only the first connection works.

I have a XIAO 7.5 which I want to try flashing and see if I get it working. Need to find the time first tho

[dmellok]

Have you got a schedule or rotation set up? Both are in the top nav. Schedules for a cron-style refresh of the page (5–15 min is normal), Rotations if you want it cycling pages. Composer's "Send" is one-shot only.

If there's already a schedule and the panel still isn't repainting, paste what journalctl -u tesserae | grep -iE 'render|push' | tail -20 shows when it should fire.

[docbobo]

Still working on the actual dashboard but I love how easy it is with Tesserae...

[docbobo]

Played a little with the free canvas capabilities this morning...

[dmellok]

Looking great!!

[bablokb]

This is a Pi3 running with a Waveshare 7" 1024x600 touch HDMI display (using CircuitPython+PyGame in fullscreen mode):

What you cannot see: cables sticking out everywhere. Not very aesthetic, but a good model for developing touch support.

[bablokb]

The Pi5 with the new 10.1" display is up as a generic CP client. There are still some problems, though. The screen dimensions are not auto-detected by PyGame, so fullscreen mode does not work. Also, in contrast to the Pi3 this does not seem to work from remote with a ssh login. The PyGame emulation currently only support 656, so there is some banding visible. All of this is not related to Tesserae. In any case, it needs some more investigation.

[bablokb]

While the Pi5+10.1" display now works fine with PiOS-lite, the HDMI Waveshare display (with Pi3) doesn't. The SDL kmsdrm-driver does not seem to cooperate, even with a video= parameter. So there is some more testing to do (Pi3+Touch-Display, Pi3+standard HDMI monitor). This is not a top priority for me, since PiOS-lite is nice to have, but it is no showstopper if PiOS-desktop is required. It only makes documentation/instructions a bit more complicated.

[dmellok]

This may be the Waveshare rather than the Pi3: those panels ship sparse EDID, and kmsdrm builds its mode list from what the connector reports, so a video= hint can still fail. Worth confirming the lite image is on full KMS too (dtoverlay=vc4-kms-v3d in config.txt, not vc4-fkms-v3d).

Your standard-monitor test should settle it: if that works on lite, it's the panel's EDID, not the Pi3.

Agreed on the docs framing: desktop as the works-everywhere path, lite as a leaner option.

[bablokb]

Some more insights:

• Pi3 with standard monitor: also does not detect dimensions. Adding the legacy config.txt options framebuffer_width= and framebuffer_height= does help though.
• Pi3 with Waveshare 7" HDMI: the framebuffer options have no effect
• Pi5 with Pi-Touch-Display-2 10": detects correct dimensions
• Pi3 with Pi-Touch-Display-2 5": does not detect dimensions

So I still have a few tests to go: Pi5 with the monitor, the Waveshare 7" HDMI and the Pi-Touch-Display-2 5".

I also tried all possible combinations of dtoverlay=vc4-(f)kms-v3d, video= cmdline.txt option, various HDMI_xxx opions (for the Waveshare), and toggeling disable_fw_kms_setup=.

[dmellok]

Useful matrix. The split looks like Pi3 vs Pi5 rather than panel type: the Pi5 does all modesetting in the kernel, while the Pi3 still leans on the firmware, which is also why the legacy framebuffer_width= / framebuffer_height= options do anything at all there.

Before working through more config.txt combinations, it's worth checking what the kernel itself sees on the failing setups: cat /sys/class/drm/card*-*/modes, or modetest -c. If the connector lists modes and PyGame still doesn't pick them up, it's SDL's side. If the list is empty, nothing downstream is going to detect dimensions and setting the size in the client config is the honest fix.

Either way I wouldn't sink much more time into it. A documented size in the client config is a fine outcome for the panels that won't report one.

[bablokb]

it's worth checking what the kernel itself sees on the failing setups: cat /sys/class/drm/card*-*/modes, or modetest -c. If the connector lists modes and PyGame still doesn't pick them up, it's SDL's side.

/sys/... is always correct. SDL claims that the kmsdrm-driver uses values from the kernel. I am not sure if this is true.

A documented size in the client config is a fine outcome for the panels that won't report one.

In cosole mode, that does not work, at least not for fullscreen. I have to test if selecting window-mode with fullscreen dimensions actually works. With Wayland, it is different. Here the challenge is to convince the window-manager to overlay the window over the icon-bar. But that probably is just a configuration thing.

[dmellok]

Something I've been working on on the side. this is the Xteink X4 an esp32 based e-reader. I've modified @uxjulia's CrossInk firmware to add support for Tesserae to be shown as a sleep screen.

[jomud9]

Still WIP and I wish my ReTerminal E1002 could have more pixel, as traditional Chinese character did not look good with less pixel.

I also want to learn from all if I want to have a clear (white) background, which theme / paper? There are "noise" after rendering, but preview looked OK

[bablokb]

The first thing to try is to turn dithering off in the dashboard (you can find this under "advanced"). It might cause problems with the shaded areas, since these aren't native display colors but it is worth a try. And ideally you would also use a theme with a reduced colorset.

See also #112 and #113.