# Emoncms Demand Shaper module **URL:** \ **Category:** Emoncms\ **Tags:** smartplug, octopus, openevse\ **Created:** [9 November 2018 16:08 UTC](https://community.openenergymonitor.org/t/emoncms-demand-shaper-module/9097 "2018-11-09T16:08:34Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![TrystanLea](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/trystanlea/32/31_2.png) [@TrystanLea](https://community.openenergymonitor.org/u/TrystanLea)\ **Post date:** [12 March 2019 12:36 UTC](https://community.openenergymonitor.org/t/emoncms-demand-shaper-module/9097/5 "2019-03-12T12:36:57Z")
I’ve updated the original post above to reflect the current state of the demandshaper module. There has been a lot of work done to improve how the module works and talks to: smartplugs, openevse, heatpump control since the last update. A number of key changes are: - EmonESP used by the smartplug, wifi relay and heatpump monitor now uses a timer based scheduling command rather than simple on/off state. This means that once the device has been scheduled by the demand shaper module, the device can continue to follow the last set schedule independently of the basestation. - The latest EmonESP firmware allows for turning on/off the device and setting the timer in the EmonESP interface, the state is reported back to the demand shaper module, so that the state is kept in sync. - Initial device discovery is all done via the demand shaper module rather than having to go via the inputs interface. - The interface has had a significant overhaul to make it more responsive and usable on mobile devices - There are now new interfaces specifically for EV car charging and Heatpump control --- _[View the full topic](https://community.openenergymonitor.org/t/emoncms-demand-shaper-module/9097)._