I have some problems with a ZMEE05434 wall insert switch.
Though it is recognized by the system and a thing with a channel is created, I got the following issues:
I can query data, e.g. power consumption, etc. BUT I cannot send any commands.
In the log file I see: “NODE 12: Timeout while sending message…” and this repeats until "Too many retries"
But the switch works fine with other zwave controllers.
What could be the reason for that?
THis device has about 12 configuration parameters, but only the first 7 are shown. Is this because of some missing definition in the database? I cannot configure for example the “scene control”
The device is recognized as a Dimmer (and by default linked with a dimmer item), but it is a switch without dimming capabilities. How does this come? Could this be a reason for 1. ?
Firstly, can you provide the link to the database for this device (ie on cd-jackson.com)? I don’t find a 5434 device from Z-Wave.me so I guess it has a different name?
I’m not sure - can you provide the XML file for this node?
Yes - if you can create a user on the database site then I can give you access to update it - so long as there aren’t multiple versions of this. Again, it would be good to find out exactly what device you have.
Again - I think we need to understand what device you have and what’s in the database…
I was actually after the XML generated by openhab for your node - it should be in the userdata/zwave folder.
If you can create a user on the database site then I can give you access to update it - so long as there aren’t multiple versions of this. I suggest before doing this though we make sure we understand the device.
According to the pepper database, it supports the multilevel_switch class which makes it a dimmer. I suspect it’s able to be used as a dimmer to controller other switches, so even if it’s only an on/off switch itself, it can control another dimmer.
Hi Chris,
thanks.
But my prio 1 problem is not the missing parameters (which could be fixed by extending the xml in your database, if I understood you right), but point 1 of my first email:
Hi Chris,
attached you’ll find a log file of my openhab2 with log level set to TRACE for org.openhab.binding.zwave.
It’s a zip file, I changed extension to .xml due to upload restrictions (or is there another way to send you the log file?) openhab-log.zip.xml (115.7 KB)
The log file contains the startup of my openhab2 server and the sending of one “switch on” command to the device (NODE12) at time 21.17.24
As I said, I can read information via METER command, but I cannot switch on /off. When I do the same with my commercial DEVOLO Controller it works.
Sorry - I missed your responses (it’s best to reply to one of my messages otherwise the forum doesn’t provide any notifications).
I’m not sure what device this is - can you tell me what it’s discovered as (5434 isn’t in the database, but presumably it is discovered as another device - I’m just not sure which one).
it is recognized as the following device (taken from PaperUI):
Z-Wave Node 12: POPP/ZWave.Me 05433-EX Zwave.Me Dimmer Set Everlux
I can read information like power consumption. But if I try to turn it ON or OFF the follwing messages can be seen in the log (no more timeout, everything looks ok in my opinion), but the switch does not react. When I use my devolo Controller the switch reacts fine and everything works.
Here is a part of the log file for TURN ON:
2017-03-11 00:33:04.800 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Command received zwave:device:1598f8d5d18:node12:switch_dimmer --> ON
2017-03-11 00:33:04.802 [TRACE] [erter.ZWaveMultiLevelSwitchConverter] - NODE 12: Converted command 'ON' to value 99 for channel = zwave:device:1598f8d5d18:node12:switch_dimmer, endpoint = 0.
2017-03-11 00:33:04.804 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 12: Creating new message for command SWITCH_MULTILEVEL_SET
2017-03-11 00:33:04.807 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 12: Creating empty message of class = SendData (0x13), type = Request (0x00)
2017-03-11 00:33:04.809 [TRACE] [ve.internal.protocol.ZWaveController] - Callback ID = 248
2017-03-11 00:33:04.811 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-11 00:33:04.811 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-11 00:33:04.816 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x70
2017-03-11 00:33:04.820 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 0C 03 26 01 63 25 F8 70
2017-03-11 00:33:04.828 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 12: Sending REQUEST Message = 01 0A 00 13 0C 03 26 01 63 25 F8 70
2017-03-11 00:33:04.830 [TRACE] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2017-03-11 00:33:04.835 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received ACK
2017-03-11 00:33:04.839 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF
2017-03-11 00:33:04.849 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-03-11 00:33:04.854 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 04 01 13 01 E8
2017-03-11 00:33:04.858 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0xE8
2017-03-11 00:33:04.861 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
2017-03-11 00:33:04.865 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Message payload = 01
2017-03-11 00:33:04.868 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
2017-03-11 00:33:04.870 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
2017-03-11 00:33:04.872 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF
2017-03-11 00:33:04.872 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-11 00:33:04.874 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0xE8
2017-03-11 00:33:04.875 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-03-11 00:33:04.877 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 F8 00 00 02 11
2017-03-11 00:33:04.877 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-03-11 00:33:04.879 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2017-03-11 00:33:04.879 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 07 00 13 F8 00 00 02 11
2017-03-11 00:33:04.880 [TRACE] [ve.internal.protocol.ZWaveController] - Incoming Message type = RESPONSE
2017-03-11 00:33:04.881 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x11
2017-03-11 00:33:04.881 [TRACE] [l.serialmessage.SendDataMessageClass] - Handle Message Send Data Response
2017-03-11 00:33:04.882 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
2017-03-11 00:33:04.882 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 12: Sent Data successfully placed on stack.
2017-03-11 00:33:04.883 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Message payload = F8 00 00 02
2017-03-11 00:33:04.884 [TRACE] [wave.internal.protocol.SerialMessage] - Ack Pending cleared
2017-03-11 00:33:04.885 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
2017-03-11 00:33:04.886 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
2017-03-11 00:33:04.887 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-11 00:33:04.889 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x1F
2017-03-11 00:33:04.890 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 F8 00 00 02 00 00 1F
2017-03-11 00:33:04.896 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 F8 00 00 02 00 00 1F
2017-03-11 00:33:04.898 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=F8 00 00 02
2017-03-11 00:33:04.899 [TRACE] [ve.internal.protocol.ZWaveController] - Incoming Message type = REQUEST
2017-03-11 00:33:04.901 [TRACE] [l.serialmessage.SendDataMessageClass] - Handle Message Send Data Request
2017-03-11 00:33:04.902 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 12: SendData Request. CallBack ID = 248, Status = Transmission complete and ACK received(0)
2017-03-11 00:33:04.903 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Starting initialisation from DONE
2017-03-11 00:33:04.905 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@f090c7 already registered
2017-03-11 00:33:04.917 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=12, callback=248, payload=0C 03 26 01 63
2017-03-11 00:33:04.922 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=F8 00 00 02
2017-03-11 00:33:04.923 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=248, expected=SendData, cancelled=false transaction complete!
2017-03-11 00:33:04.924 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-03-11 00:33:04.925 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-03-11 00:33:04.926 [TRACE] [ve.internal.protocol.ZWaveController] - Released. Transaction completed permit count -> 1
2017-03-11 00:33:04.926 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 12: Response processed after 94ms/4694ms.
2017-03-11 00:33:04.928 [TRACE] [ocol.ZWaveController$ZWaveSendThread] - Acquired. Transaction completed permit count -> 0
2017-03-11 00:33:04.996 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - transformation throws exception [transformation=org.eclipse.smarthome.transform.map.internal.MapTransformationService@c7026e, value=-]
org.eclipse.smarthome.core.transform.TransformationException: An error occured while opening file.
at org.eclipse.smarthome.transform.map.internal.MapTransformationService.internalLoadTransform(MapTransformationService.java:66)[198:org.eclipse.smarthome.transform.map:0.9.0.b4]
at org.eclipse.smarthome.transform.map.internal.MapTransformationService.internalLoadTransform(MapTransformationService.java:1)[198:org.eclipse.smarthome.transform.map:0.9.0.b4]
at org.eclipse.smarthome.core.transform.AbstractFileTransformationService.transform(AbstractFileTransformationService.java:133)[107:org.eclipse.smarthome.core.transform:0.9.0.b4]
at org.eclipse.smarthome.ui.internal.items.ItemUIRegistryImpl.transform(ItemUIRegistryImpl.java:411)[136:org.eclipse.smarthome.ui:0.9.0.b4]
at org.eclipse.smarthome.ui.internal.items.ItemUIRegistryImpl.getLabel(ItemUIRegistryImpl.java:338)[136:org.eclipse.smarthome.ui:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.render.AbstractWidgetRenderer.getLabel(AbstractWidgetRenderer.java:114)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.render.TextRenderer.renderWidget(TextRenderer.java:47)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.render.PageRenderer.renderWidget(PageRenderer.java:166)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.render.PageRenderer.processChildren(PageRenderer.java:123)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.render.PageRenderer.processPage(PageRenderer.java:86)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.smarthome.ui.classic.internal.servlet.WebAppServlet.service(WebAppServlet.java:160)[204:org.eclipse.smarthome.ui.classic:0.9.0.b4]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[79:org.eclipse.jetty.security:9.2.19.v20160908]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.Server.handle(Server.java:499)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)[80:org.eclipse.jetty.server:9.2.19.v20160908]
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
Caused by: java.io.FileNotFoundException: /etc/openhab2/transform/motion.map (Datei oder Verzeichnis nicht gefunden)
at java.io.FileInputStream.open0(Native Method)[:1.8.0_121]
at java.io.FileInputStream.open(FileInputStream.java:195)[:1.8.0_121]
at java.io.FileInputStream.<init>(FileInputStream.java:138)[:1.8.0_121]
at java.io.FileInputStream.<init>(FileInputStream.java:93)[:1.8.0_121]
at java.io.FileReader.<init>(FileReader.java:58)[:1.8.0_121]
at org.eclipse.smarthome.transform.map.internal.MapTransformationService.internalLoadTransform(MapTransformationService.java:62)[198:org.eclipse.smarthome.transform.map:0.9.0.b4]
... 31 more
the problem is that the device does not do anything. THe light does not turn on.
If I use the devolo controller it works fine. So it has to do with the OH2 binding somehow, the device itself is ok.
I already attached the node12.xml file, here it is once more:node12.xml (12.4 KB)
and what about the exception in the log? Has this something to do with the zwave binding?
Caused by: java.io.FileNotFoundException: /etc/openhab2/transform/motion.map
