Problems after 1.7.2 update

[graycrow]

I had 1.7.1 up and running till the moment I installed 1.7.2 today. Unfortunately I also upgraded (apt-get update and upgrade) my Raspbian OS right after 1.7.2 update, so I don't know if it's a bug in 1.7.2 or it's not compatible with recent Raspbian version. I tried to revert back to 1.7.1 but it doesn't help, symptoms still the same.

Now my z-way-server cannot start with following error:

Code: Select all

root@raspberrypi:/opt/z-way-server# ./z-way-server
./z-way-server: error while loading shared libraries: libzwayhttp.so: cannot open shared object file: No such file or directory

I found on this forum that it happens when libyajl2 is not installed. But it was installed and I even removed it and reinstalled this library again, but with no luck. I also found on this forum that it's possible to specify library path, so I did it and got following error:

Code: Select all

root@raspberrypi:/opt/z-way-server# sudo LD_LIBRARY_PATH=libs ./z-way-server
Z-Way version v1.7.2 from 2014-07-26 15:20:00 +0400 (build 428d48e765a32b39615c073af93e8666497724c9)
Using default configuration file config.xml
Starting Z-Way for device /dev/ttyAMA0...
failed to discover ZWay: Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)

Looks like both errors is related and I found a few topics here when people had the same problems with previous versions and in most cases they been told to replace Razberry board. But my board was working perfectly before updates and stopped working right after. I rebooted my Pi already several times, but it didn't helped.

This is a end of z-way-server.log file:

Code: Select all

[2014-07-31 16:24:42.798] Initialization done
[2014-07-31 16:24:42.798] Job 0x07 (Get controller info and supported function classes): success
[2014-07-31 16:24:42.798] Device is not compatible. Terminating...
[2014-07-31 16:24:42.798] Removing job: Get controller info and supported function classes
[2014-07-31 16:24:42.809] Worker thread exit point
[2014-07-31 16:24:42.809] Worker thread successfully finished

Any ideas?

[pofs]

Try to unplug the board (from unpowered Pi, of course!) and then plug it again after a few minutes. There was a guy with a similar problem some time ago, and it worked for him.

Also check manufacture data on your RaZberry board. If it is middle of April, you may have problems with EEPROM.

[graycrow]

Try to unplug the board (from unpowered Pi, of course!) and then plug it again after a few minutes.

Thank you! It helped.