forum

This is the version of the zwave library used by the device's firmware. SDK stands for "Software Development Kit".

I have the exact same configuration on my installation with exactly the same controller info but I do not get "the controller is secondary" message and am able to include just fine. Did you setup the controller initially as a secondary?

I am now pretty much convinced that this problem is due to corrupted frames coming in to the zwave dongle and passing the CRC check. Lowering overall RF noise on the network helps but I fundamentally, CC should never be added after the interview is complete so a block should be made to not allow CC...

This is normal... the remote access function requires a little program which exists only on the arm platform (rPi).

Long writeup with the solution here:

https://smarthome.community/topic/120/z ... tu-install

I have a few 9540 and they included just fine... with any zwave controllers. So no it needs nothing special.

all your problems seem to stem from the CURL_OPENSSL_3 which has been deprecated by ubuntu since version 18.x. You need to either force install lib curl.so.3 or try running this on ubuntu 16... or maybe have z-way-server support curl4

I just had one of my devices completely lose all of its interview results too. Completely out of nowhere. One out of 150 and luckily it was not a battery operated one so it was easy to recover. Can I suggest to put a manual lock on the interview database so that no data can be changed by any input f...

Can boot the pi off of an external SSD. (I do that) or indeed VM is the best way to go (I do that too). So as to not make it feel like overkill, the VM runs a bunch of other things...

I don't update that way. I am finding this script to fail.

I just run
knowing that I had the z.wave.me repo added to apt prior: