# Separate DHW and Space heat monitoring **URL:** \ **Category:** Heatpump\ **Created:** [2 November 2023 18:07 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686 "2023-11-02T18:07:35Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [10 November 2023 19:50 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/21 "2023-11-10T19:50:14Z")
> [@ajdunlop](#): > > Are heatpump\_dhw and \_ch the watts separated out or a flag to indicate when in heating or ch mode? They’re zero vs. non-zero to indicate when they are on. > [@ajdunlop](#): > > I have a melcloud feed that includes the mode (think 1 is DHW and 2 is CH) You can set up a virtual feed like this to provide the appropriate signal when DHW is on: ![image](https://community.openenergymonitor.org/uploads/default/original/3X/3/c/3c1090eba02a08231c82e0bd9d51f51912364631.png) Personally I find it easier to use WaterPump2Status (heating) and WaterPump4Status (dhw), although cylinders with coils don’t have that 4th pump. ---
**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\ **Post date:** [10 November 2023 19:53 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/22 "2023-11-10T19:53:51Z")
Thanks, no I only have one pump so can’t use that. Maybe there could be a feed as well for defrost cycles? ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [10 November 2023 20:45 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/23 "2023-11-10T20:45:05Z")
> [@Zarch](#): > > Could the breakdown be moved directly under COP in Window? Like this? Appears when you click “Show detail”. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/5/a/5a95f235461730a5998943041abab8444792ce26.png) “Show flow rate” moved below the stats table. ---
**Author:** ![Zarch](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/zarch/32/7947_2.png) [@Zarch](https://community.openenergymonitor.org/u/Zarch)\ **Post date:** [10 November 2023 20:50 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/24 "2023-11-10T20:50:17Z")
> [@Timbones](#): > > Like this? That would be lovely!! ---
**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\ **Post date:** [10 November 2023 21:14 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/25 "2023-11-10T21:14:08Z")
Ok I think I must be just being a bit slow… where do I get a ‘If =, skip next’. I don’t see any logical operators in the list of available processes. ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [10 November 2023 21:28 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/26 "2023-11-10T21:28:20Z")
Ah - the public instance of emoncms might not have that those operators for virtual feeds. Does the input process steps have logical operators? It is possible to do the same thing with arithmetic operators too: (untested) **Heating** : 1. Add `-2` 2. Allow negative 3. Add `1` 4. Allow positive **Hot Water** ; 1. Add `-1` 2. Allow negative 3. Add `1` How are you getting the data out of melcloud? Can you do any preprocessing before posting it to emoncms, creating some extra inputs? ---
**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\ **Post date:** [10 November 2023 21:33 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/27 "2023-11-10T21:33:22Z")
Looks like I have the same options of inputs. Maybe it would be easier to add to my pymelcloud script as another Emoncms input. ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [12 November 2023 14:08 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/28 "2023-11-12T14:08:52Z")
Actually, if you’re scraping data from Melcloud, your best option might be `ValveStatus3Way` which I’m guessing will work whether you have coil or heat exchanger. I’d suggest sticking with `WaterPump2Status` for the heating signal. ---
**Author:** ![dMb](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/dmb/32/22999_2.png) [@dMb](https://community.openenergymonitor.org/u/dMb)\ **Post date:** [12 November 2023 14:11 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/29 "2023-11-12T14:11:11Z")
> [@Timbones](#): > > **Announcement** : My Heatpump app will now accept two extra feeds: > > - `heatpump_dhw` is used to separate out the power data when heating the hot water cylinder, and highlight those cycles on the power graph. Additional UI elements will appear, as detailed below. > - `heatpump_ch` is used to highlight heating cycles (optional: is not required to compute stats) Many thanks for this Tim; very nice. I’ve just added the feeds for my system this morning. One question about the intended usage for the \_ch flag when the heat pump is in ‘standby’ (ie. not actively heating _either_ DHW _or_ CH); should that be 1 (since it’s in ‘NOT hot water’ mode) or 0 (since it’s not actively delivering heating either)? I’ve gone for the latter, so my system spends quite a lot of time with \_dhw and \_ch both set to 0 and only flips them to 1 when the compressor is running for either one or the other. Is that what you had in mind? ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [12 November 2023 14:17 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/30 "2023-11-12T14:17:47Z")
I had intended for the `heatpump_ch` to be zero when it’s not heating. The `heatpump_ch` feed is not (currently) used to determine standby mode (we’re still using the power threshold for that), and is only used to highlight the heating cycles on the chart. It’s purely decorative. The COP for heating is worked out by subtracting the energy from DHW and standby. ---
**Author:** ![Zapaman](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/zapaman/32/22773_2.png) [@Zapaman](https://community.openenergymonitor.org/u/Zapaman)\ **Post date:** [12 November 2023 15:12 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/31 "2023-11-12T15:12:04Z")
> [@Timbones](#): > > - `heatpump_dhw` is used to separate out the power data when heating the hot water cylinder, and highlight those cycles on the power graph. Additional UI elements will appear, as detailed below. > - `heatpump_ch` is used to highlight heating cycles (optional: is not required to compute stats) So these are boolean feeds right? ---
**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\ **Post date:** [12 November 2023 15:19 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/32 "2023-11-12T15:19:55Z")
> [@Timbones](#): > > (self-hosted installs will need update the _Modules/app_ component) I’ve tried this on my emonpi and still don’t see the new feeds in the HeatPump app. ---
**Author:** ![dMb](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/dmb/32/22999_2.png) [@dMb](https://community.openenergymonitor.org/u/dMb)\ **Post date:** [12 November 2023 15:43 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/33 "2023-11-12T15:43:16Z")
> [@Zapaman](#): > > So these are boolean feeds right? Yep. 0 for ‘not heating’ and 1 for ‘heating’ for DHW and CH respectively. Here’s how today’s graph for my system looks after I configured these around 10:00 (so no yellow ‘CH’ shading for the 06:30 heating cycle. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/b/2/b2cfb2998041d1a8a01d1021ef4b56ac6f60a5f0.png) ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [12 November 2023 16:14 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/34 "2023-11-12T16:14:05Z")
Which branch are you using? I think only the `master` branch has these improvements at the moment. ---
**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\ **Post date:** [12 November 2023 16:15 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/35 "2023-11-12T16:15:28Z")
Whatever the default is - I just hit the update button. I’ll take a look. Need to work out how to create those boolean values as well … ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [12 November 2023 16:17 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/36 "2023-11-12T16:17:51Z")
> [@Zapaman](#): > > So these are boolean feeds right? The app considers zero to be off and non-zero to be on, so it might work with feeds that aren’t strictly boolean, so long as they are zero when off. ---
**Author:** ![MyForest](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/myforest/32/39418_2.png) [@MyForest](https://community.openenergymonitor.org/u/MyForest)\ **Post date:** [12 November 2023 16:38 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/37 "2023-11-12T16:38:20Z")
If you keep making enhancements like this @Timbones you’ll get to my dodgy app from four years I did before I found EmonCMS: ![image](https://community.openenergymonitor.org/uploads/default/original/3X/6/0/609ee51f0f5ac8cdd13efd21b7eab2b41ab38fe9.png) Next up: little snowflakes icons for defrost 🙂 When that’s working I expect to see seasonal themes: ![Happy Christmas](https://community.openenergymonitor.org/uploads/default/original/3X/8/d/8dd5ce6c1883b3687a1c1b82f4e82c54d604b658.png) ---
**Author:** ![Zarch](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/zarch/32/7947_2.png) [@Zarch](https://community.openenergymonitor.org/u/Zarch)\ **Post date:** [15 November 2023 13:17 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/38 "2023-11-15T13:17:18Z")
> [@Timbones](#): > > ike this? Appears when you click “Show detail”. > > ![image](https://community.openenergymonitor.org/uploads/default/original/3X/5/a/5a95f235461730a5998943041abab8444792ce26.png) > > “Show flow rate” moved below the stats table. Did this change happen Tim? I’m not seeing in on [emoncms.org](http://emoncms.org) ---
**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\ **Post date:** [15 November 2023 13:21 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/39 "2023-11-15T13:21:23Z")
Not yet, just waiting for [this pull request](https://github.com/emoncms/app/pull/187) to be merged (includes several other goodies). ---
**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\ **Post date:** [16 November 2023 09:55 UTC](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686/40 "2023-11-16T09:55:50Z")
Looks like it has been merged. How does this work? ![image](https://community.openenergymonitor.org/uploads/default/original/3X/0/a/0a3ed4c6bd5073d024ffdbfe128e45abe08afbdd.png) [Previous page](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686.md?page=1) [Next page](https://community.openenergymonitor.org/t/separate-dhw-and-space-heat-monitoring/24686.md?page=3)