WebSocket for live updates in Raspberry Pi - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a WebSocket?

A WebSocket is a way for a computer to keep a connection open with a server so they can send messages back and forth instantly, like a phone call instead of sending letters.

beginner

Why use WebSocket for live updates on a Raspberry Pi?

WebSocket lets the Raspberry Pi get new information right away without asking again and again, saving power and making updates faster.

intermediate

Which protocol does WebSocket use to start a connection?

WebSocket starts with an HTTP handshake, then switches to the WebSocket protocol for continuous communication.

intermediate

How does a Raspberry Pi listen for WebSocket messages in Python?

It uses a WebSocket client library to connect and then waits for messages in a loop, reacting when new data arrives.

beginner

What is a common use case of WebSocket on Raspberry Pi?

To show live sensor data or control devices instantly from a web page without refreshing the page.

What makes WebSocket different from regular HTTP requests?

A It requires no internet connection.

B It sends data only once and closes immediately.

C It keeps the connection open for instant two-way communication.

D It uses email to send messages.

WebSocket keeps the connection open so both sides can send messages anytime without reconnecting.

Which language is commonly used on Raspberry Pi to handle WebSocket connections?

A HTML

B Python

C CSS

D SQL

Python is popular on Raspberry Pi for programming WebSocket clients and servers.

What is the first step in establishing a WebSocket connection?

A Sending a text message

B Running a SQL query

C Closing the connection

D HTTP handshake

WebSocket starts with an HTTP handshake to upgrade the connection.

Why is WebSocket good for live updates?

A Because it sends updates instantly without waiting.

B Because it stores data in a database.

C Because it uses less electricity than a light bulb.

D Because it only works offline.

WebSocket sends data instantly as soon as it is available.

Which of these is NOT a feature of WebSocket?

A Automatically saves data to disk

B Continuous connection

C Two-way communication

D Instant message delivery

WebSocket does not save data to disk automatically; it only manages communication.

Explain how WebSocket helps a Raspberry Pi show live sensor data on a web page.

Think about how the Pi and browser talk without waiting.

Describe the steps to set up a WebSocket client on a Raspberry Pi using Python.

Focus on the code flow from start to receiving data.

Practice

1. What is the main advantage of using WebSocket on a Raspberry Pi for live updates?

easy

A. It keeps a connection open for instant two-way data flow.

B. It sends data only once when the page loads.

C. It requires no network connection to work.

D. It stores data locally on the Raspberry Pi.

Solution

1. Step 1: Understand WebSocket connection behavior

   WebSocket keeps a connection open between the Raspberry Pi and the web page, allowing data to flow instantly both ways.

2. Step 2: Compare options with WebSocket features

   Options A, B, and C do not describe WebSocket's live, continuous connection feature.

3. Final Answer:

   It keeps a connection open for instant two-way data flow. -> Option A

4. Quick Check:

   WebSocket = open two-way connection [OK]

Hint: Remember: WebSocket keeps connection open for live updates [OK]

Common Mistakes:

• Thinking WebSocket sends data only once
• Confusing WebSocket with HTTP request-response
• Assuming WebSocket works offline

2. Which of the following is the correct way to create a WebSocket client connection in JavaScript on a Raspberry Pi web page?

easy

A. const socket = new Socket('ws://localhost:8080');

B. const socket = WebSocket.connect('http://localhost:8080');

C. const socket = WebSocket('https://localhost:8080');

D. const socket = new WebSocket('ws://localhost:8080');

Solution

1. Step 1: Recall correct WebSocket syntax in JavaScript

   The correct syntax to create a WebSocket client is using the WebSocket constructor with the URL starting with 'ws://' or 'wss://'.

2. Step 2: Check each option's syntax

   const socket = new WebSocket('ws://localhost:8080'); uses 'new WebSocket' with 'ws://' which is correct. Options A, B, and D use incorrect methods or protocols.

3. Final Answer:

   const socket = new WebSocket('ws://localhost:8080'); -> Option D

4. Quick Check:

   WebSocket client = new WebSocket('ws://...') [OK]

Hint: Use 'new WebSocket("ws://...")' to create connection [OK]

Common Mistakes:

• Using 'http://' instead of 'ws://'
• Calling WebSocket as a function without 'new'
• Using undefined methods like WebSocket.connect

3. Given this Python code running on a Raspberry Pi using the 'websockets' library, what will be printed when a client connects and sends 'Hello'?

import asyncio
import websockets

async def handler(websocket):
    message = await websocket.recv()
    print(f'Received: {message}')

async def main():
    async with websockets.serve(handler, 'localhost', 8765):
        await asyncio.Future()

asyncio.run(main())

medium

A. Received: Hello

B. Received: websocket

C. Error: No client connected

D. Received: None

Solution

1. Step 1: Understand the handler function

   The handler waits to receive a message from the client and then prints it with 'Received: ' prefix.

2. Step 2: Analyze what happens when client sends 'Hello'

   The message 'Hello' is received and printed as 'Received: Hello'.

3. Final Answer:

   Received: Hello -> Option A

4. Quick Check:

   Received message = 'Hello' [OK]

Hint: Handler prints whatever client sends prefixed by 'Received:' [OK]

Common Mistakes:

• Assuming it prints 'websocket' instead of message
• Expecting an error without client connection
• Thinking it prints None if message missing

4. Identify the error in this Raspberry Pi WebSocket server code snippet:

import asyncio
import websockets

async def handler(websocket):
    while True:
        message = websocket.recv()
        print(message)

async def main():
    async with websockets.serve(handler, 'localhost', 8765):
        await asyncio.Future()

asyncio.run(main())

medium

A. The server address 'localhost' is invalid.

B. The while loop should be outside the handler function.

C. Missing 'await' before websocket.recv() call.

D. The 'asyncio.run(main())' should be 'asyncio.start(main())'.

Solution

1. Step 1: Check asynchronous calls in handler

   The 'websocket.recv()' is a coroutine and must be awaited to get the message.

2. Step 2: Verify other parts of the code

   Address 'localhost' is valid, the loop inside handler is correct for continuous receiving, and 'asyncio.run' is the proper way to start.

3. Final Answer:

   Missing 'await' before websocket.recv() call. -> Option C

4. Quick Check:

   Await async calls like websocket.recv() [OK]

Hint: Always await async functions like websocket.recv() [OK]

Common Mistakes:

• Forgetting 'await' on async calls
• Misplacing the while loop
• Using wrong asyncio start function

5. You want your Raspberry Pi to send live temperature updates to a web page using WebSocket. Which approach best ensures the web page updates instantly when the sensor value changes?

hard

A. Open a new WebSocket connection every time the temperature changes.

B. Open a WebSocket connection once, then send new temperature data whenever it changes.

C. Send temperature data only when the web page reloads.

D. Use HTTP GET requests repeatedly to fetch temperature data.

Solution

1. Step 1: Understand WebSocket usage for live updates

   WebSocket keeps a connection open, so sending data only when it changes over the same connection is efficient and instant.

2. Step 2: Evaluate other options

   Opening new connections repeatedly (B) wastes resources. Sending data only on reload (C) or using HTTP polling (D) is slower and less real-time.

3. Final Answer:

   Open a WebSocket connection once, then send new temperature data whenever it changes. -> Option B

4. Quick Check:

   One open connection + send updates = instant live data [OK]

Hint: Keep one connection open; send updates as they happen [OK]

Common Mistakes:

• Opening multiple connections unnecessarily
• Relying on page reloads for updates
• Using HTTP polling instead of WebSocket