At first sight, I don't expect any issue with the behavior you described.
You just have to know how you will deal with errors.
If D/E/F is not reachable for a while, you will receive error events. You have to think about how you will deal with these errors.
Yeah, I discovered this following the links to issue on this topic yesterday, thank you for this precision, it will be useful to be conscious of awaited problems with this solution.

It looks like what you want is getting the history of the last A/B/C/bufferSize values of D/E/F/externalAttribute.
You know you could also get that by reading D/E/F/externalAttribute history from D/E/F polling buffer history if D/E/F/externalAttribute is polled.
You can tune the poll ring depth property to configure the size of the polling buffer history.
You will get a timestamp associated with each value in the polling buffer history.

If you subscribe to change events, you will receive events only when the values will change (depending on your event settings).
You just have to configure the system for what you want to achieve.

If you keep the idea of creating A/B/C/Buffer attribute, you could initialize it by reading D/E/F/externalAttribute polling buffer history. That way, if A/B/C is restarted, it will retrieve the history and fill up the buffer immediately with the latest values. In this case, depending on how the polling buffer is filled, the polling buffer history might contain consecutive values having the same values.
Yes, it helps a lot. smile
I'm not sure adjusting the buffer size to big values will be possible without performance tradeoffs on libera hardware, which is why I though about a 2d device with independant buffer.
But perhaps this solution is possible, we will keep this in mind to check.
- Philippe