Turn a spare screen into a useful monitoring kiosk

Define the screen’s one job

Choose the view the household needs most often: current energy flow, battery status or a general property view. Decide whether the screen is only for viewing or also for authorized administration. Keep a publicly accessible screen’s permissions limited to its purpose.

In Sunstead, a browser satellite displays the existing host’s data over the local network. It does not need to collect the inverter again. The host remains responsible for readings and local history.

Prove the ordinary browser path first

Before enabling full-screen startup, open the host’s displayed local URL in a normal browser. Confirm the property identity and advancing timestamps. Check the intended Wi-Fi or Ethernet path and resolve guest-network isolation if present.

Save a descriptive bookmark. If the screen cannot reliably load the page in an ordinary session, kiosk mode will mostly hide the browser controls you need for diagnosis.

Choose a supported kiosk method

Use the screen operating system’s documented method for browser startup and full-screen display. Raspberry Pi’s kiosk tutorial demonstrates the concept on Raspberry Pi OS. Its setup is for a separate kiosk environment, not an instruction to overwrite the Sunstead host image.

Browser kiosk mode is a presentation feature, not a complete security boundary. Physical access, operating-system access and saved sessions still matter. Keep a documented way for the responsible person to exit and maintain the screen.

Test interruptions that happen in ordinary use

Record any manual recovery step. “Tap the bookmark after startup” may be acceptable in a kitchen; it may be unsuitable for an unattended display at another property. Make that decision explicitly.

Tune the physical experience

Check brightness and glare at the times the screen is used. Test the layout at its actual viewing distance, including the freshness indicator. A giant battery percentage with an unreadable timestamp can make stale information look authoritative.

• Power and mounting suit continuous use.
• The browser is maintained on a supported platform.
• The view remains legible without awkward zooming.
• Touch or keyboard access matches the intended role.
• Restart and reconnect behavior are documented.

Keep the host and satellite roles in the handover. If the kiosk later freezes while another device sees fresh data, investigate the screen first. That single comparison can prevent unnecessary changes to equipment communications or the collector.