-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use hostname instead of IP with -d flag #68
Comments
The It looks like we do get some info about the device in addition to the IP address from which it broadcasted its response to our query, so it's probably possible to filter on that. In fact it may even be as simple as adding another "or" there with something like I only have one device myself so I probably won't get to this anytime soon, but I would welcome a PR ;) |
I unfortunately also only have the one, and I'm none too swift with the JS unfortunately :P I was using the home-assistant component that leverages this tool and it requires a static IP because reasons I guess. I've modified that component as a workaround for now. |
@agc93, how did you modify the component to use a hostname? Was your issue related to having ps4-waker and home-assistant in different subnets? This is the problem I'm trying to solve at the moment. |
@jcconnell I've only got the one PS4 so I just removed the I have my PS4 and HA in the same subnet, just it's on DHCP so the IP would change. |
When connecting to a specific PS4 using the
-d
flag, it would be helpful to support using a hostname rather than only an IP address. Is this something you'd consider?The text was updated successfully, but these errors were encountered: