# Demandshaper EVSE timezone issue?

**URL:** <https://community.openenergymonitor.org/t/demandshaper-evse-timezone-issue/13917>\
**Category:** Emoncms\
**Tags:** emonevse, demandshaper, openevse\
**Created:** [20 April 2020 11:54 UTC](https://community.openenergymonitor.org/t/demandshaper-evse-timezone-issue/13917 "2020-04-20T11:54:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [23 April 2020 23:11 UTC](https://community.openenergymonitor.org/t/demandshaper-evse-timezone-issue/13917/5 "2020-04-23T23:11:04Z")

</div>

Hi Paul,

It’s important when using demand shaper that the timezone on Emoncms is set correctly, see Account page:

 ![Screenshot 2020-04-24 at 00.07.01](https://community.openenergymonitor.org/uploads/default/original/2X/b/b55cf226eeb66098bedaffd10b6202461f714985.png)

> [@borpin](#):
>
> How does EVSE communicate - via MQTT? if so, have a look at what it is actually communicating in terms of the date time string (or epoch time).

The demand shaper sends the start-end time to the OpenEVSE. The OpenEVSE currently does not handle timezone, all the timezone conversion is done on Emoncms.

In [WiFi 3.x (ESP32)](https://github.com/openevse/ESP32_WiFi_V3.x/) upgrade for the OpenEVSE this is due to change, the OpenEVSE will be able to handle timezone and update time automatically via NTP e.g

 ![Screenshot 2020-04-24 at 00.09.20](https://community.openenergymonitor.org/uploads/default/original/2X/9/92ce87fc997ebdd4139c20d9f8119f1365da1634.png)

---

_[View the full topic](https://community.openenergymonitor.org/t/demandshaper-evse-timezone-issue/13917)._