IpCamera | Openhab 2 that allows you to use IP Cameras | Camera library

There are a number of ways to use snapshots with this binding. There are multiple advantages to using these methods from the binding instead of directly from the camera. See this forum thread for examples of how to use snapshots and streams in a sitemap. https://community.openhab.org/t/ip-camera-how-to-clickable-thumbnail-overview-in-sitemaps-that-opens-up-to-a-larger-view/77990. If you use Habpanel, then these widgets are worth checking out. https://community.openhab.org/t/custom-widget-camera-clickable-thumbnails-that-open-a-stream/101275.
Use the cameras URL so it passes from the camera to your end device ie a tablet, without passing any data through the openHAB server. This is always the best option if it works.
Request a snapshot with the url http://192.168.xxx.xxx:54321/ipcamera.jpg. The IP is for your Openhab server not the camera, and 54321 is the SERVER_PORT number that you specified in the bindings setup. If you find the snapshot is old you can set the gif preroll to a number above 0 and this forces the camera to keep updating the stored jpg in ram. This file does not exist on disk and is served out of ram to keep disk writes to a minimum with this binding. The binding can serve a jpg file much faster than a camera can directly, as a camera waits for a keyframe, then has to compress the data, before it can finally be sent. All of this takes time giving you a delay compared to serving the file from Ram and can make a sitemap or habpanel UI feel slow to respond if the pictures take time to appear. The ipcamera.jpg can also be cast, as most cameras can not cast their snapshots without using the binding.
Use the http://192.168.xxx.xxx:54321/snapshots.mjpeg to request a stream of snapshots to be delivered in mjpeg format. See the streaming section for more info.
Use the update GIF feature and use a preroll value >0. This creates a number of snapshots in the ffmpeg output folder called snapshotXXX.jpg where XXX starts at 0 and increases each poll amount of time. This means you can get a snapshot from an exact amount of time before, on, or after triggering the GIF to be created. Handy for cameras which lag due to slow processors and buffering, or if you do not want a hand blocking the image when the door bell was pushed. These snapshots can be fetched either directly as they exist on disk, or via this url format. http://192.168.xxx.xxx:54321/snapshot0.jpg Where the IP is your Openhab server and the port is what is setup in the binding as the SERVER_PORT.
The Image channel can be used but is not recommended unless the poll time is above 8 seconds as the image data passes through the event bus of Openhab that can create bottlenecks.
Also worth a mention is that you can off load cameras to a software package running on a separate hardware server. These have their advantages, but can be overkill depending on what you plan to do with your camera/s. Motion, Shinobi and Zoneminder are opensource projects worth checking out.
To create a tmpfs of 20mb at /tmpfs/ run this command to open the file for editing. Recommend using 20Mb per camera that uses this location although it could use less than half that amount if carefully streamlined for less ram. If using the ffmpeg -hls_wrap wrap option (causes issues for my Home Hub), you can get away with 5Mb per camera. Enter and save this at the bottom of the file using ctrl X when done.