WAKEUP sent to device...

Question

WAKEUP sent to device...

Closed this issue 4 years ago · 14 comments

I had ps4-waker working but woke up this morning and for some reason, it wasn't being recognized by my Home app. So I tried deleting the credentials file and starting over but now when I run ps4-waker (sudo or not), I always get "WAKEUP sent to device... 192.168.1.18". I've tried removing the Mobile connection from the PS4, I've tried uninstalling the plugin completely and reinstalling, I've tried moving the credentials file. Nothing seems to get ps4-waker to start over cleanly.

Answer 1 · 2020-08-23T17:39:54.000Z

I managed to get a different outcome this time - I deleted the credentials file (again) from root directory and tried to pair it again with the Playstation Mobile app. PS4-waker in the app never connects. It just sits there at "connecting..." before timing out. But regardless, every time I run 'psr-waker' in the terminal, I get "WAKEUP sent to device..." even when the PS4 is on.

Answer 2 · 2020-08-23T18:55:50.000Z

We always send the WAKEUP to the device because this seemed to be necessary for it to start accepting TCP requests. That is expected output.

If the problem is that standby and other requests (except the default wake) aren't working, I suspect this is a Sony bug, as per my latest comment on #142

Answer 3 · 2020-08-25T01:51:03.000Z

Sure, I get that requirement of that. I finally got it to work but now it requires I run ps4-waker in the terminal every time I want to the PS4 to turn on. Homebridge says it's on, but it's not. It's like once it goes to sleep for a long period of time, it's not being awoken by any signal until I run ps4-waker. The moment I run that in terminal, it starts right up.

Answer 4 · 2020-08-25T02:40:08.000Z

It's possible that because homebridge thinks it's awake, it is not doing anything. I'm not associated with homebridge, so you'll have to take that bit up with them. If ps4-waker works, that's all I can do for you.

…

On Mon, Aug 24, 2020, 9:51 PM Grady Houston ***@***.***> wrote: Sure, I get that requirement of that. I finally got it to work but now it requires I run ps4-waker in the terminal every time I want to the PS4 to turn on. Homebridge says it's on, but it's not. It's like once it goes to sleep for a long period of time, it's not being awoken by any signal until I run ps4-waker. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGHIFSHIIBTYZAUFNY5L43SCMKJJANCNFSM4QIYVURA> .

Answer 5 · 2020-08-25T23:51:59.000Z

Well, the thing is it doesn't always work. Half the time when I run ps4-waker in terminal, I still get Could not detect any matching PS4 device. I have the credentials file in the correct place, too.

Answer 6 · 2020-08-26T00:58:51.000Z

Have you tried increasing the timeout? (-t flag)

…

On Tue, Aug 25, 2020, 7:52 PM Grady Houston ***@***.***> wrote: Well, the thing is it doesn't always work. Half the time when I run ps4-waker in terminal, I still get Could not detect any matching PS4 device. I have the credentials file in the correct place, too. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGHIFS64ZVR3ZLAQR4PLRLSCRFCZANCNFSM4QIYVURA> .

Answer 7 · 2020-08-26T01:55:14.000Z

It's been set to 20000. That should be long enough, right?

Answer 8 · 2020-08-26T13:47:38.000Z

That depends on your network topology, possibly router, router config, etc. I just use the default 10000 (10 seconds) and cannot recall it ever timing out, except when the PS4 has just within the last few seconds gone to sleep, but some people have reported that increasing the timeout helps. How frequently and in what situations does it timeout? Have you compared this performance with that of the official app?

…

On Tue, Aug 25, 2020 at 9:55 PM Grady Houston ***@***.***> wrote: It's been set to 20000. That should be long enough, right? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGHIFWR4DDPOFWJ4YFSNFDSCRTQ5ANCNFSM4QIYVURA> .

Answer 9 · 2020-08-27T16:20:23.000Z

ps4-waker doesn't always show in the second screen app but maybe it doesn't need to. When I run ps4-waker in my terminal, it's kind of random when it works vs. when it doesn't. I just ran it right now and it woke it up just fine (even with my TV off), but last night, I was getting the Could not detect any matching PS4 device under the same conditions as right now. The timeout is currently set to 30000. When I do get the Could not detect any matching PS4 device, it's usually after 5-10 seconds.

I'll keep trying. It's just not consistent for me, which I know you can't affect. Just mostly wanting to see if there's something I'm doing wrong with the plugin.

Answer 10 · 2020-08-27T16:55:09.000Z

What I mean is, does the second screen app consistently wake the PS4 in situations where ps4-waker is timing out?

…

On Thu, Aug 27, 2020 at 12:20 PM Grady Houston ***@***.***> wrote: ps4-waker doesn't always show in the second screen app but maybe it doesn't need to. When I run ps4-waker in my terminal, it's kind of random when it works vs. when it doesn't. I just ran it right now and it woke it up just fine (even with my TV off), but last night, I was getting the Could not detect any matching PS4 device under the same conditions as right now. The timeout is currently set to 30000. When I do get the Could not detect any matching PS4 device, it's usually after 5-10 seconds. I'll keep trying. It's just not consistent for me, which I know you can't affect. Just mostly wanting to see if there's something I'm doing wrong with the plugin. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGHIFRTTDBLNXLDHY7L5MTSC2BVNANCNFSM4QIYVURA> .

Answer 11 · 2020-08-27T17:00:16.000Z

Ah, no. The second screen app doesn't always see the PS4. I get "No PS4 found" a lot when the PS4 is off. The app is on the same network at the PS4.

Answer 12 · 2020-08-27T17:07:34.000Z

Ah, yeah in that case unfortunately there's probably nothing much I can do. ps4-waker is based on the same protocols that app uses (by reverse engineering) so in most cases we're limited by the functionality of that app. My best guess would be a router or router config issue; it's possible your router is dropping packets sometimes. Maybe try checking for firmware updates for your router?

…

On Thu, Aug 27, 2020 at 1:00 PM Grady Houston ***@***.***> wrote: Ah, no. The second screen app doesn't always see the PS4. I get "No PS4 found" a lot when the PS4 is off. The app is on the same network at the PS4. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGHIFTAJWWMZ2BUH6XSWMDSC2GK7ANCNFSM4QIYVURA> .

Answer 13 · 2020-08-27T17:17:45.000Z

I'm not seeing any packet drops on the network. I'll keep playing with it. Thank you for the help here!

Answer 14 · 2020-11-01T07:33:45.000Z

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.