Switch for Playstation 4

[Aaraeus]

Thanks for this!

[fanuch]

@Rich_Paul

pi@raspberrypi:~ $ sudo cp /root/.ps4-wake.credentials.json /home/homeassistant/
cp: cannot stat ‘/root/.ps4-wake.credentials.json’: No such file or directory

also doesnt work…
Any help would be appreciated

Can you try
sudo find / -name "*ps4-wake.credentials*"
Perhaps your credentials file is not located there

[hmn (Henrik Nicolaisen)]

I created a custom media player instead of all of the custom switches, but it still uses the ps4-waker tool.

https://github.com/hmn/home-assistant-config/blob/master/custom_components/media_player/ps4.py

Any feedback is apreciated

[mphp]

@hmn that sounds really cool. About to start playing with it. How do you declare it in configuration.yaml? Is it autodiscovered?

[hmn (Henrik Nicolaisen)]

you just create a media_player like this

media_player:
  - platform: ps4
    host: 10.254.2.191

[Aaraeus]

This looks incredible! Sorry to be such a noob, but where do I add the .py file? Do I just add it to my .homeassistant folder where my configuration.yaml is?

[hmn (Henrik Nicolaisen)]

look at the file structure in https://github.com/hmn/home-assistant-config you just have to add the custom_components folder to your config dir

it’s also described here https://home-assistant.io/developers/component_loading/

[Aaraeus]

Ah brilliant, it’s up and running!

Weirdly though it looks like I can’t wake/unwake the ps4 anymore. When I use

sudo ps4-waker

from ssh, it works fine… but my switch and media player don’t turn the ps4 on or off respectively.

Is there a setting somewhere I need to tweak?

[hmn (Henrik Nicolaisen)]

I use docker so it might be why I don’t need to sudo, try changing the command in the module to sudo ps4-waker

[Aaraeus]

@hmn

I use docker so it might be why I don’t need to sudo, try changing the command in the module to sudo ps4-waker

I changed the bit just after ‘cmd=’ to add sudo (in the python script) and it didn’t work. Although I did also change the command in the switch to sudo too, as below:

switch:

• platform: command_line
  switches:
  playstation_4:
  command_on: ‘sudo ps4-waker’
  command_off: ‘sudo ps4-waker standby’
  command_state: 'nmap -p 9295 my_ps4_ip_address | grep -w -Eo “open” ’
  value_template: ‘{{ value == “open” }}’
  friendly_name: “Playstation 4”

and that didn’t work either. It’s really bizzare, it was working this morning! This leads me to believe maybe something else is going on.

I’ve updated my node-js to the latest stable release too, as others mentioned in this thread.

Thanks for your help on this, us noobs greatly appreciate it! Also I’m learning python atm so this is a great .py script to start with!

Edit: Just followed some instructions above that got me into /root/ on my pi and change visudo. Did all that and my switch now works - woo! Media player recognises the ps4 when it’s on, but the on/off button doesn’t quite work. For now I’m just going to disable it and I’ll try again later.

[fanuch]

I’m only 4 days into using Home Assistant but I’m incredibly impressed at the amazing work from all contributors!

@hmn , I’ve tried your script and it works flawlessly so far. My only issue was that my credentials file was stored at /home/homeassistant/ and not /home/homeassitant/.homeassistant/ .

I would love to add button controls inside the PS4 media player front end so you can navigate simple applications such as YouTube and Netfilx. I will try work on it to help out.

[Aaraeus]

It looks like I keep getting this error:

17-04-26 16:09:57 ERROR (Thread-9) [homeassistant.components.switch.command_line] Command failed: nmap -p 9295 PS4_IP_ADDRESS | grep -w -Eo “open”

Not sure why this is erroring since my ps4 waker actually works from the switch. nmap is installed too.

[Rich_Paul]

Someone has posted the answer above:

Making it work in HA
Great change that this command will not be working yet if you try to run it as a shell command in Home Assistant.
So what i did is:
Login to putty and then:
sudo su
visudo

then find this line:

User privilege specification

root ALL=(ALL:ALL) ALL

copy and past the root line. So now you have two the same lines under each other. Then change root to the username where Home Assistant is running. ( you can find that name in the path to you configuration.yaml.) I think for an all in one install it will be “hass” and for a hassbian install like i have it is “homeassistant”

So the result will be:

User privilege specification

root ALL=(ALL:ALL) ALL
homeassistant ALL=(ALL:ALL) ALL

press ctrl + x and then Y and then Enter.

After this go to the sudoers.d folder:
cd /etc/sudoers.d

And create a new file like this:
sudo nano 010_homeassistant-nopasswd

In this file copy the following line
homeassistant ALL=(ALL) NOPASSWD: ALL

and close it with ctrl + X, then Y then press Enter.

[Aaraeus]

@Rich_Paul

Someone has posted the answer above:

I tried all that and just double checked, and it’s definitely all done. Just checked visudo and all those edits are completed, same with the cd /etc/sudoers.d folder contents.

I did all that and the switch started working, but the media player still won’t budge.

[kylerw]

This looks nice! What does the ps4-games.json file look like?

Would love to see an official PR.

[hmn (Henrik Nicolaisen)]

the ps4-games.json is auto updated every time you start a game and it looks like this

{
  "CUSA01116": "YouTube", 
  "CUSA02676": "DRTV", 
  "CUSA02491": "Mass Effect\u2122", 
  "CUSA01703": "Plex", "CUSA00127": "Netflix"
}

[hmn (Henrik Nicolaisen)]

I can add it to the main project and create a pull request, but I was unsure if it was a good idea because of the ps4-waker requirements

[kylerw]

Yeah, I forgot about that. Being that it’s not in Python I doubt it would be allowed.

[kylerw]

I run in Docker and use a different default port, anyway I can specify that in the configuration.yaml?

Edit: Add to schema and then adjust on line 203-ish? Is that it? testing now.

[kylerw]

I added an option to specify the port but it doesn’t seem to register the proper state of the PS4