Unable to set up chiaki4deck with PS4 on wired connection about chiaki4deck HOT 20 CLOSED

Bumping to add that I was able to add the PS4 when I connected it to WiFi, but it is no longer accessible once I switch it back to ethernet connection.

Update: I was now able to finish the registration of the console, but every time I try to start remote play I get an error "Chiaki Session has quit: Connection Refused in Session Request." If anybody could tell me what this means and how to fix it I would really appreciate it.

from chiaki4deck.

It sounds like it’s not accepting your registration. Given your firmware is 10. I think you should be using account id instead of ps online id (you’ll get this if you don’t select ps firmware < 7) since your firmware is greater than 7 (I.e., 10 > 7). In order to get your account id follow this section using the tab new to using Chiaki on Steam Deck.

from chiaki4deck.

Thank you! I managed to get it registered, but it now won't boot up with the automated script. I can connect just fine when in SteamDeck's desktop mode, but for some reason the chiaki4deck app in my library in game mode just hangs. Any suggestions on how to fix this new issue?

from chiaki4deck.

Can you try ysing the automated script to launch it in desktop mode? Use the following command in the konsole:

"${HOME}/.var/app/re.chiaki.Chiaki4deck/config/Chiaki/Chiaki-launcher.sh"

from chiaki4deck.

This also does not work unfortunately. It says to double check that my PS4 and Deck are on the same network, which they are – double-clicking my Playstation in the Chiaki4deck window in desktop mode launches remote play just fine, it's now just the script itself that won't connect.

from chiaki4deck.

Are you using the right ip? You can double check by looking at the GUI. Also try ping -c3 ip where ip is the given ip.

from chiaki4deck.

The picture is just the script not running the script …

from chiaki4deck.

Not sure what you mean...

from chiaki4deck.

You run the script by typing

"${HOME}/.var/app/re.chiaki.Chiaki4deck/config/Chiaki/Chiaki-launcher.sh"

Into the konsole

from chiaki4deck.

Yes. I did that. Also does not work. I'll try and get a picture in a second.

from chiaki4deck.

Like you did with ping command but use that command instead … what you posted is the first several lines of the script itself which has functions that trigger on errors …

from chiaki4deck.

Here is the result of the script you just suggested (bottom most area of the screen):

from chiaki4deck.

Hmmm 38. isn’t a local subnet …. Should be 10. 172. Or 192.

from chiaki4deck.

That’s the ip it shows in the gui?

from chiaki4deck.

Interesting...yes, that's the IP address in the GUI (which connects fine!) and as it shows up on my PS4 itself

from chiaki4deck.

Is it possibly because my PS4 is connected to ethernet rather than WiFi?

from chiaki4deck.

Maybe based on your wifi settings… when you connect via wifi does it give a different ip (specifically does it give one starting with 10. 192. Or 172.)? Note: I deleted the images of your ip because it does seem to be public and accessible via the internet as opposed to a private address which doesn’t mean anything out of your local network.

from chiaki4deck.

Thank you! Yes, it did give a different IP, one that starts with 192. Unfortunately I can't use this reliably, since my PS4 drops WiFi signal pretty regularly and ethernet is the only reliable connection. Any workarounds for this?

from chiaki4deck.

Can you set a reserved ip for your device following this for your router: https://www.coolblue.nl/en/advice/assign-fixed-ip-address-router.html and then try using that address (in 192. range let’s say) I’m thinking there should be some sort of setting for this on the router as that’s what should be determining your ip. Im assuming your PS4 is connected via Ethernet to your router.

from chiaki4deck.

Thanks for the suggestion – I disconnected my ethernet cable linking my PS4 to the modem and plugged it into the remaining LAN port on my wireless router instead, which then gave the PS4 an IP beginning with 192. This seems to have resolved it! Thank you very much for the help and troubleshooting!

from chiaki4deck.