User Tools

Site Tools


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
supported_hardware:hubitat [2023/04/07 16:16] – removed some beta info and added the sendDeviceCommand documentation James Sentmansupported_hardware:hubitat [2023/11/04 13:49] (current) – [XTension Settings:] added more info about the static IP issue James Sentman
Line 5: Line 5:
  
 ====Hubitat Setup:==== ====Hubitat Setup:====
-Follow the standard initial Hubitat setup. A cloud connection is not required for XTension to talk to the Hubitat, all communications are done over the local network and so it is necessary that the Hubitat and the XTension be on the same local network subnet. If you have a more complex networking setup and need to specify the local address that it should tell the Hubitat to send push updates to please let me know and I can prioritize that to be added in a future plugin version.+Follow the standard initial Hubitat setup. A cloud connection is not required for XTension to talk to the Hubitat, all communications are done over the local network and so it is necessary that the Hubitat and the XTension be on the same local network subnet. Earlier Hubitat OS versions did not support the setting of static IP but more recent ones do. 
 + 
 + 
 +>**You should give the Hubitat a static IP address either via the built in network settings or via a reserved DHCP address on your router. The local network lookup of “hubitat.local” can be very slow and cause noticeable delays in all communication and control.**
  
 ===Install the MakerAPI Plugin on the Hubitat:=== ===Install the MakerAPI Plugin on the Hubitat:===
Line 31: Line 34:
 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.
  
-**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 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.+**NOTE: there is a problem that causes very slow performance when using the hubitat.local address. Later version of the Hubitat firmware have implemented the ability to set a static IP address and I recommend that you do this rather than rely on the local mDNS address. Then place the IP address into the Address field rather than the hubitat.local” defaultIf you can’t set this through the hubitat interface a DHCP reservation in your router will work as well.**
  
-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.
  
 Enter the API ID and Access Token from the URL's in the MakerAPI setup screen into the next section. Enter the API ID and Access Token from the URL's in the MakerAPI setup screen into the next section.
Line 80: Line 83:
  
  
-**NOTE:** The default drivers in the hubitat supports only tap and double tap eventsI’m still looking into the practicality of maintaining separate community device drivers for the devices that support more than that.+**NOTE:** The default drivers in the hubitat may not support multi-clicks more than a double clickIf you find a community driver that supports more that are not passed properly through to XTension please let me know and we can collect the information I need to properly support them.
  
 **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.
Line 122: Line 125:
 </code> </code>
  
- 
------ 
-====Things That Are Not Implemented Yet:==== 
-The Hubitat folks have a problem with multiple taps on switches beyond just a double tap. I understand that this is complex and a bit silly to try to have the family remember what a pentuple tap on a switch does. If you wish tap support beyond just a double tap you may have to find a community created device driver for the specific switch. I know these exist for the Home Seer WD200 line of switches which can support up to 5 taps or more, and possibly many other switches that support additional gestures not supported by the built in driver for these. 
  
 ----- -----
Line 167: Line 166:
   * 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   * Scene Controllers are working as of XTension 9.4.41
 +  * Valve devices, and other more unusual enumerated devices, are working as of XTension 9.5.2
supported_hardware/hubitat.1680884181.txt.gz · Last modified: 2023/04/07 16:16 by James Sentman