# Homey Self-Hosted Server on Raspberry Pi | Megathread **URL:** \ **Category:** Homey Self-Hosted Server\ **Created:** [December 5, 2025, 2:09pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433 "2025-12-05T14:09:05Z")\ **Posts on this page:** 13\ **Page:** 3
**Author:** ![Armin\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/armin_s/32/121047_2.png) [@Armin\_S](https://community.homey.app/u/Armin_S)\ **Post date:** [January 24, 2026, 10:53pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/44 "2026-01-24T22:53:35Z")
Thank you very much, the update was installed after restarting the Raspberry Pi. ---
**Author:** ![betaplar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/betaplar/32/151147_2.png) [@betaplar](https://community.homey.app/u/betaplar)\ **Post date:** [January 25, 2026, 10:38am UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/45 "2026-01-25T10:38:56Z")
After updating to 12.11.0 I am experiencing a very laggy behavior of the app, connecting to Homey SHS on my Raspi 5. It seems Homey is entering some kind of standby mode. Opening the app after several hours not using it (e. g. over night) needs a very long time showing the Homey logo, until it is connected. Widgets also don’t work then (until I open the app and wait for the connection). The Logs look okay. I’ll observe it for a while longer. ---
**Author:** ![Sander\_P](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sander_p/32/80176_2.png) [@Sander\_P](https://community.homey.app/u/Sander_P)\ **Post date:** [January 30, 2026, 7:56pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/46 "2026-01-30T19:56:16Z")
Getting the same errors in Unraid Server and Truenas Server `RRD Error updating RRD logId: homey:device:6cf0bfeb-c17d-414b-9e10-264918dbb6f6:energy_power - file: /homey/user/rrd/aa9e0b8027b3721ee1099d8d9fe40f08 - value: 0 - timestamp: 1769787900:` `Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:6cf0bfeb-c17d-414b-9e10-264918dbb6f6:energy_power:` `RRD Error updating RRD logId: homey:device:6b2aa4c3-b519-499e-a1f2-1a5f40453356:energy_power - file: /homey/user/rrd/ae8451cd9beaa2e93b191bbddb09bd0e - value: 0 - timestamp: 1769787900:` `Homey [err][ManagerInsightsLocal] Error Updating Number Log homey:device:6b2aa4c3-b519-499e-a1f2-1a5f40453356:energy_power:` ---
**Author:** ![johan\_W](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_w/32/17556_2.png) [@johan\_W](https://community.homey.app/u/johan_W)\ **Post date:** [January 30, 2026, 9:27pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/47 "2026-01-30T21:27:27Z")
Wellicht een mogelijke manier van backupen van je SHS op een Pi. ## SCP (simpel en standaard) ### Voorwaarden - OpenSSH Client geïnstalleerd op Windows 11 (Instellingen → Apps → Optionele onderdelen → _OpenSSH Client_) - SSH-toegang tot de Linux server - Je Linux-pad is: `/homey-shs/*` - Je backup locatie is `C:\data\homey-shs` ### Batchbestand (`haal_homey.bat`) > ```auto > @echo off > > set USER=linuxgebruiker > set SERVER=192.168.1.10 > set REMOTE_DIR=/homey-shs/* > set LOCAL_DIR=C:\data\homey-shs > > mkdir "%LOCAL_DIR%" > > scp -r %USER%@%SERVER%:%REMOTE_DIR% "%LOCAL_DIR%" > > pause > > ``` 👉 Wat dit doet: - `-r` = recursief (hele directory) - Kopieert **alle bestanden** uit `/homey-shs/` naar `C:\data\homey-shs` (dit zou het complete SHS bevatten) - Je wordt om het Linux-wachtwoord gevraagd (tenzij je SSH-keys gebruikt) Deze manier werkt bijna wel op iedere computer, je zou het sneller kunnen maken dmv een Rsync commando,maar deze applicatie moet je dan zowel op de PI als op je windows machine instaleren. ## Optie 1 Met SSH key (aanrader, geen wachtwoord nodig) Eenmalig op Windows: ```auto ssh-keygen ssh-copy-id linuxgebruiker@192.168.1.10 ``` Daarna werkt dezelfde batch **zonder** wachtwoordprompt. ## Optie 2 – Rsync (sneller bij grote mappen) Als rsync op de Linux server staat: ```auto rsync -avz linuxgebruiker@192.168.1.10:/homey-shs/ C:\data\homey-shs\ ``` ✔ Voordeel: kopieert alleen gewijzigde bestanden ❌ Vereist rsync (meestal wel aanwezig op Linux, maar niet aktief. En je moet rsync op je windows op je computer installeren, en dat is nog al een klusje) * * * ## Veelgemaakte valkuilen - Gebruik **forward slashes** `/` voor Linux paden - Let op rechten op `/homey-shs` - Zorg dat de Windows firewall SSH niet blokkeert ---
**Author:** ![Bas\_Versluis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas_versluis/32/120799_2.png) [@Bas\_Versluis](https://community.homey.app/u/Bas_Versluis)\ **Post date:** [July 22, 2026, 12:09pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/48 "2026-07-22T12:09:09Z")
I want to migrate my Unraid server to a Raspbery Pi (clean install, following the instructions for a Pi installation). According the documentation the backup of the /homey-shs/ folder should be copied to the SD card after flashing it with Raspberry Pi Imager, but before starting the Pi. But where do you place this file, as after flashing the SD card, only the 500 MB bootfs partition is accessible on the SD card? ---
**Author:** ![jocstone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jocstone/32/172867_2.png) [@jocstone](https://community.homey.app/u/jocstone)\ **Post date:** [August 20, 2026, 8:56am UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/49 "2026-08-20T08:56:58Z")
I got an email from Homey about “Update Homey Self-Hosted Server to fix a critical vulnerability”. My Self-Hosted server runs on a raspberry pi. To update, simply restart the raspberry and the server should be updated automatically according to the “platform’s guide” However, after doing so, nothing gets updated. Via the web interface (Settings-\> Updates) I see the update but when I select “Download & Install” or check the Automatic Updates, I get an error: Invalid Endpoint: ManagerUpdates.installUpdate Any idea to fix this? ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 20, 2026, 9:08am UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/50 "2026-08-20T09:08:25Z")
Hi jocstone and welcome, > [@jocstone](#): > > To update, simply restart the raspberry and the server should be updated automatically according to the “platform’s guide” > However, after doing so, nothing gets updated. It should: > [@Armin\_S](#): > > the update was installed after restarting the Raspberry Pi. _ **If not** _, please use the dedicated SHS Rpi topic to continue troubleshooting: > [@Homey Self-Hosted Server on Raspberry Pi | Megathread](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433): > > In this thread we can discuss running Homey Self-Hosted Server on Rasperry Pi. Installation Learn how to [Install Homey Self-Hosted Server on Raspberry Pi](https://support.homey.app/hc/en-us/articles/23975075444124-How-to-install-Homey-Self-Hosted-Server-on-Raspberry-Pi). Known Limitations None at this moment. . > [@jocstone](#): > > Via the web interface (Settings-\> Updates) I see the update but when I select “Download & Install” or check the Automatic Updates, I get an error: > Invalid Endpoint: ManagerUpdates.installUpdate > Any idea to fix this? The actual update functionality of “Settings \> Updates” is only valid for physical Homey models. So you should ignore it. Here you can view specific Homey SHS update info > **[Homey Self-Hosted Server Changelog | Homey](https://homey.app/en-us/wiki/homey-shs-changelog/)** ---
**Author:** ![Ruurd\_van\_der\_Noord](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruurd_van_der_noord/32/71093_2.png) [@Ruurd\_van\_der\_Noord](https://community.homey.app/u/Ruurd_van_der_Noord)\ **Post date:** [August 21, 2026, 3:25pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/51 "2026-08-21T15:25:52Z")
I use the normal Linux procedure on my SHS on docker installation, see Linux on the SHS support page for Raspberry on Debian. # /home/user/.homey-shs docker pull [Package homey-shs · GitHub](http://ghcr.io/athombv/homey-shs) docker stop homey-shs docker rm homey-shs docker run –name homey-shs –network host –privileged –detach –restart unless-stopped –volume ~/.homey-shs/:/homey/user/ [Package homey-shs · GitHub](http://ghcr.io/athombv/homey-shs) ---
**Author:** ![jocstone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jocstone/32/172867_2.png) [@jocstone](https://community.homey.app/u/jocstone)\ **Post date:** [August 28, 2026, 6:31pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/52 "2026-08-28T18:31:12Z")
a quick update, a few days ago is the update installed after a restart. Nothing special was done. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 28, 2026, 9:37pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/53 "2026-08-28T21:37:03Z")
Thanks for the heads up. A possible cause can be: load balancing. I can imagine updated images are offered for download one region at a time. Maybe your region was long in the queue. App updates are offered in a similar way: some receive it right away, others receive it x days later. ---
**Author:** ![prosumer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/prosumer/32/166478_2.png) [@prosumer](https://community.homey.app/u/prosumer)\ **Post date:** [September 30, 2026, 11:32am UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/54 "2026-09-30T11:32:14Z")
I currently use a Homey (later called “Pro”) from 2019, but it’s almost running out of memory. I also have a Raspberry Pi 4 Model B (for other purposes) with 8 GB of memory, which still has 4 GB of free memory, has plenty of free disk space on an SSD, and is on average using less than 10% of the CPU. 1. Would I be be better off switching to the Pi? Or is a dedicated Homey 2019 still the better platform? One complication: although I mainly use WiFi related apps/automations, there’s one exception: several Aqara door sensors, which I connected directly to the Homey 2019, using Zigbee. 1. Do I need to buy a Homey Bridge for that, or can I somehow use my Hue Bridge Pro or IKEA Trafdri bridge for them? ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [September 30, 2026, 12:01pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/55 "2026-09-30T12:01:38Z")
> [@prosumer](#): > > 1. Would I be be better off switching to the Pi? Or is a dedicated Homey 2019 still the better platform? Depends, with SHS you’re “on your own” more or less, but this community can help most people out. Pi is most probably way quicker/snappier when managing Homey. And 4GB of RAM provides for muuuch more room for apps to install. Another advantage: it’s possible to run it locally when a lifetime license is purchased. > [@prosumer](#): > > 1. Do I need to buy a Homey Bridge for that, or can I somehow use my Hue Bridge Pro or IKEA Trafdri bridge for them? IF the Aqara’s can be paired with Hue/Tradfri, then Yes. (zigbee is not universal, as in every brand will connect to / will function flawless with an other brand’s controller) When not: Instead of the Homey bridge, I’d buy a €25 Sonoff zigbee USB dongle, and [install zigbee2mqtt](https://www.zigbee2mqtt.io/guide/getting-started/) on the Pi Pair the Aqaras with zigbee2mqtt, and add those to SHS per [zigbee2mqtt community app](https://community.homey.app/t/app-pro-zigbee2mqtt-use-zigbee-devices-via-mqtt/83214) Homey Bridge is not the best zigbee hardware out there, plus it only communicates per WiFi with SHS. ---
**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\ **Post date:** [September 30, 2026, 7:19pm UTC](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433/56 "2026-09-30T19:19:43Z")
> [@Peter\_Kawa](#): > > IF the Aqara’s can be paired with Hue/Tradfri Any bulb that uses generic Zigbee clusters can be paired to a Hue bridge. Tuya bridge, Innr bridge, eWeLink Sonoff ZBBridge and probably also Tradfri bridge also work with all Zigbee lights and switches that use generic Zigbee clusters. On my ThirdReality Hub, I can pair generic devices but they drop off the network a few minutes later, so ThirdReality’s hub does not support generic Zigbee clusters. I’m not sure if Aqara’s bulbs use generic clusters though [Previous page](https://community.homey.app/t/homey-self-hosted-server-on-raspberry-pi-megathread/146433.md?page=2)