# Set incorrect time

**URL:** <https://community.homey.app/t/set-incorrect-time/93491>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [November 2, 2023, 1:44pm UTC](https://community.homey.app/t/set-incorrect-time/93491 "2023-11-02T13:44:31Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [January 31, 2024, 12:17pm UTC](https://community.homey.app/t/set-incorrect-time/93491/21 "2024-01-31T12:17:17Z")

</div>

Homey should use NTP to query remote servers for the correct time, but it looks like that’s not working for your Homey.

Do you have some sort of firewall active that might be blocking requests to any of these servers:  
[0.debian.pool.ntp.org](http://0.debian.pool.ntp.org) [1.debian.pool.ntp.org](http://1.debian.pool.ntp.org) [2.debian.pool.ntp.org](http://2.debian.pool.ntp.org) [3.debian.pool.ntp.org](http://3.debian.pool.ntp.org)

---

<div class="post-metadata">

**Author:** ![Dave\_vd\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dave_vd_w/32/99811_2.png) [@Dave\_vd\_W](https://community.homey.app/u/Dave_vd_W)\
**Post date:** [January 31, 2024, 1:34pm UTC](https://community.homey.app/t/set-incorrect-time/93491/22 "2024-01-31T13:34:36Z")

</div>

Thanks for the suggestion.

No blocking of any kind in the network. Is this different compared to Homey 2019?.. that device worked perfectly ever since 2019… ☹

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [January 31, 2024, 1:38pm UTC](https://community.homey.app/t/set-incorrect-time/93491/23 "2024-01-31T13:38:31Z")

</div>

The 2019 probably uses a different Linux distribution.

Perhaps you should contact Athom about this, because not only is your Homey’s internal clock not set to UTC, it’s also not synced.

---

<div class="post-metadata">

**Author:** ![Dave\_vd\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dave_vd_w/32/99811_2.png) [@Dave\_vd\_W](https://community.homey.app/u/Dave_vd_W)\
**Post date:** [January 31, 2024, 2:23pm UTC](https://community.homey.app/t/set-incorrect-time/93491/24 "2024-01-31T14:23:42Z")

</div>

Thanks, I just raised a ticket at Athom.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 31, 2024, 5:55pm UTC](https://community.homey.app/t/set-incorrect-time/93491/25 "2024-01-31T17:55:45Z")

</div>

Not sure if you tried to move the location pointer already?:

> [@Peter\_Kawa](#):
>
> the trick is to move it to a random location _in another timezone_, and move it back after a while.

This ‘forces’ Homey to set the correct timezone and time

[Previous page](https://community.homey.app/t/set-incorrect-time/93491.md?page=1)