Sounds like the RF signal is very strong. Is it possible for you to measure the RF signals using Spectrum Analyzer?

For Z-Wave 500, the Micro RF LinX can also be used to measure the RSSI values across channels using 'rxsweep' command. For more information about the commands, please see Micro RF LinkX for 500 Series.

The Micro RF LinkX is available at:

https://www.silabs.com/products/development-tools/software/z-wave/embedded-sdk

Hi YK,

Sorry for the late response. Not sure if you are able to successfully run the Binary Switch demo now or not.

The Gateway IP can be seen by using the Avahi daemon:

$ sudo apt-get install avahi-utils

$ avahi-browse _z-wave._udp -r

 

Also, the Gateway Discovery sample application can be used to check the current IP address using following command, use -4 option for IPv4.

./gw_discovery -4

Hi YK,

Sorry for the late response. Not sure if you are able to successfully run the Binary Switch demo now or not.

The Gateway IP can be seen by using the Avahi daemon:

$ sudo apt-get install avahi-utils

$ avahi-browse _z-wave._udp -r

 

Also, the Gateway Discovery sample application can be used to check the current IPv4 address using following command:

 ./gw_discovery -4

All available examples we have are provided in the SDK.

Not sure if the Binary Sensor example is what you want or not? This example is used to demonstrate the setting up of unsolicited address and port to the Z/IP Gateway in order to receive unsolicited sensor report.

Unfortunately I do not see any example code using this controller library.

It may be used by the Serial API but only binaries for the Serial API are offered in the Z-Wave 700 SDK.

Just a reminder, the maximum allowable baud rate for the Enhanced port (ECI) and the Standard port (SCI) is different, it can be up to 2 Mbps for ECI, but 921600 bps for SCI.

CP2105 utilizes USB Bulk transfers for larger amounts of data transmission, the bandwidth taken up by bulk data can vary, depending on other bus activities.

I am afraid it is no longer available now. Are there any information you are looking for?

Thank you for the feedback. We are aware of the timer issue in the SDK, our development team have been working on this, and hope it will be fixed in the next release.