Display Issues

This page covers issues with content rendering on display devices.

Content Not Showing

Symptom	Cause	Solution
Display shows pairing screen	Device not paired or unpaired	Pair the device to an endpoint
Display shows “No content”	Endpoint has no scene assigned	Assign a scene to the endpoint
Display shows old content	New version not published	Open the scene in Designer and click Publish
Display shows blank/black	JavaScript error in renderer	Open browser DevTools (F12) and check console

Content Not Updating

Symptom	Cause	Solution
Data-bound text shows stale values	SignalR connection dropped	Check device connectivity; renderer auto-reconnects
Published changes not appearing	Browser cache	Force refresh: `Ctrl+Shift+R` on the device
Some elements update, others do not	Incorrect data binding	Verify bindings in the Designer properties panel
Data updates on one display but not another	Different endpoint assignments	Check that both endpoints use the same scene

Rendering Errors

Symptom	Cause	Solution
Elements positioned incorrectly	Resolution mismatch	Ensure endpoint resolution matches the device’s actual resolution
Fonts not rendering	Custom font not loaded	Check font is uploaded in Media Library; verify font name spelling
Images not loading	Image URL inaccessible from device	Ensure device can reach image URLs; use Media Library for local storage
Video not playing	Unsupported codec	Use MP4 (H.264) or WebM (VP9) formats
Chart/gauge not rendering	Data binding returns null	Verify data is present in DataPool Explorer

Performance Issues

Symptom	Cause	Solution
Animations stutter	Device hardware limitations	Reduce animation complexity or use simpler transitions
Scene transitions lag	Too many elements on canvas	Simplify scenes; use components to reduce element count
Memory warning in device panel	Memory leak or too many images	Reduce image sizes; restart the renderer browser periodically

The Inspire renderer is optimised for low-power hardware and uses only 18.6 KB gzipped. If you experience rendering issues, the cause is usually data binding, network, or media-related rather than the renderer itself.

Debugging Tools

Browser DevTools

On the display device, press F12 to open browser DevTools:

Console — Shows JavaScript errors and warnings
Network — Shows data requests and WebSocket frames
Performance — Record a performance trace to identify bottlenecks

Remote Debugging

For devices without keyboard access:

Enable remote debugging in the endpoint settings
Navigate to chrome://inspect on a computer on the same network
Connect to the device’s Chrome instance
Full DevTools access remotely

Diagnostic Overlay

Press Ctrl+Shift+D on the display device to toggle the diagnostic overlay, which shows:

Current scene name and version
FPS counter
DataPool connection status
Memory usage
Network latency