# \[Modding\]\[HowTo\] Guide to Jailbreak a Homey Pro 2023

**URL:** <https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678>\
**Category:** Off-Topic\
**Tags:** homey-pro-2023, modding\
**Created:** [June 4, 2023, 4:17pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678 "2023-06-04T16:17:01Z")\
**Posts on this page:** 18\
**Page:** 4

<div class="post-metadata">

**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:** [January 6, 2026, 12:27am UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/61 "2026-01-06T00:27:32Z")

</div>

This is (one of) the problem(s):

> [@John\_Lykke\_Nielsen](#):
>
> Permission to access USB device denied. Make sure you are a member of the plugdev group.

---

<div class="post-metadata">

**Author:** ![John\_Lykke\_Nielsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_lykke_nielsen/32/47790_2.png) [@John\_Lykke\_Nielsen](https://community.homey.app/u/John_Lykke_Nielsen)\
**Post date:** [January 6, 2026, 7:41pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/62 "2026-01-06T19:41:17Z")

</div>

Thank you for your reply. I am not entirely certain how to interpret it or how to proceed.

I am following the instructions provided for this jailbreak across several sources. However, I have not been able to identify a clear solution for how to continue the attempt using Windows only. I would appreciate clarification on the appropriate next steps or confirmation as to whether a Windows-only approach is still supported.

---

<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:** [January 7, 2026, 7:17am UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/63 "2026-01-07T07:17:09Z")

</div>

Google/DuckDuckGo for “rpiboot windows”.

This isn’t, strictly speaking, a Homey issue. Homey has a Raspberry Pi Compute Module, and the usbboot/rpiboot tools are not developed by Athom or are unique to Homey.

---

<div class="post-metadata">

**Author:** ![Tomas\_Severa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_severa/32/33929_2.png) [@Tomas\_Severa](https://community.homey.app/u/Tomas_Severa)\
**Post date:** [March 5, 2026, 5:08pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/64 "2026-03-05T17:08:29Z")

</div>

Hi gents,

I replaced the module for a 8/32 version.

Everything is running except the resizing of the partitions.

It seems, I haven’t done the Jailbreak right.

I did it under Windows

I copied (overwritten) the files in ROOTB and ROOTA, ejected all the 6 drives (in LFS and I also tried it under Windows)

But I can not connect through SSH…still same - connection refused.

Port is 2222, no firewall etc.

My question is if I will try do the Jailbreak once more, should I do the restore Homey from backup before or can I just try it again without restoring?

What’s interesting - I can not also connect to sandbox on port 22.

and when I think about it, is it actually still possible? I have the latest public firmware in Homey

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [March 5, 2026, 7:36pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/65 "2026-03-05T19:36:38Z")

</div>

> [@Tomas\_Severa](#):
>
> I copied (overwritten) the files in ROOTB and ROOTA, ejected all the 6 drives (in LFS and I also tried it under Windows)

Re-mount the partitions and check if the files exists - I’m using EJECT using Linux File System by Paragon, instead of built-in Windows functionality.

> [@Tomas\_Severa](#):
>
> the resizing of the partitions

Resizing of the partitions is unrelated to the jailbreak.

> [@Tomas\_Severa](#):
>
> if I will try do the Jailbreak once more, should I do the restore Homey from backup

Nope, simply mount the partitions again and redo.

> [@Tomas\_Severa](#):
>
> What’s interesting - I can not also connect to sandbox on port 22.

Sandbox seems to be broken, it is unrelated.

> [@Tomas\_Severa](#):
>
> is it actually still possible?

Didn’t check recently.

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 10, 2026, 1:07pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/66 "2026-04-10T13:07:22Z")

</div>

All,

I am struggling with SSH connection.  
I can see the script has run, because the port in sshd\_config has changed to 2222,  
and in rc.local the last to lines pointing to the script are also gone.  
This is all in rootb, roota is ontouched as expected. But trying to ssh from any machine, win11, ubuntu and a cisco-switch says “connection refused by remotehost”

Anyone any other suggestions that I could try to login via SSH to my homey?

Many thanks in advance!

---

<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:** [April 10, 2026, 2:04pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/67 "2026-04-10T14:04:30Z")

</div>

Same issue here, ever since one of the last updates the method stopped working. I haven’t yet taken the time to figure out the issue, but my guess is that something changed in the ssh configuration of Homey’s firmware that is causing a conflict of some sort.

When I find out more I’ll post it here.

**EDIT** :

- Issue 1: filesystem has no free space left?

```auto
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [27.2 kB]
Err:3 http://security.debian.org/debian-security bullseye-security InRelease
  Error writing to file - write (28: No space left on device) [IP: 2a04:4e42:30::644 80]
Hit:4 http://archive.debian.org/debian bullseye-backports InRelease
Get:5 http://archive.raspberrypi.org/debian bullseye InRelease [39.0 kB]
Err:5 http://archive.raspberrypi.org/debian bullseye InRelease
  Error writing to file - write (28: No space left on device) [IP: 2a00:1098:80:56::1:1 80]
Reading package lists...
Building dependency tree...
Reading state information...
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease Error writing to file - write (28: No space left on device) [IP: 2a04:4e42:30::644 80]
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease Error writing to file - write (28: No space left on device) [IP: 2a00:1098:80:56::1:1 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libcbor0 libfido2-1 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6
  libxmuu1 ncurses-term openssh-client openssh-sftp-server runit-helper ucf
  xauth
Suggested packages:
  keychain libpam-ssh monkeysphere ssh-askpass molly-guard ufw
The following NEW packages will be installed:
  libcbor0 libfido2-1 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6
  libxmuu1 ncurses-term openssh-client openssh-server openssh-sftp-server
  runit-helper ucf xauth
0 upgraded, 16 newly installed, 0 to remove and 3 not upgraded.
Need to get 3,319 kB of archives.
After this operation, 14.9 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.
Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable ssh
Job for ssh.service failed because the control process exited with error code.
See "systemctl status ssh.service" and "journalctl -xe" for details.

```

**EDIT** : yup, the root partition is really almost full!

```auto
$ df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.0G 1.9G 0 100% /

```

I remember a Homey SHS user complaining about this issue, and that it turned out the SHS images were being shipped with dangling (unused) Docker images. I’ll try and see if I can prune dangling images during the boot process to see if that clears up any storage space.

**EDIT** : that didn’t help much

```auto
$ docker system prune -f
Deleted Containers:
03580d60f6c7b5c007239b359910a2377e3dff16687d45e440cb19fb6df040d6
528e240601177b605e1879a6e16c847f8a8e120420a48f6483c3e6bf94c201d4

Total reclaimed space: 0B

```

It’s now bootlooping though 😅 Installing 13.1.1…

**EDIT** : 13.1.1 installed, it looks like it might have just enough space available to install OpenSSH again.

**EDIT** : nope, there’s just not enough room available. The Docker images for Homey are pretty fat, I wouldn’t be surprised if they contain a _lot_ of unnecessary files, but I’ll have to take a look at that later. Right now I’ve installed a sort-of root shell by adding this to `/etc/rc.local`:

```auto
/usr/bin/socat -d -d TCP4-LISTEN:4443 EXEC:/bin/bash &

```

Then from my Mac I can access that root shell like so:

```auto
socat - TCP4:A.B.C.D:4443

```

(where `A.B.C.D` is the IP address of my HP2023)

Only works once after reboot so I’ll have to dive into socat options to see how I can get it to restart each time a connection is closed.

**EDIT** : this sets up a better root shell

```auto
# add to /etc/rc.local
/usr/bin/socat -d -d TCP4-LISTEN:4443,fork EXEC:"/bin/bash -li",pty,stderr,setsid,sigint,sane &

```

Then use this to connect:

```auto
socat file:$(tty),raw,echo=0 TCP:A.B.C.D:4443

```

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 12, 2026, 2:19pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/68 "2026-04-12T14:19:34Z")

</div>

Is this also a sort of SSH connection never used this before?  
Can I sent also commandos to extend the memory 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:** [April 12, 2026, 2:42pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/69 "2026-04-12T14:42:37Z")

</div>

It’s a _sort of_ SSH connection in that it gives you a (root) shell on Homey. Unlike SSH it’s not secure at all so it’s not a long-term solution.

The problem is that, at least on my Homey, the root filesystem is almost entirely out of space, which makes installing additional commands problematic. I don’t know which commands you need to “extend the memory” (do you mean resize the storage?), but if they require extra packages to be installed it might not work.

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 12, 2026, 2:53pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/70 "2026-04-12T14:53:34Z")

</div>

Socat does not work at my Homey, still not able to connect ☹

---

<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:** [April 12, 2026, 3:00pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/71 "2026-04-12T15:00:52Z")

</div>

What exactly is shown when you try to connect?

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 12, 2026, 3:03pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/72 "2026-04-12T15:03:23Z")

</div>

Network error connection refused  
I use putty A.B.C.D port 4443 RAW

---

<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:** [April 12, 2026, 3:04pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/73 "2026-04-12T15:04:50Z")

</div>

Can you show the full contents of `/etc/rc.local` on your Homey?

Also, Homey has two root partitions, `ROOTA` and `ROOTB`. You need to modify `/etc/rc.local` on both (or check which one contains the latest version of the OS, by checking `/version`, and modify that one).

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 12, 2026, 3:23pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/74 "2026-04-12T15:23:57Z")

</div>

#!/bin/sh -e

# 

# rc.local

# 

# This script is executed at the end of each multiuser runlevel.

# Make sure that the script will “exit 0” on success or any other

# value on error.

# 

# In order to enable or disable this script just change the execution

# bits.

# 

# By default this script does nothing.

# Print the IP address

\_IP=$(hostname -I) || true  
if [“$\_IP”]; then  
printf “My IP address is %s\n” “$\_IP”  
fi

/usr/bin/socat -d -d TCP4-LISTEN:4443,fork EXEC:“/bin/bash -li”,pty,stderr,setsid,sigint,sane &

#chmod 755 /home/ssh-setup.sh  
#/bin/bash /home/ssh-setup.sh &  
#Marc  
exit 0

I add them to both RootA and RootB but RootB us the one which is executed

---

<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:** [April 12, 2026, 3:46pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/75 "2026-04-12T15:46:28Z")

</div>

Assuming that the quotes that you’re using in the file are not “smart” (so regular `"` quotes and not `“`/`”`), I don’t know why it’s not working. Even though I’m not sure if Putty can be used (since there are pseudo terminals involved), I would expect it to at least be able to connect.

---

<div class="post-metadata">

**Author:** ![Marc\_Straat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_straat/32/71941_2.png) [@Marc\_Straat](https://community.homey.app/u/Marc_Straat)\
**Post date:** [April 13, 2026, 8:35am UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/76 "2026-04-13T08:35:53Z")

</div>

Robert,

Thanks enormous!!  
I guess by copying the command, the quotes changed to the ones they should not be 😉  
Changed the quotes by hand and the command was functioning as expected. I modded my homey also to 8Gb and 24Gb.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [October 31, 2026, 5:30am UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/78 "2026-10-31T05:30:33Z")

</div>

Any reason? Athom was fine with it

---

<div class="post-metadata">

**Author:** ![Mike\_Nono](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@Mike\_Nono](https://community.homey.app/u/Mike_Nono)\
**Post date:** [November 4, 2026, 5:20pm UTC](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678/80 "2026-11-04T17:20:40Z")

</div>

Ok.  
Last and final update on this. I hope.  
Fixed ssh and the small error when using sudo “missing hostname”  
(let me know if something not working, “hope not”)

EDIT: Small fix. Removed the annoying  
“-bash: gettext.sh: No such file or directory”  
when connecting to ssh.

**rc.local**

```auto
#!/bin/sh -e
#
# rc.local

# Print the IP address
_IP=$(hostname -I) || true
if ["$_IP"]; then
  printf "My IP address is %s\n" "$_IP"
fi

# How to use it: (public version)
# Replace the rc.local file content with this.

# **Thanks for the start of this "spkesde"**
# **just in case: Failsafe Socat. Thanks "robertklep" it was usefull for debugging**
#/usr/bin/socat TCP4-LISTEN:2345,reuseaddr,fork EXEC:/bin/bash,pty,stderr,setsid,sigint,sane &

# This create user "homey-one" with password "one" if it doesn't exist and set password to "one" and force password change on first login
# *** 
# Or just change user "homey-one" and password "one" to whatever you like
# And off you go, but you still need to change the password on first login.
# Unless you comment out the "chage -d 0 homey-one"
# ***

if ! id "homey-one" >/dev/null 2>&1; then
    useradd -m homey-one
    echo "homey-one:one" | chpasswd
    chage -d 0 homey-one
    # Add "homey-one" to the sudoers file. With this safer approach:
    echo "homey-one ALL=(ALL) ALL" > /etc/sudoers.d/homey-one
    chmod 0440 /etc/sudoers.d/homey-one
fi

# Get the hostname
CURRENT_HOSTNAME=$(hostname)

# Fallback if hostname is empty or not set
if [-z "$CURRENT_HOSTNAME"]; then
    CURRENT_HOSTNAME="localhost"
fi

HOSTS_FILE="/etc/hosts"

# Update or insert the hostname for 127.0.1.1
if grep -q "127.0.1.1" "$HOSTS_FILE"; then
    # Replace the existing 127.0.1.1 line with the current hostname
    sed -i "s/^127\.0\.1\.1.*/127.0.1.1\t$CURRENT_HOSTNAME/" "$HOSTS_FILE"
else
    # If 127.0.1.1 doesn't exist, insert it right after the 127.0.0.1 line
    sed -i "/^127\.0\.0\.1/a 127.0.1.1\t$CURRENT_HOSTNAME" "$HOSTS_FILE"
fi

# Remove the annoying message "missing gettext.sh" 
[-f /usr/bin/gettext.sh] || touch /usr/bin/gettext.sh

mkdir -p /run/sshd
chmod 0755 /run/sshd

ssh-keygen -A
systemctl enable --now ssh

exit 0

```

[Previous page](https://community.homey.app/t/modding-howto-guide-to-jailbreak-a-homey-pro-2023/81678.md?page=3)
