# Homey pro 2023 crashed

**URL:** <https://community.homey.app/t/homey-pro-2023-crashed/146573>\
**Category:** Questions & Help\
**Tags:** homey-pro-2023\
**Created:** [December 8, 2025, 6:07pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573 "2025-12-08T18:07:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 8, 2025, 6:07pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/1 "2025-12-08T18:07:15Z")

</div>

My homey pro 2023 gives a red breathing ledring since 5 december. Nice sinterklaas gift , not.

Anyways i tried all stuff allready.

No idea how to check what is crashing though.

I tried usb updating firmware, but it is the same 10.9.0 it allready has. Got a few disconnects as well, so I had to do it 2 times before it went ok.

Is there a way to upgrade to experimental firmware?

Any other way to get inside homey to check crashlogs etc ?

Any other ideas how to fix this ?

Would it help to wait for never firmware version as it seems backup also backups the system?

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [December 8, 2025, 6:14pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/2 "2025-12-08T18:14:29Z")

</div>

So you replaced the power adapter?

---

<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:** [December 8, 2025, 6:14pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/3 "2025-12-08T18:14:43Z")

</div>

Homey is literally a black box, no logs available (unless you root it).

But try a different power supply and/or power cable. The ones that originally come with Homey are known to be of bad quality.

---

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 8, 2025, 6:19pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/4 "2025-12-08T18:19:57Z")

</div>

offcourse i did

---

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 8, 2025, 6:22pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/5 "2025-12-08T18:22:54Z")

</div>

i did. 2.4 A 5.1 volt from my old samsung tablet and a newer one from samsung which i charge my galaxy 24 ultra with. both are good and working but no difference on the homey.

when I update firmware it get stuck on verify at the end of it.

edit: after a long time verify finished and found ok.

i just don’t want to factory reset and have to do everything again. 40+ devices and god know how many flows. i rather wait till new firmware or a way to put experimental firmware on it. backup has same firmware and stuff so that won’t help i guess.

---

<div class="post-metadata">

**Author:** ![Paddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paddy/32/120855_2.png) [@Paddy](https://community.homey.app/u/Paddy)\
**Post date:** [December 8, 2025, 6:42pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/6 "2025-12-08T18:42:35Z")

</div>

Can I ask a question? Does Homey keep backups of the configuration that can be restored in cases like this? @Da_JoJo

---

<div class="post-metadata">

**Author:** ![Paddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paddy/32/120855_2.png) [@Paddy](https://community.homey.app/u/Paddy)\
**Post date:** [December 8, 2025, 6:43pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/7 "2025-12-08T18:43:59Z")

</div>

@robertklep I am new and am considering Homey. Are there no logs?

---

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 8, 2025, 6:46pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/8 "2025-12-08T18:46:02Z")

</div>

nope. only if you make these in usb tool (which i forgot :-/, was running flawless since march ‘23) or have a backups subscription.

there are logs but not accessible when it crashed. logs only go so far. there is a app for more extended logs i thought. But yeah just the basics, not in dept.

---

<div class="post-metadata">

**Author:** ![Mike1233](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike1233/32/20991_2.png) [@Mike1233](https://community.homey.app/u/Mike1233)\
**Post date:** [December 8, 2025, 7:41pm UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/9 "2025-12-08T19:41:59Z")

</div>

The Homey 2023 needs a power supply with 2A and 5,2V.  
[https://homey.app/en-us/blog/start-of-may-development-blog-homey-pro-early-2023/](https://homey.app/en-us/blog/start-of-may-development-blog-homey-pro-early-2023/)

---

<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:** [December 9, 2025, 5:40am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/10 "2025-12-09T05:40:07Z")

</div>

> [@Paddy](#):
>
> Are there no logs?

Only when you root your Homey (which may or may not void your warranty). And apps that make extended logs (as @Da_JoJo suggests) only make logs from data available through the SDK/Web API, which is too high level and not helpful at all when trying to debug crashing issues.

---

<div class="post-metadata">

**Author:** ![Paddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paddy/32/120855_2.png) [@Paddy](https://community.homey.app/u/Paddy)\
**Post date:** [December 9, 2025, 6:37am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/11 "2025-12-09T06:37:02Z")

</div>

Do they take suggestions? Logs are pretty much essential.

---

<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:** [December 9, 2025, 7:17am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/12 "2025-12-09T07:17:18Z")

</div>

Homey has never in 10+ years had system logs made available to users, so I will not get my hopes up.

But feel free to try: [https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request](https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request)

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [December 9, 2025, 7:36am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/13 "2025-12-09T07:36:35Z")

</div>

I wrote a [TelemetryCollectorApp](https://community.homey.app/t/131546) that solves the log problem. The only downside is that the respective app developer also has to integrate it (the effort is about 10 minutes).

---

<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:** [December 9, 2025, 7:38am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/14 "2025-12-09T07:38:56Z")

</div>

> [@ChrisG](#):
>
> that solves the log problem

I think we’re talking about a completely different log problem here. Your app is unable to access the relevant information that might provide clues as to why a Homey is crashing.

---

<div class="post-metadata">

**Author:** ![ChrisG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chrisg/32/8825_2.png) [@ChrisG](https://community.homey.app/u/ChrisG)\
**Post date:** [December 9, 2025, 8:19am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/15 "2025-12-09T08:19:02Z")

</div>

> [@robertklep](#):
>
> Your app is unable to access the relevant information that might provide clues as to why a Homey is crashing.

I wrote an [API](https://community.homey.app/t/131548) for the app that runs in the Homey app process/container itself.

And there are already options for the process itself (such as uncaughtException), but I didn’t pursue this because I didn’t think Athom would be very happy about it and I wanted my app to be published.

---

<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:** [December 9, 2025, 8:31am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/16 "2025-12-09T08:31:43Z")

</div>

> [@ChrisG](#):
>
> I wrote an [API](https://community.homey.app/t/131548) for the app that runs in the Homey app process/container itself.

Homey apps run chrooted, you cannot access system logs from an app process. Within the chroot environment, there aren’t any logfiles.

---

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 9, 2025, 11:12am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/17 "2025-12-09T11:12:36Z")

</div>

Totally correct. Which sucks in my case (and probably some others). Already send numerous requests in the years since homey existed as beta.

But yeah i still need to know how i get experimental firmware on mine on usb mode. I do a simple guess that the problems is in the last firmware’s memory handling of apps which are loosened and altered in successive firmwares. Hence I thought it might be helpfull to try. As they should run in subcontainers it should not crash the homey itself and kill these automaticly or restart them. Either way it shouldn’t end up in crashing the core system. System is still accessible and working as i can make a full backup and upgrade firmware the same version. It boots a long time with white ring in the end resulting in a red breathing ring. Can only acces file system on usb and the ssh, running also in a container, is of no use. Getting root is another thing. Protection of the core system is pretty decent 🤔 .

I decided to wait for next firmware and see how that fares. Last option a factory reset but I will not be happy with that. Although it might be a good idea to check if the homey still functions 100%.

Any ideas welcome 🙏 (besides the obvious like powersupply etc

---

<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:** [December 9, 2025, 11:32am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/18 "2025-12-09T11:32:08Z")

</div>

> [@Da\_JoJo](#):
>
> Protection of the core system is pretty decent 🤔 .

Not really, it’s quite easy to get a root shell on Homey (explained [in this post](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678)).

---

<div class="post-metadata">

**Author:** ![Da\_JoJo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/da_jojo/32/8210_2.png) [@Da\_JoJo](https://community.homey.app/u/Da_JoJo)\
**Post date:** [December 9, 2025, 11:54am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/19 "2025-12-09T11:54:55Z")

</div>

thnx that’s interesting. I take it this runs in windows Unix subsystem as well. But yeah it is questionable if i can change things before it crashes.

---

<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:** [December 9, 2025, 11:56am UTC](https://community.homey.app/t/homey-pro-2023-crashed/146573/20 "2025-12-09T11:56:51Z")

</div>

The most important requirement that you need is the ability to read/write ext4 filesystems. The post suggests that this is possible from Windows, perhaps the Windows Linux subsystem can do this without any external app requirements.

[Next page](https://community.homey.app/t/homey-pro-2023-crashed/146573.md?page=2)
