Truncate MCU Temp?

[gtj0]

I'e noticed that, especially when idle, a continuous stream of events are generated solely because the MCU temperature continuously fluctuates by 0.1 degrees. Thoughts on truncating it to a whole number to reduce the event rate? I can't see where a 1/10th of a degree in the MCU temp would make any difference to anyone. Actually I can't see where it would make a difference on a bed or chamber either. Maybe it'd be a good idea to add a parameter somewhere to limit any temp output to whole numbers. I'm specifically talking about the websocket event stream, not any internal calculations or specific requests for temperature.

[T3P3Tony]

@gtj0

1. general point: DSF should, eventually, have different refresh rates for the object model on the SBC. although this is not a priority as the whole object model is refreshing well now.
2. why care? only subscribe/act on object model stuff that matters to you.

[gtj0]

@T3P3Tony said in Truncate MCU Temp?:

@gtj0

1. general point: DSF should, eventually, have different refresh rates for the object model on the SBC. although this is not a priority as the whole object model is refreshing well now.

Yeah the issue isn't on the SPI bus or Duet3 or SBC resources.

2. why care? only subscribe/act on object model stuff that matters to you.

Because I didn't know you could. The only websocket commands I see supported are PING and OK.
How would a web client indicate it's not interested in electronics.mcuTemp?

[T3P3Tony]

@gtj0 ahh I was thinking from an SBC perspective, rather than the web client.