Value Type Name seems to be not correct ? - by: Gunter

Read value with OpcCmd:

uaclient read opc.tcp://192.168.10.2:4840/Objects "ns=2;i=1001"

Reading...
Result (value): 608 {Int64} @2023-08-16T14:05:29.586 @@2023-08-16T14:05:29.586; Good
├─ServerTimestampLocal = 16.08.2023 16:05:29
├─SourceTimestampLocal = 16.08.2023 16:05:29
├─StatusCode = Good
└─StatusInfo = Normal
Command finished: read|r (0,5 seconds).

Value (608) is okay but the type (Int64) not. (is in real: UInt32)
Timestamp also OK

Same in Wireshark:

OpcUa Service : Encodeable Object
TypeId : ExpandedNodeId
ReadResponse
ResponseHeader: ResponseHeader
Results: Array of DataValue
ArraySize: 1
[0]: DataValue
EncodingMask: 0x0d, has value, has source timestamp, has server timestamp
Value: Variant
Variant Type: UInt32 (0x07)
UInt32: 2078
SourceTimestamp: Aug 16, 2023 15:51:02.756122000 Mitteleuropäische Sommerzeit
ServerTimestamp: Aug 16, 2023 15:51:02.756123000 Mitteleuropäische Sommerzeit
DiagnosticInfos: Array of DiagnosticInfo
ArraySize: 0

And the same variable readed over PubSub subscription:

[4]: Success; 9999-12-31 23:59:59.999,999,900,00; Good; Data; publisher=[UInt16]1, group=1, writer=1, origin=A2B2F6B86619, mapping=Uadp, fields: 2
Field data (sequence): 2 element(s)
╒══╤═══════════════════════╤═════════╤══════╤═════╤═════╕
│[]│Source │Server │Status│Value│Value│
│ │Timestamp │Timestamp│Code │Type │ │
│ │Local │Local │ │Name │ │
╞══╪═══════════════════════╪═════════╪══════╪═════╪═════╡
│#0│9999-12-31 23:59:59.999│ │Good │Int64│348 │
│#1│9999-12-31 23:59:59.999│ │Good │Int64│517 │
╘══╧═══════════════════════╧═════════╧══════╧═════╧═════╛

here also correct value but a wrong type and additional a wrong time stamp.
Are these config problems or bugs ?
Best regards
Gunter