WebSocket for live updates in Raspberry Pi

Introduction

WebSocket lets your Raspberry Pi talk to a web page instantly. It helps send live updates without waiting.

You want to show sensor data on a webpage as it changes.

You need to control devices from a browser in real-time.

You want to build a chat app that updates messages instantly.

You want to display live notifications or alerts on a webpage.

Syntax

Raspberry Pi

import asyncio
import websockets

async def handler(websocket):
    async for message in websocket:
        await websocket.send(f"Got your message: {message}")

async def main():
    async with websockets.serve(handler, "localhost", 8765):
        await asyncio.Future()  # run forever

asyncio.run(main())

This example uses Python's asyncio and websockets library.

The server listens on port 8765 and sends back messages it receives.

Examples

This server sends a greeting once a client connects, then prints any messages it gets.

Raspberry Pi

import asyncio
import websockets

async def handler(websocket):
    await websocket.send("Hello from Raspberry Pi!")
    async for message in websocket:
        print(f"Received: {message}")

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

asyncio.run(main())

This example sends sensor data every second to connected clients.

Raspberry Pi

import asyncio
import websockets

async def handler(websocket):
    while True:
        data = get_sensor_data()  # pretend function
        await websocket.send(str(data))
        await asyncio.sleep(1)  # send every second

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

asyncio.run(main())

Sample Program

This program runs a WebSocket server on your Raspberry Pi. It sends a fake temperature reading every 2 seconds to any connected client.

Raspberry Pi

import asyncio
import websockets
import random

async def handler(websocket):
    while True:
        temp = random.uniform(20.0, 25.0)  # fake temperature
        message = f"Temperature: {temp:.2f} °C"
        await websocket.send(message)
        await asyncio.sleep(2)

async def main():
    async with websockets.serve(handler, "localhost", 8765):
        print("WebSocket server started on ws://localhost:8765")
        await asyncio.Future()  # run forever

asyncio.run(main())

Important Notes

Make sure to install the websockets library with pip install websockets.

WebSocket connections stay open, so they use less data than asking the server again and again.

Use localhost for testing on the same device, but use your Pi's IP address for other devices.

Summary

WebSocket lets your Raspberry Pi send live updates to web pages instantly.

It keeps a connection open so data flows both ways without delay.

Use it for real-time sensor data, controls, or notifications.

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