Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Emmet last won the day on November 27 2018

Emmet had the most liked content!

Community Reputation

1 Neutral

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Emmet

    Authentication Error while Reading RFID Card.

    Hi @Odyn, The ground was indeed incorrect, but the rest of the wiring should be correct, we have now corrected that. From memory, the previous wiring issue involved a different wire and not the ground. If you are facing issues can you please create a new topic detailing what's going wrong. Cheers, Emmet
  2. Emmet

    Changing static DNS

    Hi @user1979, This is pretty simple to do, begin by editing the resolv.conf file by running the following command. sudo nano /etc/resolv.conf Within this file you will find something like below, nameserver Replace that with the following, this will change the nameservers to the IP's you specified earlier nameserver nameserver Then save the file and restart your Raspberry Pi. Let me know how that goes for you. Cheers, Emmet
  3. Emmet

    nukkit server update mcpe

    Hey @goofyblocks, It looks like the original version of Nukkit ceased development and there is now NukkitX https://nukkitx.com/. You should be able to just the .jar provided from them in place of the Nukkit one. We will look into updating our tutorial as soon as possible. Cheers, Emmet
  4. Hi @The_Joker_07, For starters there was a mistake with the following command in the tutorial, i have now gone and corrected it. The following command sudo apt-get install jstest /dev/input/js0 Should actually be. sudo jstest /dev/input/js0 Let me know if that lets you interact with your Xbox controller, I will try and find time to attempt this with my own Xbox controller to see if i can replicate the issues that you are having. Before attempting to pair the xbox one controller over Bluetooth have you tried running the following command? sudo bash -c echo 1 > /sys/module/bluetooth/parameters/disable_ertm Cheers, Emmet
  5. Hi @wallace4793, By following the tutorial the wireless network created during the tutorial should be funneled through the VPN tunnel, so any connections made to that wireless network should be running through that. Are you having any issues with the network appearing? Cheers, Emmet
  6. Emmet

    Telegram CLI - not able to receive or send msg

    Hi @Victoria, I took a look into this issue and was able to get the messages sending via the two bash scripts. The scripts that were mentioned within the existing tutorial, however, need to be modified slightly. In the tg.sh file you need to modify the following line, (echo "msg $1 $2"; echo "safe_quit") | ${tgpath}/bin/telegram-cli -k tg-server.pub -W Into (sleep 3; echo "msg $1 $2"; echo "safe_quit") | ${tgpath}/bin/telegram-cli -k tg-server.pub -W Additionally, the tg_photo.sh file also has the same problem, so that also needs to be adjusted as shown below. (echo "send_photo $1 $2"; echo "safe_quit") | ${tgpath}/bin/telegram-cli -k tg-server.pub -W Into (sleep 3; echo "send_photo $1 $2"; echo "safe_quit") | ${tgpath}/bin/telegram-cli -k tg-server.pub -W The issue was caused by the Telegram CLI not having retrieved the contacts list from the server before it was fed the "msg" command. The addition of the sleep command into the script should pause the msg command being sent long enough that the CLI tool should have retrieved the contact list. Let me know if you have any issues. Cheers, Emmet
  7. Hi @mxplea10, Are you just running the motioneye software or running the motioneye OS? The Raspberry Pi's CPU is quite limited so dealing with lots of high resolution and high frame rate cameras will very quickly push it to its limit. I can't remember whether motionEye uses hardware acceleration via the GPU either. Do you happen to know what format your IP cameras send the footage in, like h264? You could try reducing both the frame rate and resolution, see if that shows any improvements. On the note of properly logging out of motionEye, I am unsure as it has been a fair while since I have had to utilize that software. Cheers, Emmet
  8. Emmet

    Google SDK not starting on boot

    Hi @EduLordFire Can you try running the following command and retrying the service. sudo systemctl enable systemd-networkd-wait-online.service
  9. Emmet

    Google Assistant "Oauth not setup for this device"

    Hi @Rick Nasher, Can you try running the following command and retrying the service. sudo systemctl enable systemd-networkd-wait-online.service
  10. Emmet

    Google SDK not starting on boot

    Hi @EduLordFire, Thank you for posting the full error, I will see if i can reproduce this error on a clean install. I'll see if i can find out why this is happening, it kind of looks like it is trying to start up the Google Assistant software before the network is actually available 😕
  11. Emmet

    Google Assistant "Oauth not setup for this device"

    Hi Rick, The service should work fine without having to make any changes to permissions as the service file we setup in the tutorial tells the service to utilize the pi user and the pi group to run the file, so its weird you are having issues with that. The service itself is set to start up when the network becomes available, which occurs quite late in Raspbians boot-up process. It would be interesting to see the full errors from the systemd status call as the ones you have posted there are sadly cut off and don't provide quite enough to show what has actually gone wrong.
  12. Emmet

    Google Assistant "Oauth not setup for this device"

    Hi @Rick Nasher, It appears as if Google finally got around to fixing some of the issues we had to implement workarounds for, I will rerun through the tutorial a couple of times and clear out some of the additional steps that we had to have in place. It looks like you can actually complete the tutorial now without having to have a display connected. On the note of the script auto starting I cant actually replicate any issues with it, as it is auto starting fine for me. Could you provide me the response from the following two commands. sudo systemctl start assistant.service sudo systemctl status assistant.service
  13. Emmet

    Google SDK not starting on boot

    Hi @Cortney, Looking into the issue, the status code that is being returned indicates that for some reason it is failing to use that command. Can you please try running the following command on your Raspberry Pi. /bin/bash /home/pi/start_assistant.sh If that works as intended, can you try modifying the service file again, clearing all current data and re-entering it as shown in the steps below. There is the chance that the issues you are facing are being caused by an encoding issue with one of the text elements as we are unable to replicate the issue. Step 1: sudo nano /lib/systemd/system/assistant.service Step 2, replace all text with [Unit] Description=Google Assistant Wants=network-online.target After=network-online.target [Service] Type=simple ExecStart=/bin/bash /home/pi/start_assistant.sh Restart=on-abort User=pi Group=pi [Install] WantedBy=multi-user.target Step 3, Save the file. Then run the following command to start up the service sudo systemctl start assistant.service Step 4, Check the status of the service. sudo systemctl status assistant.service
  14. Emmet

    RPi Speed Monitor project question

    Hi, @gathermail, I am glad that change fixed the issues that you were having, and yes you are correct that running something as root isn't just a permissions elevations issue. A root user still has all of its own configurations, permissions and all that. That was the same assumption I had made when writing that tutorial that the crontab was a system wide file, turns out i was mistaken and each user has their own crontab which meant in turn gdrives authentication files were not being found when the root users crontab fired the script as it had none set in its own home directory. Thank you for coming to the forums and reporting the issue, helps us fix the problem for future users as well that would of likely ran into the same issue. Cheers, Emmet
  15. Emmet

    RPi Speed Monitor project question

    Hi, @gathermail, There was a mistake in the tutorial where we were modifying the super users crontab rather then the current users, which means when it went to run the gdrive software, it was looking for its authentication files in the roots home and no the pi users. The simplest solution to this is to modify the crontab as the current user by just using the following command. crontab -e You may also want to remove the entry you initially added to the super users cronjob. Let me know if that solves your issues. Cheers, Emmet