David
94b13f733a
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>
15 lines
967 B
TypeScript
15 lines
967 B
TypeScript
export declare const CONNECTIVITY_REASONS: readonly ["WIFI_BAD_PASSWORD", "WIFI_AP_NOT_FOUND", "WIFI_ROUTER_UNREACHABLE", "WIFI_AP_CHANNEL_QUALITY_LOW", "INTERNET_UNREACHABLE", "CAPTIVE_PORTAL_CHECK_FAILED", "UNKNOWN"];
|
|
/**
|
|
* Version 3.1, as the page is titled. It defines connectivity only. Examples on other pages declare 3 and 3.2;
|
|
* alex2node 1.x declared 3.3, which no page mentions.
|
|
*/
|
|
export declare const EndpointHealth: import("../types.js").InterfaceDescriptor<{
|
|
connectivity: {
|
|
name: string;
|
|
value: import("../schema.js").Schema<import("../schema.js").InferShape<{
|
|
value: import("../schema.js").EnumSchema<"UNREACHABLE" | "OK">;
|
|
reason: import("../schema.js").OptionalSchema<"UNKNOWN" | "WIFI_BAD_PASSWORD" | "WIFI_AP_NOT_FOUND" | "WIFI_ROUTER_UNREACHABLE" | "WIFI_AP_CHANNEL_QUALITY_LOW" | "INTERNET_UNREACHABLE" | "CAPTIVE_PORTAL_CHECK_FAILED">;
|
|
}>>;
|
|
note: string;
|
|
};
|
|
}, {}, {}, false>;
|