2.5 Milestone 5 Issues

And from reading the link you posted to the other thread it appears it’s been broken since at least M3. I noticed Jan checked in your other thread but maybe create an issue on the appropriate github repo so developers are aware this binding is not functioning.

RFXcom binding seems to have some issues with serial port. I don’t use either binding so can’t confirm but again, maybe create an issue in the proper github repo.

Please post links to your git issues so all of us can play along at home.

Please remember to post what version you are upgrading from and what other bindings you are using

1 Like

hi @Celaeno1
yes it is set and I also addedthe symlinks just to be sure

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/vantage:/dev/PBM:/dev/zwave:/dev/ttyACM0:/dev/IRLeser:/dev/ttyUSB0:/dev/ttyUSB1:/dev/ttyUSB2"

still the same, zwave restarts every minute now

Did you also “soft reset” the controller?

I did a soft reset an got then the following error:

2019-11-22 20:55:52.572 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2019-11-22 20:56:04.602 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2019-11-22 20:56:06.619 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.

after a restart of OH2.5 M5 I’m getting again the errors:

2019-11-22 20:59:15.040 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2019-11-22 20:59:16.138 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2019-11-22 20:59:16.232 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/zwave'
2019-11-22 20:59:16.279 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2019-11-22 20:59:16.302 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2019-11-22 20:59:16.302 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2019-11-22 21:00:14.920 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2019-11-22 21:00:16.035 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2019-11-22 21:00:16.141 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/zwave'
2019-11-22 21:00:16.197 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2019-11-22 21:00:16.245 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2019-11-22 21:00:16.245 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.

I’m trying 2.5 M4 Version of Zwave found here https://github.com/openhab/org.openhab.binding.zwave/releases just to check if error occures there too

@frieso

https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0.M4/

1 Like

no success still the same error with this m4 binding (cache.clean & reboot). are there some other bindings that I could check?

@frieso

2.5.0.M3

https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0.M3/

2.5.0.M2

https://openhab.jfrog.io/openhab/libs-milestone-local/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0.M2/

with these bindings I’m having the same issues. What I did then: installed openhab-addons 2.5 M4.kar und openhab-addons-legacy 2.5 M4.kar. Then a clean-cache and two reboots.

I’m getting now a

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [207]
  Unresolved requirement: Import-Package: org.eclipse.smarthome.io.transport.serial

As I’m using also the Davis Binding I bevore installed the feature

feature:install openhab-transport-serial

Which one does zwave need and could this be the problem?

This could be used by multiple different bindings.

I would remove the davis binding and also unplug the serial cable. Then reinstall also zwave binding.

The issue seems related to the serial port somehow. Definitely test all those different versions with Davis binding uninstalled would be a good idea if you have the time

I’m not sure, I think the zwave binding may not yet, Chris could shed some light on this but… me thinks the serial port is the issue here. there is a conflict or something

good advice Alex

The ZWave binding has always used the serial-transport feature. This is generally the only way to communicate via serial - unless a binding includes its own drvier in the binding.

2 Likes

thank you for that Chris!

After upgrading from 2.4 I am seeing a “DateTimeType” error in openhab.log (see stack trace below)

FWIW, I am also seeing the the zwave binding re-initializing every minute or so as reported above so I will keep an eye on that dialog too.

2019-11-23 04:59:18.236 [ERROR] [me.core.internal.events.EventHandler] - Creation of ESH-Event failed, because one of the registered event factories has thrown an exception: Error invoking #valueOf(String) on class ‘org.eclipse.smarthome.core.library.types.DateTimeType’ with value ‘2-01-01T00:00:00.000-0500’.
java.lang.IllegalStateException: Error invoking #valueOf(String) on class ‘org.eclipse.smarthome.core.library.types.DateTimeType’ with value ‘2-01-01T00:00:00.000-0500’.
at org.eclipse.smarthome.core.items.events.ItemEventFactory.parseSimpleClassName(ItemEventFactory.java:189) ~[?:?]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.parseType(ItemEventFactory.java:157) ~[?:?]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.getState(ItemEventFactory.java:135) ~[?:?]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.createStateEvent(ItemEventFactory.java:115) ~[?:?]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.createEventByType(ItemEventFactory.java:79) ~[?:?]
at org.eclipse.smarthome.core.events.AbstractEventFactory.createEvent(AbstractEventFactory.java:55) ~[?:?]
at org.eclipse.smarthome.core.internal.events.EventHandler.createESHEvent(EventHandler.java:134) ~[?:?]
at org.eclipse.smarthome.core.internal.events.EventHandler.handleEvent(EventHandler.java:108) ~[?:?]
at org.eclipse.smarthome.core.internal.events.EventHandler.handleEvent(EventHandler.java:85) ~[?:?]
at org.eclipse.smarthome.core.internal.events.ThreadedEventHandler.lambda$0(ThreadedEventHandler.java:67) ~[?:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_152]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_152]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_152]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.parseSimpleClassName(ItemEventFactory.java:180) ~[?:?]
… 10 more
Caused by: java.lang.IllegalArgumentException: 2-01-01T00:00:00.000-0500 is not in a valid format.
at org.eclipse.smarthome.core.library.types.DateTimeType.(DateTimeType.java:127) ~[?:?]
at org.eclipse.smarthome.core.library.types.DateTimeType.valueOf(DateTimeType.java:146) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_152]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_152]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_152]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.parseSimpleClassName(ItemEventFactory.java:180) ~[?:?]
… 10 more
Caused by: java.time.format.DateTimeParseException: Text ‘2-01-01T00T00:00:00:00:00.000-0500’ could not be parsed at index 0
at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:1949) ~[?:1.8.0_152]
at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851) ~[?:1.8.0_152]
at java.time.LocalDateTime.parse(LocalDateTime.java:492) ~[?:1.8.0_152]
at org.eclipse.smarthome.core.library.types.DateTimeType.parse(DateTimeType.java:255) ~[?:?]
at org.eclipse.smarthome.core.library.types.DateTimeType.(DateTimeType.java:121) ~[?:?]
at org.eclipse.smarthome.core.library.types.DateTimeType.valueOf(DateTimeType.java:146) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_152]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_152]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_152]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
at org.eclipse.smarthome.core.items.events.ItemEventFactory.parseSimpleClassName(ItemEventFactory.java:180) ~[?:?]
… 10 more

Issue opened for D-Link Smart Home binding problem.

1 Like

Here my list of “serial”- Features:

openhab> feature:list | grep serial
openhab-binding-lgtvserial                        x 2.5.0.M5         x          x Uninstalled x openhab-addons-2.5.0.M5        x LG TV Serial Binding
openhab-binding-serialbutton                      x 2.5.0.M5         x          x Uninstalled x openhab-addons-2.5.0.M5        x Serial Button Binding
openhab-binding-serial1                           x 1.14.0.M5        x          x Uninstalled x openhab-addons-2.5.0.M5        x Serial Binding
openhab-core-config-serial                        x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab-core-config-discovery-usbserial           x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab-core-io-transport-serial                  x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab-core-io-transport-serial-javacomm         x 2.5.0.M5         x x        x Started     x distro-2.5.0.M5                x
openhab-core-io-transport-serial-rxtx             x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab-core-io-transport-serial-rfc2217          x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab-transport-serial                          x 2.5.0.M5         x x        x Started     x distro-2.5.0.M5                x Serial Transport
openhab.tp-serial-javacomm                        x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x
openhab.tp-serial-rxtx                            x 2.5.0.M5         x          x Started     x distro-2.5.0.M5                x

I deinstalled Davis Binding but the Serial Features remained. Which one is used by zwave so i remove the others and Test

Apparently your command shows “Uninstalled” features too. Here is my list with a modified command.

openhab> feature:list | grep serial | grep Started
openhab-core-config-serial                        (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x
openhab-core-config-discovery-usbserial           (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x
openhab-core-io-transport-serial                  (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x
openhab-core-io-transport-serial-rxtx             (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x
openhab-core-io-transport-serial-rfc2217          (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x
openhab-transport-serial                          (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x Serial Transport
openhab.tp-serial-rxtx                            (0x 2.5.0.M5         x          x Started     x distro-2.5.0.M5          x

Bonus.

openhab> bundle:list | grep serial
211 x Active x  80 x 3.15.0.OH2              x nrjavaserial

Since i remove the azureiot, i didn’t had the issue anymore.

I also disabled the enocean binding, which does not work at all. I guess i will open a github issue for this one after i looked deeper into, but as i don’t have any enocean devices connected, it’s not my top priority.

The zwave binding now is 2.5.0.M4 installed over an existing 2 5.0.M5 distribution, correct?

If so, what are resulting the following commands?

bundle:list |grep ZWave 

bundle:list |grep erial 

bundle:list |grep xstream
1 Like

openhab> smarthome:audio play doorbell
Unsupported file extension!