[RELEASE] Nue Smart Fan Light Switch driver

gslender · May 10, 2021, 1:47am

Driver for the Nue Smart Fan Light Switch driver model NUE-ZBFLB

Uses parent/child components and if the driver is installed, it should self-detect the device using the fingerprint. It also re-creates the children every time you re-configure, so be wary of doing that as it may break some unintended rules/dashboards that the children are referenced in.

Parent driver will create a child standard component light and a child standard component fan that obeys the normal capabilities for those types of devices. Parent has non-standard commands, and could be used, but will be missing common capabilities.

[PRO TIP] Label the parent device (like Bed1) and if you run Configure, it will create children using that label to ensure they are easily identified (such as Bed1-Fan and Bed1-Light).

As normal, chime away with any feedback, either positive or negative...

github.com

gslender/hubitat/blob/main/nue-zigbee-smart-fan-light-switch.groovy

/**
 * =======================================================================================
 *  Copyright 2021 Grant Slender
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 * =======================================================================================
 *
 *  Last modified: 2021-05-09
 *
 */ 
 
metadata {

This file has been truncated. show original

greghoward1962 · May 18, 2021, 3:39am

Hi, I have 6 Nue Fan Light switches from 3A Smarthome in Melbourne. I installed Kevins driver a few months ago to use with them & found there is an issue with your 'Nue ZigBee Fan Light Switch' driver. It says it was updated - 'Updated by Kevin X to fix the issue that switch status failed to update on the APP on 12 Jun 2020' I had this driver on all 6 Fan light switches that I have, & with all these reporting I can't find what is setting off my alarm, so I've had to change them all the just a Nue Switch, then all the error logs stop.
Kevin now tells me it wasn't a driver to be used with Hubitat.
I've just installed your driver & set it to one of the switches. I has only created 2 child devices, 1 for the light & 1 for the fan. I would have thought it would create 4, 1 for the light & one for each fan speed? Can you advise please. Thanks

greghoward1962 · May 18, 2021, 3:44am

I'm getting this log -
dev:19012021-05-18 05:44:21.901 am debugParse returned [:]

dev:19012021-05-18 05:44:21.898 am debugParse: null

dev:19012021-05-18 05:44:21.895 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

dev:19012021-05-18 05:44:18.872 am debugParse returned [:]

dev:19012021-05-18 05:44:18.869 am debugParse: null

dev:19012021-05-18 05:44:18.866 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

dev:19012021-05-18 05:44:17.057 am errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_3A_Nue_ZigBee_Fan_Light_Switch_1057.recoveryEvent() is applicable for argument types: () values: [] (recoveryEvent)

dev:19012021-05-18 05:44:15.840 am debugParse returned [:]

dev:19012021-05-18 05:44:15.837 am debugParse: null

dev:19012021-05-18 05:44:15.834 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

dev:19012021-05-18 05:44:12.782 am debugParse returned [:]

dev:19012021-05-18 05:44:12.779 am debugParse: null

dev:19012021-05-18 05:44:12.776 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

dev:19012021-05-18 05:44:09.761 am debugParse returned [:]

dev:19012021-05-18 05:44:09.758 am debugParse: null

dev:19012021-05-18 05:44:09.753 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

dev:19012021-05-18 05:44:06.720 am debugParse returned [:]

dev:19012021-05-18 05:44:06.717 am debugParse: null

dev:19012021-05-18 05:44:06.714 am debugParsing 'read attr - raw: 851A0100060800001000, dni: 851A, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00'

gslender · May 18, 2021, 4:05am

No, the child created is a Fan capability which controls the switches for the 3 speeds. If you wanted a simple 4 child switch, just use the built in Nue switch and it creates four child switches.

It is working as expected.

greghoward1962 · May 18, 2021, 5:34am

OK thanks. So in the dashboard to control the Light I select Light part of the Fan Light & select the 'Switch' template & for the fan part , To control the fan, I select the fan part & use the 'Fan' template?

gslender · May 18, 2021, 5:51am

Yep

greghoward1962 · May 18, 2021, 8:28am

Thanks, the Dimmer template also works, It might be easier to use as it's just a matter of sliding your finger across to the required speed?

greghoward1962 · May 18, 2021, 11:10am

Getting this error now, is it OK?
dev:19012021-05-18 09:05:17.047 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_gslender_Nue_ZigBee_Smart_Fan_Light_Switch_1450.recoveryEvent() is applicable for argument types: () values: [] (recoveryEvent)

dev:19012021-05-18 09:03:58.048 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_gslender_Nue_ZigBee_Smart_Fan_Light_Switch_1450.ping() is applicable for argument types: () values: [] Possible solutions: find(), print(java.lang.Object), find(groovy.lang.Closure), print(java.io.PrintWriter), print(java.lang.Object), run() (ping)

gslender · May 18, 2021, 8:35pm

This isn’t my code and I believed the remains from the last drivers you installed.

@mike.maxwell shouldn’t the system clean up after changing drivers and removed dead scheduled method calls etc? Seems either a bug or bad design to leave that remain???

greghoward1962 · May 18, 2021, 11:58pm

I just deleted the driver, then rebooted the hub. Then re-installed the driver, re-booted again, configured it & added to the dashboard. Looks like there's no error now.
Thanks for your help
FYI @mike.maxwell

joaomf · May 29, 2021, 4:26pm

Hi,

Which online store is selling this switch?

Thanks.

2wenty787 · August 18, 2021, 1:54pm

@greghoward1962
Hey, Sorry to bring up an old thread. I just purchased the same fan controller and have had them installed.
Full disclosure, I'm new to Hubitat and anything "Smart Home" for that matter. My Nue fan switch works perfect manually. I add it to devices and use the driver listed in this thread. The light switch works fine, but im getting nothing at all regarding the fan. Was there something else you had to do?

greghoward1962 · August 18, 2021, 9:01pm

Hi, I found that the fan bit works ininitally, not after. No idea why. I only use the light with any apps so isn't a problem to me. I bought mine on Ebay Aus - 3A Smart Home | eBay Stores. Or his website is https://3asmarthome.com/ Kevin is in Melbourne

gslender · August 19, 2021, 12:11am

Which driver are you using and did you hit Configure?

2wenty787 · August 19, 2021, 12:49pm

I'm using the driver at the top of this post. I have also tried using the "Nue Zigbee Fan Controller".
Using the driver on this post, I can actually get the light to work via the dashboard/webpage.
Which more than i got using the Nue Zigbee Fan Controller driver.
I pressed configure, which gives me the 2 child devices - as stated before light works but nothing to do with the fan does. I also tried @greghoward1962 method of deleting the device and rebooting after every step, but same result. Logs show the same error he was having at one point:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: nueZigbeeFanController.componentSetSpeed() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.lang.String) values: [Fan Switch-Fan, on] (method componentSetSpeed

Like i said i am new to all this and have little idea what i am doing, i was just hoping there was a driver fix or something like that.

With all that being said, i did set the fan controller up as a generic switch, in which all switches work fine, which will be a last resort if i can't get the proper driver working.

I'd like to have a fan button on the dashboard as its a lot cleaner than 4 buttons. Plus the fan/speed icon is pretty cool.

Any other suggestions i would love to hear them - until then i'll just keep tinkering and try and find something that works.

greghoward1962 · August 19, 2021, 9:10pm

I also get that error. I would think its an error in the driver somewhere. So unless you or someoen can fix the driver I don't think anything you do will fix it.

gslender · August 19, 2021, 9:29pm

The driver at the top of this post is a driver I wrote. It works. You must delete the device, and discover the device with my driver installed in Hubitat. The device fingerprint should correctly detect this driver and offer it when the device is discovered. Don't change drivers afterwards and everything should work fine. If you have errors in the logs, post a copy of the logs into the thread as neatly / cleanly and completely as possible. You do have to hit configure to ensure the two child drivers are created. The fan should also be controllably from the parent driver, and that's a good indicator that it is working (or not).

2wenty787 · August 22, 2021, 12:23pm

Just tried again using your method:
Deleted the device
Installed the driver
Rebooted Hub
Discovered the device - automatically detects as "Advanced Zigbee Bulb".
It doesn't seem to assign your driver to it.
I changed it to your driver
Hit configure which creates Light and Fan children
As before - Light switches on and off as expected.
Fan is dead - Nothing I do can get the fan to work.
Went back to Parent device to test it there, nothing works with fan.
Changed driver to Nue Zigbee switch - Hit configure - which creates 4 more children.
1- Fan = working, 2- FanHigh = working, 3- FanMedium = working, 4- FanLow = working.

I'm probably doing something wrong - I barely would call myself an amateur at this.
Just to confirm - To install the driver, i just copy and paste the code into the drivers code and hit save correct?

Strange that yours works and mine doesn't, must be something I am doing/ not doing.

Thanks for your help anyway - I'll keep trying

EDIT In the meantime I have decided just to use rule machine to trigger the switches using a virtual switch with your driver. It will do for now.

gslender · August 22, 2021, 9:31pm

Do the process again. Remove the device from Hubitat and when you discover, copy / paste here the driver fingerprint. It must be a different device but with a similar name. The Zigbee cmds to control the fan must be slightly different.

2wenty787 · September 13, 2021, 12:24pm

Sorry for the late reply @gslender
I just removed one of the devices and copied the device fingerprint.
I assume its probably a different model maybe?

ID: E783

Manufacturer: 3A Smart Home DE

Product Name:

Model Number: LXN56-1S27LX1.2

deviceTypeId: 158

more...

manufacturer : 3A Smart Home DE

idAsInt : 1

inClusters : 0000,0003,0004,0005,0006,0008,1000

endpointId : 01

profileId : 0104

application : 00

outClusters : 1000

initialized : true

model : LXN56-1S27LX1.2

stage : 4

manufacturer :

idAsInt : 2

inClusters : 0000,0003,0004,0005,0006,0008,1000

endpointId : 02

profileId : 0104

application :

outClusters : 1000

initialized : true

model :

stage : 4

manufacturer :

idAsInt : 3

inClusters : 0000,0003,0004,0005,0006,0008,1000

endpointId : 03

profileId : 0104

application :

outClusters : 1000

initialized : true

model :

stage : 4

manufacturer :

idAsInt : 4

inClusters : 0000,0003,0004,0005,0006,0008,1000

endpointId : 04

profileId : 0104

application :

outClusters : 1000

initialized : true

model :

stage : 4

Hopefully its just a quick edit to your driver code.