Qubino inclusion nightmare
Posted: 02 Dec 2015 23:12
So I've got 4 Qubino flush mount modules, a 1-way switch (ZMNHAD1) and 3 dimmers (ZMNHDD1). I'm sure I'll see gray hair in the mirror tomorrow morning, these devices were a struggle to include and get just the basics working. There are still some more issues to sort out, but now I can at least control them via z-way.
Some of the issues I've been having
* Incomplete interview - No CCs at all
* Partially incomplete interviews (4-8 CCs). Force interview not working. Device seen as dead again
* Devices seen as "dead" immediately after interview, despite being only 20cm from rpi/uzb1.
* "Dead" devices not removed from Z-way after exclusion (probably because z-way didn't see them as his "own", message said "excluded from foreign network")
* "Dead" devices not always showing up as failed (seems like the uzb1 saw them from time to time) -> difficult to get rid of, must cut mains power in order for them to show up as failed and then manually remove
* "Ghost" devices - if i forgot to remove a "dead" device before including it again -> same physical device has 2 devices in z-way - at least one of them bad: the ghost/duplicate. Cutting mains power to be able to fail the ghost only screwed up the other device which was actually working(!). Probably because they had same physical identifiers or something -> start all over again.
I'm all new to z-wave and z-way and I did expect to run into some issues when I started this project. However, it took me a good 4-5 hours to get all 4 devices included with (almost) complete interviews and no "ghost" devices. After a lot of trying/failing I worked out a procedure that worked most of the time:
1. Z-way -> start exclusion
2. Push button on dimmer/switch for 2 secs.
3. Z-way confirms exclusion from foreign network
4. Cut mains power
5. Cold reboot of rpi/z-way
6. Connect mains power
7. Place UZB1 controller close to the device to include (Qubino manual says less than 1 meter, I used 20cm)
8. Z-Way -> start inclusion
9. Push button on dimmer/switch for 2 secs
10. Check the devices interview results. 50% chance of having incomplete interview and "device appears to be dead" -> go back to step #1
Should it really be that hard? Probably no, because some of the other modules I have (non Qubino) are much easier to include)
Also, 6 instances of 2 different CC types refuse to finish interview. All the important CCs seem to have completed interview though, and it is the same for all 4 qubino modules that doesn't complete:
Command Class / Instances
Alarm / 0,2,3
Version / 1,2,3
These Qubino modules do not officially support the Alarm CC (at least not listed in the user manual), and the interviews probably fail because the Qubino modules incorrectly advertise that they support Alarm CC while they don't. I am in other words doomed to live with a "device interview incomplete" warning for every Qubino module I add to my network - THAT is annoying. Are there any ways to suppress such warnings - for specific devices of course, I still want to know about other "non-permanent" incomplete interviews? I know a FW update from Qubino is the correct fix, but.. don't think that will happen too soon..
Also any thoughts on the Version CC failing (that one is listed in documentation as supported, it should have completed interview)- does it really mean anything that it failed? I really don't see the need for it in neither my day to day usage nor configuration of the z-wave network.
Some of the issues I've been having
* Incomplete interview - No CCs at all
* Partially incomplete interviews (4-8 CCs). Force interview not working. Device seen as dead again
* Devices seen as "dead" immediately after interview, despite being only 20cm from rpi/uzb1.
* "Dead" devices not removed from Z-way after exclusion (probably because z-way didn't see them as his "own", message said "excluded from foreign network")
* "Dead" devices not always showing up as failed (seems like the uzb1 saw them from time to time) -> difficult to get rid of, must cut mains power in order for them to show up as failed and then manually remove
* "Ghost" devices - if i forgot to remove a "dead" device before including it again -> same physical device has 2 devices in z-way - at least one of them bad: the ghost/duplicate. Cutting mains power to be able to fail the ghost only screwed up the other device which was actually working(!). Probably because they had same physical identifiers or something -> start all over again.
I'm all new to z-wave and z-way and I did expect to run into some issues when I started this project. However, it took me a good 4-5 hours to get all 4 devices included with (almost) complete interviews and no "ghost" devices. After a lot of trying/failing I worked out a procedure that worked most of the time:
1. Z-way -> start exclusion
2. Push button on dimmer/switch for 2 secs.
3. Z-way confirms exclusion from foreign network
4. Cut mains power
5. Cold reboot of rpi/z-way
6. Connect mains power
7. Place UZB1 controller close to the device to include (Qubino manual says less than 1 meter, I used 20cm)
8. Z-Way -> start inclusion
9. Push button on dimmer/switch for 2 secs
10. Check the devices interview results. 50% chance of having incomplete interview and "device appears to be dead" -> go back to step #1
Should it really be that hard? Probably no, because some of the other modules I have (non Qubino) are much easier to include)
Also, 6 instances of 2 different CC types refuse to finish interview. All the important CCs seem to have completed interview though, and it is the same for all 4 qubino modules that doesn't complete:
Command Class / Instances
Alarm / 0,2,3
Version / 1,2,3
These Qubino modules do not officially support the Alarm CC (at least not listed in the user manual), and the interviews probably fail because the Qubino modules incorrectly advertise that they support Alarm CC while they don't. I am in other words doomed to live with a "device interview incomplete" warning for every Qubino module I add to my network - THAT is annoying. Are there any ways to suppress such warnings - for specific devices of course, I still want to know about other "non-permanent" incomplete interviews? I know a FW update from Qubino is the correct fix, but.. don't think that will happen too soon..
Also any thoughts on the Version CC failing (that one is listed in documentation as supported, it should have completed interview)- does it really mean anything that it failed? I really don't see the need for it in neither my day to day usage nor configuration of the z-wave network.