# Homey Self-Hosted Server on Unraid | Megathread
**URL:** https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565
**Category:** Homey Self-Hosted Server
**Created:** [December 8, 2025, 2:33pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565 "2025-12-08T14:33:59Z")
**Posts on this page:** 9
**Page:** 2
### Author:  [@bupemko](https://community.homey.app/u/bupemko)
#### Post date: [January 25, 2026, 10:32pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/22 "2026-01-25T22:32:35Z")
I started everything from scratch as my data disappeared after host restart.
---
### Author:  [@Robert\_Lewis](https://community.homey.app/u/Robert_Lewis)
#### Post date: [January 25, 2026, 11:24pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/23 "2026-01-25T23:24:22Z")
That is what I did
But would like to know form the developers what is the best way to restore if lost.
I had a back up and that didn’t work
---
### Author:  [@Sander\_P](https://community.homey.app/u/Sander_P)
#### Post date: [January 30, 2026, 7:14am UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/24 "2026-01-30T07:14:28Z")
I have contacted support already multiple times. The developers are saying by email; they providing 0 support.
They are in breach of (EU-guidline 2019/770 and 2019/771)
Under applicable EU and national consumer/contract law, digital software must conform to the agreement and function as reasonably expected, regardless of the existence of a 30-day trial period.
Meanwhile aniother crash:
`libuv-worker[1784632]: segfault at 0 ... error 4 in libc-2.31.so`
This means:
- **`libuv-worker`** tried to access memory it wasn’t allowed to
- It tried to access **address `0`** → basically a _NULL pointer_
- The crash happened **inside `libc` (the core Linux C library)**
- Linux killed the process to protect the system
**`segfault at 0`**
- The program dereferenced a null pointer
**`error 4`**
- Means _read access violation_
- The process tried to read memory it shouldn’t
**`in libc-2.31.so`**
- The crash occurred while executing code inside the standard C library
- Often triggered by bad data or a bug _earlier_ in the program
In human terms:
> “I tried to read data from nowhere.”
The CPU says:
> “Nope. That memory is protected.”
Linux then kills the program with a **segmentation fault**.
### Is this a “programmer mistake”?
Yes — **100% a software bug**.
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [January 30, 2026, 8:14am UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/25 "2026-01-30T08:14:06Z")
> [@Sander\_P](#):
>
> Yes — **100% a software bug**.
Does ChatGPT also explain _where_? Homey SHS? Docker? Linux? Everything is **software**.
Also, ChatGPT is lying, as segfaults can also be caused due to hardware issues.
---
### Author:  [@Sander\_P](https://community.homey.app/u/Sander_P)
#### Post date: [January 30, 2026, 8:32am UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/26 "2026-01-30T08:32:15Z")
ChatGPT….. ( never get anything usfull from AI )
True in this case its excluded as Mem-test does not indicate any issues. And disks are not reporting errors. Also if this would be the case I would see simular issues with other dockers.
`RRD Error updating RRD logId: homey:device:fd120575-f9b8-4d51-b7f1-ad25cd65ed30:meter_gas - file: /homey/user/rrd/e9cca471fe1c3f356b7f4548ca6883f8 - value: 3943.646 - timestamp: 1769684400:`
`Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:fd120575-f9b8-4d51-b7f1-ad25cd65ed30:meter_gas:`
`RRD Error updating RRD logId: homey:device:50122173-64d6-474e-945b-e5a68d85838d:meter_power.day - file: /homey/user/rrd/121f2a469f91b8bbb33d7655cdc2d003 - value: 0.38 - timestamp: 1769686200:`
`Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:50122173-64d6-474e-945b-e5a68d85838d:meter_power.day:`
`RRD Error updating RRD logId: homey:device:95eb2f18-58b2-4fbf-b110-7b6cd4860e7c:energy_power - file: /homey/user/rrd/a9a14f02f26b1afc1f8f4df9ac0ac517 - value: 0 - timestamp: 1769688000:`
`Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:95eb2f18-58b2-4fbf-b110-7b6cd4860e7c:energy_power:`
`RRD Error updating RRD logId: homey:device:fd120575-f9b8-4d51-b7f1-ad25cd65ed30:meter_gas - file: /homey/user/rrd/e9cca471fe1c3f356b7f4548ca6883f8 - value: 3943.985 - timestamp: 1769688000:`
`Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:fd120575-f9b8-4d51-b7f1-ad25cd65ed30:meter_gas:`
How ever i do see RRD errors that matches timestamp of crash.
This cause of this could be manny things.
- **Homey tried to write new stats into its RRD database and failed ?**
- **Corrupted RRD ?**
- **RRD refusing value written ? (Values look normal)**
- **App crashed mid-write ?**
- **Could indicate bad / buggy Homey App ? ( Homewizzard app ? )**
- **RRD Error updating RRD logId: homey:device:: looks like its failing for several devices but not sure its 1 App.**
- **1769688000 time stamp matches last fatal crash against unraid logs.**
- **My best guess currently is Homewizzard add is causing crashes – But testing to verify. Not sure how to match Device ID’s**
- **Is there a NTP sync issue with the clock ? ( or temp clock jump ? )**
**Im comparing this against the Test servers. To Validate the cause. ( Time consuming**…. )
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [January 30, 2026, 8:56am UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/27 "2026-01-30T08:56:33Z")
> [@Sander\_P](#):
>
> Could indicate bad / buggy Homey App ? ( Homewizzard app ? )
Apps don’t write Insights values directly, that’s all done through the SDK. It could be an issue with a corrupt RRD file, but that can never be the fault of an app. Apps also don’t run in the same process that writes to those RRD files, so even if an app crashes, it cannot cause RRD file corruption.
However, the issue occurs with multiple RRD files, not just one. It also happens at different times:
- 1769684400 → Thu Jan 29 12:00:00 CET 2026
- 1769686200 → Thu Jan 29 12:30:00 CET 2026
- 1769688000 → Thu Jan 29 13:00:00 CET 2026
So at least for an hour, and with different files (albeit all RRD-related).
You could try to stop the Docker container and remove all RRD files to see if that solves any issues, but it would basically mean a full reset of Insights (and I’m not 100% sure if Homey can handle RRD files not existing, but if you back them up first you should be able to restore them).
---
### Author:  [@Sander\_P](https://community.homey.app/u/Sander_P)
#### Post date: [January 30, 2026, 7:40pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/28 "2026-01-30T19:40:04Z")
Recreated the same issue on another unraid server and Truenas Server.
Also RRD Errors.
---
### Author:  [@bupemko](https://community.homey.app/u/bupemko)
#### Post date: [January 31, 2026, 5:03pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/29 "2026-01-31T17:03:45Z")
I had issues with Insights before I lost all my data as described above due to a mistake on my end when setting up the instance.
However since fixing the parameters and starting from scratch I have no issues (knocking on wood) - also have not tried setting up any Matter devices natively as reading here those seem to be somewhat unreliable currently, so for now I am sticking to the community and official apps, I have the following ones active:
1. Broadlink
2. Home Assistant Community
3. LG ThinQ
4. Meross
5. Sensibo
6. Shelly
7. Wake on LAN
8. Yeelights LAN
---
### Author:  [@Sander\_P](https://community.homey.app/u/Sander_P)
#### Post date: [February 3, 2026, 7:21am UTC](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565/30 "2026-02-03T07:21:34Z")
> [@Stephan\_Valkaer](#):
>
> e to transfer all my devices and
What hardware you running on ? i have 2 Unraid Servers that keeps crashing.
ASRock J4105-ITX - Non working
Intel N100 - Non working
0 support from Athom.
[Previous page](https://community.homey.app/t/homey-self-hosted-server-on-unraid-megathread/146565.md?page=1)