forum

Hi,

When I started out with Z-Wave, I used to the RaZberry on a RPi (think z-way was 1.4.1) and whilst it worked, quite often the z-way server would fail.

I got around this by setting up a watchdog to auto restart it.

This did work most of the time, but I also had time's when the service could not be restarted and not even a reboot of the PI sorted things.

It required a power cycle of the RPi to restore comms and the z-way service.

I since moved over to the z-stick (with z-way) and a local z-way server instance and this had been fault less.

Just curious, as my RPi and RaZberry are sitting doing nothing, I was gonna revive it.

Has this the stability issue's I found (and other user's I know) been resolved?

Thanks

Neil

Judging from your signature, you still use an early 1.7 release. For production 1.7.2 has long been recommended.
In the meantime v.2.0.0 is at the final stage of development many of the testers have indicated that it is better than 1.7.2. So if yout Raspberry is not used for critical applications you should definitely give v2.0.0-RC 24 a try.

Hey pz1,

My system features an embedded z-way server for zstick operation and due to the network usb server I use (which is reliant on kernel 2.6.x), I cannot go higher than 1.7.1 at the moment (not found a 1.7.2 for linux x86 yet).

Of course, not an issue with the RaZberry and since there are new releases (like the v2.0.0 you suggested), I was thinking of resurrecting it.

I still prefer running the z-way server locally though and it makes life a lot easier for my uses when all they have to do is plug a USB stick in.

I'm quite tempted to try grabbing the /dev/ttyxxx of the RPi over the network, but not looked into that much as of yet.