When device is connected with controller, along with controller-attribute-value-change notification, we also seeing another device-attribute-value-change notification which is not valid.
Logs:
[20:57:25.170] DEBUG (1): received event: {"ietf-restconf:notification":{"notifications-1-0:attribute-value-changed-notification":{"new-value":"New value not yet defined.","attribute-name":"attribute-name-not-yet-defined","timestamp":"2024-03-21T21:57:25+01:00","counter":10,"object-path":"/core-model-1-4:control-construct"}},"event-time":"2024-03-21T20:57:25.168Z","node-id":"CO15338"}
[20:57:25.175] DEBUG (1): starting notification of 1 subscribers for '/v1/notify-device-attribute-value-changes', source-stream is OpenDayLight1 -> HTTP://x.x.x.x:xxx/rests/notif/device?notificationType=device
When device is connected with controller, along with controller-attribute-value-change notification, we also seeing another device-attribute-value-change notification which is not valid.
Logs: