Hi,
I hope someone can help me with this.
I’m trying to setup OpenHab 2.2.0 with an Aeotec Z-stick Gen5 and a few Everspring AD142 dimmers. I’m not new to OH (been using 1.x for some time now), but Z-wave is new for me.
In short:
- USB hardware seems to be working correctly
- pairing works (nodes are shown in OH ui and logs)
- controlling the items just won’t work, they won’t respond.
While troubleshooting this, I came across 2 different ways to configure the item. According to the OH2 docs, you should do something like:
Dimmer Light1 {zwave="3"}
But after reading other pages and forum posts, I came across:
Dimmer Light1 {channel="zwave:device:cef0f9ef:node3"}
When I use the latter, the log shows:
[.ItemChannelLinkAddedEvent] - Link 'Light1-zwave:device:cef0f9ef:node3' has been added.
Which sounds good I guess? But I sounds odd that the docs are wrong at this point.
Anyhow, I tried both types of configurations, no luck.
The dimmers I am using are branded “Eminent” but are detected as “Everspring” so they are probably rebranded by Eminent. Should be no issue offcourse.
The dimmer has also 1 button for manual switching the output. When I press that button, the following shows up in the debug log:
[WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 49 84 03 09 03 11 01 26 27 72 86 75 73 D7
[ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
[wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 49 84 03 09 03 11 01 26 27 72 86 75 73 D7
[ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 49 84 03 09 03 11 01 26 27 72 86 75 73 D7
[ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 03 09 03 11 01 26 27 72 86 75 73
[essage.ApplicationUpdateMessageClass] - NODE 3: Application update request. Node information received.
[alization.ZWaveNodeInitStageAdvancer] - NODE 3: Starting initialisation from DONE
[ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@30f4d8b6 already registered
[essage.ApplicationUpdateMessageClass] - NODE 3: Application update request. Requesting node state.
[ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveDelayedPollEvent
[ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveDelayedPollEvent
[ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling intialised at 1800 seconds - start in 75 milliseconds.
[.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=3, callback=13, payload=03 01 00
[.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 03 09 03 11 01 26 27 72 86 75 73
[.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=13, expected=SendData, cancelled=false MISMATCH
[ding.zwave.handler.ZWaveThingHandler] - NODE 3: Polling...
So there is some kind of communication.
My items file looks like this:
Dimmer Light1 {channel="zwave:device:cef0f9ef:node3"}
Sitemap looks like this:
sitemap default label="Main Menu" {
Frame label="Test" {
Slider item=Light1
}
}
For testing I’m using the openhab 2.2.0 zip file downloaded from openhab.org
I also tried setting commands in the items file like SWITCH_MULTILEVEL, but nothing makes the dimmers repond.
I’ve set the zwave binding to debug level. The log shows this when changing the dimmer level:
[ome.event.ItemCommandEvent] - Item ‘Light1’ received command 50
[vent.ItemStateChangedEvent] - Light1 changed from 0 to 50
I would expect that there should be also some zwave logging, right (particulalry in debug)?
Is there something wrong with the node configuration? I sometimes read that it helps to show the node xml file, so here it is:
<node>
<deviceClass>
<basicDeviceClass>SLAVE</basicDeviceClass>
<genericDeviceClass>MULTILEVEL_SWITCH</genericDeviceClass>
<specificDeviceClass>POWER_SWITCH_MULTILEVEL</specificDeviceClass>
</deviceClass>
<homeId>0xec224642</homeId>
<nodeId>3</nodeId>
<version>3</version>
<manufacturer>0x60</manufacturer>
<deviceId>0x1</deviceId>
<deviceType>0x3</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<supportedCommandClasses>
<entry>
<commandClass>SWITCH_ALL</commandClass>
<switchAllCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<mode>SWITCH_ALL_INCLUDE_ON_OFF</mode>
</switchAllCommandClass>
</entry>
<entry>
<commandClass>POWERLEVEL</commandClass>
<powerLevelCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</powerLevelCommandClass>
</entry>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>0</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>96</deviceManufacturer>
<deviceType>3</deviceType>
<deviceId>1</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>PROTECTION</commandClass>
<protectionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<localModes/>
<rfModes/>
</protectionCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE</libraryType>
<protocolVersion>2.64</protocolVersion>
<applicationVersion>1.2</applicationVersion>
</versionCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups/>
<nodeNeighbors/>
<lastSent>2018-01-13 16:01:00.933 UTC</lastSent>
<lastReceived>2018-01-13 16:01:00.970 UTC</lastReceived>
</node>
Sorry for the wall of text, but I’m just not getting why this won’t work.
Am I missing something obvious? Hopefully someone can help me out.
Regards,
Hugo
. What normally happens when you upload an XML (among other things) is that the database searches to see if the device id/type is already in the database, and if it is, it uses that database entry. This is designed to prevent duplication…
.