I have updated my script to gather the values now but how do I use mmsp.json to set up the remaining feeds? And is my node name of melcloud OK?
Scrub that. I restarted apache (I guess something was cached somewhere) and then could edit my melcloud device to be of the MyForest/MMSP ASHP type. It offered to create the feeds it did not yet have.
Two hiccups: the wrench on the web interface does nothing when clicked and the config/application-configuration.json only seems to use some Rate1 values, not the Rate2 as well. I also added RoomTemperatureZone1 to the heating chart: I know you don’t use it, but I think it’s nice to see what it does.
@mjr If you want to go crazy and send a PR for your changes I’ll see if it makes sense to merge them in, notably the RoomTemperatureZone1 change is probably useful for sensible people who have room thermostats or who benefit from the Ecodan one.
I’m not sure this is worth splitting out into a pull-request. The RoomTemperatureZone1 one is just the following added to config/application-configuration.js after TargetHCTemperatureZone1:
"RoomTemperatureZone1": {
"displayOptions": {
"label": "Inside",
"color": "purple"
},
"type": "feed",
"autoname": "RoomTemperatureZone1",
"engine": 5,
"optional": true,
"description": "The room temperature in Zone1 in degrees Celsius (°C)"
},
This currently has x60 in the input processing. How confident are you about that? It seems to be almost exactly double the amount consumed in the next report.
I treat the HeatPumpFrequency to be a percentage of the rated input power, i.e. between 0 and 100.
So, my 11.2 kW unit has a max input of 3.73 kW, so I multiply the frequency by 3.73 * 1000 / 100 to get the current power consumption in watts. It seems to track actual consumption reasonably well, better than the unit’s own estimate.
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 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?
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.
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!
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:
