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/10/08 15:51] – [XTension Settings:] added mDNS lookup bug description James Sentman | supported_hardware:hubitat [2023/04/07 15:42] – [Things That Are Not Implemented Yet:] removed things that are supported now James Sentman | ||
---|---|---|---|
Line 91: | Line 91: | ||
====Things That Are Not Implemented Yet:==== | ====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. | 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. | ||
- | |||
- | Devices with more than the 2 buttons on a regular paddle switch do appear to be working. The third " | ||
- | |||
- | 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. | ||
- | |||
- | Sensor type devices that should be controllable, | ||
- | |||
- | The support for location events, control of modes and control of the " | ||
- | |||
- | 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 118: | Line 108: | ||
set value of “Thermostat Mode Unit” to “cool” | set value of “Thermostat Mode Unit” to “cool” | ||
</ | </ | ||
+ | |||
+ | |||
+ | ====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: | ||
+ | |||
+ | < | ||
+ | http:// | ||
+ | </ | ||
+ | |||
+ | 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: |
supported_hardware/hubitat.txt · Last modified: 2023/11/04 13:49 by James Sentman