You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening a feature request to gain feedback on what features (if any) should be added and if they offer enough advantage (will they get used) to be used in rules and gain some testing on proposed solution on different peoples cameras.
What channels should there be?
What the channels should be labelled? 3 words to describe what the channel does.
Does the below work on your cameras?
Sending the camera http://192.168.1.x/cgi-bin/devVideoInput.cgi?action=getCaps&channel=0 does this give you caps.NightOptions=true ? We can remove the channels for cameras that return false that they do not support certain features.
The publically available Amcrest API states that NightOptions is not recommended anymore and that newer features are recommended instead, so if any of the older API is implemented, it should be made automatic to remove the channels on cameras that do not support them anymore. Example of some API features that could be used that are in the list of 'not recommended' is found here where an exact time for sunset and sunrise can be sent to the camera: https://community.openhab.org/t/ipcamera-new-ip-camera-binding/42771/2521
The new API has this to fetch the cameras settings: http://192.168.1.x/cgi-bin/configManager.cgi?action=getConfig&name=VideoInDayNight
Possibly the Sensitivity and Delay can be used to debounce the auto detection so that clouds do not trigger the change over when it is getting close to sunset, preventing a constant switching back and forth. Is it a matter of tweaking these values and no features are needed in openHAB, or does it make sense to add further ones? if so which ones?
The text was updated successfully, but these errors were encountered:
Opening a feature request to gain feedback on what features (if any) should be added and if they offer enough advantage (will they get used) to be used in rules and gain some testing on proposed solution on different peoples cameras.
http://192.168.1.x/cgi-bin/devVideoInput.cgi?action=getCaps&channel=0
does this give youcaps.NightOptions=true
? We can remove the channels for cameras that return false that they do not support certain features.The publically available Amcrest API states that NightOptions is not recommended anymore and that newer features are recommended instead, so if any of the older API is implemented, it should be made automatic to remove the channels on cameras that do not support them anymore. Example of some API features that could be used that are in the list of 'not recommended' is found here where an exact time for sunset and sunrise can be sent to the camera:
https://community.openhab.org/t/ipcamera-new-ip-camera-binding/42771/2521
The new API has this to fetch the cameras settings:
http://192.168.1.x/cgi-bin/configManager.cgi?action=getConfig&name=VideoInDayNight
Possibly the Sensitivity and Delay can be used to debounce the auto detection so that clouds do not trigger the change over when it is getting close to sunset, preventing a constant switching back and forth. Is it a matter of tweaking these values and no features are needed in openHAB, or does it make sense to add further ones? if so which ones?
The text was updated successfully, but these errors were encountered: