Adding the camera is just a matter of using the correct URL for your particular camera. The trouble is that there is no standardize way for the URL syntax of IP cameras. This means that it is going to be different for each camera manufacturer. The documentation that is therefore needed is from the camera manufacturer. The Meteobridge doesn't care what it is...it just wants a URL. But it is important to differentiate what the URL will provide as the URL can be for a live video stream or it can be for an image still shot. And this is what most people screw up. They try and give the Meteobridge a live video stream and that won't work. What you need is the image still URL for the camera. Another difficult part is that this URL documentation is often not included in the normal user manual for the camera. Often you need to seek this resource and it may not even be available on the seller website. That may seem strange until you realize that most camera brands are really not the manufacturer but rather just a reseller of some manufacturer's stuff. The seller isn't always concerned with providing every possible use for the IP camera. They usually provide a computer application and a mobile app and that is it. They don't want to complicate their support costs and training, so they reduce options. Basically this means that IP cameras have vastly more potential than what it may seem.
So often you are left to hunt for this extra documentation. But now that you know what you are looking for it isn't that hard to do a simple Google search: "so-and-so-brand IP camera API" or "so-and-so-brand IP camera image URL"...you get the idea. But if you know where to look you can directly go to one of the best sources for this, that is like a Wikipedia for camera API of all brands.
iSpy Connect Camera Connection Database:
https://www.ispyconnect.com/sources.aspxWell as good as that iSpy Connect resource is it can be daunting. It actually is my second best resource. I try to first find the official API from the reseller / manufacturer. It's good to know who the manufacturer is of the brand you have. One of the biggest manufacturers is Dahua. They are a Chinese company and they sell worldwide and you'll find a different brand slapped on a Dahua just about anywhere. But you don't want a Chinese manual and even if they had an English manual it probably would not be very good. So the largest Dahua reseller in the US is Amcrest. And they have API documentation. The neat thing is that it works for any other Dahua clone. It's all the same stuff. So the Amcrest API documentation is pretty good as you would expect.
Amcrest API Documentation (works for any Dahua clone brand)
https://s3.amazonaws.com/amcrest-files/AMCREST_CGI_SDK_API.pdfBut to save you the trouble here is the all important URL syntax for Amcrest (Dahua)
http://user:pwd@ip:port/cgi-bin/snapshot.cgiYou can often leave the :port number out so:
http://user:pwd@ip/cgi-bin/snapshot.cgiReplace user and pwd with the username and password. And replace IP with the IP address of the camera.
If you have a camera system NVR with many cameras you can actually pull an image from any channel.
http://user:pwd@ip/cgi-bin/snapshot.cgi?channel=X&loginuse=admin&loginpas=adminIn the above URL, you replace X for the camera channel that you want. But keep in mind that channel 0 is the first camera. So if you want camera 5 then that is actually channel 4. The ending loginuse= and loginpas= should stay as admin admin as that is the default login to the cameras. Usually when you set up an NVR there is no need to change these because the cameras are on an isolated network behind the NVR. You authenticate with the NVR in the beginning part of the URL.