Axis M3005 Camera

matt1 · September 2, 2020, 11:44pm

If your firewall / router allows the devices to use NTP servers they should update on their own if you have the right Timezone and daylight savings options set right. If still out change the Timezone to the wrong one until the time is lining up. This is a security feature of onvif to stop hackers from playing back recorded network traffic to turn off your cameras. Most cameras don’t seem to care but some do.

Edit: we should diagnose the problem first but your previous post seemed to have the onvif replies cut short. Any ideas why and does the log show longer replies back from the camera when the binding first starts and connects to the camera?

Daniel101 · September 3, 2020, 10:42am

Hi Matt - Once again Thank you for your help. Making progress.

1- Changed to Camera time to sync

Couple of additional errors.

2020-09-03 11:39:11.134 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [hls @ 0000029239cb5080] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2020-09-03 11:39:11.134 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [rtsp @ 0000029239a4e700] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8)
2020-09-03 11:39:11.135 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mpegts @ 000002923a424440] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2020-09-03 11:39:11.135 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mpegts @ 000002923a424440] first pts value must be set
2020-09-03 11:39:11.135 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - av_interleaved_write_frame(): Invalid data found when processing input

Daniel101 · September 3, 2020, 10:45am

Replay

2020-09-03 11:42:50.906 [DEBUG] [nding.ipcamera.onvif.OnvifConnection] - Openhabs UTC dateTime is:2020-09-03T10:42:50.905Z
2020-09-03 11:42:51.065 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-03 11:42:51.066 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Unhandled Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-03 11:42:56.267 [INFO ] [ing.ipcamera.handler.IpCameraHandler] - Binding has no snapshot url. Will now use your CPU and FFmpeg which must be installed to create snapshots from RTSP.
2020-09-03 11:42:56.268 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Starting ffmpeg with this command now:C:\IPcamera\bin\FFmpeg.exe -rtsp_transport tcp -threads 1 -skip_frame nokey -hide_banner -loglevel warning -i rtsp://root:xxxx@192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast -an -vsync vfr -update 1 http://127.0.0.1:6001/snapshot.jpg
2020-09-03 11:43:02.842 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [swscaler @ 000001a90eb383c0] deprecated pixel format used, make sure you did set range correctly

matt1 · September 3, 2020, 11:00am

So what happens now when you enter this url into any web browser?
http://openhabianpi:6001/ipcamera.jpg

Replace ‘openhabianpi’ with the IP address of openHAB if your not using openhabian on a pi or the url does not work.

Daniel101 · September 3, 2020, 12:23pm

I get a snapshot pic.

matt1 · September 5, 2020, 5:08am

So now you need to give the binding the correct snapshot URL for your camera so it does not use ffmpeg anymore.

I would like to get to the bottom of why your onvif replies in the log are cut short. Are you cutting them off or is the binding not getting a full reply back from the camera? This could be the root of why your having issues as that will stop auto discovery of the URLs if the full reply is not reaching the binding.

Daniel101 · September 5, 2020, 7:59pm

2020-09-05 20:55:24.043 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Starting ffmpeg with this command now:C:\IPcamera\bin\FFmpeg.exe -hide_banner -loglevel warning -i rtsp://root:xxx@192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast -strict -2 -f lavfi -i aevalsrc=0 -acodec aac -vcodec copy -hls_flags delete_segments -hls_time 2 -hls_list_size 4 C:\IPcamera\Camera1\ipcamera.m3u8

Daniel101 · September 5, 2020, 8:06pm

Once again thank you for your help.

Updated config:

Thing ipcamera:ONVIF:AxisM3005 “Axis M3005” @ “Cameras”

[

IPADDRESS="192.168.1.250", PASSWORD="xxxx", USERNAME="root", 

SERVER_PORT=6001, ONVIF_PORT=80,

ONVIF_MEDIA_PROFILE=1,

SNAPSHOT_URL_OVERRIDE="http://192.168.1.200:6001/ipcamera.jpg",

STREAM_URL_OVERRIDE="http://192.168.1.200:6001/ipcamera.mjpeg",

FFMPEG_LOCATION="C:\\IPcamera\\bin\\FFmpeg.exe",

FFMPEG_INPUT="rtsp://192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast",

FFMPEG_OUTPUT="C:\\IPcamera\\Camera1\\"

]

Daniel101 · September 5, 2020, 8:08pm

2020-09-05 21:05:07.915 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model ‘IPcamera.things’
2020-09-05 21:05:07.936 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:Unsubscribe
2020-09-05 21:05:07.956 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-05 21:05:07.957 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Unhandled Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-05 21:05:11.446 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - All Mjpeg streams have stopped, cleaning up now
2020-09-05 21:05:11.466 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Possible NIC/IP match found:192.168.1.200
2020-09-05 21:05:11.470 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - File server for camera at 192.168.1.250 has started on port 6001 for all NIC’s.
2020-09-05 21:05:11.472 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:GetSystemDateAndTime
2020-09-05 21:05:11.547 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-05 21:05:11.547 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:GetCapabilities
2020-09-05 21:05:11.548 [DEBUG] [nding.ipcamera.onvif.OnvifConnection] - Cameras UTC time is : 20:4:32
2020-09-05 21:05:11.548 [DEBUG] [nding.ipcamera.onvif.OnvifConnection] - Cameras UTC date is : 2020-9-5
2020-09-05 21:05:11.548 [DEBUG] [nding.ipcamera.onvif.OnvifConnection] - Openhabs UTC dateTime is:2020-09-05T20:05:11.548Z
2020-09-05 21:05:11.564 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-05 21:05:11.564 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Unhandled Onvif reply is:<?xml version="1.0" encoding="UTF-8"?>
2020-09-05 21:08:47.873 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Starting ffmpeg with this command now:C:\IPcamera\bin\FFmpeg.exe -hide_banner -loglevel warning -i rtsp://root:xxxx@192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast -strict -2 -f lavfi -i aevalsrc=0 -acodec aac -vcodec copy -hls_flags delete_segments -hls_time 2 -hls_list_size 4 C:\IPcamera\Camera1\ipcamera.m3u8
2020-09-05 21:08:50.637 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [hls @ 00000248b2b7c3c0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2020-09-05 21:08:50.637 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [rtsp @ 00000248b2b3e700] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8)
2020-09-05 21:08:50.637 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mpegts @ 00000248b2b95e40] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2020-09-05 21:08:50.637 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mpegts @ 00000248b2b95e40] first pts value must be set
2020-09-05 21:08:50.637 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - av_interleaved_write_frame(): Invalid data found when processing input
2020-09-05 21:08:54.875 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Starting ffmpeg with this command now:C:\IPcamera\bin\FFmpeg.exe -y -t 8 -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://root:xxxx@192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast -r 2 -filter_complex scale=-2:360:flags=lanczos,setpts=0.5*PTS,split[o1][o2];[o1]palettegen[p];[o2]fifo[o3];[o3][p]paletteuse C:\IPcamera\Camera1\ipcamera.gif
2020-09-05 21:08:56.551 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Recording 10 Seconds to MP4 format.
2020-09-05 21:08:56.551 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Starting ffmpeg with this command now:C:\IPcamera\bin\FFmpeg.exe -y -t 10 -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://root:xxx@192.168.1.250/onvif-media/media.amp?profile=profile_1_h264&sessiontimeout=60&streamtype=unicast -c:v copy -c:a copy C:\IPcamera\Camera1\ipcamera.mp4
2020-09-05 21:09:03.674 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mp4 @ 000002359e957040] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2020-09-05 21:09:03.675 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mp4 @ 000002359e957040] pts has no value
2020-09-05 21:09:03.675 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mp4 @ 000002359e957040] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.
2020-09-05 21:09:03.675 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [mp4 @ 000002359e957040] Non-monotonous DTS in output stream 0:0; previous: 1, current: 0; changing to 2. This may result in incorrect timestamps in the output file.
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF220400
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF4F0C00
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF661200
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF691F00
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF711800
2020-09-05 21:09:06.487 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - [Parsed_palettegen_3 @ 00000203bfc47380] Dupped color: FF7B2600
2020-09-05 21:09:07.665 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - Animated GIF has been created and is ready for use.
2020-09-05 21:09:09.679 [DEBUG] [hab.binding.ipcamera.internal.Ffmpeg] - MP4 has been created and is ready for use.
2020-09-05 21:09:15.411 [WARN ] [nding.ipcamera.onvif.OnvifConnection] - Camera did not report any ONVIF preset locations to the binding
2020-09-05 21:09:18.026 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Trying to move with new PTZ Absolute move.
2020-09-05 21:09:18.026 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:AbsoluteMove
2020-09-05 21:09:18.688 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Trying to move with new PTZ Absolute move.
2020-09-05 21:09:18.688 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:AbsoluteMove
2020-09-05 21:09:19.280 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Trying to move with new PTZ Absolute move.
2020-09-05 21:09:19.280 [TRACE] [nding.ipcamera.onvif.OnvifConnection] - Sending ONVIF request:AbsoluteMove

matt1 · September 6, 2020, 6:22am

hhhmmm not right You need to tell the binding where it can get the snapshot and mjpeg stream from. The snapshot is probably easy, just run the ‘Onvif Device Manager’ program and it should display the url for snapshots. The mjpeg stream you will be best to google for it.

Just be sure to test that the URLS work in a browser first before you expect the binding to use bad or broken links.

All of this would not be necessary if we worked out why the auto detection is failing. It does not make sense as the ONVIF replys are clearly working otherwise the binding would not be displaying the date and time that the camera reports. Can you give some trace log that shows the full startup and connecting to the camera for the first time. All the logs are not showing the beginning of making a connection.

Daniel101 · September 24, 2020, 5:17pm

2020-09-24 18:15:51.693 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.150:3702 => /0.0.0.0:59779, PooledUnsafeDirectByteBuf(ridx: 0, widx: 1442, cap: 2048))
2020-09-24 18:15:51.694 [INFO ] [camera.internal.onvif.OnvifDiscovery] - Camera found at xAddr:http://192.168.1.150/onvif/device_service
2020-09-24 18:15:51.785 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Cameras Login page is: Index page Your browser has JavaScript turned off.
For the user interface to work, you must enable JavaScript in your browser and reload/refresh this page.
2020-09-24 18:15:51.786 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘ipcamera:onvif:1921681150’ to inbox.
2020-09-24 18:15:51.787 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.150:3702 => /0.0.0.0:59779, PooledUnsafeDirectByteBuf(ridx: 0, widx: 1442, cap: 2048))
2020-09-24 18:15:51.787 [INFO ] [camera.internal.onvif.OnvifDiscovery] - Camera found at xAddr:http://192.168.1.150/onvif/device_service
2020-09-24 18:15:51.866 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Cameras Login page is: Index page Your browser has JavaScript turned off.
For the user interface to work, you must enable JavaScript in your browser and reload/refresh this page.
2020-09-24 18:15:56.893 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.150:3702 => /0.0.0.0:59779, PooledUnsafeDirectByteBuf(ridx: 0, widx: 1442, cap: 2048))
2020-09-24 18:15:56.894 [INFO ] [camera.internal.onvif.OnvifDiscovery] - Camera found at xAddr:http://192.168.1.150/onvif/device_service
2020-09-24 18:15:56.976 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Cameras Login page is: Index page Your browser has JavaScript turned off.
For the user interface to work, you must enable JavaScript in your browser and reload/refresh this page.
2020-09-24 18:15:56.977 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.150:3702 => /0.0.0.0:59779, PooledUnsafeDirectByteBuf(ridx: 0, widx: 1442, cap: 2048))
2020-09-24 18:15:56.978 [INFO ] [camera.internal.onvif.OnvifDiscovery] - Camera found at xAddr:http://192.168.1.150/onvif/device_service
2020-09-24 18:15:57.067 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Cameras Login page is: Index page Your browser has JavaScript turned off.
For the user interface to work, you must enable JavaScript in your browser and reload/refresh this page.
2020-09-24 18:15:57.070 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 292, cap: 2048))
2020-09-24 18:15:57.071 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 301, cap: 2048))
2020-09-24 18:15:57.071 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 295, cap: 2048))
2020-09-24 18:15:57.072 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 292, cap: 2048))
2020-09-24 18:15:57.072 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 301, cap: 2048))
2020-09-24 18:15:57.072 [TRACE] [camera.internal.onvif.OnvifDiscovery] - Device replied to discovery with:DatagramPacket(/192.168.1.101:1900 => /0.0.0.0:59781, PooledUnsafeDirectByteBuf(ridx: 0, widx: 295, cap: 2048))

matt1 · September 24, 2020, 8:17pm

That is discovery not what happens when the camera connects to the binding and goes from offline to online. If you change a config it will trigger this to occur.

Daniel101 · September 25, 2020, 10:59am

system · November 6, 2020, 3:09am

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.