@sl92656
Glad you like the binding and find it useful. If you have any feedback on what you found a hurdle to get it going please do so as I use it to update the readme and the binding and feedback from new comers is valuable as often when you program the binding you overlook how someone else thinks or expects something to work…
Great to hear as most people here don’t mind giving people help if they put the effort in to learn instead of wanting to be spoon fed.
Yes it is implemented but sadly not all cameras are truly ONVIF as there is no requirement to have a camera independently tested before it can advertise onvif compliance, often they passed a onvif 1.1 test and hence they put a label on the product when we are now at > 2.4 onvif version.
My Amcrest camera will report its position, but note that the binding only does this when the camera is connected for the first time, if you move the camera in a 3rd party app and want Openhab to reflect the change then this would need to be a feature request.
There is an example of how I do it in the readme file for my baby monitor. I use openhab to create the presets as this will be cleaner and more consistent between camera brands and also it allows you to learn the concept of SCENES which can be used for lighting in your home. It also means you don’t need to setup things in the camera and your backups contain a better snapshot of how your setup truly is. Do some searches in the solution forum for scenes and you will find posts like this one that will explain how to tackle things in new ways you may not have thought about…