Pi Recipes

August 2024:  Openvoice OS has settled down nicely.    Visit openvoiceos.org and download an image or follow install instructions posted @  community.openconversational.ai/t/howto-begin-your-open-voice-os-journey-with-the-ovos-installer.

June 2024:  Added RaspOVOS because it is probably the closest to Picroft yet:  Download Image, burn to Micro SD and boot! 

Late Feb/March 2024:  Our good old Picroft voice assistant finally stopped working due to the demise of Mycroft servers.  Furthermore, Mycroft forums seem to have moved over here -> community.openconversational.ai.   It is all still a tad confusing but there is a comparison of ongoing Mycroft spinoff's here -> neon.ai/ComparingNeon-OVos-Mycroft 

Here are a couple of quick recipes for Picroft alternatives with Mycroft underpinnings.  Be a little careful, both of these seem toj be works-in-process ... Some things work sometimes, reboot and retry before giving up.  Check Matrix for chatter!

• ovos-raspbian:   Appears to be released/ready!   Release Notes are HERE.  This should be the closest to Picroft by far!  Just beginning to play ... more to come

  1. Download ovos-raspian.zip from https://www.openvoiceos.org/downloads

  2. Used Raspberry Pi Imager to burn to 32g Micro SD (I did not apply any os customisation)

  3. Boot on the Pi 

• neon.ai - There is a bootable image (or two) available for download here -> neon.ai/Download.  Neon AI appears to have picked up Mycroft product development and appears to be best way to see Mark II product in action.  Doc can be found here -> neongeckocom.github.io/neon-docs/ and here ->  mycroft-ai.gitbook.io/mark-ii/.   Matrix chat (support) here -> matrix.to/#/#NeonMycroft:matrix.org.    Here are breadcrumbs from installation on the RPI4:

  1. Downloaded "recommended_mark_2.img.xz" (2.1GiB) from this page -> neon.ai/NeonAIforMycroftMarkII

  2. Burned a SD card 64g USB3 Stick using Raspberry Pi Imager.   I misread original post .. SD card was a problem, boot this thing off of USB Stick/drive plugged into upper right USB port!

  3. RPI hardware:  RPI4/2g w/ USB Camera for Mic (C525), a small HDMI monitor w/ sound, Ethernet connection (WiFi will prob work too) and a small keyboard/trackpad (for luck)

  4. Neon boots right up .... but it takes a  while (minutes).   It may try to talk you into an update - be careful, see if it works before updating!  GUI (display) takes a REALLY long time to load .... be patient.
     // ssh is enabled, uc/pw=neon/neon, will force pw change //
     
     

• openvoiceos.org (OVOS) - Still trying to figure this one out, but it appears to be a free-for-all community focused on opensource Mycroft AI platform and related components.   Looks to be a good foundation for a custom voice-bot thingy project.  Doc can (sort of) be found here -> openvoiceos.github.io/community-docs/   - not as solid as Neon, but much more tweakable IF you can get it up and running.  it's pretty squirrelly. I tried and tried to find install steps that worked consistently on the hardware I was using.  Steps below for installing OVOS as a virtualenv on top of newer RaspOS:  

  1.  Burned 32g SD via Raspberry Pi imager:    Ended up using RPIOS 64-Bit LITE (Bookworm) and pre-configuring user=ovos, locale and ssh access.  Running on same RPI4/2g contraption described above - with sd boot instead of usb.

  2. Boot up, apt update & full-upgrade as needed and double check raspi-config ... 

     • System Options-> Set Audio & Hostname  // ACK!  RPIOS Lite did not offer ANY audio initially - boot! //

     • Interface Options-> Enable SSH

     • Localisation Options-> Set Locale & Timezone

  3. Per OVOS readme, install prerequisites for installer (plus joe, my fav editor & some pulseaudio):
     sudo apt-get install curl git sudo joe pulseaudio-utils

  4. Run Installer script.  This will take some time but don't walk away, there is dialog required to get it rolling:
     sh -c "curl -s https://raw.githubusercontent.com/OpenVoiceOS/ovos-installer/main/installer.sh -o installer.sh && chmod +x installer.sh && sudo ./installer.sh && rm installer.sh"
     // Notes: 
     - Installer will occasionally fail due to some ansible download errors - it could take a a re-run (or two). 
     - I also chose virtualenv over docker/containers
     - My installation requires one more tweak to get HDMI audio working - seems to be RPI Lite issue
     // 

IF and when installer finishes successfully, OVOS' virtual environment can be accessed via: 
source .venvs/ovos/bin/activate

Collection of links and a quick-start guide for bringing a dead PicoBrew (Kurig-like Beer brewing machine!) back to life after the company tanked in 2020.   Working on my buddy's Pico Model C.  VERY interesting gizmo.   Links/notes to self below, may be useful to others.

Contraption Overview

• Software:  This guy created a local alternative to picobrew.com - Picobrew server, runs on a Raspberry Pi. 
  Details @ https://trevor-mack.com/picobrew-raspberrypi-setup/ 

  • Github project @ https://github.com/chiefwigms/picobrew_pico/blob/master/README.md

  • Detailed sing-a-long @  https://github.com/chiefwigms/picobrew_pico/releases/tag/v0.0.1-beta6

• Hardware:  Tested with Raspberry Pi Zero(w) but settled on Raspberry Pi 3 A+ because there was one was lying around.  Both seemed to work fine.   16g Micro SD was plenty 

PicoC seemed much simpler than diagram in the blogpost ... our network setup looks like this:

+-----------------+            +-------------+                 !  Home Devices

! PicoC Brewer    ! <- wifi -> ! RaspberryPi !                 !  - Desktop
! IP=192.168.72.1 ! "PICOBREW" ! <Hostname>  ! <---- wifi ---->!  - Laptop
+ (Hardcoded IP)  !            !  (or IP)    !  (home network) !  - IPad
+-----------------+            +-------------+                 !  ... etc

In a nutshell:  The Raspberry Pi sits between home network and the PicobrewC device, providing access/brewer control via a web browser.  

Setup Step-by-Step

(breadcrumbs in case I need to start over): 

• • Downloaded latest/stable version of Picobrew_pico from the "Assets" area of this page:
    https://github.com/chiefwigms/picobrew_pico/releases/tag/v0.0.1-beta6.  
    Downloaded "ps_server_stable_beta6.zip"  (latest was from 2021).   

  • Burned the image to a 16g MicroSD using Raspberry Pi Imager (other options in blogpost): 
    Device=RPI3, OS=Other/Custom (PS_SERVER_STABLE_BETA6..ZIP), Storage,<=my 16g SD)
    // No Customization (if running newer RPI imager) //

  • Booted the SD card on RPI3A+ w/ monitor and keyboard to keep an eye on things ... 

  • Configure RPi using a laptop or desktop with WiFi capabilities ....

    • Connect to WiFi network "PICOBREW" (Password is also "PICOBREW")

    • Customize config via browser (safari, explorer, chrome, etc) via:   http://192.168.72.1/setup
      // Setup may need to be re-selected via top menu after each change, make sure you stay connected to PICOBREW SSID.   Setup is also available on menu via:  System->Setup/Configure Pi  //

      • Setup YOUR home WiFi network  

      • Change the Password on Access Point interface (PICOBREW network)

      • Change the RPi Hostname (if desired).  I used "PicoPi".   PicoPi will reboot after this one ...
        // During reboot, watch for message:  "My IP address is 192.168.72.1 192.x.x.x" ... useful info! //

      • Quick Raspberry Pi Security tweak (optional, but good idea): 
        // You'll also see a 'security risk warning' on RPi console that provides instructions //
        Via Monitor/Keyboard or SSH:   Change RPI password:
        login to RPi using default uc/pw (pi/raspberry), then enter passwd to change password

// The RPi reboot may take some time, I left the monitor connected to watch the action //

• • Using PICOBREW front panel:  Connect PICOBREW to RPi Server   

    • Select Settings/Network/WiFi

    • Scroll to and select "PICOBREW" network
      // you may have to wait for old network to timeout // 

    • Carefully (& painfully) enter WiFi password you assigned to the Access Point in the previous step. 
      Find/Click "OK" to set password.
      // you should see "Connected!" on the display //

  • You should now be able to access the PicoPI via a browser via http://<hostname or IP> 

  • Via PicoPi  Browser screen:

    • Select System->Devices and Press "+ Add New Device"

      • Set Machine Type, Product ID (from picobrew display:  Settings/About) and an Alias

  • That should do it for set up .... 

Random Notes/Tour 

• • Main Screen:  Access by clicking on "PicoBrew Server" in upper left. 
    You should see the Device setup in last step above.  If you click/expand the device you can monitor brewing.

  • Pico Recipes: To create, import and select recipes to send/run on the PicoBrewC.  

    • Importing recipes appear to require RFID of original PicoPak's.   

    • Recipes can be deleted (trash can), cloned/copied, downloaded or 'archived' (green check), which also sends the recipe to the PicoBrew.

    • Clicking on the Title of the recipe provides access to brew steps.  Steps 3-10 can be adjusted  (time, temp, etc).  ** Remember to SAVE (green icon) if tweaking a recipe **

    • Downloaded (or uploaded) recipes are in 'json' format (e.g.  "Base_Recipe_-_American_IPA.json".  

      • There are is a list of Base Recipes under 'Support' menu:  Support->Pico C   ... These can be downloaded/saved to you PC via Right-Click-> 'Save Link As'

      • Upload json file via the Pico Recipes->Library menu item 

  • Support:  Manuals, HowTo Videos, Base Recipes ... 

  • System:  Technical info.  RPi stop/start/setup, logging/debugging, etc

  • Samba:   Picobrew_Pi filesystem can be accessed via samba, still need to investigate potential here.

Resources

• picobrew.com - Still alive as of Jan 2024.  You can still make an account and access public recipes

• www.brewcomputer.com/recipes - Downloadable json recipes?

• Good article @ thirstybastards.com/pakhacking-customizing-picobrew-packs/

• Archive of PicoBrew's Public Recipe Library - https://justin-credible.github.io/picobrew-recipes/ 

To-Do's

• Figure out how to covert beerxml recipies to Picobrew_pico json format

• <prob more here>

October 2023:  Quick(?) look at Threat Hunting ... stumbled upon this https://github.com/jeffvader84/piHunter *AND* had a RPi4 & 64gSD on the workbench

September 2023 - I DID manage to get greenbone/openvas running but NOT on a Raspberry PI.   Ended up using Parrot OS on a little faster x86 machine.   Notes in Tech Tinkering area. 

----

August 2023 - slight change of direction? ... now looking at Threat Hunting.  Lots to learn, compare/contrast with IDS, Vulnerability Scanning, et al.

... Stumbled upon PIhunter @ https://github.com/jeffvader84/piHunter.  Will see if I have a rpi/buster kicking around.  

• RPI4 2g + a 64g SD (hopefully enough to play with this)

• Buster Lite from https://www.raspberrypi.com/software/operating-systems/#raspberry-pi-os-legacy

Sing-a-long with https://github.com/jeffvader84/piHunter/blob/main/README.md

1. Boot 64g - remember, default uc/pw on raspios was pi/raspberry

2. sudo raspi-config (while connected to monitor and keyboard)

   • System Options:  Change Pi Password, Set Hostname

   • Interface Options:  Enable SSH

   • Localisation Options:  Set Locale, Timezone & WAN Country code (in case we need it?)

   • Advanced Options:  Expand Filesystem

   • <more to come>

-------------------

Haven't played with OpenVAS for a very long time, and never on an RPI.  Interested to see how its evolved and how all these IoT 'Things' do on vulnerability scans  ...

*** June 2023 - initial playtime

• Dietpi Base ... DietPi_RPi-ARMv7-Bookworm.img to see if SentinelPi (RPI 2 v1.1) could handle this 

  • Software:  Docker and Portainer (port 9002)

• OpenVAS via Docker:  Sing-a-long with https://pensivesecurity.io/blog/2020/11/16/RPi-Network-Vulnerability-Scanner/

• Brute Force install via https://dayne.broderson.org/2018/05/24/RPi_Vulnerability_Scanner.html 

  • Kali via https://www.offensive-security.com/kali-linux-arm-images/ - blow-by-blow on RPI OS Alternatives  page

  • Steps
    sudo apt-get install openvas (this substituted gvm)
    sudo gvm-setup // Couple of errors (or warnings) when attempting to change directory to /home/kali ... we'll see //
    sudo gvm-check-setup // "It seems like your GVM-22.5.0 installation is OK" ... woo hoo!   //
    sudo greenbone-feed-sync // If any feed sync's faile during setup ... then re-run check-setup until its good to go //

  • Tried to fire up browser to see if https://127.0.0.1:9392/ was alive ... kali hung ... Boot-A-Roo!

  • Gave up on OpenVAS on RPI .... for now.   Not sure there was enough horsepower.   See Greenbone notes in Tech Tinkering area

Initial play with private AI gizmos ... Actually some progress here, but research/breadcrumbs moved for now ...

January 2024 - This one got out of hand ... waaaay too much fumbling and experimenting - created a separate project site to organize.   Here are a few links for now.  

• OpenVoiceOS is still looking good for this, it's a work-in-process but I have a lot of time

• Interesting one @ https://thesecmaster.com/how-to-turn-your-raspberry-pi-into-an-ai-chatbot-server

This one looks like a keeper! ...  cleaned upped  the recipe and and posted on  ServerPi page.   It is now basically a local utility server with a nice face (UI) .... I think there will be a number of handy Self-Hosted apps to come.

This one is turned into SentinelPi - original notes/fumbling/flailing moved over there

Jan 2023:  FINALLY Back at it!  Ran GCompris on stock RPIOS for the heck of it and it ran MUCH better than on DietPi ... not sure why, but it's running great on an RPI3 and looks like it will live in harmony with CutiePi world if need be .. .

Final notes/recipe @  SmartiePi - First Computer for 4-6 Year Old

Feb 2022:  Moved to this site.  Cut/Paste from 'Classic' Google site page @ http://ventures.tpedersen.net/errata/raspberrypi/smartiepi ... did not paste in very well!  

I often make Pi's for others - pre-configuring them for WiFi in someone else's home is a pain in the drain!

Gave Comitup a quick once over - there was a downloadable image @  https://davesteele.github.io/comitup/.    It looks to be JUST what I need AND it WORKS!

Posted experiences with the downloadable image (RaspOS that boots up with Comitup) in Raspberry Pi OS Alternatives.  

I am currently exploring installing/incorporating  Comitup packages into my projects as opposed to starting with the image because I use a variety of OS underpinnings - Q4OS, DietPi, Manjaro ...  it (comitup-1.15-1) seems to be in latest RaspOS which should allow me to apt-get install on everything except Manjaro.  I don't see it in Manjaro or Arch AUR

1. Dietpi+Comitup:  

   • Downloaded Dietpi ARMv6 32-bit. Uses the Raspbian package repository which provides comitup for install!

   • Booted on RPi4 to start with ... usual blow-by-blow

     • Auto updates itself & reboots - now at v8.3.1 - ~5min

     • Forced PW changes, disabled serial console

     • Dietpi config/software

       • Audio:   Enabled, Sound card usb-dac (I'm going to mess with CutiePi enhancements first)

       • Language/Regional:  Locale en_US.UTF8, Timezone & us keyboard

       • Security:  Set Hostname

       • Network/Adapters:  Enable Wifi

       • Network/Other:  Turned Off Boot wait for network (just to be safe)

       • Dietpi Software (season to taste:  I installed stuff I want to live/play together):  Shairport, Murmur, Raspotify, RPI.GPIO, python3, go, ALSA, GIT

     • Stuff I had to install by hand ... via ssh 

       • My editor:  good old joe - apt-get install joe

       • comitup from https://davesteele.github.io/comitup/ - apt-get install comitup
         // Whoops!  WiFi was disabled by default in Dietpi, comitup choked during install - Make sure you add Network steps in dietpi-config above //

       • Whoops AGAIN!  I forgot to RTFM @ https://github.com/davesteele/comitup/wiki/Installing-Comitup ... and I quote:

         • Allow NetworkManager to manage the wifi interfaces by removing references to them from /etc/network/interfaces.

         • Rename or delete /etc/wpa_supplicant/wpa_supplicant.conf.

         • The systemd.resolved service should be disabled and masked to avoid contention for providing DNS service.

         • The line dns=dnsmasq should not be in /etc/NetworkManager/NetworkManager.conf.

         • also changed default ssid in /etc/comitup/comitup.conf - now ap_name: <hostname>-<nnn>

       • I also added comitup to dietpi-services (right or wrong?)

       • comitup-cli is a useful command line tool here

   • Hey!  It works!
     
     

2. Q4OS+Comitup 

   • <next in queue ... I'd think it would work, raspos-based>

Playing w/ OpenCanary Honeypot ... this is a mess/work-in-process

Sing-a-long w/ https://github.com/thinkst/opencanary#readme but ....
.... watching this one as I do:  https://simpaul.com/opencanary-on-a-pi-quick-setup/

Step by step (notes to self)

RPIOS - lite is fine, usual setup:  update/upgrade, rpi-config: pw, hn, local/kb, yada/yada

Switch to Ubuntu 20.04 LTS 32-Bit for 3 reasons - NOPE!  That came out badly

From guide ....

1. OS Tweaks:  Set interesting Mac Address (per Paul's guide) ... add "smsc95xx.macaddr=<enticing mac>" to cmdline.txt

2. Python Prep is a combo Open Canary Guide & Paul's (Including samba and scapy/pcapy because I want it all!)
   sudo apt-get install python3-dev python3-pip python3-virtualenv python3-venv python3-scapy libssl-dev libpcap-dev
   sudo apt install samba # if you plan to use the smb module

3. Back to Paul's guide - looks like he skipped virtual env this go round ... sounds simpler

pip3 install --upgrade setuptools
git clone https://github.com/thinkst/opencanary
cd opencanary
sudo apt-get install libffi-dev # Paul may have missed this one, fatal err missing
sudo python3 setup.py install

4. Set up a couple of links ... from Paul's guide but check version of scripts directory in copy below ... his were 3.7, mine are 3.9
   sudo link /usr/local/bin/twistd /home/pi/opencanary/bin/twistd
   sudo cp ./build/scripts-3.9/opencanary.tac /usr/local/bin/opencanary.tac

5. Back to Opencanary guide for this part ... it did generate config file for me
   $opencanaryd --copyconfig
   [*] A sample config file is ready /etc/opencanaryd/opencanary.conf
   [*] Edit your configuration, then launch with "opencanaryd --start"

6. Edit /etc/opencanaryd/opencanary.conf ... I just poked around initially - Banners 

7. Fire it up ... see if it runs foreground
   opencanaryd --dev

8. Couple of warnings to cleanup from initial run ...

<clip>
UserWarning: You do not have a working installation of the service_identity module: 'No module named 'service_identity''. 
Please install it from <https://pypi.python.org/pypi/service_identity> and make sure all of its dependencies

are satisfied.  Without the service_identity module, Twisted can perform only rudimentary TLS client hostname verifica

tion.  Many valid certificate/hostname mappings may be rejected.

I'm a good guesser ... closed my eyes and fixed this via ...
pip3 install service_identity

9. Turn it into a service so it starts on boot (thx again, Paul)
   File /etc/systemd/system/opencanary.service created, it now contains:

[Unit]
Description=OpenCanary honeypot

After=syslog.target

After=network.target

[Service]

User=root

Restart=always

WorkingDirectory=/home/pi/opencanary

ExecStart=/home/pi/opencanary/bin/opencanaryd --dev

[Install]

WantedBy=multi-user.target

10. Fire it up ...
    sudo chmod 644 /etc/systemd/system/opencanary.service
    sudo systemctl enable opencanary.service
    sudo systemctl start opencanary.service
    sudo systemctl status opencanary.service

11. Boot ... to see what happens

enough for now ...

-----------------

Leftovers to deal with
pip install scapy pcapy # optional

Install fail that forced me to install libffl h

Whoops!  that failed
No package 'libffi' found
c/_cffi_backend.c:15:10: fatal error: ffi.h: No such file or directory
15 | #include <ffi.h>
    |          ^~~~~~~

Samba install output (in case I need it)

Setting up samba (2:4.13.13+dfsg-1~deb11u3) ...

Adding group `sambashare' (GID 125) ...

Done.

Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service

Please ignore the following error about deb-systemd-helper not finding those services.

(samba-ad-dc.service masked)

Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.

Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory

Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.

samba-ad-dc.service is a disabled or a static unit, not starting it.

Processing triggers for man-db (2.9.4-2) ...

Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) ...

A few links at this point ... my bookmarks are a mess

https://github.com/mental32/spotify.py

https://getuikit.com/

Related:  Murmer Server for Push4Papa testing

• DietPi software - https://dietpi.com/docs/software/media/#murmur

• Murmer Server config @ /etc/mumble-server.ini

Also:  Dietpi possibilities for V4

• Samba instead of FTPing - https://dietpi.com/docs/software/file_servers/#samba

• Raspotify?  Playlist rather than uploaded songs/sounds?

• Lighttpd for configing and such - https://dietpi.com/docs/software/webserver_stack/#lighttpd

Bottomline:  This MAY work if I need it ... more putzing to do to get it installed and not as full featured as rpi default vnc server (realvnc).

Considerations/ToDo's
- XP lookswitcher (XPQ4 Desktop) does not show in remote session (I'm probably NOT in the session I'd like to be)
- Below includes definitions for systemd service but I think I'd just fire this up via CLI on an as needed basis
- I still need to double check that it works via remote.it (remote control gizmo I use)

-------

Motivation:  Struggling with stock (RealVNC) vncserver on latest GramPi rebuid ... thought I'd try TightVNC for the heck of it

Rough notes as I go ... Working with Q4OS, but I'd guess this will work on RaspiOS too

TightVNC looks to be GPL, actively maintained and has been around for a long time (> 10 years).  

Most doc seems to be focused on windoze, but this guy posted a RPi step-by-step 

Notes as I go in case I need to retrace my steps

1. Turned off stock VNC Server via sudo raspi-config -> Interface Options -> Disable VNC

2.  Install via sudo apt-get install tightvncserver (this did remove package realvnc-vnc-server)

3. Initial run of vncserver to setup passwords ... it went a little like this ...
   
   vncserver
   
   You will require a password to access your desktops.
   Password: 
   Verify:   
   Would you like to enter a view-only password (y/n)? n
   New 'X' desktop is GramPiV2:1
   Creating default startup script /home/pi/.vnc/xstartup
   Starting applications specified in /home/pi/.vnc/xstartup
   Log file is /home/pi/.vnc/GramPiV2:1.log
   
   

4. Create service per devdude's example, it looks like this:
   cat /etc/systemd/system/vncserver.service

[Unit]
Description=TightVNC Server
After=network.target

[Service]
Type=forking
User=pi
ExecStart=/usr/bin/vncserver :1
ExecStop=/usr/bin/vncserver -kill :1

[Install]
WantedBy=multi-user.target

5. Enable the service to get links built and such ... like this

sudo systemctl enable vncserver

systemctl status vncserver

● vncserver.service - TightVNC Server

  Loaded: loaded (/etc/systemd/system/vncserver.service; disabled; vendor preset: enabled)

  Active: inactive (dead)

pi@GramPiV2:~ $ systemctl enable vncserver        

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===

Authentication is required to manage system service or unit files.                                 

Multiple identities can be used for authentication:

1.  pi

2.  root

Choose identity to authenticate as (1-2): 1

Password:  

==== AUTHENTICATION COMPLETE ===

Created symlink /etc/systemd/system/multi-user.target.wants/vncserver.service → /etc/systemd/syste

m/vncserver.service.

==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===

Authentication is required to reload the systemd state.                                            

Multiple identities can be used for authentication:

1.  pi

2.  root

Choose identity to authenticate as (1-2): 1

Password:  

==== AUTHENTICATION COMPLETE ===

6. Tested via screen sharing on macbook and tigervnc viewer on linux ... seems to work
   some notes ...
   - port is 5901
   - not as full featured as realvnc

Moved to tech.tpedersen.net Feb 2022.  Cut'n Paste from 'Classic' Google site page @ http://ventures.tpedersen.net/errata/raspberrypi/occupi ... VERY STRANGE, this page pasted into new sites quite well, PanelPi was a total mess!

OccuPi - Remote Controlled Full Screen Kiosk-Like thingy

Last update:  09 October 2020

Original 15 September 2020

VERY EARLY Stages, this page will be a mess as I stumble thru this ...

The Goal is to build a little Pi that will connect to my parents TV to allow me to share (project) videos, web pages and such.  Will be used during COVID-19 to keep them occupied over the winter months.  More to come as this idea develops.

Notes/Updates

09 Oct:  Struggling to find OS fast enough to use Google Streetview in Full Screen or Kiosk mode on a Raspberry Pi 3.  It appears that I MUST run Chromium browser to pull this off.  Have tried Arch, Dietpi and Raspbian lite.  On to Chromium OS.  Also created subordinate startpage to simplify testing ... we may end up with a simple webpage providing links to all activities,  

25 Sept:  General concept works very well, even had an old gyration remote control working with it.  RaspOS was painfully slow on the RPi3.  Switching to LXDE desktop from Dietpi to see how that runs.  Dietpi has been my goto for servers, really haven't played with desktop. 

Dietpi/Chromium kiosk is pretty slow.  Friggin streetview map is upside down too!  Added a startpage to facilitate adding activities/features without connecting to or messing with OccuPi system

Research/Reference 

- https://blog.gordonturner.com/2020/06/30/raspberry-pi-full-screen-browser-2020-05-27-raspios-buster/

- https://www.instantstreetview.com/

- https://peter.sh/experiments/chromium-command-line-switches/

- Upside down google maps - https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=274315

- Bigscreen Project - https://plasma-bigscreen.org/

- Chromium OS - Image to try quickly here - https://github.com/FydeOS/chromium_os-raspberry_pi/releases

- Chromium remote desktop - https://remotedesktop.google.com/?pli=1

- Puffins OS - https://www.puffin.com/raspberry-pi/ - Install

Software

- Stock RaspOS - Raspberry Pi OS (32-bit) with desktop to start

- Switching to Rspbian via Dietpi

Hardware

- RPi 3 

- 16g 

- Old Gyration MCE Remote!

Dietpi Setup Notes

• Diepi-config ... minimal work here, let software packages tweak as needed

  • Language/Regional:  en_US.UTF-8, set TZ and US Keyboard

  • Security:  Set Hostname

  • Autostart:  Try Chromium under browser kiosk! - NOT YET!

• dietpi-software

  • [X} Chromium: web browser for desktop or autostart

  • [X] RealVNC Server: desktop for remote connection  

  • [X] Remot3.it: (Weaved) access your device over the internet

  • REMEMBER to select START INSTALLATION!

• NOW back to diet-pi-config

  • Autostart: Chromium under browser kiosk!

  • 
    

----------- RaspOS aborted for now - Save in case I fallback -----------

Steps (raspos)

• Etcher 

• New RaspOS (or whatever) resizes & does a GUI setup on first boot

  • Set Language, Timezone and keyboard

  • Forces user pi password change

  • Screen Setup - gets rid of boarder

  • WiFi Connect (if needed)

  • Software Update - But .... "Error Comparing Versions" - Nice try!

  • <Attempted reboot ... but I wasnt read!>

  • Via Terminal - sudo raspi-config

    • Boot Options

      • Desktop w/ Autologin Pi

      • Wait for Network

      • Graphical Splash Screen

    • Interfacing Options

      • SSH Enable (for remote me!)

      • VNC Enabled (for remote me!)

  • Couple of Installs

    • Joe - my editor of choice -> sudo apt-get install joe

    • remote.it - Remote Control software (nice)  

      • sudo apt-get install remoteit (to install)

      • http://occupi.local:29999 (to config - sooo nice!)

  • Now Attempt Full Screen Browser ...
    from https://blog.gordonturner.com/2020/06/30/raspberry-pi-full-screen-browser-2020-05-27-raspios-buster/

    • Finally learning to follow directions!
      
      

    • sudo apt-get update -y 

    • sudo apt-get upgrade -y
      sudo apt-get dist-upgrade -y
      sudo apt-get autoremove -y

    • Install Dependencies
      
      

    • sudo apt-get install -y ttf-mscorefonts-installer unclutter x11-xserver-utils

    • 
      According to guide:
      ttf-mscorefonts-installer adds common web fonts
      unclutter is used to hide the mouse cursor
      x11-xserver-utils installs xset, which is used to disable screen blanking
      
      

2023 Back to it!

• Will start with a fresh dietpi on good old (almost 10 years) RPI1B!    DietPi_RPi-ARMv6-Bookworm

• Dietpi-software:  Start with Python3, RPi.GPIO and WebIOPI (web interface to play with GPIO leads)

• Webiopi @ https://dietpi.com/docs/software/hardware_projects/#webiopi

Last Update - 21 July 2020

Here wee go again!  PanelPi - A little Pi help to integrate old wired alarm system

*** VERY early in the project, this page is expected to be a mess for quite a while (as usual) ***

Background

PanelPi was initially cobbled together to explore sprucing up our wired home security system.  Current plan is to integrate a number of hardwired sensors into our 'Smart' home.  We'll see!

Software 

• Dietpi.com - My Favorite!  Download latest RPI version (Donate!)

• Etcher.io - Much easier way to flash OS images to SD 

• Couple of Software installs from DietPi's Optimised Software Collection

  • OpenSSH instead of Dropbear SSH Server.  Supports SCP xfers

  • RPi-Monitor - Web interface system stats

  • RPi.GPIO - gpio interface library for rpi (python) 

  • WebIOPi - web interface to control rpi.gpio  

• WebIOPi - web interface to control GPIO.  Install by hand dietpi install fails

Hardware

Current Config

• Raspberry Pi 1 Model B.  Arm6 w/ Ethernet + two USB ports

• EDIMAX USB WiFi adapter

• Old/Original RPi Power Supply (1 amp!)

• Really Old 8g Micro USB card

• Multimeter, some hook clip test thingies (from my Burroughs days!!!)

Stuff to Explore

• Shelly.cloud - Smart relays, switches, sensors

• EnvisaLink EVL-4EZR For DSC & Honeywell Systems

• Konnected.io - Designed to smarten old wired alarms/sensors 

• https://reolink.com/use-upgrade-existing-home-security-alarm-system/ 

• https://www.instructables.com/id/Ethernet-Enabled-DSC-Home-Security-System/

Step by Step (rough notes to self, I'll cleanup later)

Phase I - Pi in Panel. 

Get Panel online - currently in Wifi deadspot.  Use Webiopi to see what is going on with existing sensors.   

• Dietpi via etcher

  • dietpi-config  - as usual - security, naming, etc

  • dietpi-software:  Openssh + RPI-Monitor, RPi.GPIO from optimized software list

  • Don't forget my  editor - apt-get install joe

• Webiopi via instructions @ http://webiopi.trouch.com/INSTALL.html

  • Easiest to download via gui on main system and scp to PanelPi.  Syntax: 

  • scp WebIOPi-0.7.1.tar.gz root@panelpi:/home/WebIOPi-0.7.1.tar.gz

  • Via SSH:

    • Install (setup.sh took a looong time on RPi 1!) 

    • $ tar xvzf WebIOPi-x.y.z.tar.gz

    • $ cd WebIOPi-x.y.z
      $ ./setup.sh

    • Fire it up to test 

    • webiopi -d -c /etc/webiopi/config

  • Access via http://panelpi:8000 

    • Default user/pw "webiopi"/"raspberry".  

    • Change pw using  webiopi-passwd

    • Check /etc/webiopi/config

  • Run a daemon
    
    

  • /etc/init.d/webiopi start/stop

  • Start at boot
    
    

  • update-rc.d webiopi defaults

  • <reboot> to get the witches out and to make sure it all comes up OK before disconnecting keyboard & monitorand moving to the panel!

• Cleanup

  • RPi Monitor data.conf (no ethernet):  Comment out network.conf, uncomment wlan.conf 

  • Disable wifi powersave mode (iwconfig wlan0 power off DID NOT WORK)
    
    iw dev wlan0 set power_save off

  • Reboot with old PS, just to make sure it works!

• Hardware Contraption

  • <coming soon>
    
    

Notes

- PanelPi will have to Wifi to SuitiePi - forgot to run Ethernet to panel area when I had wall out!!! Argh!

    - remember to static route and reserve dhcp so I can find/access PanelPi on that subnet

- WebIOPI did not install via Dietpi ... attempting by hand

    - RPi 1 Model B -> Install instructions @ http://webiopi.trouch.com/INSTALL.html

    - RPi 2 and beyond (40pin GPIO) @ https://thepiguy.altervista.org/webiopi-rp3/

Log, Odd and Ends and fond memories

July 2020 - rebuild

• Can't recall details but had to rebuild,  Dietpi Buster

• Decided to switch to RPI 1 Model B - good use for it

  • 26-pin GPIO is fine. 

• FINALLY traced my steps .... current recipe above

June 2020 - Back at it

• Had to turn on WiFi reconnect in dietpi-config.  I wonder if wifi is dowzing off, powersave?

downloaded attached a GPIO pinout leaf - We'll see if it helps, pretty small print for old eyes!

https://github.com/splitbrain/rpibplusleaf

- Ghazooks!  To keep all this stuff going on our network remember the following.

1. Add host to local DNS in protected router

2. DHCP reservation in AP (SuitiePi), remember to change when hardware is swapped

3. Static Route to PanelPi in ISP router