I think it used to be something like Watt-hour in the next minute so multiplying by 60 gives you Watts. I know it made my head hurt.
However, these days it seems to be misleading so I’ve actually filtered it out in my “Post to EmonCMS” script.
For example, the heat pump is running, other stats are changing, but it’s still showing the value it was when we rolled over the hour (which was 52 minutes ago).
I just noticed that:
“DemandPercentage”: 100,
is in the device.json but it’s at 100 even when the heat pump is off so that’s not looking at all helpful either.
@mjr do we need to alter something in the system to keep you working with the news from you and @Timbones about it being a percentage?
I did a few tweaks to get the Inside looking the way I imagine you want it @mjr
Would you mind taking a look at this PR to see if you’d like it done a different way?
I checked out the add-inside-temperature branch because I couldn’t see how to do anything with that PR. That looked good, except for whitespace on the end of the RoomTemperatureZone1 json bracket.
Is there space to add it to the header next to the outside temperatures, too? Does anything special need to be done to add it up there?
By the way, the wrench doesn’t work for me.
You’ll probably find that DemandPercentage drops to 30% whenever it’s heating water. Compare it against WaterPump4Status.
The other value it drops to (70%? mine goes to 90%) doesn’t seem to correlate to anything useful.
It’ll be difficult to provide a sensible default multiplier to convert HeatPumpFrequency into approximate consumption, as it needs to be specific to whichever heat pump the user has installed. I’d suggest keeping it as a simple percentage, maybe documenting how to estimate consumption from it.
The ‘wrench’ icon has never worked for me either.
WaterPump4Status is always 0 for me: either my hot water heating is driven from the main pump somehow, or something isn’t connected properly.
Comparing it to OperationMode instead suggests that DemandPercentage drops to 30 a few minutes before heating water (most often 2 minutes, but sometimes 4) and remains there until it’s heated. However, sometimes water is heated while DemandPercentage remains at 100!
Ah, the perils of using Github’s web-based editor 
I’m probably biased because I live on my phone where there really isn’t even room for the current set!
Not really @mjr - it just needs a <td> something like this:
Fixed it up and merged it in for you. Hope that helps.
I know what you mean, but really, any two of Efficiency, Using and Producing would convey the same info and you only need whichever of Outside and Effective you actually use. Full details are on the graphs scrolling down.
Failing that, floating divs with a minimum width should adapt to screen width better than a table anyway. Three columns where possible, two where not, and so on. I’ll try to mock it up after I finish on a customer’s store front today, unless you scream that you hate the idea and it’s never getting merged.
I can now access the config, and select a bunch of settings I couldn’t before (like solar, which is nice). The main MMSP display still shows while editing the config, whereas other EmonCMS apps (e.g. My Heatpump) hide theirs while configuring. Not a huge issue, just seems a little odd.
I had to edit config/application-configuration.json to have engine = "0,2,5" to get some of my feeds to appear, as I’m using MYSQLTimeSeries (0) and PHPTimeSeries (2) for some of them.
(I’m not sure I’ve picked the right engines for my feeds, but I’m kinda stuck with them now).
Room Temperature is showing in the chart, though I need to fix the rounding of my data: 
Edit: looks like "fixed": 1 is missing from RoomTemperatureZone1’s “displayOptions”.
It works better after I add this line to the config:
That’s unexpected. I don’t see that. You aren’t being misled by the huge JPEG embedded on the config page are you?
Yep, that’s right.
Yeah, I have all my data stored externally so I can switch by dropping the feeds and replaying all my historic data.
Thanks.
I should mention that I use “Using” to compare how much it’s using relative to things like the cooker or the car. “Produced” probably not so interesting.
I look at the delta between “Outside” and “Effective” to make sure it looks sane given the conditions - notably I want to see it get bigger during a storm. I partly use it to see if the anemometer has blown off (again!)
That’s true, but you can’t really see them very well on the phone, so I tend to use the big round numbers up the top, especially if I’m just showing it to some poor person who doesn’t want me telling them about heat pumps
Let’s see what your mock-up looks like and we can make it look lovely for you @mjr
D’oh! - totally missed the fact that those charts aren’t from my own heat pump 
Thanks for the fixes.
How is the Efficiency being plotted? I get a slightly different shape when I plot CoP directly. Is there some smoothing or something?
MMSP app at the bottom, graph of CoP on the top, both to same scale [0 - 5] and size.
Enhancement ideas that I’m being too slow to investigate myself:
Yes, that sounds useful.
I did have it, but I took it away because I wasn’t using it. It’s normally late in the day when I use the app so I just look at today.
Have a look around the other apps and see how they name to help this app be vaguely consistent.
Yep, that would interesting. Well, especially back when I had that data
This might need to come from the server because if there’s a large time window the granularity of the data will mean you can’t really tell how much it was on/off in the segment. I think it does something like 800 chunks in the desired time window so you’d be safe doing it client-side whilst a chunk is less than one minute. Maybe non-integer-minute segments would still be wrong though.
Thanks for sharing.
