Homebridge Integration Guide

[LordZork]

Updated 04/17/2021

1. Homebridge Integration
2. Installation & Configuration
   | STEP 1 – Install playactor
   | STEP 2 – link PlayStation
   | STEP 3 – install & configure CMD plugin
3. playactor Commands

Homebridge Integration

1. This discussion/guide is for Integrating playactor in Homebridge.
2. It is assumed you have already setup and are familiar with Homebridge. If not, start here:
   a. [Homebridge.io] [Homebridge on GitHub] [Homebridge Wiki] or...
   b. [Homebridge alternative: HOOBS]
3. The info here is for PS5, but is applicable for PS4 as well.
4. [OPTIONAL] For PS4, it is still possible to use ps4-waker (CLI) with ps4-waker-platform (plugin).

Installation & Configuration

All CLI commands are run in Homebridge Terminal

STEP 1 – Install playactor

1. Run: sudo npm install -g playactor
   View README.md for additional info/details.

STEP 2 – link PlayStation

IF... only ONE PlayStation is on network...

1. Run: playactor login
2. Follow prompts/instructions

IF... MULTIPLE PlayStations are on network...

1. Run: playactor browse to browse (scan network) for PlayStations
2. look for specific/desired PlayStation (example: "type": "PS5")
3. More specifically, look for PlayStation's name (example: "name": "PS5-XXX")
   Alternatively, look for PlayStation's id (example: "id": "XXXXXXXXXXXX")
4. Run: playactor login --host-name PS5-XXX or...
   Run: playactor login --host-id XXXXXXXXXXXX
   Replace X's with your device's numbers/letters
5. Follow prompts/instructions

IF... ONE PlayStation 4 and ONE PlayStation 5 are on your network [OPTIONAL]...

1. Run: playactor login --PS5 or...
   Run: playactor login --PS4
2. Follow prompts/instructions

STEP 3 – install & configure CMD plugin

Install a command-based (CMD) plugin that will issue CLI commands (preferably one that supports state checking).

Currently known options:
homebridge-cmdaccessory – WORKING (used for this guide)
homebridge-cmdswitch2 – WORKING [here]
homebridge-cmdswitch2-no-logs – WORKING [here]
homebridge-cmd4 – haven't figured this one out, but it looks awesome
homebridge-cmdtriggerswitch – WORKING (basic switch ONLY—does not support state checking)

1. Install homebridge-cmdaccessory [README.md]
2. Add (and modify) the following JSON Config template...

{
    "platform": "cmdAccessory",
    "name": "CMD Accessory",
    "switches": [
        {
            "name": "PS5",
            "on_cmd": "playactor wake --host-name PS5-XXX",
            "off_cmd": "playactor standby --host-name PS5-XXX",
            "state_cmd": "playactor check --host-name PS5-XXX | grep -i '200 Ok'",
            "polling": true,
            "interval": 60,
            "manufacturer": "Sony",
            "model": "PS5-XXX",
            "serial": "XXXXXXXXXXXX",
            "type": "Switch"
        }
    ]
}

Note: I am not sure what this  | grep -i '200 Ok' does, or if it's even necessary. I carried it over from an old CmdSwitch2/ps4-waker config template. The plugin/config works with or without it, so I left it.

playactor Commands

All CLI commands are run in Homebridge Terminal

command:	usage:
sudo npm install -g playactor	Install playactor
sudo npm uninstall -g playactor	Uninstall playactor
playactor -h	<subcommand> list

<subcommand> list (as of v0.2.4):

browse     - Browse for device on the network            
check      - Detect a device and its state on the network
login      - Login to the device                         
osk-submit - Submit the on-screen keyboard               
send-keys  - Send a sequence of keys                     
standby    - Request the device enter standby/rest mode  
start-id   - Start an app or game by its Title ID        
wake       - Wake up the device                          

Discovering subcommand options:
playactor <subcommand> -h

You can add -h after any <subcommand> to get a list of options, including device-specific options, for that command.

Running commands/subcommands:
playactor <subcommand>
playactor <subcommand> --<device-specific option>

<device-specific option>:	usage:
--host-name <name>	Select a specific device by its host-name
--host-id <id>	Select a specific device by its host-id
--ps4	Ignore non-PS4 devices
--ps5	Ignore non-PS5 devices

Examples:
--host-name
playactor login --host-name PS5-XXX
playactor wake --host-name PS5-XXX
playactor standby --host-name PS5-XXX
playactor check --host-name PS5-XXX
--host-id
playactor login --host-id XXXXXXXXXXXX
playactor wake --host-id XXXXXXXXXXXX
playactor standby --host-id XXXXXXXXXXXX
playactor check --host-id XXXXXXXXXXXX

[aclerok]

Note: I am not sure what this | grep -i '200 Ok' does, or if it's even necessary.

This looks like a status check to update the switch status. The first part runs the playactor check command, and the second part searches that command's result for '200 Ok'.

[toniolio]

Hi, excited to get this set up, but for some reason when I use playactor login nothing happens. playactor browse does work though, so it appears I've installed it properly. It says "In a moment, we will attempt to open a browser window for you to login to your PSN account. When the page shows "redirect", copy the URL from your browser's address bar and paste it here." — but nothing happens.

I'm on Safari but I don't think I have pop-ups blocked (if that's what is supposed to happen)? I am already logged into my PS5, so should I log out and go to the login screen?

[Jordenjj]

Flag it with --no-open-urls
so :
playactor login --no-open-urls

[toniolio]

this worked, thanks!

[rossvarrette]

So I’ve followed the instructions but I’m getting stuck at login.

The prompt says "open PS4 second screen app and attempt to connect to a device named: playactor"

I've downloaded the app on my phone but no device shows up with the "playactor" name just my PS4.

any help is appreciated.

[esabol]

The exact same thing happened to me, @rossvarrette. I reported it as issue #25, but the author closed the issue because he couldn't reproduce it. I'm sorry you're having the problem, but I'm happy to not be the only one. I recommend opening a new issue.

[Screenfeed]

Hi, thanks for this guide <3

After entering the PIN code given by the PS5, I had this error:

Error: Registration error: 403: Forbidden: Other Error                                                                                                                     
    at Object.<anonymous> (/usr/local/lib/node_modules/playactor/dist/remoteplay/protocol.js:88:19)                                                                        
    at Generator.next (<anonymous>)                                                                                                                                        
    at fulfilled (/usr/local/lib/node_modules/playactor/dist/remoteplay/protocol.js:5:58)                                                                                  
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

The solution is to enable the distant login: after entering the PIN code, the console gets you back to the previous screen, and at the top of the list there's a switch to activate the feature.

[mesoblaste]

Hello all,
I follow all the steps above and I think everything went fine.
I now have a PS5 switch on Apple Home and homebridge,
The problem is that it stays off even when PS5 is on, and that nothing happen when I press that switch.

I’m new on GitHub so I hope it’s the right place to ask for help.

here is the log I have when I restart homebridge and then press the switch (I just change the PS5 number by XXX) :
—————————
[29/12/2021, 19:39:39] [CMD Accessory] Failed to determine PS5 state.
[29/12/2021, 19:39:39] [CMD Accessory] /bin/sh: 1: playactor check --host-name PS5-XXX: not found
/bin/sh: 1: grep -i 200 Ok: not found

[29/12/2021, 19:39:40] [CMD Accessory] PS5 is off.

[29/12/2021, 19:40:12] [CMD Accessory] PS5 is off.
[29/12/2021, 19:40:12] [CMD Accessory] PS5 is off.
[29/12/2021, 19:40:13] [CMD Accessory] true
[29/12/2021, 19:40:13] [CMD Accessory] Failed to turn on PS5
[29/12/2021, 19:40:13] [CMD Accessory] /bin/sh: 1: playactor wake --host-name PS5-XXX: not found

[29/12/2021, 19:40:13] [CMD Accessory] PS5 is off.
[29/12/2021, 19:40:15] [CMD Accessory] PS5 is off.
[29/12/2021, 19:40:39] [CMD Accessory] Failed to determine PS5 state.
[29/12/2021, 19:40:39] [CMD Accessory] /bin/sh: 1: playactor check --host-name PS5-XXX: not found
/bin/sh: 1: grep -i 200 Ok: not found
—————————

Thanks for your help

[Jordenjj]

You probably entered an incorrect hostname. If you only use one PS5 you can just omit the hostname flag and the hostname itself altogether and it should autodiscover

[mesoblaste]

Thanks for the tips, the hostname seems to be right but i start from there to think about my problem and what i've done is the following :
i uninstall cmdaccessory and try cmdswitch2 instead as the config didn't mention hostname (#15),
i had some improvement but it didn't work at every try ; so i just add --ps5 in the wake and sleep command as i figure out sometimes it tried to wake or send to sleep a PS4 i have in the same network :
{
"name": "homebridge-cmdswitch2",
"switches": [
{
"name": "PlayStation 5",
"on_cmd": "playactor wake --ps5",
"off_cmd": "playactor standby --ps5",
"state_cmd": "playactor check --ps5| grep -i '200 Ok'",
"polling": true,
"interval": 900,
"timeout": 2000,
"manufacturer": "Sony",
"model": "PS5"
}
],
"platform": "cmdSwitch2"
}

And now it seems to work quite well, just have to be patient to let the status update while the PS5 is turning on/off.

I notice also that using lower case to type 'ps5' instead of 'PS5' is quite important because if not homebridge log says that the command is unknown, at least with cmdswitch2.

Hope that could help for those with the same issue.

[mesoblaste]

Hello again,
i notice another little problem that is bugging me :
when i press the PlayStation 5 switch in Apple Home app, the PS5 turn on, and the switch button on the app turn white for a few second but after that it goes black again with an exclamation dot, so i think the app doesn't wait long enough for the Homebridge confirmation that the PS5 is turned on... Is there a way to increase the delay in Apple Home in order it wait a few more second to get that confirmation?
For now i have to wait and press again the switch button after the PS5 is fully turned on, and then i can press again to turn it off.

[Jordenjj]

I think this is more of an issue with the status command. Can you post your config?

[mesoblaste]

{
"name" : "homebridge-cmdswitch2",
"platform" : "cmdSwitch2",
"switches" : [
{
"interval" : 900,
"manufacturer" : "Sony",
"model" : "CFI-1016A",
"name" : "PlayStation 5",
"off_cmd" : "playactor standby --ps5",
"on_cmd" : "playactor wake --ps5",
"polling" : true,
"serial" : "xxxxxxxxxxxx",
"state_cmd" : "playactor check --ps5| grep -i '200 Ok'",
"timeout" : 2000
}
]
}

[gradyhouston]

Yeah, same issue as @mesoblaste, expect mine doesn't turn it on or off. I can see it, but nothing happens when I press the "PS5" button in the Home App.

[gradyhouston]

So, I have it set up correctly and can see it in the Home App, but tapping on/off doesn't actually turn it on or off. Homebridge sees it as "on" or "off" and the Home App sees the PS5 as "on" or "off", but the PS5 doesn't actually turn on or off. When I run playactor check, the PS5 is in standby and nothing happens. When it's "awake" nothing happens either. It does however work from the CLI. I can run playactor standby and the PS5 goes to sleep.

BUT...Homebridge and the Home App see it. Using the cmdswitch2 plugin:

{
                    "name": "PlayStation 5",
                    "on_cmd": "playactor wake --ps5",
                    "off_cmd": "playactor standby --ps5",
                    "state_cmd": "playactor check --ps5| grep -i '200 Ok'",
                    "ip": "192.168.1.120",
                    "polling": true,
                    "interval": 900,
                    "timeout": 40000,
                    "manufacturer": "Sony",
                    "model": "PS5"
                }

This works but it also "doesn't". I get this in Homebridge when trying to turn on the PS5 from standby ERR Device PS5-704 must be awake for initial registration.. Does this imply that it turning it on isn't "waking" it?

[Jordenjj]

Can you try to remove the --ps5 so just "playactor wake"

[mesoblaste]

I tried just before applying change, it was still working, and when I delete --ps5 from the on_cmd line I get this on the log :

[05/01/2022, 14:02:08] [homebridge-cmdswitch2] Failed to turn on PlayStation 5
[05/01/2022, 14:02:08] [homebridge-cmdswitch2] ERR Device PS4-xxx must be awake for initial registration.

[mesoblaste]

For information, before cancelling my recent changes I try also to turn off the PS5 via Apple Home after turning it on with the DualSense, it works because I kept --ps5 on the off_cmd line ; but I noticed that the status didn't update on Homebridge and Apple home by turning it on via the pad, the switch remains off...
It is the same after adding back --ps5 to the on_cmd line, so there's definitely something to improve about updating the status, but what, is there a command line to add on Config which would 'ping' the PS5 to get its status?

[gradyhouston]

Yeah, I do have a PS4 on the same network, but it works just fine still using PS4-waker. Here's my config now...I've even tried using two different switch plugins:

        {
            "platform": "cmdSwitch2",
            "name": "CMD Switch",
            "switches": [
                {
                    "name": "Playstation 4",
                    "on_cmd": "/usr/bin/ps4-waker -c /var/lib/homebridge/.ps4-wake.credentials.json",
                    "off_cmd": "/usr/bin/ps4-waker -c /var/lib/homebridge/.ps4-wake.credentials.json standby",
                    "state_cmd": "/usr/bin/ps4-waker -c /var/lib/homebridge/.ps4-wake.credentials.json search | grep -i '200 Ok'",
                    "polling": true,
                    "interval": 500000,
                    "ip": "192.168.1.118",
                    "timeout": 40000,
                    "manufacturer": "Sony Corporation",
                    "model": "XXX-XXXXX",
                    "serial": "XXXXXXXXXX"
                }
            ]
        },
        {
            "platform": "cmdAccessory",
            "name": "CMD Accessory",
            "switches": [
                {
                    "name": "PS5",
                    "on_cmd": "playactor wake --ps5 -c /root/.config/playactor/credentials.json",
                    "off_cmd": "playactor standby --ps5 -c /root/.config/playactor/credentials.json",
                    "state_cmd": "playactor check --ps5 -c /root/.config/playactor/credentials.json | grep -i",
                    "polling": true,
                    "interval": 500000,
                    "ip": "192.168.1.120",
                    "timeout": 40000,
                    "manufacturer": "Sony",
                    "model": "XXX-XXXXX",
                    "serial": "XXXXXXXXXX",
                    "type": "Switch"
                }
            ]
        }

The timeout at 40000 is just a carryover from my PS4-waker setup. I was having issues early on with my PS4 not doing anything, so it was suggested to raise the timeout period, so I just kept it.

Just now I tried asking Siri to "turn on the PS5" and it replied with "The PS5 is not responding". It also shows not responding in the Home App. It is currently in standby mode.

[FranciRoosters]

This entire would make sense if Remote Play didn’t disconnect every two seconds.

[whothefuzz]

I am using Windows 10 - Homebridge 1.4.0

I was able to get playactor installed successfully via the Node.js command prompt (open as admin). Was this the right terminal to install? After install and linking, I am able to control my PS5 from command prompt with all playactor commands (wake/standby/check). However I am unable to control from Homebridge/Homekit, because I am receiving an error:

Checking my logs in Homebridge shows -

[cmdSwitch2] Failed to determine PlayStation 5 state. [cmdSwitch2] 'playactor' is not recognized as an internal or external command, operable program or batch file.

Thinking this is because I am not to sure if I am installing playactor in the right place? I am unable to get to terminal via Homebridge UI but I'm not sure if that is default in windows or something I've done (or misunderstanding)?

Any insights will be gladly appreciated!!

Thanks,

[kopiro]

Hello everyone, I just looked at this discussion and created a new package that simplify and wraps everything:

https://github.com/kopiro/homebridge-playstation

Let me know!

[whothefuzz]

Gave this a shot @kopiro !

I am running Windows 10 - Execute commands in Node.Js Command Prompt (run as administrator)

I was able to succesfully install homebridge-playstation

When I get to homebridge-playstation-login I just keep on receiving this error:
C:\Windows\System32>homebridge-playstation-login Connection succeded, restart HomeBridge now!

After restarting Homebriddge, I do not get any auth request or url, nor does an accessory (switch) end up on my Homebridge/Homekit.

I think this may be due to the fact that playactor is already connected to my PSN account. So i went ahead and uninstalled playactor with npm, and tried again. Still recieving te same error. I reinstalled playactor again and was able to control my PS5 without reauth, so Im wondering if it never really lost the link. Would you or anybody know how to reset playactor to reauth to playstation? I have tried on PS5 to disable remote play and re-enable, with no luck. There is no list I am aware of that is all devices that can control PS5.

[adamrzanek]

@kopiro great! Will try later today🙏

[whothefuzz]

@kopiro thank you! look forward to trying this later!!

I ended up using Shortcuts and SSH command to run playactor commands. This method does not allow for the PS5 to be a switch in Homekit, per say, but can still be woke/sleep with Siri.

[esabol]

@whothefuzz wrote:

I ended up using Shortcuts and SSH command to run playactor commands. This method does not allow for the PS5 to be a switch in Homekit, per say, but can still be woke/sleep with Siri.

Interesting! Do you have instructions on how to do that? I'd like to avoid running Homebridge if I can.

[whothefuzz]

@esabol and whoever is interested..

I have created a guide on how to complete this without using Homebridge or Home Assistant as a middle man:

STEP 1

Install playactor on a local machine (Windows, Macos, Linux).
Pre-requisite: NPM has been installed.
Run: sudo npm install -g playactor

STEP 2

Link PlayStation
IF... only ONE PlayStation is on network...

Run: playactor login
Follow prompts/instructions

IF... MULTIPLE PlayStations are on network...

Run: playactor browse to browse (scan network) for PlayStations
look for specific/desired PlayStation (example: "type": "PS5")
More specifically, look for PlayStation's name (example: "name": "PS5-XXX")
Alternatively, look for PlayStation's id (example: "id": "XXXXXXXXXXXX")
Run: playactor login --host-name PS5-XXX or...
Run: playactor login --host-id XXXXXXXXXXXX
Replace X's with your device's numbers/letters
Follow prompts/instructions

STEP 3

Whatever local machine you just installed this on, make sure it allows SSH access. (This machine will be the middle man that sends the command to the Playstation, so I highly recommend an always-on device and not a laptop.)
Mac - https://osxdaily.com/2011/09/30/remote-login-ssh-server-mac-os-x/
Windows 10 - https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse
Linux - https://www.tecmint.com/disable-or-enable-ssh-root-login-and-limit-ssh-access-in-linux/

STEP 4

Create Shortcut (can be an automation or a regular shortcut).
Pre-requisite: The application, 'Shortcuts', has been installed on your iOS device.
I will show the different shortcuts I've created as possible examples for your setup. I like having them all available at my disposal.

Using a Shortcut

1. Create a new shortcut and title it whatever statement you want to say to Siri. In my case the title is "Fire Up the Sticks!"
2. Search for and add the module: Run Script Over SSH
3. Add the command, in this case: playactor wake -PS5-XXX (PS5-XXX is not required when there are no other Playstations on the network, as is my case)
4. Add the IP Address of the machine from Steps 1-3, in my case: 192.168.0.35
5. Add user and password if required to get into that machine
6. *Optional: Add a quirky message from Siri using the Text and Show Result modules respectively
7. $$Optional: Add the Shortcut to your home screen, essentially making this Shortcut an app
   UX: Say "Hey Siri, Fire Up the Sticks!" to any of your Homekit devices to turn of your PS5
   ..or..
   Click on the "Fire Up the Sticks!" app on your home screen to turn on your PS5 (requires number 7$$)

Using a Focus (as of iOS 15)
Focus is a great way to make your phone ready for certain points of your day, like getting yourself shifted into work focus or going from work to play. Now with automations it can also control your home to coinside with your set Focus.

1. Create a new Focus called Gaming (or whatever you'd like) > Swipe down Control Center > Select "Focus" > New Focus '+'
2. Configure your Focus however you'd like
3. In Shortcuts app..
4. Select Automation > New '+' > Create Personal Automation
5. Find Focus > Select your new Focus (Gaming) > Choose 'When Turning On' and press Next
6. Complete Steps 2-6* of Using a Shortcut
   UX: Open Control Center on your iOS device and select Gaming to turn on your PS5

Using an NFC Tag
My Favorite option right now.
-They are so cheap and Apple has added them as an option directly in HomeKit/Shortcuts. You can get some here, definitely play around with all the fun stuff you can do with these.
-Homekit (account secured to Apple ID) is secure enough for me to leave these outside my house, allowing me to open garage or front door with just a scan. Only reacting to my iOS device.

1. In Shortcuts app..
2. Select Automation > New '+' > Create Personal Automation
3. Select 'NFC'
4. Scan an NFC Tag to register it then hit Next
5. Complete Steps 2-6* of Using a Shortcut
6. Place your NFC Tag anywhere (physically) where you can easily scan. See my picture for possible location. As my controller is behind a glass door and the PS is on the ground, I placed the tag in a picture frame on my entertainment center.
   UX: Hold your phone in front of wherever you place your NFC tag to turn on your PS5.

Other options:

Using a Time or Location:
I have other devices for my media, but if your Playstation is your hub for everything maybe you want it to turn on right when you get home from work, or at a specific time when your WFH workday ends:

1. In Shortcuts app..
2. Select Automation > New '+' > Create Home Automation
3. Choose either People Arrive or A Time of Day Occurs
4. Configure your arrival/time settings and hit Next
5. When on the page of your Home's scenes and devices, scroll to the very bottom > Select 'Convert to Shortcut'
6. Complete Steps 2-6* of Using a Shortcut
   UX: Whenever you arrive home, Automations turn on your PS5.
   ..or..
   Anytime of the day, Automations turn on your PS5.

Whatever you can think of really!!

Let me know if you have any cool ideas or if you have any questions/comments/haikus about what I've shown here :)

[esabol]

None of this makes any sense, but this is what I would do:

1. In the Shortcut, change "playactor" to "/usr/local/bin/playactor".
2. Use BBEdit to edit /usr/local/bin/playactor and change the first line to "#!/usr/local/bin/node". Make a backup copy of /usr/local/bin/playactor first.

If that doesn't work, I don't have any other ideas.

[LaurentCole]

The playactor file is in fact an alias which leads to index.js

[LaurentCole]

Did step 1 & 2 and still doesn't work.
?????
What a mystery!

[LaurentCole]

So, I did steps 1 & 2 again in case of…but I changed the first line of the index.js file instead of the playactor file…and it WORKS fine now!
Thx very much for all the help you gave.
Cheers!

[esabol]

Cheers! Finally!

[AmericanNoir]

I'm a NOOB and I'm requesting some help. I've installed Homebridge running on Terminal (MAC). I run Homebridge, then I install PlayActor. It seems to go fine so far. I've run [Playactor -about] but when I run [PlayActor -Login] I get an error and I can't figure out what to do next. "ERR Device Playactor must be awake for initial registration" - Help

[esabol]

What's the output of the commands whoami; ls -ld /home/pi; ls -l /home/pi/.ps4-wake.credentials.json?

[LukasDuitmann]

pi
drwxr-xr-x 16 pi pi 4096 May 31 23:12 /home/pi
-rw-r--r-- 1 pi root 120 Dec 15 2021 /home/pi/.ps4-wake.credentials.json

[esabol]

That doesn't make any sense to me. You are the "pi" user, and the file and directory are owned by "pi". So you shouldn't be getting any permission denied errors.

That said, you really shouldn't be deleting these files. I recommend renaming them, like this:
mv /home/pi/.ps4-wake.credentials.json /home/pi/.ps4-wake.credentials.json.save

Don't bother doing anything with playactor's credentials file.

[LukasDuitmann]

mv: cannot stat '/home/pi/.ps4-wake.credentials.json': No such file or directory

[esabol]

Well, then you've already deleted it, so continue on with the workaround.

[Karo-X]

I'll put it this way... it makes troubleshooting a lot more difficult if you have to explain how to send a ping. I see many challenges that are currently unclear. Is there a firewall running on the Mac?
How is the network set up (firewall, and the questions I asked earlier).
Can you access HomeBridge (the website) from your mobile phone? Do you use HomeBridge for other/other plugins?

[LukasDuitmann]

Oh, sorry for that... No firewalls are activated. I didn't separate 2.4ghz and 5ghz networks. In this case I use only a network and no guest network. I can access HomeBridge with my mobile phone, but mostly I use it for safari on my mac. I use Homebridge for a lot of plugins, like Xiaomi Roborock Vacuum, Shelly, Camera Ui or my Security System.

[Karo-X]

thank you. and you run homebridge on your mac, right?

[LukasDuitmann]

No, on my raspberry pi

[CarlComputerGuy]

Hello. I'm having trouble and can't seem to get past getting it authenticated. I've tried numerous times and it times out every time after I enter in the PIN. This is what I'm getting:
Error: Timeout
at Timeout._onTimeout (/opt/homebridge/lib/node_modules/playactor/dist/remoteplay/registration.js:90:51)
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)

Any help is appreciated. Thanks!

[esabol]

You should probably open an issue.