Homey Self-Hosted Server on Unraid | Megathread

Homey Self-Hosted Server
22

I started everything from scratch as my data disappeared after host restart.

23

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

24

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.

25

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.

1 Like
26

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ā€¦. )

27

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).

28

Recreated the same issue on another unraid server and Truenas Server.

Also RRD Errors.

29

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