No Bytes

After the successful initial set up of my Rock Pi S, I started going on with my project self made smart home assistant. Therefor, it is necessary to configure the network interface. SSH Does Not Mean Network Is Fine Though we already are able to connect to the Rock Pi S via SSH, we probably cannot yet ping servers outside our local network. A ping to google.com, for example, will result in no answer: Destination Host Unreachable The reason is, that there is no standard gateway set in the network configuration, which causes, that only local network hosts inside the same subnet can be reached. The gateway is like the door of your flat. If You don't know, where it is, You cannot even leave your flat and see the rest of the street. To find out your standard gateway, there are different approaches between Windows and Linux. Maybe You need to investigate this for your client operating system. On Windows, You open a command line and type: ipconfig The output loo

Update / Warning: Until now, I was not able to get this project working. So if You are looking for a working solution, this is none. Maybe You do not need to read the following part of this project, because they were written, before I figured out, that this will not work. As it turned out, the Rock Pi S cannot run Snips.ai any more (after a Kernel update to get the sound working).  (Original Article Starts Here) With the progress of my smart home assistant project , I finally found an adequate hardware with the possibility to connect up to eight microphones: the Rock Pi S from Radxa . What sounded like a promising small device turned out to be a little bit tricky. Inspired by an interesting  article of the german IT publisher heise.de , I decided to order a Rock Pi S for my project. So I took the version with 512 MB RAM, Bluetooth and WiFi (ordered at the at this time point only available store n Germany, maker-store.de ). After delivery and unboxing of the device, the