AlexaErrors has a helper for each of the 73 types of the table on alexa-errorresponse.html, named after the type in camel case: 63 take the message only, 10 take the payload fields their page documents. A field the page requires (reason, currentDeviceMode, currentChargeState, resourceType) is a required argument, so leaving it out does not compile; from JavaScript the helper throws a TypeError that lists the values. validRange is optional, as the page says, and has both ends when given. temperatureOutOfRange and setpointsTooClose stay as shorter names. The helpers are compared with the 15 examples of the four error pages. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
21 lines
807 B
TypeScript
21 lines
807 B
TypeScript
/**
|
|
* Something that is on or off, under an instance name: the oscillation of a fan, the light of an oven. The one
|
|
* generic controller that Alexa hunches work with (SetEcoOn, SetEcoOff, EcoOn, EcoOff).
|
|
*/
|
|
export declare const ToggleController: import("../types.js").InterfaceDescriptor<{
|
|
toggleState: {
|
|
name: string;
|
|
value: import("../schema.js").EnumSchema<"OFF" | "ON">;
|
|
};
|
|
}, {
|
|
TurnOn: {
|
|
name: string;
|
|
payload: import("../schema.js").Schema<import("../schema.js").InferShape<{}>>;
|
|
};
|
|
TurnOff: {
|
|
name: string;
|
|
payload: import("../schema.js").Schema<import("../schema.js").InferShape<{}>>;
|
|
};
|
|
}, import("../schema.js").InferShape<{
|
|
semantics: import("../schema.js").OptionalSchema<import("../types.js").Semantics>;
|
|
}>, true>;
|