Issue with ps4-waker

[luisiam]

So I have some issues running homebridge-cmd with ps4-waker. When I use Siri to turn on the PS4 using ps4-waker, Siri always cannot get a response from the device. However, the PS4 does turns on. Probably the process is too long and Siri quit waiting for the response. Can you add a timeout, i.e. 2 seconds, so that it assumes the command is succeed if it doesn't throw an error?

Another issue happens when I ask Siri to issue off command while PS4 is turned off. It will throw an error. For my case, I set up the "I'm leaving" scene to turn off everything. If my PS4 is turned off and I issue the scene, Siri will throw an error and have trouble activating the scene.

[kevireilly]

Have you tried the --failfast and/or --timeout 2000 parameters that you can pass to ps4-waker?

[luisiam]

I think I found the reason behind that. For turning on the PS4, the whole process just takes too long, around 10 seconds, and Siri will quit waiting. --failfast or --timeout won't work. It's not failing. It connects to the PS 4 successfully and it's just in the process of turning it on, i.e. turn on --> sign in.

For turning off the PS4, ps4-waker will always throw error if the system is turned off. As callback(error) is used, that always cause the problem. It's just how ps4-waker is designed.

I managed to find some work around and rewrote the whole plugin for myself.

[kevireilly]

Ah OK, good to know. Is it available on Github should someone else want to use it? Also, you may want to consider making pull requests for this plugin and/or ps4-waker because someone will surely experience this again.

[luisiam]

I pretty much rewrite almost everything and created a new plugin. I also added a status check feature. It will be kinda hard to create pull request. I did put it on Github. You can take a look and give me some comments =]

https://github.com/luisiam/homebridge-cmdswitch