How-to Article on MakeUseOf

So I made a major boo boo, plz help.

I removed the openhab start daemon then added

/opt/openhab/start.sh

To

/etc/rc.local just before console

Now when the pi starts up, it starts openhab, but can only access the osgi. I want to stop this and remove that from rc.local…it aver made it to the console to be able to log in. How do I stop the osgi and get to the console so I can nano the rc.local file?

I would ssh to the pi from another machine. login as root (aka “pi”).
Do what you want from that shell.
Then in that shell.

sudo shutdown -r now

Hopefully your pi will then reboot without misbehaving in this regard.

If there was a weekly award for MVCM “most valuable community member”, I would nominate @bob_dickenson for his excellent forum support.

And @Branden_Smale, I hope you realise that right now you are where lots have been before. The question is whether you will use your current experience and now help update documentation for other new people, or you will continue down the more exciting path of learning the next step in building your final HomeAutomation solution. You already know the path that most choose, and challenge of most Open Source projects and good documentation.

Thank you for your kind words. We all stand on each others shoulders.

Again, thanks bob, you are a lifesaver…

Hi,

I am trying to use Razberry Z-Wave with openhab. I followed the whole article and installed openHAB. To connect with my Fibaro Z-Wave Switch I installed Z-Way. I connected the device and stopped the Z-Way service.

After this I installed the Z-Wave Binding (“org.openhab.binding.zwave-1.7.1.jar”) as well as HABmin2.

I added "-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0 " to
/etc/init.d/openhab
as well as to
/OpenHAB Home/bin/openhab.sh (via the samba connection)

In my openhab.cfg I uncommented port and healtime:

# The Z-Wave controller port. Valid values are e.g. COM1 for Windows and /dev/ttyS0 or
# /dev/ttyUSB0 for Linux
zwave:port=/dev/ttyAMA0

# Z-Wave nightly heal time. This is the hour (eg 2AM) at which the automatic nightly
# network heal will be performed.
zwave:healtime=2

Still I get the following error while starting OpenHAB and can’t control my Z-Wave devices via HABmin:

015-10-25 18:33:34.968 [DEBUG] [.z.internal.ZWaveActiveBinding] - ConverterHandler not initialised. Polling disabled.
2015-10-25 18:33:34.974 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyAMA0
2015-10-25 18:33:34.975 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, healtime = 2
2015-10-25 18:33:34.977 [DEBUG] [.z.internal.ZWaveActiveBinding] - Initialising zwave binding
2015-10-25 18:33:34.979 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started
2015-10-25 18:33:34.985 [DEBUG] [.o.b.ntp.internal.NtpActivator] - NTP binding has been started.
2015-10-25 18:33:35.140 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
2015-10-25 18:33:35.142 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2015-10-25 18:33:35.144 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyAMA0
2015-10-25 18:33:35.158 [DEBUG] [.myopenhab.internal.MyOHClient] - Transport.EVENT_REQUEST_HEADERS
2015-10-25 18:33:35.158 [DEBUG] [.rrd4j.internal.RRD4jActivator] - RRD4j persistence bundle has been started.
2015-10-25 18:33:35.227 [DEBUG] [.p.internal.PersistenceManager] - Initializing rrd4j persistence service.
2015-10-25 18:33:35.256 [ERROR] [b.z.i.protocol.ZWaveController] - Serial Error: Port /dev/ttyAMA0 does not exist

Any suggestions how to get the error fixed?
Which openhab file is the correct one for adding "-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0 "?

// Got the same error while using HABmin1

Thanks!

Did you add your user for openhab to the dialout group ?

Hi Bob,

In addition to adding openhab to the dialout group (sudo usermod -a -G dialout openhab) I gave for testing purpose every user access to the port:

pi@raspberrypi ~ $ sudo chmod a+rw /dev/ttyAMA0
pi@raspberrypi ~ $ ls -l /dev/ttyAMA0
crw-rw-rwT 1 root dialout 204, 64 Oct 26 10:08 /dev/ttyAMA0

Thanks!