Device PlayActor must be awake for initial registration #54
Labels
helpme
Requests for help using the app
Comments
|
Also, when I try other prompts like this one: I get all the accurate info, in the come app, the status of the PS4 is shown but not responsive to any command from home app showing this error on homebridge |
|
It seems like you must have another instance of If the Second Screen app is not showing If still no joy, you can try enabling debugging with the |
|
Yes, you're right, the PS4 is showing on Second Screen but PlayActor isn't. Tried that, got this response: When prompting the same but with the debug flag, I get this: Any ideas? :/ |
|
I also tried to connect directly to the PS4 again and got this debug: |
|
I think the problem might be that "wake" time for Playactor to send the signal to Second Screen is set up as +0ms Can be that? In that case, how can I solve it? Thanks!! |
|
What is that
That number is just how long has elapsed since the previous log was written. What might weird is that the next line is printed immediately.... Does the process actually end there or is it hanging there, still running, and you have to I see that it's still detecting another device called |
Oops! My bad! changed it to a used and an unused IP address. Still the same.
Yes, It stops just at the moment it shows the About homebridge… I don't actually know how to kill the service. Every time I kill the process, it restarts again by itself. I'm going to disable the plugin, if it helps… |
|
So, I changed IP for a good one, disabled the homebridge plugin and restarted homebridge. Run a debug again and… Is the second PlayActor still there? Maybe I'll restart the hole system |
|
So, I restarted the Mac and now the process doesn't end by itself, but still no Here is the debug log for the first try (the best one): |
|
Just to clarify: after you see the "Open the PS4 Second Screen app" prompt, are you opening the app and scanning for devices? It looks like it's doing the right thing and is just waiting for the app to ping it. If you are opening the app after seeing that prompt, then that means it's not receiving messages from the app for some reason, which could point to the router not forwarding the UDP packets for... some reason 🤔 As a sanity check: your Mac and your phone are both on the same WiFi, correct? EDIT: Also, it looks like the ghost "PlayActor" device is gone, so that's good :) |
|
I was thinking something like this would be the reason as it’s not the first time my Eero router messes with PS services (in fact I had to wire my PS4 to play online because it kept disconnecting). Have you any insight on this?
|
|
I don’t have any direct suggestions since I don’t have an eero, but it’s
interesting to learn that other services are having issue on the wifi.
Basically the way the protocol works is:
1. The phone app sends a *broadcast* message asking any PS4 messages on
the network to identify themselves
2. Physical PS4 devices (and playactor) receive these messages
3. The receivers all respond by sending a message to the sender (via the
information in the broadcast) with their own messages identifying
themselves.
Since we don’t see any log output indicating that we’ve received messages,
it’s *likely* that somewhere on the network that broadcast message in step
1 is not reaching your Mac. But, because it can see the PS4, we can assume
that it does reach wired devices. You could try wiring in your Mac to the
router directly, if practical, just as a test. Alternatively, you could
search the router's settings for something about broadcast messages, device
discovery, things like that. It may be a privacy setting.
Out of curiosity, how did you get ps4-waker working? I would expect
playactor’s setup process to be fairly equivalent to ps4-waker’s—if
ps4-waker works without any special hacks then it’s possible I missed a
trick or two when migrating that code to playactor...
…On Sep 6, 2022 at 3:32:05 PM, rafacampoamor ***@***.***> wrote:
I was thinking something like this would be the reason as it’s not the
first time my Eero router messes with PS services (in fact I had to wire my
PS4 to play online because it kept disconnecting). Have you any insight on
this?
—
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGHIFVQ32WXT3NQITW6BZ3V46L3LANCNFSM6AAAAAAQFWUQAI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I've tried switching to the cable router wifi and still doesn't see the |
I followed this instructions https://www.reddit.com/r/homebridge/comments/hox47a/guide_ps4_to_homekit_homebridge/ |
|
Huh. So basically just the normal flow and it worked without any tricks?
I’m not sure when I’ll have time to set up my PS4 to test this but it’s
possible there’s something wacky going on.
In the meantime, you may be able to manually prepare the credentials file
based on the credentials established by ps4-waker.
Create a file at: /Users/rafa/.config/playactor/credentials.json
It should look like:
{
<deviceId>: <credentials>
}
Where <credentials> is the contents of the ps4-waker credentials file and
<deviceId> is the id property from the browse command results, in quotes.
…On Sep 6, 2022 at 4:10:05 PM, rafacampoamor ***@***.***> wrote:
Out of curiosity, how did you get ps4-waker working? I would expect
playactor’s setup process to be fairly equivalent to ps4-waker’s—if
ps4-waker works without any special hacks then it’s possible I missed a
trick or two when migrating that code to playactor…
I followed this instructions
https://www.reddit.com/r/homebridge/comments/hox47a/guide_ps4_to_homekit_homebridge/
—
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGHIFR2DHOPKCWRZFB2AELV46QJ3ANCNFSM6AAAAAAQFWUQAI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Got it! Now a tricky one… When configuring Homebridge-playstation, I get an error and I'm not sure is not because of my JSON file. So, just to be sure, the complete JSON syntax should be: just that? Thanks for all the help |
|
There should not be any IIRC the credential file is a JSON object and not a string, so where you have YYY should not be in quotes. Something like: This is a guess from memory but hopefully is sufficient to put you on the right track. |
|
Just for you to know, I think we've arrive to a block. In the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I prompt
sudo playactor loginIt only responds with
ERR Device PlayActor must be awake for initial registration.What should I do?
EDIT: For more info, I have
PS4 wakerworking with home bridge, I just wanted to get advantage of this new plugin. If I promptplayactor login --host-name PS4-654, I get to:No credentials for PS4-654 and unable to request (need root permissions). Attempting to request root permissions now (we will relinquish them as soon as possible)... Registering with device via Second Screen. Open the PS4 Second Screen app and attempt to connect to the device named: PlayActorAnd then it "closes", not showing anything on Second Screen app and with the terminal waiting for a new prompt.
The text was updated successfully, but these errors were encountered: