Remove ZWave association, is this possible?

[Domodude]

Howdy all,

Is it possible to remove an association in zwave, without taking the associated unit out and/or resetting it?

[hari]

use the set association command and put a "-" sign in front of the node id, e.g. send the set association to node 5, group 1, value -8
this would remove node 8 from the association group 1 in node 5

[Domodude]

OK. Is there a way to display all associations of all nodes in the network? It looks like like I need to know the exact association I want to cancel, not just "cancel every association related to node X".

Question 2, kind of basic I fear: how is the mesh laid out (i.e., designed) when I use SUC/SIS? I have a feeling the network is not as good as it could be. Any way to tune it or is it fully automagical?

[hari]

OK. Is there a way to display all associations of all nodes in the network? It looks like like I need to know the exact association I want to cancel, not just "cancel every association related to node X".

Question 2, kind of basic I fear: how is the mesh laid out (i.e., designed) when I use SUC/SIS? I have a feeling the network is not as good as it could be. Any way to tune it or is it fully automagical?

I don't understand the first question.. but you can display the associations of a group when omitting the node id parameter, e.g. just sending a set association to node x, association group y, and then leave the node list empty. It will then print out the associations in the z-wave device log (when level 36 is enabled).

Regarding the second question, the best way to get a reliable network is to include the nodes in a smart order. E.g. start with routing slaves close to the dongle. After that add routing slaves that are further apart. After that add routing slaves in problematic locations (e.g. plenty of metal around the rocker box, locations very far off, etc.). After that add non-routing slaves. In theory, nodes should fetch the latest network info from the SUC/SIS. In reality not all nodes do so. If you follow this recommendation you should get a solid network. Btw, *never* move routing slave nodes around while they're included.
Where does your "feeling" come from? Do you encounter specific issues?

[Domodude]

My feeling comes from things like this in the log:

Code:

05 04/03/12 11:56:56.614 No callback received: await_callback: 97 timer: 31 <0x4086fb70>
36 04/03/12 11:56:56.718 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:56:59.822 No callback received: await_callback: 97 timer: 31 <0x4086fb70>
36 04/03/12 11:56:59.926 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:57:03.030 No callback received: await_callback: 97 timer: 31 <0x4086fb70>
01 04/03/12 11:57:03.030 ERROR: Dropping command, no callback received after three resends <0x4086fb70>
36 04/03/12 11:57:03.134 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:57:06.237 No callback received: await_callback: 98 timer: 31 <0x4086fb70>
36 04/03/12 11:57:06.341 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:57:09.445 No callback received: await_callback: 98 timer: 31 <0x4086fb70>
36 04/03/12 11:57:09.549 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:57:12.653 No callback received: await_callback: 98 timer: 31 <0x4086fb70>
01 04/03/12 11:57:12.653 ERROR: Dropping command, no callback received after three resends <0x4086fb70>
36 04/03/12 11:57:12.757 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x4086fb70>
05 04/03/12 11:57:15.861 No callback received: await_callback: 99 timer: 31 <0x4086fb70>

After I reset the core, for example. things work fine for a while... Maybe I should try adding stuff in the suggested order.