Thanks everyone for the valuable input and feedback on these Device Handlers. To make use the button mapped capabilities, you can use the stock Smart Lighting or Button Controller SmartApps (the Button Controller smartApp is currently limited to the first 4 buttons), Button Controller Plus, or of course CoRE.
The links below will always have the most current version of the Device Handler - so there’s no need to skim through this thread to find the latest version: The single, double, triple, and hold functions for each of the up/down cases are mapped to device buttons 1-8 ( mapping here)
Homeseer reviews full#
There are also preference options to turn the light on full brightness following a double-tap or single-tap up action, as well an option to set the dim level to 25% after a double-tap down action. The WD100+ dimmer device handler includes preference options for the device firmware capabilities to set local and remote ramp rates and to reverse the dimmer direction. The device handlers display the current switch firmware version and also include virtual buttons on the mobile app to allow triggering double and triple tap as well as hold actions. These device handlers provide support for the switch’s firmware capabilities for Central Scene notifications for double-tap, triple-tap, and hold functionality for both up and down presses, as well as instant status. HomeSeer could really make this ecosystem better by providing guidance and possibly even enforcing minimum standards for documentation, especially for developers who charge $30-40 for their plugins.After several months in beta, this is an initial release of the device handlers for the HomeSeer HS-WS100+ on/off switch and the HomeSeer HS-WD100+ dimmer. It may be posted on an independent website, posted within a forum as a downloadable document, or even just exist as a collection of forum messages by the developer interspersed with user questions - sort of a deploy then answer as you have time approach. Documentation, if it exists, may be copied to any number places when the plugin is installed or not at all.
Homeseer reviews install#
While HS has made a folder for documentation in their install folder (which puts user-editable files under C:\Program Files (x86)), 3rd parties don't seem to follow any rules. The documentation is even more disorganized.
Homeseer reviews code#
Plugins are sometimes available through the plug-in manager, but some problems are resolved by posting code on a forum.
Homeseer reviews trial#
It's a free-for-all, and it makes development very difficult, depending more on fellow users in a forum for trial and error, and the occasional casually delivered insight from the plug-in developers. Perhaps the biggest disappointment has been HomeSeer has not established or at least enforced any particular style or location for documentation. The limited usability of HS without 3rd party plugins makes it difficult to review HomeSeer alone, and it is in the plugins that the quality varies significantly from one to the next While HomeSeer has some HomeSeer-developed plugins, there are far more available through 3rd parties. Part of this may be due to the involvement of HS and 3rd party plugins. NET script, but there are no exposed triggers to fire the script without depending on the logic in the GUI event builder. There are variables, but you cannot set, test, or manipulate them in the GUI event logic, and special commands are necessary to access them from script.Ībout that script: HomeSeer DOES support VB and C. There is no method of grouping logic statements with parenthesis, so AND/OR in the same logic can be dicey, depending on order of precedence. For example, there are if statements, but no else. Having previously run a JDS Technologies StarGate, I was disappointed in the limits of the HomeSeer product, particularly in the event builder, a GUI for creating event logic.
0 kommentar(er)
