There seems to be some confusion:
-
This ps4 component is suitable if you’re using ps4-waker. Typical use-case: ps4-waker and home assistant run on the same host. E.g The docker image @glassbase just mentioned and regular installs like hassbian venv ect… For the full documentation check this wiki. This would be suitable for you @TehRobot1 & @Bieniu.
-
The component component I posted depends on ps4-hass-waker by @vkorn (a REST wrapper around ps4-waker). A typical use-case would be if ps4-hass-waker and hass run on different hosts. ps4-hass-waker is available within vkorn’s hass.io repository or within my docker image (you can build it yourself though). Why is ps4-hass-waker (REST wrapper) even necessary? ps4-waker has an API, but doesn’t expose its service to the network (if I understood that correctly?!). Since docker best-practice is to run one application per container, I chose to build my own docker image with ps4-hass-waker only and didn’t just use the image hnicolaisen/home-assistant (@glassbase be sure that you still run a “pure” home-assistant container and check out the readme of my image on how I generated the ps4-config.json).
Hope I could help you somehow, even though I’m not an expert 
.