Qubino dual relay module

3 of my 4 dual relays are 1.02/s5 i did just happen to do all testing on my forth relay which is a 1.01. After resetting, the three 1.02's work fine. I'll what i will do with the remaining 1.01. Thank you for your help.

Press the ON/OFF buttons on it a few times, then from the Trigger's setting dialog press the button to write to the Event Log the most recently received Z-Wave commands. Copy/paste those results into a reply for me and we'll see if we can figure it out.

Hi Matt, I'm probably doing it wrong, please have a look :

First, I toggle the switch a few times and then I create a new trigger, Zwave command received -> received from device -> choose device and Match raw packet...


I paste the recent commands to the log :


And then copy and paste one of the lines (the first) back to the match raw packet dialog.
I tried the full raw packet, and also a partial packet with the * wildcard



... the trigger action is set to simply log some text to the log, just to see if the trigger works, but it never logs the text.
I know that the action works, because when I set the trigger to another device (something else than this qubino) it logs to text to event log...


edit : sorry for the retina screenshots...

[matt (support)]

The problem is that Indigo defines both devices for that module to use endpoints, but yours isn't sending the endpoint commands so the test on the From popup of the device is failing. Change the From popup to Any Device then you can specify a pattern like:

* 0x29 0x03 0x20 0x01 *

The 0x29 in this case is the node ID so it will only trigger on the command from that module (generally the node ID is always the 6th byte). The pattern you have in your screen shot will also work, I believe. You'll just want to make sure you include the 0x29 byte in there so that the nodeID is specified.

Hi Matt, thanks so much, this works perfect !

I have got one of these relay modules, which doesn't report back changes at the switch to Indigo,and discovered it has firmware 1.01
Followed the above methodology matching to the raw Z-wave packet and have developed a practical work around.
Thanks for all the support guys.

Do I understand from all this however that buying a new Quibino device with the latest firmware will now work perfectly with Indigo, or are they still a bit dodgy. I tried Quibino because of their compatibility with a 24V supply voltage, although this particular application is mains. Otherwise have found Fibaro relay devices to be fine, contrary to earlier comments in this chain.

Geoff

[matt (support)]

Hi Geoff,

Do I understand from all this however that buying a new Quibino device with the latest firmware will now work perfectly with Indigo, or are they still a bit dodgy.

I believe that is correct. Version 1.02 or newer should work much better and will broadcast out changes to Indigo that it will catch correctly.

I have now removed a number of my dual relays and will ship them off early next week.

In relation to the firmware update I just got an email today to confirm my modules have been updated and will be returned shortly. Service is a bit slow but nevertheless hopefully it will be worth the wait for a reliable device.

I just got a chance to power up one of my upgraded devices, see log below.
@CrazyFin I notice that the Application Version on the upgraded device is now 5.00 whereas yours was 1.02 - maybe you or someone else will be able to pick up on what differences there are between the versions.
Bad news is that I'm not getting any status change from either wall switch
@Matt - where to next??

Code: Select all

Indigo Z-Wave Version: 2.0.68
Node ID: 49
Model: Flush 2 Micro Relay (ZMNHBD)
Model ID: 00020051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 5.00
Model Definition Version: 5
Library Type: 3
Class Name: Relay Power Switch
Class Hierarchy: 04 : 10 : 01
Command Class Base: 25
Command Versions: 20v1 60v4 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: 1:(10 : 01), 2:(10 : 01)
Multi-Endpoint Classes: 1:[5E 86 25 20 27 85 8E 59 32], 2:[5E 86 25 20 27 85 8E 59 32]
Multi-Instance Counts: - none -
Features: routing, beaming, energyMeter
Neighbors: 13, 14, 15, 19, 22, 23, 43, 44, 46
Associations: 1:[1] 2:[] 3:[] 4:[] 5:[] 6:[] 7:[] 8:[1]
Config Values: 64:0 1:1 2:1 110:32536 120:5 30:0 63:0

Hi Colly,

I have also sent one of my Qubinos in for a firmware upgrade. It also shows firmware version 5 inside Indigo. I have another dual relay that shows firmware 1.02
I see no difference in functions and behaviour between the two, so I wouldn't worry about the different firmware being displayed in Indigo.

However, when I first received my upgraded (fw5) module, it behaved exactly as you describe. I could operate the relays from Indigo, but when operated from the switch, I still got no status updates.
After a while of pulling my hair, I noticed that I had wired the module incorrectly. I had mistakenly switched the live and neutral wires around. It still operates that way as it is just a relay in a circuit, but the qubino behaves weird when not wired correctly.
Can you double check your wiring ? Maybe you made the same mistake as I did.

Hi Pete,

Will check this evening. I just temporarily connected it to check it out so that's a possibility! Thanks for the tip, will report back later.


Sent from my iPhone using Tapatalk

Checked the wiring and there's no issue there. Also resynced the device again for good measure but still not getting a status update for local switching.

[matt (support)]

Have you tried a full exclude and re-include (then sync) of it? Turn on the debug logging option and include the sync results from that (exclude, re-include, sync). Also control the switch locally with the debug logging on to see if any debug messages are showing.

If you received more than one of these replacement modules, then you might also want to connect it up to rule out a faulty module.

Hi Matt,

The device didn't get recognised from it's previous existence in my setup so it was a new device inclusion after upgrade. I didn't exclude and re-include. Will try that and other requests as you suggest, probably be tomorrow at this stage. I have indeed received a number of these back after upgrade so will rule out a faulty device also.

Matt,

Quick summary - I've done as requested and also included a 2nd device to see if the same issues exist. They do unfortunately, I don't see the status in Indigo once switched locally. I notice from the logs that on some occasions more details get logged, mostly it's just:

Code: Select all

   Z-Wave Debug                    RCVD requestRelayStatus: 01 09 00 04 00 36 03 25 03 FF 1E

Sometimes:

Code: Select all

   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 36 0A 32 02 21 34 00 00 00 0F 00 00 FD
   Z-Wave Debug                    . .  requestMeterLevel: node 054, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 1.5 W (float: 1.500000)
   Z-Wave                          received "054 - Relay 1" power load to 1.5 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 36 0A 32 02 21 34 00 00 00 03 00 00 F1
   Z-Wave Debug                    . .  requestMeterLevel: node 054, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 0.3 W (float: 0.300000)
   Z-Wave                          received "054 - Relay 1" power load to 0.3 W

If there's anything else that I can do let me know.

[matt (support)]

So the odd thing is all of your syncs are showing that the Group 1 association to the Z-Stick already exists:

Z-Wave Debug SENT requestAssociations: 01 0A 00 13 36 03 85 02 01 25 8E FE
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 36 06 85 03 01 01 00 01 40
Z-Wave Debug . . requestAssociations: node 054, group: 1, num associations: 1, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 054, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]

But it shouldn't, especially if the module has never been included. So a couple of things to try:

1) See if the manual has steps for how to do a factory reset. For most Z-Wave modules it is just an exclude/re-include, but some have other steps. If the Qubino does, then try those steps.

2) If that doesn't help, then use the Interfaces->Z-Wave->Manage Associations... menu item to manually remove the association for Group 1 (to the Z-Wave Controller) on those devices, then re-sync them.

Do either of those get it working? Include the Event Log results of any syncs you do after #1 or #2 above into a reply for me.