IR Remote Control Web Interface

A Blazor WebAssembly application with ASP.NET Core hosting that serves as an IR (Infrared) remote control web interface for controlling circulator/fan devices.

Architecture

This is a client-server application with two main projects:

1. **CoolerSystemController** (Server) - ASP.NET Core host

- Serves the Blazor WebAssembly client

- Provides `/api/ir` endpoint for IR command forwarding

- Communicates with external IR device at `http://192.168.1.22/simplecode`

2. **CoolerSystemController.Client** (Client) - Blazor WebAssembly

- UI components and pages for device control

- Sends IR commands to server API

Key Files

Server-Side

Client-Side

Development Instructions

Running the Application

1. **Start development server:**

```bash

dotnet run --project CoolerSystemController

```

- HTTP endpoint: `http://localhost:5187`

- HTTPS endpoint: `https://localhost:7011`

2. **Build the solution:**

```bash

dotnet build

```

3. **Restore dependencies:**

```bash

dotnet restore

```

4. **Clean build artifacts:**

```bash

dotnet clean

```

Publishing

To publish to the configured network share:

```bash

dotnet publish -p:PublishProfile=FolderProfile

```

Target location: `\\LATTESERVER\KougiSiryou\Dev\IRController`

Communication Flow

1. User interacts with Blazor UI (`Circulator.razor`)

2. Client sends POST request to `/api/ir` endpoint with `SimpleIRCode` payload

3. Server `IRController` forwards command to external IR device

4. IR device at `http://192.168.1.22/simplecode` executes physical command

Technical Details

Making Changes

Adding New IR Commands

1. Update `SimpleIRCode.cs` model if new command format needed

2. Add UI controls in `Circulator.razor`

3. Ensure client sends proper POST requests to `/api/ir`

4. No changes needed in `IRController.cs` unless forwarding logic changes

Modifying UI Layout

Changing IR Device Endpoint

Constraints