Ok I understand. My advice is to update to 3.3M2. I see that after 3.2 was released the association on the device was changed a bit and that might explain it. My other thought is that the OH core has been working on strict parameter validation and that may be preventing the assignment of a node to group 2. You might be able to get a Debug message by following my post here.
Bob