Mac Home Automation

User Tools

Site Tools

You are here: Macintosh Home Automation With XTension » Plugins » Hubitat
supported_hardware:hubitat

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
supported_hardware:hubitat [2021/02/10 14:41] – James Sentmansupported_hardware:hubitat [2023/04/07 15:42] – [Things That Are Not Implemented Yet:] removed things that are supported now James Sentman
Line 31: Line 31:
 If you have only a single Hubitat on your network you can leave the defaults for **Address** as "hubitat.local" under normal circumstances the port should be left as "80." If you have only a single Hubitat on your network you can leave the defaults for **Address** as "hubitat.local" under normal circumstances the port should be left as "80."
  
-If you are running multiple Hubitat's on the network then you will need to provide them with Static IP addresses so you know which one XTension is connecting to. There is no interface to this inside the Hubitat itself so you will need to visit the configuration of your router and create a DHCP reservation for the 2 devices, then restart them to make sure they pick up the new address if you changed it from what they were using at the time. Then enter that into the address field. +If you are running multiple Hubitat's on the network then you will need to provide them with Static IP addresses so you know which one XTension is connecting to. There is no interface to this inside the Hubitat itself so you will need to visit the configuration of your router and create a DHCP reservation for the 2 devices, then restart them to make sure they pick up the new address if you changed it from what they were using at the time. Then enter that into the address field. 
 + 
 +**NOTE:** there is a bug somewhere either in their firmware or in the Mac implementation of the bonjour lookups that can make it take between 5 and 10 seconds or more to resolve the hubitat.local address. Until I or they figure out what changed and how to fix it please use a DHCP reservation or the static IP capabilities of the more recent firmware updates and change the address of the hubitat in the XTension address field to use the IP address instead of the mDNS name. This will remove the extended delay when controlling anything that many folks, including myself, but not all folks are seeing when using the hubitat.local address.
  
 If you have setup local access security on the Hubitat check the "Send Authentication" checkbox and enter the user and password. **NOTE:** as of this beta version sending passwords is not implemented. If this is something you need sooner please let me know and I will move it up the list of items yet to implement. It will be available before the plugin is promoted out of beta. If you have setup local access security on the Hubitat check the "Send Authentication" checkbox and enter the user and password. **NOTE:** as of this beta version sending passwords is not implemented. If this is something you need sooner please let me know and I will move it up the list of items yet to implement. It will be available before the plugin is promoted out of beta.
Line 42: Line 44:
  
 ---- ----
 +
 +====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 73: Line 78:
  
  
-**Note:** as of this beta version there is not yet an "insert" toolbar menu item to insert a default handler for these actions. That will be added before the release. +**NOTE:** The default drivers in the hubitat supports only tap and double tap events. I’m still looking into the practicality of maintaining separate community device drivers for the devices that support more than that.
- +
-**NOTE:** Unlike the Vera it seems that the Hubitat only supports single and double clicks. Devices that support multiple clicks beyond that do not share that data with XTension yet. When this becomes available in the Hubitat API I will make sure it works properly with XTension.+
  
 **Device Notifications:** If the device supports a notification such as the flashing light on some switches and you define that in the Hubitat that notification will show up as a separate unit in XTension that will allow you to turn on and off the notification display by turning on and off the unit. **Device Notifications:** If the device supports a notification such as the flashing light on some switches and you define that in the Hubitat that notification will show up as a separate unit in XTension that will allow you to turn on and off the notification display by turning on and off the unit.
  
-====Things That Are Not Implemented Yet:==== +===Scene Controllers:=== 
-Multiple taps on a central scene switch beyond single and double tap are not sent by the Hubitat. If you make use of the triple or more click capability of some switches that is not currently working. This is a limitation in the Hubitat and so I cannot say when or if it will be addressed but since I use that functionality I will certainly be pushing for it from them. It does appear that the Hubitat itself supports more taps than just the double tap it is just a matter of them making this information available to the MakerAPI protocol and then I can support it as well.+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.
  
-Devices with more than the 2 buttons on a regular paddle switch do appear to be working. The third "config" button on the Innovelli switches does come in as a tap on button 3. (though no double tap is supported on it) So I expect that central scene controllers with multiple buttons will also work normally but I have not yet tested this. At least they should work normally for single and double taps, more than that are probably not supported yet given the above limitation. 
  
-Virtual units may not be controllable from XTension yet but they will send their value and state changes to XTension. I'm not sure yet why some appear to work normally and others do not but will get this sorted out for the release.+====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:hs-wd200|article about the WD200]] for more info and code examples.
  
-Sensor type devices that should be controllable, for example door locks or garage door controllers may not be controllable yet from XTension. If you have a device like this that does not work properly please drop me a note and we can gather some data to help make this work properly. +====Things That Are Not Implemented Yet:==== 
- +Multiple taps on a central scene switch beyond single and double tap are not sent by the Hubitat. If you make use of the triple or more click capability of some switches that is not currently working. This is a limitation in the Hubitat and so I cannot say when or if it will be addressed but since I use that functionality I will certainly be pushing for it from them. It does appear that the Hubitat itself supports more taps than just the double tap it is just a matter of them making this information available to the MakerAPI protocol and then I can support it as well.
-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 "HSM" or security features of the Hubitat are completely untested as of this first beta. If you are using these things and they do not work as expected please drop me a note and we can collect some more data to make it easier for me to properly implement them on our side. +
- +
-Since this is a new Hub and a new plugin and I have not built a large system with it yet there will almost certainly be other issues and limitations with specific devices and I cannot yet speak about those. Overall it appears the Hubitat has very good support for the more standard ZWave and ZigBee devices. Please visit their support community to verify that any other more exotic devices you might use are supported and working before you dive in. +
  
 The Hubitat and it's MakerAPI protocol are moving targets as of this moment, new firmware updates may break things, or fix things or add or remove features. I do not have control of that but will of course do everything I can to keep up with the latest upcoming changes. There may be frustrations ahead but by doing some integration of this device you will definitely help get it as reliable and feature complete as it is possible to be. The Hubitat and it's MakerAPI protocol are moving targets as of this moment, new firmware updates may break things, or fix things or add or remove features. I do not have control of that but will of course do everything I can to keep up with the latest upcoming changes. There may be frustrations ahead but by doing some integration of this device you will definitely help get it as reliable and feature complete as it is possible to be.
Line 110: Line 108:
 set value of “Thermostat Mode Unit” to “cool” set value of “Thermostat Mode Unit” to “cool”
 </code> </code>
 +
 +
 +====Gathering Data For Unsupported Devices:====
 +If you have a device that is either not showing up at all or it showing no updates or the wrong updates please do the following to capture info about it. First I need a full database dump from your hubitat and the name of the device or it’s address so I can find the pertinent data in the potentially large database info. Please visit this link on your Hubitat, filling in your Access Token as described above in the initial setup:
 +
 +<code>
 +http://hubitat.local/apps/api/<replace with your APP ID Number as above>/devices/*?access_token=<replace with your access token as above>
 +</code>
 +
 +That will download some pages of JSON data into your browser, you can cut and paste it into an email to me or save it to a file and email me that if the data is too large.
 +
 +Second I will need some of the push data that the hubitat sends when values change or are updated. In the Interface List window in XTension control click, or perform a contextual click on the hubitat interface you created there and select “Turn Debug Mode On” Now all the push information that is received will be written to the XTension log. Do whatever you need to in order to create some push updates from the Hubitat and then copy and paste those lines into an email to me as well. I’ll do whatever possible to support any devices that aren’t already handled properly.
  
 ====History:==== ====History:====
Line 115: Line 125:
   * 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