openHAB Z-Wave 1.5 on Raspberry Pi

[franz.di...@gmail.com]

I use openHAB on a Raspberry Pi with Java  8 (being much faster than 7) and using the latest HABmin related jars from Chris Jacksons repository.

 

For openHAB 1.4 this worked at least partially, i.e. at least a subset of the Z-Wave devices was visible :-) But starting with 1.5 all of the Z-Wave stuff is broken. Obviously no communication with the controller takes place.

 

Is there anybody else experiencing this problem?

 

I mentioned the Java version for the sake of completeness. Switching to Java 7 does not change anything. The same is true about using the HABmin jars.

 

[Tom]

I had the same(?) problem recently when trying to use Chris' ZWave binding jar published on the HABmin page: the binding seemed to start (got the usual warnings about a few configuration mistakes I still have not cleaned up) and then seemed to just not start talking to the controller. As I assumed I had just done a silly mistake myself and my ambitions to make it work were rather low this day I have just reverted back to the official 1.5 snapshot. So, I do not know the solution to this. I still assume having made a silly mistake since quite a few users are actually using Chris' snapshots without such problems.

BTW: I am using Java 7

Best regards,
Tom

[Chris Jackson]

It would be really useful to get a log file of the startup so I can see if there’s something obviously wrong before this gets merged into the master branch…

Cheers

Chris

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[franz.di...@gmail.com]

Sure. Hopefully I will find some time for that this evening. Any special settings?

 

Via ssh on my mobile I see that the only thing openhab.log says about zwave is: "...ZwaveActiveBinding: .... Update config. port=/dev/ttyUSB0" and *nothing* else. Normally, there are all those messages about the nodes found. I don't need to tell you ...

 

Cheers

 

Dieter

[Chris Jackson]

Thanks Dieter,
If you are running in debug mode that should be fine. It looks like a fundamental problem in that for some reason it’s not opening the COM port or something - it would be worth checking for any exceptions around this point as well…

I’ve not made any changes to this part of the code so it’s a little strange, but let’s see what the log shows on startup….

Cheers
Chris

[Lars Bretschneider]

how do you installed java 8 ?

[franz.di...@gmail.com]

Get it from https://jdk8.java.net/download.html

cd /usr/local

sudo tar zxvf *thefileyoujustdownloaded*

sudo chown -R root:staff /usr/local/jdk1.8.0

sudo ln -s -f /usr/local/jdk1.8.0/bin/java /usr/local/bin/java

So I have java 8 in /usr/local/bin and java 7 in /usr/bin/

You may need to set explicit paths in some places, e.g. /etc/init.d/openhab in case you use this to start openHAB.

[franz.di...@gmail.com]

zwave.log:

 

2014-03-18 20:48:30 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding has been started.

2014-03-18 20:48:31 INFO  o.o.b.z.i.ZWaveActiveBinding[:233]- Update config, port = /dev/ttyUSB0

Sorry. Nothing else. My assumption is that this does not really help you in debugging :-)

I am willing to help as much as I can, though. 

[Chris Jackson]

Thanks, but nope - not so useful unfortunately :(

It would be worth taking a look in the openhab.cfg log as well since sometimes exceptions will get logged there (depending on where they are thrown). If there’s nothing in there, then I’ll add more debug around this area to try and find out where it fails.

Cheers
Chris

[franz.di...@gmail.com]

20:45:21.847 INFO  o.o.c.internal.CoreActivator[:61]- openHAB runtime has been started (v1.5.0).

20:45:56.329 INFO  o.o.m.c.i.ModelRepositoryImpl[:79]- Loading model 'db4o.persist'

[...more models deleted...]

20:46:25.823 INFO  o.o.m.c.i.ModelRepositoryImpl[:79]- Loading model 'holiday.script'

20:46:35.997 INFO  o.o.io.rest.RESTApplication[:141]- Started REST API at /rest

20:46:42.218 INFO  o.o.u.w.i.s.WebAppServlet[:79]- Started Classic UI at /openhab.app

20:46:54.194 INFO  o.o.m.c.i.ModelRepositoryImpl[:79]- Loading model 'security.rules'

20:46:57.151 INFO  o.o.m.c.i.ModelRepositoryImpl[:79]- Loading model 'holiday.rules'

20:47:23.444 INFO  o.o.i.habmin.HABminApplication[:180]- Started HABmin REST API at /services/habmin

20:48:24.436 INFO  o.o.c.s.AbstractActiveService[:169]- HTTP Refresh Service has been started

20:48:26.184 INFO  o.o.c.s.AbstractActiveService[:169]- FritzAHA Refresh Service has been started

20:48:26.924 INFO  o.o.c.s.AbstractActiveService[:169]- NetworkHealth Refresh Service has been started

20:48:28.624 INFO  o.o.c.s.AbstractActiveService[:169]- Cups Refresh Service has been started

20:48:29.969 INFO  o.o.c.s.AbstractActiveService[:169]- Exec Refresh Service has been started

[Chris Jackson]

Hmmm - equally as useful :( It’s strange that no exceptions are being logged…

I’ll add some debug and create a new version shortly…

Thanks.

Cheers
Chris

[Chris Jackson]

Give this version a go - it should be basically the same as the current version, but with some additional debug so we can see where it’s going wrong (hopefully!).

Chris

[franz.di...@gmail.com]

2014-03-18 22:24:27 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding has been started.

2014-03-18 22:24:28 DEBUG o.o.b.z.i.ZWaveActiveBinding[:236]- update 1

2014-03-18 22:24:28 INFO  o.o.b.z.i.ZWaveActiveBinding[:241]- Update config, port = /dev/ttyUSB0

2014-03-18 22:24:28 DEBUG o.o.b.z.i.ZWaveActiveBinding[:243]- update 2

(it's getting late now, I will finish for today...)

Cheers

Dieter

[joe bob]

I'm running 1.5.0 from about a week ago with Java 1.7 on Cubieboard2 (Cubiuntu) with Z-Stick2.  That was running fine.  I just installed this attachment and that runs fine as well (at least with a 2 min check).  I do get one warning below.

Log:
20:37:02.331 INFO  o.o.b.z.i.ZWaveActiveBinding[:198] - Update config, port = /dev/ttyUSB1
20:37:02.344 INFO  o.o.c.s.AbstractActiveService[:169] - ZWave Refresh Service has been started
20:37:02.376 INFO  o.o.b.z.i.p.ZWaveController[:109] - Starting Z-Wave controller
20:37:02.378 INFO  o.o.b.z.i.p.ZWaveController[:778] - Connecting to serial port /dev/ttyUSB1
20:37:02.431 INFO  o.o.b.z.i.p.ZWaveController[:791] - Serial port is initialized
20:37:02.585 INFO  o.o.c.s.AbstractActiveService[:169] - HTTP Refresh Service has been started
20:37:02.796 WARN  o.o.m.i.i.GenericItemProvider[:108] - Attempted to register a second BindingConfigReader of type 'zwave'. The primaraly reader will remain active!
20:37:03.125 INFO  o.o.c.s.AbstractActiveService[:169] - NTP Refresh Service has been started
20:37:03.192 INFO  o.o.b.z.i.p.ZWaveController[:504] - NODE 1:  FOUND
20:37:04.986 INFO  o.o.b.z.i.p.ZWaveController[:504] - NODE 3:  FOUND
20:37:07.922 INFO  o.o.b.z.i.p.ZWaveController[:504] - NODE 4:  FOUND
20:37:07.924 INFO  o.o.b.z.i.p.ZWaveController[:504] - NODE 5:  FOUND
20:37:07.932 INFO  o.o.b.z.i.p.ZWaveController[:504] - NODE 6:  FOUND

------------------------

[franz.di...@gmail.com]

The "20:37:02.796 WARN  o.o.m.i.i.GenericItemProvider[:108] - Attempted to register a second BindingConfigReader of type 'zwave'. The primaraly reader will remain active!" is not a problem as far as I see it. In those times long ago when my Z-Wave interface was still working it was reported, too.

[Chris Jackson]

Do you have zwave:healtime set in openhab.cfg? If so, what is it set to?

Cheers
Chris

[franz.di...@gmail.com]

Bingo!

 

The line looked like

 

zwave:healtime = 02:00

 

So it was either the blanks around the assignment operator (don't know how they got there) or (much less likely) something with the 02:00. I did not have enough time this morning to check for the details, but at least by commenting out the line things came back to life.

 

Thanks for your help. Anyway it would be a good idea to catch problems like this in the config file reader.

 

Dieter

[Chris Jackson]

Great - this is my fault for not explaining what the format is (and arguably, not having a very good format).

Currently, the time is expecting simply a single number - ie the hour, so I have mine =2.  I will take a look at this tonight and make it more tolerant - sorry for the hassle...

Cheers

Chris