I assume you are graphing temperatures from the API ? If so, a temperature of "128" degrees actually means "unknown" temperature. You will see 128 at the same time that the controller displays an hour glass. I actually have special case handling for 128 in my own graphing scripts for this reason so it doesn't cause a huge jump in my graphs...Although I don't know for sure, it's possible the controller also sends a temperature of "128" to other devices in the zone when the true temperature is unknown.
Do you have failsafe mode enabled in the controller ? One thing fail safe does is if the controller and heating/boiler BDR91's loose comms with each other for approximately one hour (which will bring on the red LED on the BDR91) the BDR91's will then automatically start cycling on at a 30% duty cycle so your house and pipes don't freeze due to a loss of comms...
However I have wondered aloud on this forum a couple of times whether comms loss between HR92's and Controller would also trigger any fail safe action, and nobody knew. Your graph seems to confirm this is the case - not long after the measured temperature of a zone went to unknown, the flow temperature request increased. And perhaps the brief high temperature requests are to cycle some water through the system to avoid freezing pipes.
In general I leave fail safe mode off during the summer and seasons where there is very low risk of freezing and only turn it on in winter (and especially if I'm away from home) when there is a significant risk of pipes freezing should comms fail.