NI IMAQdx inconsistent attribute values for GigE camera in "Listener Mode"?

[RSteinbrück]

After opening two sessions: 1st as Listener, 2nd as Controller to the same GigE vision camera on a single PC I observed for some attributes different values in both sessions.

For example:

-(A) A LabVIEW VI opens a "Listerner Session" and polls Attributes

   (I) StatusInformation::AcqInProgress

   (II) AcquisitionAttributes::AdvancedEthernet::BandwidthControl::ActualPeakBandwidth

   (III) CameraAttributes::DeviceInformation::TemperatureAbs

-(B) In NI Max I open the same camera ("Controller Mode") change DesiredPeakBandwidth from 1000 to 500, start to "Grab" and observe the 3 attributes in the tree control at the bottom.

Result:

(A)-(I) = False; (B)-(I) = True  (NOT consistent)

(A)-(II) = 1000; (B)-(II) = 500  (NOT consistent)

(A)-(III) = 52; (B)-(III) = 52  (consistent)

My idea was to implement a monitoring application that is operating in "Listener Mode" only, to collect status information of a bunch of cameras in our network. Now some informatin does not reflect the actual state of the camera. Some of the parameters seem to be per session some for the camera. Is this expected behavior? I'm still in the middle of a GigE-Vision learning curve. Any hints are welcome!

Test setup:

Camera: Basler acA1300-75gm

LabVIEW 2019 SP1, IMAQdx 19.5

Grabber-NIC: Basler GigE Interface Card, 4 Port PoE

[p4keal]

To be honest, I have only tried to work in listener mode once and failed...
From a practical point of view, I would recommend packing all attributes in the controller into a JSON string or something similar and publishing them in a shared variable, for example.
Basically, the cameras hold several settings (user sets) in their EPROM. But NI-Vision also has a local settings file for each camera that overrides the internal camera settings when you configure the acquisition. Unfortunately, I can't say which of these you will see in listening mode.

P.S.
If you have done a mistake in one of the settings and the camera does not start recording at all, you can sometimes simply fix this by loading a working user set.