3.2.0 release but no changelog

[kosinus33]

I also can confirm, the update is working now, thx.

[vinisz]

Is something changed in the API ? All connections outbound to node-red (using zway node) are not working anymore.
For example, I can switch on a device from node-red, that works.
But if I switch on a device from Zway gui, then node-red does not get notified anymore (same for sensors etc)
That is unworkable for me, as whole automation is build on node-red

[PoltoS]

There should be no changes in the API compared to v3.1.3. At least they are all listed in the ChangeLog

[otverber]

upgraded to 3.2.0 gone wrong; cannot find hub after upgrade... what to do?

tried to restart service
"sudo /etc/init.d/z-way-server restart
Restarting z-way-server:
Stopping z-way-server: start-stop-daemon: warning: failed to kill 369: No such process
done.
Starting z-way-server: done.
"
but z-way server is obviously not running. and not starting either

tried this afterwards
Z-Way can then be started using the simple shell command from inside the Z-Way folder:
LD_LIBRARY_PATH=./libs ./z-way-server

An error message indicating a missing lib version gave me e hint.
Did a full dist-upgrade from stretch to buster and a reboot fixed my problem

[sylwus99]

Same as @GokMasE and @otverber here. z-way-server not running, no PID. Rolled back to 3.1.4 and it works fine. Redo the upgrade just to confirm but same issue.
I'm on Raspbian Buster on RPi 3b+

[vinisz]

Same as @GokMasE and @otverber here. z-way-server not running, no PID. Rolled back to 3.1.4 and it works fine. Redo the upgrade just to confirm but same issue.
I'm on Raspbian Buster on RPi 3b+

How did you rolled back ?

[sylwus99]

I downloaded the previous release from https://storage.z-wave.me/z-way-server/ and just did "sudo apt install /my/download/path/z-way-3.1.4_armhf.deb" without the quotes. I answered yes to confirm that I wanted to install and older version.

[GokMasE]

I finally got 3.2.0 working by updating from Stretch to Buster earlier today. The only remaining problem is that the Razberry ID (used for remote access) has been erased (it probably happened when unsuccessfully trying to update to 3.2.0 before the intended release date). I get reminded of the missing ID every time I access the "Settings" option in Smarthome since I then get a couple of warnings that remote access data could not be initialised.

Apart from that glitch, z-way-server itself is chugging along just fine so far.

Edit: The missing Razberry ID has been fixed now, huge thanks to poltos for helping me sort that out. I am happy to have current version of ZWay fully working again without warnings and glitches

[xurg]

tried to restart service
"sudo /etc/init.d/z-way-server restart
Restarting z-way-server:
Stopping z-way-server: start-stop-daemon: warning: failed to kill 369: No such process
done.
Starting z-way-server: done.
"
but z-way server is obviously not running. and not starting either

This could be related to what I reported in this thread: After upgrade to 3.2.0 LD_LIBRARY_PATH seems not to be set up correctly

[vinisz]

Needed to downgrade also...
After downgrade, device specifications are back, associations can be set again (from expert gui) and connection to node-red is working right again.
@poltos, I think there is some work to do here, too many issues with 3.2.0 at the moment...