Add yandex-smart-home extension

[beautyfree]

Description

Control Yandex Smart Home devices and run scenarios from Raycast.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new Yandex Smart Home extension that enables users to control smart home devices and run scenarios directly from Raycast.

Key Features:

• OAuth 2.0 PKCE authentication with verification code flow
• Device control with support for on/off, brightness, color temperature, scenes, and RGB/HSV colors
• Scenario execution for active scenarios
• Comprehensive device property display (sensors: temperature, humidity, battery, etc.)
• Well-organized code structure with proper TypeScript typing

Critical Issue:

• Duplicate clientId preference definition in package.json (lines 30-45) will cause validation errors and prevent the extension from working

Code Quality:

• Clean separation of concerns (API, auth, commands, utils)
• Proper error handling with user-friendly messages
• Follows Raycast extension patterns and conventions
• Good UX with detailed device information and intuitive controls

Confidence Score: 2/5

• This PR has a critical syntax error that will prevent the extension from working
• The duplicate clientId preference definition is a blocking issue that will cause validation errors. Once fixed, the code quality is excellent with proper architecture and error handling.
• extensions/yandex-smart-home/package.json has a critical duplicate preference definition that must be fixed before merge

Important Files Changed

Filename	Overview
extensions/yandex-smart-home/package.json	Extension configuration with duplicate preference definition causing validation error
extensions/yandex-smart-home/src/api/oauth.ts	Well-structured OAuth PKCE implementation with proper token handling
extensions/yandex-smart-home/src/api/yandex-iot.ts	Comprehensive Yandex Smart Home API client with proper typing and helpers
extensions/yandex-smart-home/src/commands/devices.tsx	Feature-rich device control with brightness, color, temperature, and scene support
extensions/yandex-smart-home/src/commands/scenarios.tsx	Simple scenario execution command with proper error handling

[greptile-apps]

_{4 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

extensions/yandex-smart-home
Missing required metadata/ folder with screenshots. Extensions with view-type commands must include Raycast-styled screenshots in a metadata/ folder. See: https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

Context Used: Rule from dashboard - What: Extensions with view-type commands must include a metadata/ folder containing Raycast-styled... (source)

[beautyfree]

Hi, @0xdhrv! Sorry to bother you 😊
Is it possible to pay attention to this PR, I want to share it by Monday if everything works out

[0xdhrv]

@greptileai, could you please do a fresh review of this PR?

[greptile-apps]

_{5 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}