No "PlayActor" device listed in PS4 Second Screen app #25
Comments
You cannot connect both consoles at the same time with playactor. I think so. First, you need to disconnect your PS4 from the network. And then connect ps5 with playactor. After successfully connecting ps5, you need to turn off ps5 and then connect ps4 with https://github.com/dhleong/ps4-waker It works fine for me. I also have ps4 and ps5. |
That doesn't seem right to me. I think it should be possible to use playactor with both a PS4 and PS5. Surely, you just need to specify Just to clarify, I currently have playactor working with my PS5. I just can't get it working with my PS4. |
esabol
changed the title
I understood. |
|
@NikDevx I don't think that's the issue (connecting both at the same time), as @esabol was having this problem before he connected his PS5 with playactor. I know this because he posted this problem in one of my discussions and – at the time – he hadn't yet connected his PS5. Something else is going on. Though, I'm not exactly sure what as I have yet to try playactor with my PS4... only my PS5. Like you, I still use ps4-waker with my PS4. That said... @esabol... I do believe you should try disconnecting ps4-waker and your PS4 from Second Screen, and start from scratch. You can always set it up again if you are unable to resolve your playactor issue. Also, as already mentioned, you can use ps4-waker with your PS4... and playactor with your PS5. |
|
@LordZork is correct here; you should be able to connect any number of devices with @esabol I'll try to take a look at reproducing this over the weekend. The behavior with the PS4 should be pretty identical to that of IIRC you cannot directly transfer credentials to another computer, because that device won't have been registered with the PS4 and it will ignore WAKEUP packets from it, but you could certainly try. The |
Uh, that’s what I said.
No, but I’ll try the
Well, it’s not a different computer. It’s the same computer. After a lot of searching, I eventually found where ps4-waker and playactor store the credentials, but the contents don’t look at all similar, but maybe it’s a difference between PS4 and PS5? I’ll try |
You both said it; their comment was just the last I saw. No need to get territorial; we're all just trying to help each other out here!
Ah in that case it might "just work!" The PS4 and PS5 do indeed have different credential formats since we connect to them in different ways, but they can both live in the same playactor credentials file. It'll look something like: {
"<host-id-for-ps4>": {
"user-credential": "...",
"device-type": "C",
// ...
},
"<host-id-for-ps5>": {
"RP-Key": "...",
// ...
}
}Playactor may include some extra info in the block for the PS4 than |
|
Anyway, I tried specifying |
|
Well, I got it working. I'm not sure how though. Here's what I did: After many tries using playactor, I thought I'd try reproducing getting the credentials using ps4-waker. So I moved So I thought I'd try playactor one more time.... This time it worked! I still never saw the "PlayActor" device listed in the PS4 Second Screen app. What I did differently though was that I connected to my PS4 in the PS4 Second Screen app and then disconnected. From that interaction, it appears playactor was able to get the credentials. Fortunately, I executed playactor with the Anyway, I'm now able to wake up and standby both my PS4 and my PS5 using playactor. EDITED TO ADD: I meant to mention that I was able to reproduce this starting from a clean slate. I renamed |
|
I think you may have discovered a bug in the PS4 Second Screen app, haha. Here's what I think happened:
This is all a guess; I haven't tested against my actual device yet, but I fixed my bug and PlayActor shows up in the Second Screen app, so that bit should work properly now 🤞 |
|
Great! Thanks! |
|
Hmmm, I just upgraded to 0.2.3, and I'm still not seeing any "PlayActor" device in the PS4 Second Screen app.... 😢 The debug output says it's emulating a host with the name "PlayActor", so I think it should be working, but not for me for some reason. 🤷 Let me know if there's anything else you want me to try. |
|
Do you see any lines like "responding to SRCH" when |
Interestingly, I don't if I Here's an example: I upgraded to 0.2.4 prior to the above attempt. |
|
May I suggest reopening this issue? I don’t think it is resolved. |
|
I just tested again locally and it works fine for me. It's possible there's still something off in the implementation but it seems to be doing what
Are you saying in either case that the "PlayActor" device does not appear in the Second Screen app? |
Well, not for me. I think there’s something off.
Correct. With or without |
It's possible—this code is much less battle-tested than ps4-waker. I'm not trying to dismiss your experience, here. I'm just trying to gather data, and the fact that it works fine on my network/etc is very important data.
Again, I'm just trying to make things as clear as possible to focus a potential investigation. From my reading of your last comment, I thought perhaps without Are you using the PS4 Second Screen app on iOS or Android? I'm using Android; perhaps the iOS app is parsing the packet differently, and I'm not sending exactly the same thing ps4-waker is.
This is very valuable information, thank you. The reason I have not reopened this issue is because the original issue as reported and as reproduced on my end has been fixed. I'm in data-gathering mode right now, and may prefer to open a new, separate issue, since there may be a separate bug in the code. |
iOS. |
I have both a PS4 and PS5. I've successfully configured ps4-waker in the past.
When I execute
playactor loginon my Mac, it says to "Open the PS4 Second Screen app and attempt to connect to the device named: PlayActor". When I go into the PS4 Second Screen app, I don't see any device named "PlayActor". All I ever see is my PS4. I've hit Refresh many times. Any suggestions or tips?In my PS4's Mobile App Connection Settings, I have an entry for PS4 Waker. Is it possible to transfer the credentials from ps4-waker to playactor and skip this step?
The text was updated successfully, but these errors were encountered: