Qubino Flush 1D Relay ZWAVe PLUS VERSION

flush.jpg (34.83 KiB) Viewed 1642 times

HI

I have this qubino flush 1d z–wave plus relay. Iam NOT able to include it only once it was not included correct so I tried resync and it failed I cloud not even associate groups.
so exclude and re include I could not.


I can include very well in zipato and vera with no issues.

1. I tried total RESET of the device no luck
2. tried power off module set Indigo to include power on no luck.
3. tried to take aeon labs wave plus stick in hand an hold it 10 cm from device no luck + tried all include methods also.

is this device not defined in indigodomo yet ?

NB also tried reboot Mac reload zwave

I got it to work Finally

I need to only use the service button but since im using 230 Volt I am not allowed to do this according to the manual.

Normally I need to push s1 3 times in 3 sec, that is working in zipato and vera.

so my guess is that maybe the module is broadcasting a different inclusion token in these two methods.

maybe the aeon labs firmware is not cable of regonice this.

Now the input is not working have followed the manual/wiki serval times and 100 is set to 9

stil no status update and do not seem to find any z.wave hex codes for the device inout 2 either

I also tried associate group 3-4-5 all and single no difference

Indigo Z-Wave Version: 2.0.91
Node ID: 51
Model: Flush 1 Micro Relay (ZMNHAD)
Model ID: 00020052
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.01
Model Definition Version: 5
Library Type: 3
Class Name: Relay Power Switch
Class Hierarchy: 04 : 10 : 01
Command Class Base: 25
Command Versions: 20v1 85v1 86v1 8Ev1 59v1 5Av1 5Ev1 60v4 30v1 25v1 27v1 72v1 70v1 71v1 32v4 73v1
Encryption Status: Not Supported
Multi-Endpoint Types: 1:(10 : 00), 2:(20 : 00)
Multi-Endpoint Classes: 1:[5E 86 20 27 25 85 8E 59], 2:[5E 86 20 30 71 85 8E 59]
Multi-Instance Counts: - none -
Features: routing, beaming, energyMeter
Neighbors: 4, 25, 47
Associations: 1:[1] 2:[1] 3:[] 4:[] 5:[] 6:[] 7:[] 8:[]
Config Values: 1:1 2:0 3:0 100:9 101:0 120:5 110:32536 30:0 63:0

sent "051 - Relay" status request
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 33 07 60 0D 01 01 25 03 FF 76
Z-Wave Debug . . multiEndPointPacket: node 051, endPoint 1
Z-Wave Debug RCVD requestRelayStatus: 01 09 00 04 00 33 03 25 03 FF FF
Z-Wave Debug . . requestRelayStatus: node 051, endpoint 1, value 255
Z-Wave Debug RCVD requestMeterLevel: 01 10 00 04 00 33 0A 32 02 21 34 00 00 00 83 00 00 74
Z-Wave Debug . . requestMeterLevel: node 051, endpoint None, meterType 01, raw value 3400...
Z-Wave Debug . . requestMeterLevel: 13.1 W (float: 13.100000)

[matt (support)]

I don't know what the problem was with the inclusion (and exclusion) not working – I suspect the module got into a bad state. It isn't related to Indigo or the Z-Stick though. The inclusion commands are the same no matter what.

It sounds like you saw this note in the UI:

Enabling Input 2 or 3 notifications (which sets parameter 100/101 to 9) requires that after saving the change you exclude the module, wait 30 seconds, re-include it, then re-sync it in Indigo. For more information see the Qubino manual.

I have no idea why Qubino makes it so difficult to change input notifications, but you do indeed have to follow all of those steps for it to work. I'm not sure why it isn't working, but I am pretty sure it is related to those steps. Note the module has to be fully excluded from the Z-Stick after the configuration parameter is changed.

Thanks for your reply Matt

Yes I have read both the manual and your wiki page about this module.

I even did a total reset of the module before including it.

It is strange that the other controllers take it so "easy" when include either by service button or the I1 3 times in 3 sec.

what about the association what do I need only group 1 & 2 ?

when you mean total exclusion you mean set the exclusion on the exclude (the log writes red text excluding xx device)

also delete the device ? because in your wiki it state not to delete the device in the UI and to reinclude in the same "old" device again.