ONVIF
Michael Tröger
Integration of IP cameras and encoders (ONVIF Profile S, T and G) in Symcon
Included Modules
- ONVIF Configurator
- ONVIF Digital Input
- ONVIF Digital Output
- ONVIF Discovery
- ONVIF Events
- ONVIF IO
- ONVIF Image Grabber
- ONVIF Media Stream
- ONVIF Recording
Version History
Version 2.61:
Important:
- New IO instances verify the HTTPS certificate of the device. Existing instances keep the previous behavior (no verification), the option "Verify HTTPS certificate" can be enabled in the configuration of the IO. Devices with self-signed certificates may then have to be operated without verification.
- The address of the event hook (now "/hook/ONVIF/
/ ") now contains a secret token and therefore changes. It is automatically registered again on the device during the update. If the address was entered manually elsewhere (e.g. port forwarding with path check), it must be adjusted there.
Security: - Discovery: Responses from devices are strictly validated, manipulated responses in the network could inject code into Symcon. Devices may still be reported by IP address or DNS name
- IO: Option "Verify HTTPS certificate" (enabled for new instances), also applies to the snapshot retrieval of the Image Grabber
- IO: The event hook only accepts messages with the secret token in the address
- Credentials are no longer shown in the debug output (Discovery, Image Grabber, Media Stream, HTTP headers of the SOAP requests)
- Image Grabber: Credentials are no longer part of the snapshot address
Bug fixes: - Recording: Recording jobs whose token contains characters such as "-" (e.g. "Cam1Rec0-1") were not created as status variables because of an invalid ident
Version 2.60:
- The descriptions of the ONVIF services (WSDL) were updated to ONVIF 26.06
- Relay outputs of devices with DeviceIO service could not be switched
- Digital Input: Events were not applied because of a faulty presentation of the status variable
- Digital Output: For devices with several data values in the event, the state of the output was possibly read from the wrong value
- If a device rejected a request without a SOAP response (HTTP 400), this was not detected as an error (e.g. "Renew without response" after a restart of the device)