I seem to have found a couple of undocumented features 
If I send a payload like this -
payload: object
ambient_temperature: 20.6
target_temperature: 12
mode: "user"
away: "false"
Nothing happens with the display until I send it again. If I send 2 different payloads the 2nd message causes the 1st msg to be displayed 
The input msg accepts numbers but if I change via gui the output is a string -
Can this be changed to a number ?
object
topic: "changed_state"
payload: object
ambient_temperature: 20.7
target_temperature: "19.5"
mode "user"
switch_state: "off"
away: false
EDIT
I had to add a trigger node on the output to only send latest msg after 2 second delay to stop it spamming my flow, also had to delete msg.socketid so that updates go to stats on all browser sessions.
You might consider adding these functions in to the template ?
There also seem to be some odd rounding errors eg
target temp of 20.1 and 20.2 is shown as 20.1
target temp of 20.3 and 20.4 is shown as 20.3
target temp of 20.5 is shown as 20.5
target temp of 20.6 and 20.7 is shown as 20.6
target temp of 20.8 and 20.9 is shown as 20.8
EDIT 2
Really sorry but I found another issue (may be related to above?)
If I have the same stat visible on multiple browsers, and adjust the setpoint so that the LED ring lights up on the browser I’m using, the other stats do not light up.
The change of setpoint is updated on each browser(after I send 2x message, without socket.id) but it requires a 3rd message to get the other browsers to light the ring up.
So I now have 2 trigger nodes set to repeat an incoming message 3 times at 500ms intervals, in order to get the stats to be responsive to changes.
Happy to help with beta testing
