The CoP of the heat pump often seems related to the outside temperature.

However, that temperature is measured at the heat pump and so it's micro-climate affects the behaviour. Notably we see local cooling when the heat pump is running and local heating around defrosts.

This makes it hard to establish the behaviour of the heat pump relative to the larger mass of air surrounding it. We're measuring the heat pump's own internal sensor.

The app gained the ability to show an effective temperature in recent commit a03ecb7 .

However, that's only displayed, what we want is for it to be used in the CoP calculations.

We're assuming the user is finding a useful local effective temperature feed from something they trust to represent the mass of air near their heat pump.

The top line of the app shows when the heat pump is active, by shading the 'Space Heating' and 'Hot Water' symbols in red based on their respective pump activity. However, on my system, both symbols are always lit when either pump is running.

For example, right now, WaterPump4Status (hot water) is high, and WaterPump2Status (heating) is low, and yet both of them are highlighted in red. Which is generally not possible for this model of heat pump.

@MrTimbones and mjr have been pondering how to show the pump operation time:

https://community.openenergymonitor.org/t/heat-pump-experimentation-app-release-news/13423/47

This seems like a plausible and sensible enhancement.

It's hard to know what specific values a series has at a point in time.

It would be good to show them when hovering.

At the moment we fetch all the feeds as soon as one is updated on the server.

This means that if you have a feed updating every 6 seconds then we'll fetch the feed history (for the selected time window) for every feed every six seconds.

We should only refresh a feed's history if the feed history on the client is out of date.

Seeing a CoP of 7000% is worrying people and doesn't match how people think about the performance of a heat pump.

We should smooth the CoP out over 5 minutes so it looks more sane.

It's confusing even if there are ways to explain it.

There's also a bug where the CoP isn't shown for the first few readings.

The faint yellow line is hard to see amongst the more dominant power curves

Some algorithms work with an effective temperature rather than the actual outdoor temperature so we should make this visible on the app.

I'm also investigating how defrosts are affected by the dew point so we'll add that too.

Of course they only show if they are available.

• Effective
• Dew Point

After heating the hot water this morning (until 10:37), there was a sizeable gap between the end of that and the start of the space heating (11:10), yet the Efficiency chart still counts the new heat generated as being with the hot water. I would have expected those last two blue bars to be green...

Notably the:

• section headings
• time navigation
• current values with three digits or more
• the legend labels

all wrap in awkward ways. Ironically each seems to fail in it's own unique way.

We shouldn't include sensitive data in the URL because it's logged by web servers.

Also, we're echoing it into the HTML which is fine if you are using HTTPS but it does open you up to code that might sneak into the DOM and do bad things.

This app is intended to have lots of content and be scrollable so that code trying to make it fit the screen like a kiosk app isn't appropriate

At the moment the graph updating is switched on and off fairly grossly by the length of the time window.

It's particularly annoying if you go back in time and select a short window because the auto-updater starts up again and yo lose what you were working on.

When doing analysis over a long period of time it's nice to be able to see the graphs in a wider format.

At the moment the content container is restraining the graphs to 1150px.