Luminys IP CamerasN2/N3/N4/N5 does not allow access to all ONVIF Profile streams!

sharby

November 04, 2026 14:28

Just an FYI that Network Optix only has access to the bottom 3 resolutions in Profile000 on the Luminsys cameras. This isn't a VMS issue, but rather an implementation issue with the Luminsys existing ONVIF profile-S firmware. The workaround is to “Keep cameras streams and profile setting”.  Then you must log into the camera's web GUI and set desired streaming parameters. 

This is a PITA and not acceptable when adding multiple cameras into the system.

Here is the root cause when I test a Luminys camera using ODM:

QUESTION: There is an issue pulling an ONVIF Stream. When I select a different video streaming resolution, I receive a “Invalid address” error message. Why is this happening?

Answer from Claude:

The error comes from the camera rejecting an empty multicast address in the “change resolution” request. It isn’t a network or login problem.

What the capture shows

Each time you change the resolution, ODM sends a SetVideoEncoderConfiguration request to 10.1.0.58. The camera answers with this fault:

s:Sender → ter:InvalidArgVal → ter:InvalidIPv4Address

Reason: "Invalid address"

This happened on all three attempts: 1280×960, 2688×1520 and 352×240.

Why the camera rejects it

ODM first reads the current settings with GetProfile. The camera returns the video encoder’s multicast block with a blank address: <tt:IPv4Address></tt:IPv4Address>, port 0, TTL 0.

When you pick a new resolution, ODM edits only the width and height. It sends the rest of that configuration back unchanged, including <Multicast><Address><Type>IPv4</Type><IPv4Address/></Address>….

The camera’s firmware checks that field on write and rejects the empty value as an invalid IPv4 address. The request never gets as far as the resolution change.

So the camera hands out a configuration it won’t accept back. This is a firmware quirk (a non-compliant ONVIF implementation), and ODM is just echoing what it was given.

The resolution values aren’t the cause. All three requests carry valid ones, and 1280×960 and 2688×1520 are on the camera’s advertised list. 352×240 is not on that list, but the fault is about the address, not the size.

Streaming itself works. The RTSP sessions to rtsp://10.1.0.58:554/video/livemedia?Ch=1&Streamtype=0&unicast=true&proto=Onvif negotiate normally (OPTIONS, DESCRIBE, SETUP and PLAY over TCP). Only the settings write fails.

What to try

Change the resolution in the camera’s own web interface, or with the vendor’s app. That bypasses the faulty round trip.  DID THAT AND RESOLVES until VMS changes resolution back to 1920x1080

Update the camera firmware. This is the real fix, and the vendor may have patched the validation. NEED A FW Fix ASAP

Use a client that fills in a valid multicast address on write. Where the client lets you edit the multicast fields, setting something like 239.0.0.0 (or whatever the camera accepts) should get past the check. I can’t confirm from the capture that the camera accepts a specific value.

If you contact the vendor, quote the fault code ter:InvalidIPv4Address on SetVideoEncoderConfiguration together with the empty IPv4Address the camera itself returns in GetProfile. 

0

• 

  Norman

  • Network Optix team

  November 04, 2026 15:52 Edited

  Hi sharby,

  Thanks for the write-up.

  You mentioned that the VMS changes the resolution back to 1920x1080, which means the Media Server is writing to the camera successfully and is using similar Onvif requests. 

  Nx Witness also doesn’t use Profile000. When camera optimization is on, the Media Server creates its own two profiles on the camera:

  • Primary stream: the highest resolution and frame rate the camera advertises.
  • Secondary stream: a resolution close to 640x480, at 7 FPS. The VMS uses this stream for motion detection and adaptive scaling.

  The Media Server manages these profiles and keeps applying its settings, so any change you make in the camera’s web interface gets overwritten. Profile000 or any other profile only comes into play when you select Keep camera stream and profile settings. 

  In that case, Nx stops managing the camera and uses the profiles that already exist on it. That’s why you only see the limited Profile000 resolutions with the workaround. You can find more detail here: https://support.networkoptix.com/hc/en-us/articles/221031507-Managing-camera-optimization

  You don’t need the workaround or the camera’s web interface to change the resolution. Clear Keep camera stream and profile settings, then use the Desktop Client:

  1. In the resource tree, right-click the camera and select Camera Settings.
  2. Click the Expert tab and make sure Keep camera stream and profile settings is cleared.
  3. Click the Advanced tab.
  4. Set the resolution for the primary or secondary stream, then click Apply.

  The Media Server then applies your chosen resolution to its own profiles and keeps it. 

  The Advanced tab can only list the resolutions the camera reports to the VMS. If the resolution you need isn’t in the list, the camera’s ONVIF firmware isn’t advertising it. 

  Best regards.

  0

Please sign in to leave a comment.