Pinging the console throws an error, but connecting works about chiaki4deck HOT 3 CLOSED

The ping command will wait up to 30 seconds for availability already with a minimum of 3 seconds, continuing once 3 successful pings (1 every second) are received. If the device is not up the ping command won’t return until later. As soon as it’s up for 3 seconds, it will return. If ping isn’t working for you I’d suggest a sleep of 10 seconds to be safe … I have found 4 to be inadequate. In general, ping is a much better solution than just sleep. I am going to upgrade the ping to an even better solution later (ie using the Chiaki discover protocol to send a properly formatted packet since that port has to be open for remote play to work). Until then, I’ll just leave this as a workaround for people that ping doesn’t work for. (I.e The workaround is deleting the ping command and the two sleep 1 and replacing with sleep 10).

from chiaki4deck.

Yeah, I need to check why exactly ping is not working, I woke up the console manually and pinged from the deck to make the tests and got not response - I do think it must be something on my end, but it's good to know that it still works and yo u can connect nonetheless.

from chiaki4deck.

You should be able to update now by (either updating the flatpak in the discover store or run flatpak update in the console) and going back through https://streetpea.github.io/chiaki4deck/setup/automation/ to update your launch script. It should work for you now as it no longer requires ping. Let me know how it goes.

from chiaki4deck.