ade34b7da6
* fix(alexa): v3 API compliance fixes, fan speed, and security panel control Bring the Alexa Smart Home integration in line with the current v3 API. Tier 1 (malformed responses / missing handlers): - BrightnessController: report brightness under the Alexa.BrightnessController namespace instead of Alexa.PowerController so Set/AdjustBrightness responses match the advertised capability. - SmartVision ObjectDetection: flatten the doubly-nested payload.events array. - SecurityPanelController: add Arm/Disarm directive handlers (previously advertised but unhandled, silently falling through to a fake success), wired to armSecuritySystem/disarmSecuritySystem. Enforce the spec rule rejecting a direct ARMED_AWAY -> other armed-state transition with AUTHORIZATION_REQUIRED. Drop the advertised FOUR_DIGIT_PIN authorization, which Scrypted cannot honor. - Auth failures now return an Alexa INVALID_AUTHORIZATION_CREDENTIAL ErrorResponse instead of a bare HTTP 500 that Alexa retries and surfaces as a generic skill error. API modernization: - EndpointHealth: downgrade to the documented v3.1 / connectivity-only shape and stop emitting the undocumented battery property (and 3.2 version), which risks the whole capability being rejected. - Fan: add Alexa.RangeController (Fan.Speed, 0-100%) for devices implementing the Fan interface, alongside the existing PowerController on/off. Cleanups: - addAccessToken: initialize event.endpoint as an object, not an array. - Hoist getArmState to a shared export instead of duplicating it. Bump version to 0.4.0. * fix(alexa): improve camera stream quality and connectivity Tune the WebRTC negotiation for Alexa camera sessions. - Resolution: raise the proxied stream cap from 720p to 1080p. The previous 1280x720 screen hint forced the transcoder into medium-resolution mode for every endpoint, so even an Echo Show 15 or Fire TV only received 720p. 1080p lets larger displays render sharply while the transcoder still clamps width and falls back to 720p when H.264 High can't be negotiated. We cap rather than send the uncapped source, since Alexa's directive carries no display hint and a 4K stream would waste bandwidth on smaller Echo devices. - Two-way audio: only advertise isFullDuplexAudioSupported when the camera implements the Intercom interface. Advertising full duplex on a one-way camera makes Alexa set up a return mic path that goes nowhere. - TURN: stop unconditionally disabling TURN, and expose a "Use TURN Servers" plugin setting (on by default). Alexa sessions are proxied and often cross NATs where a TURN relay is the only path that connects; combined with disabled trickle ICE (all candidates in the initial SDP), omitting the relay candidate left NAT-blocked sessions with no fallback. When enabled, TURN usage defers to the WebRTC plugin's own setting, matching the Google Home integration; disabling it force-disables TURN for Alexa sessions only. Bump version to 0.5.0.
Scrypted
Scrypted is a high performance home video integration platform and NVR with smart detections. Instant, low latency, streaming to HomeKit, Google Home, and Alexa. Supports most cameras. Learn more.
Installation and Documentation
Installation and camera onboarding instructions can be found in the docs.
Community
Scrypted has active communities on Discord, Reddit, and Github. Check them out if you have questions!
Development
Debug Scrypted Plugins in VS Code
# this is an example for homekit.
# check out the code
git clone https://github.com/koush/scrypted
cd scrypted
# get the dependencies for the server and various plugins
./npm-install.sh
# open the homekit project in VS Code
code plugins/homekit
You can now launch (using the Start Debugging play button) the HomeKit Plugin in VS Code. Please be aware that you do not need to restart the Scrypted Server if you make changes to a plugin. Edit the plugin, launch, and the updated plugin will deploy on the running server.
If you do not want to set up VS Code, you can also run build and install the plugin directly from the command line:
# currently in the plugins/homekit directory.
npm run build && npm run scrypted-deploy 127.0.0.1
Plugin SDK Documentation
Want to write your own plugin? Full documentation is available here: https://developer.scrypted.app
Debug the Scrypted Server in VS Code
Debugging the server should not be necessary, as the server only provides the hosting and RPC mechanism for plugins. The following is for reference purpose. Most development can be done by debugging the relevant plugin.
# check out the code
git clone https://github.com/koush/scrypted
cd scrypted
# get the dependencies for the server and various plugins
./npm-install.sh
# open server project in VS Code
code server
You can now launch the Scrypted Server in VS Code.