{"id":1697,"date":"2015-08-09T03:14:24","date_gmt":"2015-08-09T02:14:24","guid":{"rendered":"https:\/\/stevepedwards.today\/DebianAdmin\/?p=1697"},"modified":"2023-10-28T21:00:40","modified_gmt":"2023-10-28T20:00:40","slug":"testing-webcams-with-fswebcam-pi-noir-picam-and-remote-view-of-motion-on-the-pi","status":"publish","type":"post","link":"https:\/\/stevepedwards.today\/DebianAdmin\/testing-webcams-with-fswebcam-pi-noir-picam-and-remote-view-of-motion-on-the-pi\/","title":{"rendered":"Testing Webcams With fswebcam, Pi Noir Picam and Remote View of Motion on the Pi"},"content":{"rendered":"
<\/div>\n

<\/path><\/svg><\/i> \"Loading\"<\/p>\n

<\/div>\n

This App may get you started with what webcams work with the Pi, and get on with using the PiCam, which gets seen as \/dev\/video0 if it is the only camera.<\/p>\n

From prior research, it may be a good idea to load the PiCam v4l2 driver module at boot by setting:<\/p>\n

bcm2835-v4l2<\/p>\n

in \/etc\/modules:<\/p>\n

\"\"<\/p>\n

After a reboot, you can check it has loaded with:<\/p>\n

root@PiBlanc:~# lsmod | grep v4l<\/span>
\nbcm2835_v4l2 37225 0<\/span>
\nvideobuf2_vmalloc 3009 1 bcm2835_v4l2<\/span>
\nvideobuf2_core 33578 1 bcm2835_v4l2<\/span>
\nv4l2_common 5077 2 bcm2835_v4l2,videobuf2_core<\/span>
\nvideodev 122487 3 bcm2835_v4l2,v4l2_common,videobuf2_core<\/span><\/p>\n

This makes the PiCam v4l2 compatible, so install the v4l-utils<\/p>\n

apt-get install fswebcam v4l-utils
\n<\/span><\/p>\n

man fswebcam
\n<\/span><\/p>\n

SYNOPSIS
\n<\/span><\/p>\n

fswebcam [<options>] <filename> [[<options>] <filename> ... ]
\n<\/span><\/p>\n

DESCRIPTION
\n<\/span><\/p>\n

fswebcam is a small and simple webcam app for *nix. It can capture images
\n<\/span><\/p>\n

from a number of different sources and perform simple manipulation on the
\n<\/span><\/p>\n

captured image. The image can be saved as one or more PNG or JPEG files.
\n<\/span><\/p>\n

The PNG or JPEG image can be sent to stdio using the filename \"-\". The out\u00c3:
\n<\/span><\/p>\n

put filename is formatted by strftime.
\n<\/span><\/p>\n

Capture Options
\n<\/span><\/p>\n

-d, --device [<prefix>:]<device name>
\n<\/span><\/p>\n

Set the source or device to use. The source module is selected auto
\n<\/span><\/p>\n

matically unless specified in the prefix.
\n<\/span><\/p>\n

Default is \/dev\/video0.
\n<\/span><\/p>\n

Available source modules, in order of preference:
\n<\/span><\/p>\n

V4L2 - Capture images from a V4L2 compatible video device.
\n<\/span><\/p>\n

V4L1 - Capture images from a V4L1 compatible video device.
\n<\/span><\/p>\n

FILE - Capture an image from a JPEG or PNG image file.
\n<\/span><\/p>\n

RAW - Reads images straight from a device or file.
\n<\/span><\/p>\n

TEST - Draws colour bars.
\n<\/span><\/p>\n

If you access \u00a0the Pi remotely as I do via PuTTY, create a \/Share in samba accessible to Windows\/Mint, then you view any video test files you create in Win\/Mint A\/V Apps also.<\/p>\n

Check the camera works as normal first with a quick video:<\/p>\n

raspivid -o \/Share\/vidtest.h264<\/span><\/p>\n

View it back in VLC remotely or locally with omxplayer:<\/p>\n

omxplayer \/Share\/vidtest.h264<\/span><\/p>\n

You can check the camera works with fswebcam by taking a TEST in the format above:<\/p>\n

fswebcam -d TEST:\/dev\/video0 \/Share\/TEST.jpg<\/span><\/p>\n

You get the colour bar .jpg picture in Windows photo viewer:<\/p>\n

\"TEST.jpg\"<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

fswebcam -d v4l2:\/dev\/video0 \/Share\/test2.jpg<\/span><\/p>\n

These frames can be replayed by avplay, and appears to just play the single frame continuously like a video, on the HDMI TV until you CtrlC:<\/p>\n

root@raspberrypi:\/home\/stevee# fswebcam -d v4l2:\/dev\/video0 \/Share\/testfs2.jpg<\/span><\/p>\n

--- Opening v4l2:\/dev\/video0...
\n<\/span><\/p>\n

\/dev\/video0 opened.
\n<\/span><\/p>\n

No input was specified, using the first.
\n<\/span><\/p>\n

--- Capturing frame...
\n<\/span><\/p>\n

Captured frame in 0.00 seconds.
\n<\/span><\/p>\n

--- Processing captured image...
\n<\/span><\/p>\n

Writing JPEG image to '\/testfs2.jpg'.
\n<\/span><\/p>\n

root@raspberrypi:\/home\/stevee# avplay \/Share<\/span>\/test2.jpg<\/span><\/p>\n

avplay version 9.14-6:9.14-1rpi1rpi1, Copyright (c) 2003-2014 the Libav developers
\n<\/span><\/p>\n

built on Jul 22 2014 15:08:12 with gcc 4.6 (Debian 4.6.3-14+rpi1)
\n<\/span><\/p>\n

Input #0, image2, from '\/testfs2.jpg':
\n<\/span><\/p>\n

Duration: 00:00:00.04, start: 0.000000, bitrate: N\/A
\n<\/span><\/p>\n

Stream #0.0: Video: mjpeg, yuvj420p, 384x288 [PAR 1:1 DAR 4:3], 25 tbn
\n<\/span><\/p>\n

^C 6.69 A-V: 0.000 s:0.0 aq= 0KB vq= 0KB sq= 0B f=0\/0 0\/0
\n<\/span><\/p>\n

root@raspberrypi:\/home\/stevee# fswebcam -d TEST \/TEST.jpg
\n<\/span><\/p>\n

--- Opening TEST...
\n<\/span><\/p>\n

--- Capturing frame...
\n<\/span><\/p>\n

Captured frame in 0.00 seconds.
\n<\/span><\/p>\n

--- Processing captured image...
\n<\/span><\/p>\n

Writing JPEG image to '\/testfs.jpg'.
\n<\/span><\/p>\n

root@raspberrypi:\/home\/stevee# avplay \/test.jpg<\/span><\/p>\n

avplay version 9.14-6:9.14-1rpi1rpi1, Copyright (c) 2003-2014 the Libav developers
\n<\/span><\/p>\n

built on Jul 22 2014 15:08:12 with gcc 4.6 (Debian 4.6.3-14+rpi1)
\n<\/span><\/p>\n

Input #0, image2, from '\/test.jpg':
\n<\/span><\/p>\n

Duration: 00:00:00.04, start: 0.000000, bitrate: N\/A
\n<\/span><\/p>\n

Stream #0.0: Video: mjpeg, yuvj420p, 384x288 [PAR 1:1 DAR 4:3], 25 tbn
\n<\/span><\/p>\n

72.80 A-V: 0.000 s:0.0 aq= 0KB vq= 0KB sq= 0B f=0\/0 0\/0
\n<\/span><\/p>\n

You can use fswebcam to test different webcams for compatibility in linux for V4l1, v4l2 or raw formats:<\/p>\n

root@raspberrypi:\/home\/stevee# fswebcam -d v4l1:\/dev\/video1<\/strong> \/titan.jpg
\n<\/span><\/p>\n

--- Opening v4l1:\/dev\/video1...
\n<\/span><\/p>\n

\/dev\/video1 opened.
\n<\/span><\/p>\n

\/dev\/video1: Not a V4L device?
\n<\/span><\/p>\n

VIDIOCGCAP: Inappropriate ioctl for device
\n<\/span><\/p>\n

\/dev\/video1 closed.
\n<\/span><\/p>\n

root@raspberrypi:\/home\/stevee# fswebcam -d v4l2:\/dev\/video1<\/strong> \/titan.jpg<\/span><\/p>\n

--- Opening v4l2:\/dev\/video1...
\n<\/span><\/p>\n

\/dev\/video1 opened.
\n<\/span><\/p>\n

No input was specified, using the first.
\n<\/span><\/p>\n

Unable to find a compatible palette format.
\n<\/span><\/p>\n

root@raspberrypi:\/home\/stevee# fswebcam -d raw:\/dev\/video1<\/strong> \/titan.jpg<\/span><\/p>\n

--- Opening raw:\/dev\/video1...
\n<\/span><\/p>\n

No palette format specified.
\n<\/span><\/p>\n

 <\/p>\n

What great little command line App after all the complexity and disappointment with ZM.<\/p>\n

For RasPi useable webcams see here:<\/p>\n

https:\/\/elinux.org\/RPi_USB_Webcams<\/a><\/p>\n

As expected, the Creative Optia cam is v4l2 compatible and creates a picture also:<\/p>\n

\"\"<\/p>\n

The other that worked was a<\/p>\n

Bus 001 Device 016: ID 0ac8:305b Z-Star Microelectronics Corp. ZC0305 Webcam
\n<\/span><\/p>\n

\"\"<\/p>\n

Note the auto change in dimensions between the different cameras.<\/p>\n

https:\/\/www.slblabs.com\/2012\/09\/26\/rpi-webcam-stream\/<\/a><\/p>\n

One of the nice features of fswebcam is that it's possible to add a footer to the capture, where you can specify your text of choice.
\nFor instance, this is the command I ran fswebcam with:<\/span><\/p>\n

$ fswebcam -r 640x480 -S 15 --flip h --jpeg 95 --shadow --title \"SLB Labs\" --subtitle \"Home\" --info \"Monitor: Active @ 1 fpm\" --save home.jpg -q -l 60
\n<\/span><\/p>\n

https:\/\/www.home-automation-community.com\/surveillance-with-raspberry-pi-noir-camera-howto\/<\/a><\/p>\n

Ok, that's a big help for future considerations and testing of cheap surveillance webcameras, and after ZM did not seem to run the Pi Noir, I'll try Motion as the surveillance App.<\/p>\n

man motion
\n<\/span><\/p>\n

SYNOPSIS
\n<\/span><\/p>\n

motion [ -hns ] [ -c config file path ] [ -d level ] [ -p
\n<\/span><\/p>\n

process_id_file ]
\n<\/span><\/p>\n

DESCRIPTION
\n<\/span><\/p>\n

Motion uses a video4linux device to detect motion. If motion is
\n<\/span><\/p>\n

detected both normal and motion pictures will be taken. Motion can also
\n<\/span><\/p>\n

take actions to notify you if needed. Creation of automated snapshots
\n<\/span><\/p>\n

is also possible.
\n<\/span><\/p>\n

OPTIONS
\n<\/span><\/p>\n

-c Full path and filename of config file. E.g.
\n<\/span><\/p>\n

\/home\/kurt\/motion.conf. Default is \/usr\/local\/etc unless speci\u00c3:
\n<\/span><\/p>\n

fied differently when building Motion. Many RPMs and debian
\n<\/span><\/p>\n

packages will most likely use \/etc or \/etc\/motion as default.
\n<\/span><\/p>\n

-h Show help screen.
\n<\/span><\/p>\n

-n Run in non-daemon mode.
\n<\/span><\/p>\n

-s Run in setup mode. Also forces non-daemon mode
\n<\/span><\/p>\n

-d level
\n<\/span><\/p>\n

Run in debug mode, level 1-9.
\n<\/span><\/p>\n

-p Full path and filename for process id file (pid file). E.g
\n<\/span><\/p>\n

\/var\/run\/motion.pid. Default is not defined. Pid file is only
\n<\/span><\/p>\n

created when Motion is started in daemon mode.
\n<\/span><\/p>\n

CONFIG FILE OPTIONS
\n<\/span><\/p>\n

These are the options that can be used in the config file. They
\n<\/span><\/p>\n

are overridden by the commandline! All number values are inte\u00c3:
\n<\/span><\/p>\n

ger numbers (no decimals allowed). Boolean options can be on or
\n<\/span><\/p>\n

off (values \"1\", \"yes\" and \"on\" all means true and any other
\n<\/span><\/p>\n

value means false).<\/span><\/p>\n

The link above<\/p>\n

https:\/\/www.slblabs.com\/2012\/09\/26\/rpi-webcam-stream\/<\/a><\/p>\n

has done a brief overview of Motion so let me try some things with it.<\/p>\n

First, backup the motion.conf file to somewhere, then recap the conf file settings overview in the Post I wrote when researching it first time:<\/p>\n

cp -v \/etc\/motion\/motion.conf \/Share\/motion.conf.bak<\/span><\/p>\n

https:\/\/stevepedwards.today\/DebianAdmin\/usb-cam-intro-to-motion-and-zoneminder\/<\/a><\/p>\n

vi \/etc\/motion\/motion.conf<\/p>\n

Leaving it at defaults for now to see what happens, and check first output when motion is run:<\/p>\n

root@raspberrypi:~# motion<\/span><\/p>\n

[0] Processing thread 0 - config file \/etc\/motion\/motion.conf
\n<\/span><\/p>\n

[0] Motion 3.2.12 Started
\n<\/span><\/p>\n

[0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478785
\n<\/span><\/p>\n

[0] Thread 1 is from \/etc\/motion\/motion.conf
\n<\/span><\/p>\n

[1] Thread 1 started
\n<\/span><\/p>\n

[1] cap.driver: \"bm2835 mmal\"
\n<\/span><\/p>\n

[1] cap.card: \"mmal service 16.1\"
\n<\/span><\/p>\n

[0] motion-httpd\/3.2.12 running, accepting connections
\n<\/span><\/p>\n

[1] cap.bus_info: \"platform:bcm2835-v4l2<\/strong>\"
\n<\/span><\/p>\n

[0] motion-httpd: waiting for data on port TCP 8080
\n<\/span><\/p>\n

[1] cap.capabilities=0x85200005
\n<\/span><\/p>\n

[1] - VIDEO_CAPTURE
\n<\/span><\/p>\n

[1] - VIDEO_OVERLAY
\n<\/span><\/p>\n

[1] - READWRITE
\n<\/span><\/p>\n

[1] - STREAMING
\n<\/span><\/p>\n

[1] Test palette YU12 (320x240)
\n<\/span><\/p>\n

[1] Using palette YU12 (320x240) bytesperlines 480 sizeimage 115200 colorspace 00000001<\/strong>
\n<\/span><\/p>\n

[1] found control 0x00980900, \"Brightness\", range 0,100
\n<\/span><\/p>\n

[1] \"Brightness\", default 50, current 50<\/strong>
\n<\/span><\/p>\n

[1] found control 0x00980901, \"Contrast\", range -100,100
\n<\/span><\/p>\n

[1] \"Contrast\", default 0, current 0
\n<\/span><\/p>\n

[1] found control 0x00980902, \"Saturation\", range -100,100
\n<\/span><\/p>\n

[1] \"Saturation\", default 0, current 0
\n<\/span><\/p>\n

[1] found control 0x0098090e, \"Red Balance\", range 1,7999
\n<\/span><\/p>\n

[1] \"Red Balance\", default 1000, current 1000
\n<\/span><\/p>\n

[1] found control 0x0098090f, \"Blue Balance\", range 1,7999
\n<\/span><\/p>\n

[1] \"Blue Balance\", default 1000, current 1000
\n<\/span><\/p>\n

[1] mmap information:
\n<\/span><\/p>\n

[1] frames=4
\n<\/span><\/p>\n

[1] 0 length=115200
\n<\/span><\/p>\n

[1] 1 length=115200
\n<\/span><\/p>\n

[1] 2 length=115200
\n<\/span><\/p>\n

[1] 3 length=115200
\n<\/span><\/p>\n

[1] Using V4L2<\/strong>
\n<\/span><\/p>\n

[1] Resizing pre_capture buffer to 1 items
\n<\/span><\/p>\n

[1] Started stream webcam server in port 8081<\/strong>
\n<\/span><\/p>\n

Let's see what's in a browser as the Noir LED is lit, after changing remote access:<\/p>\n

# Restrict webcam connections to localhost only (default: on)
\n<\/span><\/p>\n

webcam_localhost off
\n<\/span><\/p>\n

# Restrict control connections to localhost only (default: on)
\n<\/span><\/p>\n

control_localhost off
\n<\/span><\/p>\n

\"\"
\n<\/span><\/p>\n

Setup mode is working on ports 8080 so now stop and turn off in the conf file.<\/p>\n

# Start in Setup-Mode, daemon disabled. (default: off)
\n<\/span><\/p>\n

setup_mode off
\n<\/strong><\/span><\/p>\n

Restart and try 8081
\n<\/strong><\/p>\n

[1] Using V4L2
\n<\/span><\/p>\n

[1] Resizing pre_capture buffer to 1 items
\n<\/span><\/p>\n

[1] Started stream webcam server in port 8081
\n<\/span><\/p>\n

KMeleon Browser:<\/p>\n

\"\"
\n<\/strong><\/p>\n

https:\/\/www.instructables.com\/id\/Raspberry-Pi-remote-webcam\/<\/a><\/p>\n

Lots of Q+As link - Chrome and IE viewer problems! No good for Motion's stream mjpeg<\/p>\n

\"\"<\/p>\n

IE thinks the stream is a file download!<\/p>\n

\"\"<\/p>\n

Now to test for max screen values starting at 640 x 480:<\/p>\n

# Image width (pixels). Valid range: Camera dependent, default: 352
\n<\/span><\/p>\n

#width 320
\n<\/span><\/p>\n

width 640
\n<\/span><\/p>\n

# Image height (pixels). Valid range: Camera dependent, default: 288
\n<\/span><\/p>\n

#height 240
\n<\/span><\/p>\n

height 480
\n<\/span><\/p>\n

[1] Test palette YU12 (640x480)
\n<\/span><\/p>\n

[1] Using palette YU12 (640x480) bytesperlines 960 sizeimage 460800 colorspace 00000001
\n<\/span><\/p>\n

OK!<\/p>\n

\"\"
\n<\/span><\/p>\n

3 times bigger? 960 x 720? Yep!<\/p>\n

\"\"
\n<\/span><\/p>\n

4 X? 1280 x 960?<\/p>\n

[1] Test palette YU12 (1280x960)
\n<\/span><\/p>\n

[1] Using palette YU12 (1280x960)
\n<\/span><\/p>\n

\"\"
\n<\/span><\/p>\n

5X = 1600 x 1200. Try it...yep!<\/p>\n

[1] Test palette YU12 (1600x1200)
\n<\/span><\/p>\n

[1] Using palette YU12 (1600x1200)
\n<\/span><\/p>\n

 <\/p>\n

\"\"<\/p>\n

I can see detail on the wallpaper and curtains now!<\/p>\n

Try 6X? 1920 X 1440? Yep!<\/p>\n

[1] Test palette YU12 (1920x1440)
\n<\/span><\/p>\n

[1] Using palette YU12 (1920x1440)
\n<\/span><\/p>\n

\"\"<\/p>\n

And finally! A cool command to find what formats the Pi Noir camera is capable of:<\/p>\n

root@raspberrypi:\/# v4l2-ctl -d \/dev\/video0 --list-formats<\/span><\/p>\n

ioctl: VIDIOC_ENUM_FMT
\n<\/span><\/p>\n

Index : 0
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'YU12'
\n<\/span><\/p>\n

Name : 4:2:0, packed YUV
\n<\/span><\/p>\n

 <\/p>\n

Index : 1
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'YUYV'
\n<\/span><\/p>\n

Name : 4:2:2, packed, YUYV
\n<\/span><\/p>\n

 <\/p>\n

Index : 2
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'RGB3'
\n<\/span><\/p>\n

Name : RGB24 (LE)
\n<\/span><\/p>\n

 <\/p>\n

Index : 3
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'JPEG' (compressed)
\n<\/span><\/p>\n

Name : JPEG
\n<\/span><\/p>\n

 <\/p>\n

Index : 4
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'H264' (compressed)
\n<\/span><\/p>\n

Name : H264
\n<\/span><\/p>\n

 <\/p>\n

Index : 5
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'MJPG' (compressed)
\n<\/span><\/p>\n

Name : MJPEG
\n<\/span><\/p>\n

 <\/p>\n

Index : 6
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'YVYU'
\n<\/span><\/p>\n

Name : 4:2:2, packed, YVYU
\n<\/span><\/p>\n

 <\/p>\n

Index : 7
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'VYUY'
\n<\/span><\/p>\n

Name : 4:2:2, packed, VYUY
\n<\/span><\/p>\n

 <\/p>\n

Index : 8
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'UYVY'
\n<\/span><\/p>\n

Name : 4:2:2, packed, UYVY
\n<\/span><\/p>\n

 <\/p>\n

Index : 9
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'NV12'
\n<\/span><\/p>\n

Name : 4:2:0, packed, NV12
\n<\/span><\/p>\n

 <\/p>\n

Index : 10
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'BGR3'
\n<\/span><\/p>\n

Name : RGB24 (BE)
\n<\/span><\/p>\n

 <\/p>\n

Index : 11
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'YV12'
\n<\/span><\/p>\n

Name : 4:2:0, packed YVU
\n<\/span><\/p>\n

 <\/p>\n

Index : 12
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'NV21'
\n<\/span><\/p>\n

Name : 4:2:0, packed, NV21
\n<\/span><\/p>\n

 <\/p>\n

Index : 13
\n<\/span><\/p>\n

Type : Video Capture
\n<\/span><\/p>\n

Pixel Format: 'BGR4'
\n<\/span><\/p>\n

Name : RGB32 (BE)
\n<\/span><\/p>\n

root@raspberrypi:\/# v4l2-ctl -d \/dev\/video0 --list-framesizes=YUYV<\/span><\/p>\n

ioctl: VIDIOC_ENUM_FRAMESIZES
\n<\/span><\/p>\n

Size: Stepwise 16x16 - 2592x1944<\/strong> with step 2\/2
\n<\/span><\/p>\n

If you want to understand the details of 4:2:0 or 4:2:2 watch guru Monty Montgomery explain it all:<\/p>\n

https:\/\/xiph.org\/video\/vid1.shtml<\/a>
\n<\/span><\/p>\n

\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/div>\n

<\/path><\/svg><\/i> \"Loading\"<\/p>\n

<\/div>\n

This App may get you started with what webcams work with the Pi, and get on with using the PiCam, which gets seen as \/dev\/video0 if it is the only camera. From prior research, it may be a good idea to load the PiCam v4l2 driver module at boot by setting: bcm2835-v4l2 in \/etc\/modules: After ...\u00a0 Testing Webcams With fswebcam, Pi Noir Picam and Remote View of Motion on the Pi<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-1697","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"a3_pvc":{"activated":true,"total_views":1,"today_views":0},"_links":{"self":[{"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/posts\/1697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/comments?post=1697"}],"version-history":[{"count":1,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/posts\/1697\/revisions"}],"predecessor-version":[{"id":10020,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/posts\/1697\/revisions\/10020"}],"wp:attachment":[{"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/media?parent=1697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/categories?post=1697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stevepedwards.today\/DebianAdmin\/wp-json\/wp\/v2\/tags?post=1697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}