Closed frossmant closed 2 years ago
This is not support for the homebridge plugin (I did not write that), so the amount of help I can provide is limited.
If you use playactor directly (install with npm i -g playactor
) does the CLI work for you? If not, try the troubleshooting steps here:
Yes i know that. Check the commands I've used and ignore the user named homebridge.
I'm running your playactor scripts here not homebridge plug-ins.
Regards
Also tried it on my Mac now, with the same issues as on my Linux host.
➜ ~ npm i -g playactor
/Users/frossmant/.nvm/versions/node/v14.18.1/bin/playactor -> /Users/frossmant/.nvm/versions/node/v14.18.1/lib/node_modules/playactor/dist/cli/index.js
+ playactor@0.4.1
added 71 packages from 81 contributors in 7.853s
➜ ~ playactor login
No credentials for PS4-889 and unable to request (need root permissions).
Attempting to request root permissions now (we will relinquish them as soon as possible)...
Password:
Registering with device via Second Screen.
Open the PS4 Second Screen app and attempt to connect to the device named:
PlayActor
Nothing appears in the playstation second screen app.
Regards
I only saw homebridge in the original email.
Did you try all the troubleshooting steps I linked?
I've just tried ps4-waker instead of using playactor, that seems to work. At least it's showing up and the "second screen app"
yep tried a couple of switches eg. binding port and ip etc. with no success
After fooling around with this and the homebridge plugin I was able to get it working following these instructions:
https://github.com/kopiro/homebridge-playstation/issues/30#issuecomment-1093921211
same procedure worked here also so I'm closing this issue. thanks
Just for future reference, the workaround is this:
With playactor login no device appears in second screen app. With ps4-waker a PS4-Waker device appears and I am able to connect. While ps4-waker already exits, the second-screen app continues to try to connect to this fake device. At the same time I once again executed playactor login, which then immediately succeeds.
I need to try this workaround! It's funny how ps4-waker always shows up in the Second Screen app, but, for a lot of people, playactor does not. This would seem to indicate a problem with playactor to me...
System Information Timezone GMT+0200 OS openSUSE Leap (15.3) Node.js Version v16.13.1 Npm Version v8.3.0 playactor v0.4.1 (latest)
Im trying to authenticate playactor against PS4 but it won't appear in my "PS4 Second Screen IOS App"
Here are some logs when running debug mode and trying to scan within the Second Screen App from an IOS client