UZB/RaZberry Firmwares - Update

[rafale77]

If this (node-red+homeassistant) is your preferred approach, I would recommend moving to hubitat, there is a custom component for it on home-assistant. It is a much better implementation of zwave and zigbee than vera. Otherwise you will have to wait for the z-way component (which is in the works?). From all my testing, vera has become pretty much the worse zwave implementation available. I am sure there are worse ones but I have not tried them. openzwave is a little better, hubitat is much better and homeseer and z-way are top notch.

[sender]

Hubitat cloud/subscription-free?

[rafale77]

hubitat was created by a few smartThing users who got tired of the obvious misuse and abuse of the cloud so you can see it as a local version of SmartThing. It uses the same language and device drivers along with many of the same concepts.

[sender]

thanks, will look into. As I see now this is not an "official" integration for homeassistant but a so called custom component...

[sender]

Is hubitat so new? https://hubitat.com/products It's unbuyable

[sender]

Rafale, thanks again. I quit, 7th time. Thanks and maybe speak later. (I may not swear, but be lucky one can't hear me)

[rafale77]

I had one, and only gave it away after migrating to z-way as I saw it as a backup solution.
For device support, it does not support S2 unlike z-way and homeseer. It uses a mostly community driven device driver development which is shared with SmartThings so it truly supports every device (except S2 ones) unlike the vera and ezlo which rely on a library and forced preset device list. The one controller which really supports everything zwave is Z-way.
It also doesn't really support being a secondary controller and has some quirks when setup that way. I know, I tried...

It is not new at all, it is actually a couple of years old. I have had mine for at least 2 years.

As for the message on the vera about waiting for the name, it is the vera attempting to configure the z-way controller. You can ignore it by setting the z-way device in vera to no auto configure. It is normal by vera standard. What you should see though is the vera device list in z-way.
When using two controllers, you should also set the primary as SUC/SIS. (should be device 1, the vera). That way you can use z-way to include devices and you can also run the "request network updates from SUC/SIS" if z-way did not get the device list from the vera.

The inclusion process for zwave goes like this (I posted a graph somewhere on this forum too):
controller set in include mode -> client device wakeup -> controller adds device to its network list and sends HomeID and DeviceID -> client device gets both IDs, saves them and send ack frame back -> controller sends node info frame (NIF) to device -> client responds with list of supported command classes -> If security is supported controller sends security key exchange frame -> Then device updates neighbor nodes and sends its neighbor list to controller->after it is complete if client is controller, it will send a get network info to controller -> controller responds with list of devices.

The vera tends to fail at sending security keys as it hangs there easily so everything behind it will not happen.
You can manually force everything to happen except for the security key exchange which... I actually managed to do it by manually inserting the key in the z-way controller and bypass this entire process.

[sender]

Thank you, my z-way adventure is over. The Virtual Machine is shutdown.

I will monitor communication around it and if there is a supported home assistant integration I will give it another try.

I just added another zigbee device in my deconz (container in homeassistant) and instantly works... Just want to say, that if z-wave wants to keep seeing the light it should be made stable, by whoever wants to do so (vera, z-way, openzwave)...

Thanks again!

[PerH]

Curl trouble:

x@x:/usr/lib/x86_64-linux-gnu$ sudo apt-get -y install libcurl3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcurl3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libcurl4

E: Package 'libcurl3' has no installation candidate

..?

[rafale77]

@PerH

The problem is that libcurl3 is not in the standard repo you have listed.
assuming you are on ubuntu download it from here:

Ubuntu – Error

You need to pick from the correct platform.
wget --url you can paste from the link above--

i.e

wget http://no.archive.ubuntu.com/ubuntu/pool/universe/c/curl3/libcurl3_7.58.0-2ubuntu2_amd64.deb

downloading from the norwegian mirror for x64

Then run

dpkg -i libcurl3_7.58.0-2ubuntu2_amd64.deb

might need sudo authority to install.

Edit: Another idiot way to do it is to not install libcurl3 at all and instead create a symbolic link for libcurl3 to call libcurl4 (That's how I am running mine )

sudo ln -s /usr/local/x86_64-linux-gnu/libcurl-gnutls.so.4 /usr/local/x86_64-linux-gnu/libcurl-gnutls.so.3

sudo ln -s /usr/local/x86_64-linux-gnu/libcurl.so.4 /usr/local/x86_64-linux-gnu/libcurl.so.3

Note that you will need to find where your libcurl library was installed. I just gave you the ubuntu location.

[PerH]

Thanks.
the GUI is up and running now, but i can't update the vendor list, nor start inclusion mode.. any clues?
this funny message is showing in the log..

trying to start inclusion mode:

[2020-09-29 22:29:05.117] [I] [zway] Max number of devices (1) reached

trying to update vendor list:

[2020-09-29 22:26:33.433] [I] [core] Notification: error (core): Error has occured during updating the Z-Wave devices list

I realize it can be annoying with all these noob questions, can only hope you bear with me.

[rafale77]

You probably need a license for the uzb (unlike the razberry which has an embedded license).
I though the device limit was 3 without a license but this may have changed.
The license is not required though to update the uzb firmware.