[RELEASE] Qubino Flush 1D Relay, Flush 2 Relays, Flush 1 Relay, & Flush Dimmer

Chrisgla · April 4, 2017, 9:59pm

Excellent thank you. I’ve updated handlers for both relay 1d and dimmer, and added child device. All devices now showing i2 or i2+i3 as appropriate. Have added a few new Smart Lighting routines against the extra open/close contacts.
Can’t connect wiring to extra terminals to test until the weekend- looking forward to closing off a few items from my wish list.!

Can I ask if you intend uploading the handlers to.SmartThings to try to start the process of getting them added? Particularly in the U.K. where we don’t get GitHub integration this would be the icing on the cake.

If SmartThings had such a thing as an App Store I’d be more than happy to pay for them- until then I’d be happy to offer a donation either directly or to a charity of your choice…

Thank you again- wonderful piece of work for these fantastic modules

erocm1231 · April 5, 2017, 6:27am

I have honestly never tried to publish my work through SmartThings. Have heard bad things about the experience, but maybe that is a thing of the past. I’ll give it a shot and see how it goes. I’ll let this version of the handler settle in for a bit before submittal to make sure there aren’t any bugs.

Kjamsek · April 6, 2017, 8:17am

Gentlemen, did you manage to get the Flush Dimmer included while both I2 and I3 are enabled via this handler?

I’m writing a common device handler for these that would support all features but am having trouble with SmartThings detecting the device during inclusion at all when both inputs are enabled.

erocm1231 · April 6, 2017, 4:22pm

Which features are you looking to add that aren’t already supported with this handler?

I have found that the dimmer is kind of finicky with inclusion and usually have to try several times.

Kjamsek · April 7, 2017, 6:59am

I’m mainly trying to add a full multichannel context to the device that would support the full configuration range for the device’s capabilities in a single handler, so both configurable inputs and the optional temperature sensor along with single and multi channel associations.

It’s most likely not an issue on the device itself since on the z-wave network level all commands are answered correctly, but for some reason i can’t get it to recognize the device with both inputs enabled (with just 1 it’s paired normally).

erocm1231 · April 8, 2017, 9:36pm

So the only thing mentioned there that my handler doesn’t support is the direct associations, but I do recommend people use the Z-Wave Tweaker smartapp for associations as it is a great tool with feedback for confirmation etc.

[BETA] Z-Wave Tweaker Community Created Device Types

Z-Wave Tweaker Version: 0.08 (2017-03-16) Source: https://github.com/codersaur/SmartThings/tree/master/devices/zwave-tweaker This is a device handler to assist with interrogating and tweaking Z-Wave devices. It's designed for end-users who want to tweak their devices and for developers who want to quickly discover and report the functionality of new devices. It is intended to temporarily replace a device's normal device handler. Key features in v0.08: Discover association groups, multi-channel endpoints, and configuration parameters. Configure association group members from the SmartThings GUI. Configure parameter values from the SmartThings GUI. Configure Protection and Switch_All modes from the SmartThings GUI. Discover supported meter/alarm/notification/sensor report types. Aut…

erocm1231 · April 8, 2017, 10:14pm

Last update to these handlers added support for the i2 & i3 inputs. It also switched the Qubino 2 Relay device over to SmartThings new composite device method of handling multichannel devices. This is something I have been waiting for for a long time! (but it does require child device handlers to be installed)

I have just commited a new update that allows you to dynamically change the inputs of i2 & i3 to several different types of sensors (smoke, carbon monoxide, motion, contact, water, carbon dioxide). Here is a video of it in action:

This functionality will be in the Flush 1D Relay as well as the Flush Dimmer.

Mike_Rolle · April 11, 2017, 10:27pm

Is there a way to have a smart app pick up the temp from this unit? I’d assume it would be by setting parameters for the digital temp sensor reporting, but I am not clear on what those parameters do.
I am trying to run a ventilation fan when the temp reaches a certain point and was using the samsung multi sensor, which I think are awful, but it worked…replacing the batteries every week just got old.
Any help greatly appreciated.

erocm1231 · April 11, 2017, 10:43pm

Yes, the handlers all support temperature sensors. To have them automatically report temperature, they have to be included while the temperature sensor is connected. Any app that lets you select a device with the “Temperature Measurement” capability should be able to use the temperature sensor on these.

magnil · April 16, 2017, 7:15am

Does input i2 and i3 support double and triple click?

bmmiller · April 18, 2017, 2:51pm

Any hope of getting the Flush 1 Relay added to your list of compatible devices?

I’m using it on outdoor GFCI outlets and prefer it to the Flush 2 Relay in this case because of the 10A max.

There is an existing integration but it requires polling for power usage.

EDIT: On a whim, I tried the DTH for the 2 Relay module and it works but has a nuisance alert for failure to create child device (which I don’t need for the 1 relay module) and all the Q2 parameters that don’t apply. I’ll either rip that stuff out myself or a parameter to state 1 Relay or 2 Relays in the DTH would work too to limit things.

Truthfully, I hate to have to rip stuff out as it then diverges from the original master branch and I might lose updates

erocm1231 · April 19, 2017, 1:14am

They do not support that functionality.

@bmmiller I just got the 1 Relay and will be adding support for it in the next couple days.

bmmiller · April 19, 2017, 2:03am

After further review, the 2 relay one doesn’t work quite right on the 1 Relay module as-is.

Seems like on/off status doesn’t report but on/off command works. Energy works but not configure (not surprising) so things can’t be reconfigured either.

I am sure this would all be obvious to you but providing feedback in case it is useful at all.

erocm1231 · April 19, 2017, 10:57pm

I have a handler for the 1 Relay module. It does need child devices installed if you plan on using the i2 & i3 inputs. I will probably modify that in the future to default to disabled and only bug the user about the child devices if they have enabled them in preferences.

github.com

erocm123/SmartThingsPublic/blob/master/devicetypes/erocm123/qubino-flush-1-relay.src/qubino-flush-1-relay.groovy

/**
 *
 *  Qubino Flush 1 Relay
 *   
 *	github: Eric Maycock (erocm123)
 *	Date: 2017-04-19
 *	Copyright Eric Maycock
 *
 *  Includes all configuration parameters and ease of advanced configuration. 
 *
 *  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.
 *
 */

This file has been truncated. show original

bmmiller · June 25, 2019, 8:33am

Awesome!

Just so I understand, what is the device capable of for meter functionality?

I’ve set this in the settings and the orange dot disappeared. I’d expect to see updates very 2 seconds with the Debug Logging Level set to ‘All’ but nothing really happens.

I will say I don’t have anything plugged into it right now, so the power draw is literally just the receptacle being powered up. Things might change if I plug a real device in? Otherwise, things work great. There is the nuisance alert when it can’t find the child DTH it is looking for, but if it’s harmless, no worries.

Dennis_Tegenbosch · April 22, 2017, 2:07pm

Great work again @erocm1231

I have the Flush 2 Relays working, the only thing i notice is that when i use the physical switch for the light, the “child” (Q1 or Q2) device doesn’t go on in the app, but the main switch in the app does go on, but then i still don’t know which of the 2 is on when i look into the app.

The settings are default.
Can that be solved or am i doing something wrong.?

erocm1231 · April 22, 2017, 4:36pm

I will look into this a little later today.

@Dennis_Tegenbosch I believe there is something going on with the SmartThings platform. There is something in the handler that is not working anymore, and it seems like maybe others are reporting something similar. I’ll keep this thread posted when I figure it out.

erocm1231 · April 24, 2017, 3:31pm

@Dennis_Tegenbosch just an update. SmartThings does have a platform issue that is causing problems with a lot of device handlers. SmartThings staff have identified the issue but have not mentioned an ETA on a fix.

Recent Platform Update Broke Parse Method Response/Result (April 2017) Writing Device Types

Update: After a lot more testing, the initial issue I explained below always existed, but manually applying the response command to each item in the list didn't always work either so I think there's a larger issue with the way the parse result is being handled. The one thing I do know is that if you use sendHubCommand and sendEvent instead of returning items from the parse method, everything will work the way it's supposed to... A few days ago most of my devices started reporting that they were offline and I tracked the problem down to SmartThings ignoring the events being returned from the WakeUpNotification event handler. I ended up changing all of my device handlers to use sendEvent instead of using createEvent and that solved the problem, but it didn't explain why it was only…

bmmiller · June 25, 2019, 8:34am

After doing some testing and looking at the logs, it looks like parameter 40 (and maybe 42) aren’t getting set to ‘0’ when requested in the DTH.

Below are logs after setting to 0:

As you can see it states it is trying to update to 5, which isn’t right. If I try and set it to some non-zero value, like say 1:

Since ‘5’ is the default, I’m guessing it isn’t a coincidence. I’m more interested in the time interval parameter 42 myself, but this stuck out as potentially conflicting. I’m not sure how it reacts if you have % AND time as non-zero, but it seems like % might override time and if that’s the case, it’ll never report on time.

I haven’t started looking at the code yet to see if there is an obvious bug where 0 gets reset to the default 5 before send yet.

Just reporting what I’ve noticed.

erocm1231 · April 27, 2017, 10:17pm

@bmmiller Alright, so I did find the bug you are referring to and posted a fix. You can now set those parameters. I haven’t tested whether that fixes your initial issue so you will have to let me know.

Edit: I don’t think the device sends reports when it is off other than the initial 0W report. Did you end up connecting anything to it?

@Dennis_Tegenbosch forgot to mention that the platform error was corrected and the problem you were experiencing should be fixed.

[RELEASE] Qubino Flush 1D Relay, Flush 2 Relays, Flush 1 Relay, & Flush Dimmer

Customers

Developers

Download the SmartThings App