-
re: 0.0.0.0 I would need to add some more logging to narrow down why it happens, but as you mention if you use the Openhab servers IP instead of the 0.0.0.0 it should still work.
-
Re delay on PTZ, yes I get around 8 seconds here on mine so some delay is to be expected but if it is really 30 seconds I would suggest you look at what the poll time is setup for the camera as it will wait until the next poll time before it starts to process the new location. If you have a 20 second poll time selected it will move faster if you drop that value down. I just looked at the logs and it appears the 3 location values are not set all at the same time? Are you just moving them manually? When set all at the same time in a rule they should all move at the same time after around 8-10 seconds if you camera behaves the same as mine. The readme has an example rule and how I setup buttons to make a camera jump to a set location.
@spudatron
Yes the binding needs a snapshot to determine if the camera is online or not so without one the camera will stay offline, otherwise you could use it for casting the cameras with HLS as these come from a rtsp source. I would personally get a better camera as the other features in the firmwares are very useful depending on your use case. You could work around it using a script or using the command action to call ffmpeg to generate snapshots or a non stop stream for openhab to use. This would use the rtsp feed as the source…
This will chew your CPU which wont be much for a snapshot. The other option would be to use a Pi and the motion software to keep the rtsp stream alive and generate what you need and would give you decent movement detection and more…