supported_hardware:hubitat
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
supported_hardware:hubitat [2021/02/09 14:34] – James Sentman | supported_hardware:hubitat [2021/06/23 12:53] – added unit naming convention info James Sentman | ||
---|---|---|---|
Line 24: | Line 24: | ||
in this case the API ID is the " | in this case the API ID is the " | ||
+ | ---- | ||
====XTension Settings: | ====XTension Settings: | ||
{{: | {{: | ||
Line 39: | Line 40: | ||
Click the Save button to save the Hubitat plugin instance in XTension. You can then enable the plugin in the Interfaces list window. | Click the Save button to save the Hubitat plugin instance in XTension. You can then enable the plugin in the Interfaces list window. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ====Unit Naming Conventions: | ||
+ | When XTension sees a new unit in the Hubitat it will automatically create a new unit for it with all the proper settings. It will also use the name you have given the unit in the Hubitat as it’s starting point. Once the unit is created the name of the unit is no longer important to the connection and you can change the name in XTension without changing it in the Hubitat. This can be useful if there are name length restrictions or if the naming convention you are using inside the hubitat would not be as useful as what you want to use in XTension. | ||
====Using The Hubitat Plugin:==== | ====Using The Hubitat Plugin:==== | ||
Line 70: | Line 76: | ||
- | **Note:** as of this beta version there is not yet an " | + | **NOTE:** The default |
- | + | ||
- | **NOTE:** Unlike the Vera it seems that the Hubitat | + | |
**Device Notifications: | **Device Notifications: | ||
+ | |||
+ | ===Scene Controllers: | ||
+ | As of XTension 9.4.41 scene controllers and other devices with buttons or inputs should again behave properly. Wireless scene controllers will now create a single unit in XTension. It will not change state itself, but it will receive central scene events about which button was pressed and the number of clicks as available. Hold and release are handled the same as the examples above for switches. | ||
+ | |||
+ | |||
+ | ====Controlling Status LEDs:==== | ||
+ | As of XTension 9.4.41 you can now control the status LED’s of the Home Seer WD200+ dimmers. Please see the [[supported_modules: | ||
====Things That Are Not Implemented Yet:==== | ====Things That Are Not Implemented Yet:==== | ||
Line 84: | Line 95: | ||
Sensor type devices that should be controllable, | Sensor type devices that should be controllable, | ||
- | |||
- | As of this moment it does not appear that setting of device firmware data is supported by the Hubitat protocol. So things like setting the LED display colors on the Innovelli or Home Seer switches is not yet possible. I hope to either have this sorted out or to have a feature request in to the Hubitat folks to implement it as soon as possible but since it is up to them on their side I cannot guarantee when or if this will ever work properly. It is something I make a lot of use through the Vera and so I will be pushing hard to find a way to make this work. It does appear that the hub itself supports setting this information. It is just a matter of bringing it out to the MakerAPI protocol so that we can do it remotely. | ||
The support for location events, control of modes and control of the " | The support for location events, control of modes and control of the " | ||
Line 112: | Line 121: | ||
* Thermostats are working as of XTension version 9.4.36 plugin version 1.1 | * Thermostats are working as of XTension version 9.4.36 plugin version 1.1 | ||
* Ceiling Fan control is working as of XTension version 9.4.37 plugin version 1.2 | * Ceiling Fan control is working as of XTension version 9.4.37 plugin version 1.2 | ||
+ | * Scene Controllers are working as of XTension 9.4.41 |
supported_hardware/hubitat.txt · Last modified: 2023/11/04 13:49 by James Sentman