Establish the source you control
Use a camera or media stream you own or have permission to access and present. Obtain its documented media endpoint from the actual device or publisher. A device management webpage is not automatically its media stream, and a visible camera image does not authorize publishing it elsewhere.
Record the stream format, intended viewers and the server that will fetch it. Keep credentials and private addresses out of public screenshots and examples. Start with one source so a failed import or unexpected guide entry is not obscured by hundreds of unrelated items.
Give the input an explicit identity
Channels documents custom M3U input for MPEG-TS or HLS sources, including a required unique channel-id. It warns that reused channel numbers can merge with another lineup’s channel. Choose an identifier and number deliberately and preserve them in the source inventory.
Do not borrow a commercial station identity for a personal camera. A label such as workshop entrance is more honest and easier to maintain. Use only the fields needed for the initial check; decorative metadata can be added after the identity and playback route are understood.
Separate list import, playback and programme data
Inspect whether the intended single channel appears, whether the server opens its stream and whether the viewer gets the expected picture and sound. Those are different results. If the list loads but playback fails, retain the working list result and investigate the media endpoint rather than repeatedly changing its display name.
If using fallback guide text, make it describe the source rather than inventing a broadcast schedule. A static title in a guide is not evidence that a camera supplies programme events, replay or an archive. Check any needed recording behavior separately and only within the permissions for that source.
Keep the small integration supportable
Channels documents a 750-channel limit and says its custom-source feature is not supported for large IPTV lineups. Keep the intended scope attached to the task. This is a personal-source integration, not a promise that the server accepts every subscription or authentication method.
Retain a private setup note with the source owner, format, identifier, chosen number and first verified stage. No camera, Channels server, media endpoint or recording was tested for this guide. The contribution is an original acceptance plan for a deliberately small authorized input.
Questions answered
Can I use the camera’s settings webpage as its stream URL?
Only if the device documents that address as the actual supported media endpoint; a webpage alone does not establish that.
Does a guide label prove an archive exists?
No. Placeholder metadata and available recorded media are separate.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.