Custom Device Drivers [Wiki]

[brwill]

Hello, I haven't the knowledge, nor can find the documentation, to create a device driver for the Leviton VRCZ4, which is a 4-channel Z-Wave ZONE controller (essentially 4 independent On/Off/Dim transmitters.) Can anyone guide me / assist me in this endeavour? Thanks, Brian

[aaiyar]

@brwill

to create a device driver for the Leviton VRCZ4,

@mpk has created an app and driver for this device and made it available on their Github. See this post for details:

App and driver porting to Hubitat

Thanks, @csteele -- I've put the Leviton VRCZ4-M04 Zone Controller App and Driver up on my personal github site, with an intermediate Readme pointer at GitHub - HubitatCommunity/mpk: Hubitat Elevation Apps and Drivers. Let me know (@bobbyD?) if/how I should update Community Apps, Community Device Drivers (AKA Compatible Devices Wiki), or any other listings? Looks like it's de rigueur to point from these lists to a new [RELEASE] topic in category Apps and Drivers > Community Apps (or Community…

[brwill]

Hello aaiyar,

I replied to you with thanks, but I did it by email, and it died. I am still working on it. Thanks.

[mpk]

Let me know if I can answer any questions about the VRCZ4 app/driver

[WMarcolin]

Hi, I was looking for a way to integrate my Samsung SmartThings Wi-Fi air conditioner with HE, and couldn't find it on this list and topics. Talking to a community of friends, they recommended this integration, test, and working well.

Wouldn't it be the case to include it in the initial list? I recommend. Or is there some criterion I don't know about for an eventual non-disclosure?

Drivers for Samsung Appliances controlled via SmartThings Cloud API

This series of drivers uses the SmartThings Cloud to control the referenced Samsung Appliance. It does not require a SmartThings Hub, but does require a SmartThings account as well as access to the SmartThings app on you phone. There are some special installation instructions contained in the references below. GitHub Repository: HubitatActive/SamsungAppliances at master · DaveGut/HubitatActive · GitHub Installation Details: HubitatActive/README.md at master · DaveGut/HubitatActive · GitHub …

[amithalp]

@WMarcolin

Samsung SmartThings Wi-Fi air conditioner

What is exactly your Samsung system you integrated?

[djgutheinz]

They are still in Beta Test mode. Additionally, the series is also a concept to encourage others to develop their own integrations.

[WMarcolin]

I am integrating it with a Samsung WindFree air conditioner (AR12TSFABWKXAP). It is a WiFi operated equipment. As I said, it is already working with HE, it has some details like not exporting information to HomeBridge, or behaving as a switch to turn on and off, unlike other thermostats that when put in cool already understands that is to turn on, but works with small adjustments in the rules.

[djgutheinz]

Bobby,

The TP-Link Kasa Integration is not on either list of drivers/integrations (checked today).

[user3101]

Happy for you to add my driver which is for
POPP zigbee TRV
Hive zigbee TRV
Danfoss Ally TRV
The github link is here: GitHub - JellyGreen/Public-Hubitat-Code: My attempt at hubitat driver code is available here
v1.6 is current

[marktheknife]

Edited OP to add to list with link to driver v1.6.

[neillythere]

Popp zigbee TRV should be listed under Zigbee devices, not Z-Wave.

[marktheknife]

Fixed.

[H_Local]

Linked

[Wiki] Where is the Wiki… [find what you are looking for]

A starting point for your search, below you find a selection of wikis, scattered throughout the forum. Some are marked [wiki] or (wiki) in their topic others are mentioned as “guide” or “howto” As with any wiki, if you have the rights, feel free to add, update or improve this post. ———————————————The Wiki Links ————————————— Most important i guess, getting started; by bobbyD (Hubitat staff) And by @rlithgow1 Also usefull, what devices have custom drivers available; by bobbyD as well O…

[user4661]

i need Hyundai HT Drivers for hubitat please

[marktheknife]

I’m not at all familiar with Hyundai’s platforms for connected cars, so this might be related to your system but I believe the only potentially related thread is here:

[RELEASE] Hyundai Bluelink Remote Start/Lock Support (Beta)

I just got my first Hyundai vehicle and had a chance to explore the functionality that Hyundai Bluelink has for doing things like remotely starting the vehicle. This Application/Driver exposes that Bluelink functionality to Hubitat Elevation. See the README.md file for details. Features: Supports remotely locking, unlocking, starting the engine, stopping the engine, getting vehicle status, and reporting the vehicle's location. How to Get It: Github Project: https://github.com/tyuhl/Hyundai-B…

Edit: actually it looks like Hyundai HT has nothing to do with Hyundai cars.

https://www.hyundaiht.co.kr/product/en/

Since this thread is for device drivers developed by the community that already exist, please consider starting a new thread if you’d like to discuss more about this Hyundai smart home platform.

[user4661]

thank you for your response actually I'm not talking about the Hyundai cars l'm talking about Hyundai smart home they have a product for smart home solution so please take a look at this link bellow

https://www.hyundaiht.co.kr/product/en

thank you very much.

[earl1]

There is this thread : [Updated and re-released by a new developer] Rheem EcoNet Integration - #43 by dman2306. which is a new Rheem driver. It worked for me, so wondering if the list should be updated?

[victor.hernandez.oga]

Hi, am trying to use this driver

martinkura-svk/Hubitat/blob/main/Moes ZigBee Wall Switch

for a tuya zigbee 1 gang wall switch. drivers contain the device definition but didn't work

Manufacturer name: _TZE200_oisqyl4o (already on the driver)
ZLC version: 03
Model Identifier: TS0601
Applicaiton version: 44 (on drivers is defined as 42)

this is the log from HE

dev:9182023-05-29 10:09:57.880 PMinfoRefreshing...

dev:9182023-05-29 10:09:57.783 PMdebugThis device have only: 1 button, Child devices not needed.

dev:9182023-05-29 10:09:57.782 PMdebugParent createChildDevices

dev:9182023-05-29 10:09:57.780 PMinfomodel: _TZE200_oisqyl4o buttons: 1

dev:9182023-05-29 10:09:57.771 PMdebugParent deleteChildren

dev:9182023-05-29 10:09:57.769 PMdebugParent setupChildDevices

dev:9182023-05-29 10:09:57.767 PMwarnDebug logging will be automatically disabled after 30 minutes!

dev:9182023-05-29 10:09:57.766 PMinfoInitializing...

dev:9182023-05-29 10:09:17.643 PMdebug[raw:catchall: 0104 EF00 01 01 0040 00 EFCF 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EFCF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:9182023-05-29 10:09:17.590 PMinfoTurn all switches OFF

dev:9182023-05-29 10:09:17.072 PMdebug[raw:catchall: 0104 EF00 01 01 0040 00 EFCF 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EFCF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:9182023-05-29 10:09:16.930 PMinfoTurn all switches ON

dev:9182023-05-29 10:03:54.099 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Moes_1_31_Moes_ZigBee_Wall_Switch_1_2_3_Gang_1014.ping() is applicable for argument types: () values: []
Possible solutions: find(), print(java.lang.Object), print(java.lang.Object), print(java.io.PrintWriter), find(groovy.lang.Closure), run() (method ping)

dev:9182023-05-29 10:01:01.234 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Moes_1_31_Moes_ZigBee_Wall_Switch_1_2_3_Gang_1014.checkPresence() is applicable for argument types: () values: [] (method checkPresence)

dev:9182023-05-29 10:00:58.631 PMdebug[raw:catchall: 0104 EF00 01 01 0040 00 EFCF 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EFCF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]