In this thread we can discuss running Homey Self-Hosted Server on TrueNAS.
Installation
Learn how to Install Homey Self-Hosted Server on TrueNAS.
Known Limitations
None at this moment.
Hello
Very excited about the self-hosted option! I’ve got a Homey Pro (2023) and a Homey Bridge with MANY devices connected and extensive Flows controlling my whole house. I have been having some issues with flows fulling executing each step and I’ve been wondering if the Homey Pro has just been struggling a bit to process everything, so I am currently working on moving everything from my Homey Pro to Homey Self-Hosted on my TrueNas server, and subsequently also moving over my Homey Bridge to handle the Zigbee/Z-Wave/etc protocols.
My question is this, after doing a manual back up (via USB to my PC) of my Homey Pro, how can I then use that file to effectively “restore” my Homey system on the new self-hosted setup?
Thanks
Never mind. I see in a different thread that transferring settings/flows/devices/etc from HP23 to HSHS is not an option yet. Nor is using HP23 as a bridge. Bummer. Oh well. Thanks for always innovating though and making the barrier for entry easier to get through compared to Home Assistant. I look forward to being able to more easily migrate from HP23 to HSHS in the future.
Thanks
Just tried installing this in TruenNAS following the instructions and it fails to run. Anyone get this working?
2025-12-17 17:27:44.324364+00:00Service:dbus-daemon Starting…
2025-12-17 17:27:44.327819+00:00Service:dbus-daemon Started after 1 attempt(s)
2025-12-17 17:27:44.385161+00:00Service:rrdcached Starting…
2025-12-17 17:27:44.391129+00:00Service:rrdcached Started after 1 attempt(s)
2025-12-17 17:27:44.392366+00:00Service:avahi-daemon Starting…
2025-12-17 17:27:44.395626+00:00Service:avahi-daemon Started after 1 attempt(s)
2025-12-17 17:27:44.396414+00:00Service:homey-matter net.ipv6.conf.default.disable_ipv6=0 (0)
2025-12-17 17:27:44.396874+00:00Service:homey-matter net.ipv6.conf.default.accept_ra=2 (2)
2025-12-17 17:27:44.397270+00:00Service:homey-matter net.ipv6.conf.default.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.397779+00:00Service:homey-matter net.ipv6.conf.enp5s0.disable_ipv6=0 (0)
2025-12-17 17:27:44.398280+00:00Service:homey-matter net.ipv6.conf.enp5s0.accept_ra=2 (2)
2025-12-17 17:27:44.398738+00:00Service:homey-matter net.ipv6.conf.enp5s0.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.399074+00:00Service:homey-matter net.ipv6.conf.br-9859348f71b1.disable_ipv6=0 (0)
2025-12-17 17:27:44.399426+00:00Service:homey-matter net.ipv6.conf.br-9859348f71b1.accept_ra=2 (2)
2025-12-17 17:27:44.399727+00:00Service:avahi-daemon Exited with code 255 and signal null
2025-12-17 17:27:44.399891+00:00Service:avahi-daemon Unexpected stop. Exit code: 255. 1 stops within time frame
2025-12-17 17:27:44.399946+00:00Service:avahi-daemon Restarting…
2025-12-17 17:27:44.400004+00:00Service:avahi-daemon Stopping…
2025-12-17 17:27:44.400181+00:00Service:avahi-daemon Stopped
2025-12-17 17:27:44.400562+00:00Service:homey-matter net.ipv6.conf.br-9859348f71b1.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.401001+00:00Service:homey-matter net.ipv6.conf.br-b30c6ed4ea11.disable_ipv6=0 (0)
2025-12-17 17:27:44.401452+00:00Service:homey-matter net.ipv6.conf.br-b30c6ed4ea11.accept_ra=2 (2)
2025-12-17 17:27:44.401796+00:00Service:homey-matter net.ipv6.conf.br-b30c6ed4ea11.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.402032+00:00Service:homey-matter net.ipv6.conf.br-944ba1c1dfa3.disable_ipv6=0 (0)
2025-12-17 17:27:44.402367+00:00Service:homey-matter net.ipv6.conf.br-944ba1c1dfa3.accept_ra=2 (2)
2025-12-17 17:27:44.402637+00:00Service:homey-matter net.ipv6.conf.br-944ba1c1dfa3.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.402904+00:00Service:homey-matter net.ipv6.conf.br-dde2257e6a2c.disable_ipv6=0 (0)
2025-12-17 17:27:44.403159+00:00Service:homey-matter net.ipv6.conf.br-dde2257e6a2c.accept_ra=2 (2)
2025-12-17 17:27:44.403425+00:00Service:homey-matter net.ipv6.conf.br-dde2257e6a2c.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.403678+00:00Service:homey-matter net.ipv6.conf.br-96de67d7b511.disable_ipv6=0 (0)
2025-12-17 17:27:44.403922+00:00Service:homey-matter net.ipv6.conf.br-96de67d7b511.accept_ra=2 (2)
2025-12-17 17:27:44.404202+00:00Service:homey-matter net.ipv6.conf.br-96de67d7b511.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.404486+00:00Service:homey-matter net.ipv6.conf.veth523d567.disable_ipv6=0 (0)
2025-12-17 17:27:44.404777+00:00Service:homey-matter net.ipv6.conf.veth523d567.accept_ra=2 (2)
2025-12-17 17:27:44.405059+00:00Service:homey-matter net.ipv6.conf.veth523d567.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.405375+00:00Service:homey-matter net.ipv6.conf.veth6ed50fa.disable_ipv6=0 (0)
2025-12-17 17:27:44.405662+00:00Service:homey-matter net.ipv6.conf.veth6ed50fa.accept_ra=2 (2)
2025-12-17 17:27:44.405942+00:00Service:homey-matter net.ipv6.conf.veth6ed50fa.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.406241+00:00Service:homey-matter net.ipv6.conf.veth64e74cc.disable_ipv6=0 (0)
2025-12-17 17:27:44.406555+00:00Service:homey-matter net.ipv6.conf.veth64e74cc.accept_ra=2 (2)
2025-12-17 17:27:44.406867+00:00Service:homey-matter net.ipv6.conf.veth64e74cc.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.407163+00:00Service:homey-matter net.ipv6.conf.veth3b8467c.disable_ipv6=0 (0)
2025-12-17 17:27:44.407477+00:00Service:homey-matter net.ipv6.conf.veth3b8467c.accept_ra=2 (2)
2025-12-17 17:27:44.407808+00:00Service:homey-matter net.ipv6.conf.veth3b8467c.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.408132+00:00Service:homey-matter net.ipv6.conf.veth0b082f6.disable_ipv6=0 (0)
2025-12-17 17:27:44.408451+00:00Service:homey-matter net.ipv6.conf.veth0b082f6.accept_ra=2 (2)
2025-12-17 17:27:44.408786+00:00Service:homey-matter net.ipv6.conf.veth0b082f6.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.409121+00:00Service:homey-matter net.ipv6.conf.veth819fef3.disable_ipv6=0 (0)
2025-12-17 17:27:44.409455+00:00Service:homey-matter net.ipv6.conf.veth819fef3.accept_ra=2 (2)
2025-12-17 17:27:44.409769+00:00Service:homey-matter net.ipv6.conf.veth819fef3.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.410076+00:00Service:homey-matter net.ipv6.conf.veth3b17684.disable_ipv6=0 (0)
2025-12-17 17:27:44.410409+00:00Service:homey-matter net.ipv6.conf.veth3b17684.accept_ra=2 (2)
2025-12-17 17:27:44.410730+00:00Service:homey-matter net.ipv6.conf.veth3b17684.accept_ra_rt_info_max_plen=64 (64)
2025-12-17 17:27:44.411360+00:00Service:homey-matter Starting…
2025-12-17 17:27:44.415132+00:00Service:homey-matter Started after 1 attempt(s)
2025-12-17 17:27:44.415499+00:00Service:homey-matter:socket Connect Called
2025-12-17 17:27:44.667183+00:00Service:homey-matter:socket Connecting to: unix:/run/homey-matter.sock
2025-12-17 17:27:44.672330+00:00Service:homey-matter:socket Connected After 1 attempt(s)
2025-12-17 17:27:46.941846+00:00Failed to start required daemon: Socket /run/avahi-daemon/socket Unavailable After 2500ms (50 attempts)
I got it working on my TrueNas. My only issue was the first step of unchecking the mDNS box. It wasn’t where they said and for that matter, even Gemini gave the same wrong setting location as the Homey instructions. I found it under “Network” on the side bar, then “Global Configuration” and “Settings”.
Other than that, it all worked just as the Homey guidance said.
Hmm I can’t seem to get the app to stay running. I followed the guide exactly and end up getting:
Failed to start required daemon: Socket /run/avahi-daemon/socket Unavailable After 2500ms (50 attempts)
Odd.
Hi,
Whenever i try to add any matter bridge; Hue + Ikea
I get this error:
2025-12-18 00:57:42.592364+00:00Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
2025-12-18 00:57:42.594302+00:00Homey [log][ManagerMatterLocal] [Pairing:0x7c469557] Start
2025-12-18 00:57:42.595528+00:00Homey [log][ManagerMatterLocal] [Pairing:0x7c469557] Got status update: SEARCHING (-0x01, Unknown)
2025-12-18 00:57:42.596205+00:00Homey [log][ManagerMatterLocal] Updating PAA certs
2025-12-18 00:57:42.596284+00:00Homey [log][ManagerMatterLocal] DCLs: https://on.dcl.csa-iot.org. Git: false
2025-12-18 00:57:42.597679+00:00Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
2025-12-18 00:57:42.720430+00:00Homey [err][ManagerMatterLocal] [Pairing:0x7c469557] Finished with error: Unknown error (Matter code: INTERNAL (0x00ac))
2025-12-18 00:57:42.722167+00:00Homey [err][ManagerMatterLocal] [Pairing:0x7c469557] Could not cleanup pairing: Unknown error (Matter code: INTERNAL (0x00ac))
2025-12-18 00:57:42.723858+00:00Homey [err][ManagerMatterLocal] [Pairing:0x7c469557] Could not stop pairing: Could not stop pairing (Matter code: INCORRECT_STATE (0x0003))
2025-12-18 00:57:42.724657+00:00Homey [err][ManagerMatterLocal] [Pairing:0x7c469557] Failed: Unknown error (Matter code: INTERNAL (0x00ac)) (at stage: unknown)
I have tried to restart both bridges, the docker instance etc but i cannot get it to connect
025-12-18 01:04:53.377612+00:00Homey [err][ManagerMatterLocal] Could not initialize matter daemon: MatterError: Could not init Matter daemon (Matter code: ENDPOINT_POOL_FULL (0x00c1))
2025-12-18 01:04:53.377649+00:00at wrapMatterError (file:///app/packages/homey-local/node_modules/@athombvathombv/homey-matter/dist/util/Util.js:209:19)
2025-12-18 01:04:53.377654+00:00at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
2025-12-18 01:04:53.377658+00:00at async HomeyMatter.init (file:///app/packages/homey-local/node_m@athombvdules/@athombv/homey-matter/dist/HomeyMatter.js:94:26)
2025-12-18 01:04:53.377665+00:00at async MatterDaemon.initializeMatter (file:///app/packages/homey-local/lib/MatterDaemon.mts:206:36)
2025-12-18 01:04:53.377669+00:00at async ManagerMatterLocal.onMatterDaemonConnected (file:///app/packages/homey-local/lib/ManagerMatterLocal.mts:570:5) {
2025-12-18 01:04:53.377675+00:00code: 193,
2025-12-18 01:04:53.377679+00:00original: RPCError: Error response for conversation 0. Domain: 2, code: 193
2025-12-18 01:04:53.377683+00:00at RPCManager.handleIncomingResponse (file:///app@athombvnode_modules/@athombv/homey-rpc/dist/RPCManager.js:355:27)
2025-12-18 01:04:53.377686+00:00at RPCManager.parseIncomingData (file@athombv///app/node_modules/@athombv/homey-rpc/dist/RPCManager.js:329:25)
2025-12-18 01:04:53.377693+00:00at RPCManager.onIncomingDat@athombv (file:///app/node_modules/@athombv/homey-rpc/dist/RPCManager.js:260:36)
2025-12-18 01:04:53.377697+00:00at Socket. (file:///app/node_modules/@athombv/homey-rpc/dist/RPCManager.js:59:18)
2025-12-18 01:04:53.377701+00:00at Socket.emit (node:events:508:28)
2025-12-18 01:04:53.377707+00:00at addChunk (node:internal/streams/readable:559:12)
2025-12-18 01:04:53.377711+00:00at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
2025-12-18 01:04:53.377714+00:00at Readable.push (node:internal/streams/readable:390:5)
2025-12-18 01:04:53.377718+00:00at Pipe.onStreamRead (node:internal/stream_base_commons:189:23) {
2025-12-18 01:04:53.377724+00:00code: 193,
2025-12-18 01:04:53.377728+00:00serviceId: 2
2025-12-18 01:04:53.377731+00:00},
2025-12-18 01:04:53.377734+00:00serviceId: 2
2025-12-18 01:04:53.377737+00:00}
I also seem to be getting this error whenever i load up via a new image
Any idea why this happens? I only installed one instance of Homey on my TrueNas but it shows me several, with only one of these that actually works.
And when I click on one that doesn’t work, this is what I get. Weird.
Thanks
After rebooting the container can’t connect anymore to the instance:
Tried setting up a new homey server from the app and it works, then if I reboot again even that new instance is inaccessible.
Can you check You assigned a share while creating the container. That’s the Appdata of SHS. Stored ‘outside’ the container. So it won’t be deleted when the container is updated. or restarts ?
