# Can't connect to Homey cloud

**URL:** <https://community.homey.app/t/cant-connect-to-homey-cloud/95823>\
**Category:** Vragen & hulp\
**Tags:** homey-pro\
**Created:** [November 26, 2023, 9:10am UTC](https://community.homey.app/t/cant-connect-to-homey-cloud/95823 "2023-11-26T09:10:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mario\_Truyens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mario_truyens/32/79282_2.png) [@Mario\_Truyens](https://community.homey.app/u/Mario_Truyens)\
**Post date:** [November 26, 2023, 9:10am UTC](https://community.homey.app/t/cant-connect-to-homey-cloud/95823/1 "2023-11-26T09:10:33Z")

</div>

Hi,

I have my homey for quite a while now, but had problems reconnecting it to wifi a while ago after a power failure and finally gave up. I moved it to a different location with a different AP, and now it can connect again but it also received a new IP (used to be 192.168.1.131 and now it’s 192.168.1.134). I can’t configure the DHCP to always deal out .131 for its MAC address, so I’m stuck with .134. Unfortunately, it also means it cannot connect to the cloud (homey says it’s unconnected and the web app also can’t connect) because athom seems to think that it should still use .131 to contact my homey (saw this using browser devtools). Shouldn’t homey broadcast its new IP to athom?

---

<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:** [November 26, 2023, 9:23am UTC](https://community.homey.app/t/cant-connect-to-homey-cloud/95823/2 "2023-11-26T09:23:53Z")

</div>

> [@Mario\_Truyens](#):
>
> Shouldn’t homey broadcast its new IP to athom?

Yes, it should, and you may have found the reason why so many people so often get a “Homey offline” message. It would be useful to create a support request to Athom with the information you’re posting here, so they _finally_ might be able to fix this long-standing issue.

---

<div class="post-metadata">

**Author:** ![Mario\_Truyens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mario_truyens/32/79282_2.png) [@Mario\_Truyens](https://community.homey.app/u/Mario_Truyens)\
**Post date:** [November 26, 2023, 10:22am UTC](https://community.homey.app/t/cant-connect-to-homey-cloud/95823/3 "2023-11-26T10:22:06Z")

</div>

I was planning to but then I saw that the predicted response time was 3 (!) weeks. But now I will, thanks!