Hi,

Your understanding is correct. We'd like to support PG12, MG12 starter kits with one sensor EXP board. The jumper is used to address an IO pin conflict.

Regards,
Tony

Hi,

That's not ensured by the controller. The end device will have to pass the certification test before production. Any CC requirements specified in the specification will be tested against the device.

Regards,

Tony

I think you can look for a Z-Wave switch that supports 3-way installation and see if you can connect your switch to it. Normally, they only support a regular 3-way on/off switch. 

Regards,

Tony

Hi,

I'd recommend you to contact our local sales and get an answer from them. We cannot comment on that on the forum.

Regards,

Tony

Hi,

BMA280 is not Silicon Lab's sensor product. I'm afraid that you posted the question on the wrong forum. We won't be able to answer your questions.

Regards,

Tony

Hi,

A reasonable approach would be: the device stores the region selected by the user in the flash, reboot and then configure RadioConfig before ZW_ApplicationRegisterTask(). You can use NVM3 to store that.

Regards,

Tony

Hi,

What's your hardware setup? Which software/example project did you use to test the communication?

If you're using the ribbon cable, it could also be that the cable is broken.

Regards,

Tony

Hi,

You can create an association with its lifeline group. For example, a light node that only supports binary switch CC in lifeline group without having any other groups won't allow you to send commands to another node. But you can configure other nodes, say a motion sensor node, to turn on/off the light through association.

Regards,

Tony

Hi,

You can create an association with its lifeline group. For example, a light node that supports binary switch CC, but doesn't have any other groups. It doesn't allow you to send commands to other nodes, but you can use another node, say motion sensor node, to turn on/off the light through association.

Regards,

Tony

Hi,

The controller may send a "KEX Fail" frame saying that the key exchange has failed. That will trigger the joining device to clear the 240s timeout and proceed.

Otherwise, the joining node should timeout after 240s and aborts S2 bootstrapping silently

Regards,

Tony