Plugin Name
homebridge-script2
Link To GitHub Repo
https://github.com/pponce/homebridge-script2
Plugin Icon (Optional)
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟢 Yes
The plugin successfully installs and does not start unless it is configured.
🟢 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
🟢 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
🟢 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
🟢 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
🟢 Yes
More Information
Script2 combines separate command-execution and optional HomeKit-acknowledgement deadlines with per-switch duplicate suppression, serialized opposite-state actions, shared state reads, and late-failure reconciliation. A long-running command can continue after HomeKit is acknowledged without being launched again; if it subsequently fails, Script2 bypasses its cache and corrects HomeKit using the configured state source.
Additional controls include configurable state-cache lifetime, optional cache reset after successful actions, configurable handling of ordinary nonzero state-command exits, filesystem-based state notifications, and stateless switches that trigger on either On or Off and reset without issuing another command.
The distinction is this combination of behaviors in a focused, configurable switch plugin—not a claim that basic command execution, polling, or queues are individually exclusive to Script2.
Plugin Name
homebridge-script2
Link To GitHub Repo
https://github.com/pponce/homebridge-script2
Plugin Icon (Optional)
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟢 Yes
The plugin successfully installs and does not start unless it is configured.
🟢 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
🟢 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
🟢 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
🟢 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
🟢 Yes
More Information
Script2 combines separate command-execution and optional HomeKit-acknowledgement deadlines with per-switch duplicate suppression, serialized opposite-state actions, shared state reads, and late-failure reconciliation. A long-running command can continue after HomeKit is acknowledged without being launched again; if it subsequently fails, Script2 bypasses its cache and corrects HomeKit using the configured state source.
Additional controls include configurable state-cache lifetime, optional cache reset after successful actions, configurable handling of ordinary nonzero state-command exits, filesystem-based state notifications, and stateless switches that trigger on either On or Off and reset without issuing another command.
The distinction is this combination of behaviors in a focused, configurable switch plugin—not a claim that basic command execution, polling, or queues are individually exclusive to Script2.