Fibaro FGMS001 Zwave Plus Motion Sensor with Device Type 801 not working properly

[anordvall]

openhab debug.log.txt

The new ZWave Plus (Device Type 801) of Fibaro FGMS001 does not seem to get initialized properly. I do not have any problems with the earlier generation (Device Type 800).

Controller: Aeon Labs Z-Stick OS: Raspberry Pi 3 with Raspian OS. Z-Wave addon: Downloaded from cloudbees today April 10th.

Please find the debug log attached. The Fibaro Motion Sensor is NODE 7. I reset the node and included it in the controller before starting openHAB.

Really appreciate if you can have a look at this one @cdjackson . My brother have the exact same problem but with a Z-Stick connected to a PC running Windows, so at least I'm not the only one seeing it.

I can also mention that the device does not work properly either. When motion is detected, openHAB logs it as receiving a command class ALARM (same as what is logged when you shake the device to trigger Tamper Alarm)

[cdjackson]

We need to create a new version in the database - this is different. The immediate problem is that parameter 26 is no longer included in version 3.2, but there may be other issues.

I’ve created a new entry in the database -: http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328 http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328

Please can you upload your XML file to this (hopefully it will detect the correct version) and then ensure that all the parameters and association groups are correct as per the manual (I’ve loaded the manual from the Fibaro site for version 3.2).

Any problems, please let me know.

Chris

On 10 Apr 2016, at 19:19, Andreas notifications@github.com wrote:

openhab debug.log.txt https://github.com/openhab/openhab/files/211904/openhab.debug.log.txt The new ZWave Plus (Device Type 801) of Fibaro FGMS001 does not seem to get initialized properly. I do not have any problems with the earlier generation (Device Type 800).

Controller: Aeon Labs Z-Stick OS: Raspberry Pi 3 with Raspian OS. Z-Wave addon: Downloaded from cloudbees today April 10th.

Please find the debug log attached. The Fibaro Motion Sensor is NODE 7. I reset the node and included it in the controller before starting openHAB.

Really appreciate if you can have a look at this one @cdjackson https://github.com/cdjackson . My brother have the exact same problem but with a Z-Stick connected to a PC running Windows, so at least I'm not the only one seeing it.

I can also mention that the device does not work properly either. When motion is detected, openHAB logs it as receiving a command class ALARM (same as what is logged when you shake the device to trigger Tamper Alarm)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4274

[anordvall]

There is no XML generated yet. Do you mean the XLM generated once I try with the new DB?

[cdjackson]

Hmmm - good point. Ok - if you can get the configuration corrected we can update the database in the binding, then it should create the XML...

[anordvall]

You lost me. Might be because I had a couple of glasses of red wine :) Can you point me in the right direction of what I should do? Many thanks!

[cdjackson]

Are you registered on the database site? If not, first register and then I’ll give you access. The you should make sure that all the parameters are correct - I know that parameter 26 needs to be deleted, but maybe there are other parameters that are different in this version. There’s probably not many changes, but it would be good to get it correct.

Once you’re happy this is ok, then email me and I’ll update the database - it should then work, and then it should create the XML.

Enjoy the wine :)

[anordvall]

I assume "the database site" is the cd-jacksson site you linked? I've now registered an account (btw, it mailed me my password in plain text?!) :)

[cdjackson]

Yes, and I’ve just given you edit access…

I thought I’d disabled the sending of passwords - it’s a very annoying default feature of Joomla! I’ll try and find the setting again - thanks.

On 10 Apr 2016, at 21:05, Andreas notifications@github.com wrote:

I assume "the database site" is the cd-jacksson site you linked? I've now registered an account (btw, it mailed me my password in plain text?!) :)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4274#issuecomment-208056425

[anordvall]

I'll go through the device manual parameter by parameter tomorrow. Thanks as always for all your help Chris!

[anordvall]

@cdjackson - Quite some changes compared to the previous version. I went through the manual parameter by parameter and attached are my findings for the ones that have changed.

Fibaro motion sensor diff.txt

The manuals I compared was: OLD: http://manuals.fibaro.com/content/manuals/en/FGMS-001/FGMS-001-EN-A-v1.01.pdf NEW: http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1146/FGMS-001-EN-A-v1.02.pdf

[cdjackson]

Wow - that's a comprehensive check 👍

Can you update the new device in the database with the changes?

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328

Thanks Chris

[anordvall]

I will be away for 2 weeks now but after that I will give it a shot unless someone else beats it to me, which I hope someone do :)

[xdxoxkx]

I am new and testing Openhab with this sensor ... I got Version 4 ... the behavior is quite strange ... hope for some updates ... thx

[tiger-seo]

i have the same type (device type 801) of the device and also can't initialize it with openhab

[cdjackson]

What version are you using? What device type/id does the device report?

[xdxoxkx]

From openHAB Admistration Interface:

Version: 4 Product: FGMS001 Motion Sensor Device Type: 801 Device ID: 1001 Application Version: 3.2 Protocol Version: 4.5

... and ... Generic Device Class: Garage_Door Specific Device Class: Simple_Garage_Door

[cdjackson]

And what version of the binding are you using?

[xdxoxkx]

At the moment ... -> org.openhab.binding.zwave-1.9.0-fibaro-eye-hack.jar

before: org.openhab.binding.zwave-1.9.0-SNAPSHOT.jar and before org.openhab.binding.zwave-1.8.1.jar

[cdjackson]

What does "the behavior is quite strange" mean?

If the problem is still related to the database issues that were explained above, then it would be appreciated if someone can update the database with the changes for the new device -:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328

[tiger-seo]

here is my zwave log https://gist.github.com/tiger-seo/48d4745709095fb91e9c220b6cb016ac

[cdjackson]

Thanks - so it looks like the same problem I already identified……..

[anordvall]

@cdjackson I just found some time to dig into this, but I believe I still don't have edit rights? When I login and browse to:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328

It says:

"Please note that you must contact the administrator to get edit rights to the database once you have registered."

... and I don't find any edit button anywhere, so I assume I don't have access yet :)

[cdjackson]

It looks like you should have access - do you see the edit buttons on the device summary page?

If not, please email me your login name and I’ll triple check...

[anordvall]

You mean the Device Overview page, shown after clicking on a device in the devicelist? Nope, no Edit buttons... my username is "anordvall". I've tried in both IE and Chrome.

[cdjackson]

Ok - should be good now (there’s a few people called Andreas :) - I got the wrong ones - sorry ).

[anordvall]

Looks better now :) Ok I will give this a try...

[anordvall]

Chris, I updated a lot of parameters and it said they all waited for review. Then I added parameter 25 and now it only says that parameter 25 is waiting for review. Can you check so not all my other changes got lost?

[anordvall]

Never mind... seems I accidentally added param 25 to the old device database entry. Trying to correct this ... :)

[cdjackson]

You probably won’t be able to change this - I can delete it though if you set its label to DELETE ME or something like that.

On 15 May 2016, at 17:08, Andreas notifications@github.com wrote:

Never mind... seems I accidentally added param 25 to the old device database entry. Trying to correct this ... :)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4274#issuecomment-219294579

[anordvall]

It's not in the list so I can't edit it (?). Anyway, I pressed request for review... so please delete it right away so it's not forgotten about.

[anordvall]

Hmm... I now see parameter 25 ended up correctly in device 328, but the change message ended up incorrectly in 115 :) Seems there is a bug in the system..

[cdjackson]

Seems so :( Did you swap between browser windows or something? Sometimes this sort of thing happens if you have two sessions open?

Looks ok though - thanks. I’ll get this added tonight, so let me know how it goes…

Just to confirm - you need this on OH1 right?

[anordvall]

Yes I have both the old and new device config open at the same time, and I probably clicked Edit on the old one just to check something, and then went back.

Yes I need it for OH1. I still have some parameters to update so give me another hour :)

[cdjackson]

Ok - no probs - just let me know when you’re done…

[anordvall]

All done. Note that parameter 28 and 29 looks almost identical but it's not a mistake. They only differ slightly when mentioning 3rd and 5th association groups. Feel free to edit the labels if you think they should differ. Also notice that two options in parameter 24 should be deleted (marked as DELETE ME).

[cdjackson]

Thanks - I’ve deleted the two options…

[anordvall]

Chris, I downloaded the new zwave build from cloudbees today and tried it out. The Fibaro Motion sensor then was identified (still as a garage door though?), an XML was created and I saw the updated configuration parameters from the new DB entry. Still, the sensor didn't work as expected... when motion was detected it sent an alarm (whyyy?) as it did previously, so no improvement. Anyway, I excluded the device, reset it and included it again. Now the device was added using the old database entry! Perhaps 0801:1001 must be removed from the older product version (DB entry 115)? I've attached debug log (NODE 13) and node13.xml from this last attempt. Appreciate if you can have a look at them.

openhab.log.txt node13.xml.txt

[cdjackson]

I don’t see anything obviously wrong.

Changing the database won’t change what the device sends, so it won’t change the fact that it sends an alarm.

Don’t worry about the ‘garage door’ thing - that’s just a name and isn’t relevant.

Why do you think it was detected as the wrong database entry?

[anordvall]

Ah, it must have been my browser that cached the old page because I could see suddenly see all old parameters after my last include. Now without having done any change, I see the new parameters again.

Anyway, any idea why it sends an alarm at motion detection? I can't figure out how to solve this... Anyone else reading this thread have any idea? I'm almost thinking about returning the devices and buy old non-plus ones.

[cdjackson]

Some devices send alarms (notifications) - that’s quite normal.

[anordvall]

Hi Chris. I realized there are also changes to the association groups compared to previous version. This explains why I currently get proper motion events (though don't understand why I get double events) when setting the Tamper association group (which is nowadays Motion association group). Please review especially the "max nodes" as I'm not sure it should be set to 5 especially in the 5th association group.

Also, note that I have not even reviewed the End Points configuration as I have no idea what that should look like.

[cdjackson]

Thanks. I think it looks ok. I removed the ‘controller’ tag from group 3 as this will cause multiple notifications (at least it does on other Fibaro devices if you use the lifeline group, and have other groups linked to the controller.

The endpoints should be ok - this gets read from your XML so should be directly from the device. It’s possible though that it might miss some stuff as I’ve recently added a feature to ensure we get all command classes logged, which wasn’t the case previously… For OH1 though, it’s probably fine.

I’ll try and remember to update the OH1 database tonight.

[anordvall]

Ah, I noticed #3 had Controller since before. I meant to remove it but I forgot :) I changed from "garage" in Endpoints now as well. Please review =)

[anordvall]

Please do... I'm eager to test this now :)

[cdjackson]

Hmm - not a good idea to change the class - it should stay as Garage for now. Ultimately I will change the name but it needs to be changed in many places at the same time as this name, even though it is wrong, is used to link things together (the actual name doesn’t matter, but it needs to be consistent in the database and the binding and the XML files).

On 21 May 2016, at 14:01, Andreas notifications@github.com wrote:

Please do... I'm eager to test this now :)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4274#issuecomment-220776642

[anordvall]

Ok I see. Please decline my change.

[cdjackson]

Have done - I need to update all this as I do understand it’s confusing to people…

On 21 May 2016, at 14:01, Andreas notifications@github.com wrote:

Please do... I'm eager to test this now :)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4274#issuecomment-220776642

[anordvall]

Chris, even though the association group names are wrong for me with my current binding version, I now set Group 1 to 0, Group 2 to 1 and Group 3 to 0. When I trigger motion this is what is logged:

13:17:21.450 [DEBUG] [eController$ZWaveReceiveThread:1530 ] - Receive Message = 01 09 00 04 08 0D 03 20 01 FF 2A
13:17:21.451 [DEBUG] [eController$ZWaveReceiveThread:1446 ] - Receive queue ADD: Length=1
13:17:21.451 [DEBUG] [b.z.i.protocol.ZWaveController:1194 ] - Receive queue TAKE: Length=0
13:17:21.452 [DEBUG] [o.b.z.i.protocol.SerialMessage:243  ] - Assembled message buffer = 01 09 00 04 08 0D 03 20 01 FF 2A
13:17:21.453 [DEBUG] [b.z.i.protocol.ZWaveController:1195 ] - Process Message = 01 09 00 04 08 0D 03 20 01 FF 2A
13:17:21.453 [DEBUG] [b.z.i.protocol.ZWaveController:194  ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 0D 03 20 01 FF
13:17:21.454 [DEBUG] [ApplicationCommandMessageClass:40   ] - NODE 13: Application Command Request (ALIVE:PING)
13:17:21.455 [DEBUG] [ApplicationCommandMessageClass:58   ] - NODE 13: Incoming command class BASIC
13:17:21.455 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:73   ] - NODE 13: Received Basic Request
13:17:21.456 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:77   ] - NODE 13: Basic Set sent to the controller will be processed as Basic Report
13:17:21.456 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:106  ] - NODE 13: Basic report, value = 0xFF
13:17:21.457 [DEBUG] [b.z.i.protocol.ZWaveController:648  ] - Notifying event listeners: ZWaveCommandClassValueEvent
13:17:21.457 [DEBUG] [.z.internal.ZWaveActiveBinding:449  ] - ZwaveIncomingEvent
13:17:21.458 [DEBUG] [.z.internal.ZWaveActiveBinding:466  ] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
13:17:21.459 [DEBUG] [ApplicationCommandMessageClass:89   ] - Transaction not completed: node address inconsistent.
13:17:21.487 [DEBUG] [eController$ZWaveReceiveThread:1530 ] - Receive Message = 01 09 00 04 00 0D 03 20 01 FF 22
13:17:21.488 [DEBUG] [eController$ZWaveReceiveThread:1446 ] - Receive queue ADD: Length=1
13:17:21.488 [DEBUG] [b.z.i.protocol.ZWaveController:1194 ] - Receive queue TAKE: Length=0
13:17:21.489 [DEBUG] [o.b.z.i.protocol.SerialMessage:243  ] - Assembled message buffer = 01 09 00 04 00 0D 03 20 01 FF 22
13:17:21.490 [DEBUG] [b.z.i.protocol.ZWaveController:1195 ] - Process Message = 01 09 00 04 00 0D 03 20 01 FF 22
13:17:21.490 [DEBUG] [b.z.i.protocol.ZWaveController:194  ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 0D 03 20 01 FF
13:17:21.491 [DEBUG] [ApplicationCommandMessageClass:40   ] - NODE 13: Application Command Request (ALIVE:PING)
13:17:21.491 [DEBUG] [ApplicationCommandMessageClass:58   ] - NODE 13: Incoming command class BASIC
13:17:21.491 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:73   ] - NODE 13: Received Basic Request
13:17:21.492 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:77   ] - NODE 13: Basic Set sent to the controller will be processed as Basic Report
13:17:21.492 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:106  ] - NODE 13: Basic report, value = 0xFF
13:17:21.492 [DEBUG] [b.z.i.protocol.ZWaveController:648  ] - Notifying event listeners: ZWaveCommandClassValueEvent
13:17:21.493 [DEBUG] [.z.internal.ZWaveActiveBinding:449  ] - ZwaveIncomingEvent
13:17:21.493 [DEBUG] [.z.internal.ZWaveActiveBinding:466  ] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
13:17:21.494 [DEBUG] [ApplicationCommandMessageClass:89   ] - Transaction not completed: node address inconsistent.

Any idea why the motion sensor (NODE 13) sends a duplicate event?

Also, when "Controller" is set in an association group config (as you earlier noticed in group 3)... does it only mean the controller is by default assigned to the association group, or does it mean that it is forced to the group and can not be removed? Just for my understanding.

[cdjackson]

I’m not sure why it would send two notifications. Maybe it’s a config setting, or maybe not - I’m not sure…

Regarding the controller setting in the database - this just means that it will be set there by default - you can remove it, although when the binding restarts, it might restore this, so to some degree it will be forced...

[RosaEinhorn]

Hi everybody,

I am having problems using the same device (version: 4) with habmin. Yesterday, the device worked for some hours and sent some data to the controller, than it changed to grey in habmin and finally to red. However, it is still sending data to the controller (e.g. when there is motion). But there are problems with the data:

NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255 Transaction not completed: node address inconsistent.

I am also getting this error: 2016-06-03 12:54:27.382 [ERROR] [.s.container.ContainerResponse] - The RuntimeException could not be mapped to a response, re-throwing to the HTTP container java.lang.NullPointerException: null at org.openhab.binding.zwave.internal.config.ZWaveConfiguration.getConfiguration(ZWaveConfiguration.java:127) ~[bundlefile:na] at org.openhab.io.habmin.services.zwave.ZWaveConfigResource.getConfig(ZWaveConfigResource.java:73) ~[na:na] at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) ~[na:na] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_60] at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_60] at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) ~[jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) [jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) [jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) [jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) [jersey-server-1.18.1.jar:1.18.1] at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) [jersey-servlet-1.18.1.jar:1.18.1] at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) [jersey-servlet-1.18.1.jar:1.18.1] at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) [jersey-servlet-1.18.1.jar:1.18.1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) [javax.servlet_3.0.0.v201112011016.jar:na] at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:135) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:206) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:105) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.container.Jetty7CometSupport.service(Jetty7CometSupport.java:57) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.container.JettyAsyncSupportWithWebSocket.service(JettyAsyncSupportWithWebSocket.java:67) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:2076) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:211) [atmosphere-runtime-2.2.5.jar:2.2.5] at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:197) [atmosphere-runtime-2.2.5.jar:2.2.5] at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) [javax.servlet_3.0.0.v201112011016.jar:na] at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) [javax.servlet_3.0.0.v201112011016.jar:na] at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na] at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na] at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na] at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) [javax.servlet_3.0.0.v201112011016.jar:na] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598) [org.eclipse.jetty.servlet_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:486) [org.eclipse.jetty.servlet_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413) [org.eclipse.jetty.servlet_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.Server.handle(Server.java:350) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:890) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:944) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:630) [org.eclipse.jetty.http_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230) [org.eclipse.jetty.http_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606) [org.eclipse.jetty.io_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46) [org.eclipse.jetty.io_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603) [org.eclipse.jetty.util_8.1.3.v20120522.jar:8.1.3.v20120522] at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538) [org.eclipse.jetty.util_8.1.3.v20120522.jar:8.1.3.v20120522] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]

Would be cool if someone could help. :-)

[cdjackson]

What version of ZWave are you using?