Bug: rbusDateTime only supports second-level precision, cannot handle microseconds

[Sreedevi29]

Problem/Opportunity

For the speed test, we have the TR143 data model, which supports microsecond precision in order to get accurate results.

`root@:~# dmcli eRT getv Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
CR component name is: eRT.com.cisco.spvtg.ccsp.CR
subsystem_prefix eRT.
getv from/to component(eRT.com.cisco.spvtg.ccsp.tdm): Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Execution succeed.
Parameter 1 name: Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
type: dateTime, value: 2026-02-12T09:31:52.575889Z

root@:#
root@:#
root@:~# rbuscli -i
rbuscli> get Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Parameter 1:
Name : Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Type : datetime
Value : 2026-02-12T09:31:52Z
rbuscli> `

Using dmcli, we are able to retrieve the value with microseconds precision: 2026-02-12T09:31:52.575889Z. However, when using rbuscli, the value only returns up to seconds precision: 2026-02-12T09:31:52Z, so the microseconds are not included.

Cause:
Looking at the RBUS code (rbus_value.h):
https://github.com/rdkcentral/rbus/blob/develop/include/rbus_value.h#L92

The rbusDateTime type is implemented with time_t (or equivalent), which stores time in seconds since the epoch. As a result, any millisecond or microsecond information is discarded.

Would it be possible to extend rbusDateTime to support fractional seconds (milliseconds or microseconds)?

Steps to reproduce

No response

Expected Behavior

rbuscli> get Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Parameter 1:
Name : Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Type : datetime
Value : 2026-02-12T09:31:52.575889Z
rbuscli> `

Actual Behavior

rbuscli> get Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Parameter 1:
Name : Device.IP.Diagnostics.DownloadDiagnostics.BOMTime
Type : datetime
Value : 2026-02-12T09:31:52Z
rbuscli> `

Notes (Optional)

No response

[Sreedevi29]

@karuna2git, Could you please address this issue?

[karuna2git]

Hi @gladish , the PR#441 will not address it.

@gladish @Sreedevi29 ,
The rbusValue_t for RBUS_DATETIME format is as per ISO-8601 where this does not specify the millisecond/microsecond and rbus do not have it implemented.

We can define it to have microsecond accuracy and can be implemented.

[Sreedevi29]

Hi @karuna2git,

I’ve added changes to support microseconds in the RBUS_DATETIME parameter.

PR: #447

Could you please review the changes?

We have tested and validated them in our setup, but not yet on RPI. In the meantime, we will work on adding unit tests and testing on RPI as well.