Have you tried 'lsusb' when your stick is plugged in?

Also note that you can use /dev/ttyAMA0 directly, but I think that it's only available on the beta chain. I had huge problems using an alias (/dev/ttyUSB20), where Domoticz would regularly lose contact with the RaZberry board

Yep! I put a print statement before the 'on for' command, and it only gets triggered once.

It's being fired by a motion detector, but even if there are no more triggers it still stays on. I've seen other reports of this, and it seems to be only when linked to a motion sensor. weird!

I've just started experimenting with LUA scripts, and have come across something that doesn't seem to be working correctly. If I use commandArray['Lounge Dimmer'] = "On FOR 10" , the lamp comes on, but stays on. I've tried different values, thinking that there may be a minimum value, to no avail ...

It could be a faulty Razberry module. When you power up your Pi, does the red LED on the Razberry module illuminate for around 1 second? As another test, you could try installing the z-way server, as that has more diagnostic capabilities than those provided within Domoticz. If you do install it ...

First thing that I would say is, don't use /dev/ttyUSB20 (didn't see any mention of you creating a symlink from /dev/ttyAMA0 to /dev/ttyUSB20), use /dev/ttyAMA0 (you may need to be on the beta chain for this to be an option). Make sure that you have no other software trying to connect to RaZberry ...

Hi SuneRadich. Did you by any chance install the z-way software too? If so, it is probably set to launch on boot, and taking ownership of /dev/ttyAMA0. You can try stopping it by issuing 'sudo service z-way-server stop', then 'sudo service domoticz restart'. Did you disable the serial console in ...

hamish, thanks for that steer! Just upgraded to the beta version, and ttyAMA0 appears ..... excellent!

After doing some experimenting, using 'HomeGenie', i have come to the conclusion that talking to the RaZberry card through a symlink e.g. /dev/ttyUSB20, doesn't work very well, giving loads of timeouts. In HomeGenie, I initially tried connecting to the USB20 symlink, and saw very similar problems as ...

Hi Egregius; I believe that it works with either. I think that you may need a license if you use it with a non 'zwave.me' device though.

Update: I've been running with just the z-way software for 48 hours now, and all devices are present, no timeouts, no dead nodes, and the network routing is all green. There is definitly something wrong with the z-wave implementation in Domoticz. Please can we have an idea about a fix for this, as I ...

I'm seeing similar behavior using a RaZberry controller. I'm starting to think that it's an issue with the z-wave driver in Domoticz, as I have run my system for 24 hours, just using the Z-way software, and have seen no timeouts, dead nodes etc. I'm going to leave it for another 24 hours to prove ...

Perhaps I spoke too soon. I'm having problems with nodes appearing to be dead, and a reboot of the pi fixes it. Anybody else having 'dead nodes' problem?

Setup: RPi3, RaZberry, Jessie, and three TKB dimmers.

Just to add to randytsuch's excellent reply, you can issue the command to find out which access points can be seen.

Luckily, my setup worked first time. Like free_nsc, I had disabled the serial console, but also followed the advice on the Vesternet website, and created a symlink from /dev/ttyAMA0 to /dev/ttyUSB20. Then choose 'OpeWaveUSB' as the device, and select /dev/ttyUSB20 as the serial port.