I have the EU version of this remote.
ZRC-90 Scene master 8 button remote
zwave:remotec_zrc90_00_000
Scene master 8 button remote
Is it possible to get it added to the database?
zwave:device:0e4e20e7:node6
Sorry. Solution found by enabling Wake mode while adding the device to OpenHAB
I have a Fibaro “The Button” GPB-101-3 ZW5 v3.2 and it is listed in the Zwave data base (in HABmin) however it is discovered as an unknown device via Paper UI inbox. I’ve researched the forum however, I can’t seem to find how to add this device correctly. I have removed and re-added and also restarted OpenHAB.
I am running OpenHAB 2 stable branch on Ubuntu 1604 installed via apt-get.
Any pointers would be greatly appreciated.
Further to my post, here is the details of The Button after pressing it multiple times to wake it up and allow OpenHAB to discover it.
zwave_class_basic ROUTING_SLAVE
zwave_class_generic REMOTE_SWITCH_2
zwave_neighbours 1
zwave_frequent false
zwave_nodeid 2
zwave_version 0.0
zwave_listening false
zwave_routing true
zwave_plus_devicetype UNKNOWN_TYPE
zwave_beaming true
zwave_class_specific SWITCH_REMOTE2_MULTILEVEL
Logs show that the device has been updated after multiple presses.
017-05-13 18:06:56.388 [hingStatusInfoChangedEvent] - ‘zwave:device:15bfcb09cfe:node2’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-05-13 18:06:56.388 [hingStatusInfoChangedEvent] - ‘zwave:device:15bfcb09cfe:node2’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-05-13 18:06:56.389 [ThingUpdatedEvent ] - Thing ‘zwave:device:15bfcb09cfe:node2’ has been updated.
2017-05-13 18:07:25.766 [ThingUpdatedEvent ] - Thing ‘zwave:device:15bfcb09cfe:node2’ has been updated.
2017-05-13 18:07:25.770 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-05-13 18:07:26.529 [ThingUpdatedEvent ] - Thing ‘zwave:device:15bfcb09cfe:node2’ has been updated.
2017-05-13 18:07:26.529 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-05-13 18:07:26.695 [ThingUpdatedEvent ] - Thing ‘zwave:device:15bfcb09cfe:node2’ has been updated.
2017-05-13 18:07:26.695 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-05-13 18:07:27.171 [ThingUpdatedEvent ] - Thing ‘zwave:device:15bfcb09cfe:node2’ has been updated.
2017-05-13 18:07:27.171 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
Nothing futher happens and it still remains as unknown. Im not able to add any Things for this device.
We need to see the device type/id that should also be displayed in the attributes.
Thank you for your reply Chris. Please see the full table of attributes which has built up since my original post by pressing the button multiple times.
zwave_class_basic ROUTING_SLAVE
zwave_class_generic REMOTE_SWITCH_2
zwave_neighbours 1
zwave_frequent false
zwave_version 3.2
zwave_listening false
zwave_plus_devicetype WALL_CONTROLLER
zwave_deviceid 12288
zwave_nodeid 2
zwave_routing true
zwave_wakeup_time 2017-05-13T08:15:41Z
zwave_beaming true
zwave_class_specific SWITCH_REMOTE2_MULTILEVEL
zwave_manufacturer 271
zwave_devicetype 3841
This looks to be in the database already. Are you using the snapshot version, or the release version of OH? You will need to be using a recent snapshot for this device to be included.
Thanks Chris I’m using the main release version of OpenHAB. Hmmmm, I’ll have to do some reading on how to change versions…
Hello @chris , I also have “Unknown Device”, which is actually “Zwave.Me Dimmer” model: zme05433/06433.
I have found it in database http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/343# but it is currently awaiting for review.
By using windows zwave software I found that it has ManufacturerID: 0115, and productid: 1000:0002.
Please approve it to be included to zwave binding.
Hi,
There’s a button that you can press to request the review - it’s the best way to get things updated. Anyway, I’ve now approved it so it should be in the binding in the next few days.
Chris
Hi Simon, could you please be more specific on how you did this? I have same problem and not able to get around it - for now (with the ZRC-90)
thanks 
/Chris
Just keep pushing the wake button close to the receiver it might take 10-20minuts but just keep doing it.
I did some reboots while doing this.
Or you can just jump ship. There are better and essayer open source software on the marked. Wont name names here.
Thanks for the quick reply, was afraid of that! I guess the real problem is that this ZRC only has a wakeup time of 30sec after pushing the button - in compare to others which have 10 minutes.
I kinda like OH, but thanks!
/Chris
@chris
I’m having trouble getting OH to discover the ZRC-90EU, is there a way to force OH to do a discovery?
Thanks,
Chris
In PaperUI, you can use the Inbox screen, and then the scan option. This is really the only way to start discovery.
If this is a battery device, and you need to get it to be interrogated, the only way to do this is to wake up the device. This is independent of the system being used as battery devices sleep most of the time, and they can only be woken by pressing a button on the device. This should NOT take 20 minutes as stated above, and you should definitely NOT reboot your system.
30 second wakeup should be fine. If it takes too long, then there may be another issue and it would then be worth getting a debug log to see what is happening.
I have a Fibaro KeyFob and are having trouble adding it to OpenHab it is discovered as an unknown device via Paper UI inbox. I can’t seem to find how to add this device correctly. I have removed and re-added and also restarted OpenHAB.
I’ve enabled logging for the zwave binding and there is an entry in the log:
2018-09-29 10:26:02.691 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 36: Device discovery completed
2018-09-29 10:26:02.697 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 36: Device discovery could not resolve to a thingType! Manufacturer data not known.
I also get entries in the log when I click the different buttons on the key:
2018-09-29 10:27:37.944 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Application Command Request (ALIVE:REQUEST_NIF)
2018-09-29 10:27:37.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0
2018-09-29 10:27:37.947 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: SECURITY not supported
2018-09-29 10:27:37.949 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 36: Received COMMAND_CLASS_CENTRAL_SCENE V0 CENTRAL_SCENE_NOTIFICATION
2018-09-29 10:27:37.950 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 36: Received scene 2 at key 0 [Single Press]
2018-09-29 10:27:37.954 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-29 10:27:37.957 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CENTRAL_SCENE, value = 2.0
2018-09-29 10:27:37.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Commands processed 1.
2018-09-29 10:27:37.965 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@5e2fc9.
But it’s still listed as unknown.
The same goes for a Z-Wave.Me Secure Wall Controller I’m trying to add to OpenHab.
Any tips would be helpful.
Thanks
Arild
The device is not initialised yet, so the binding doesn’t know the details about what it is, so it can’t correlate it to any of the entries in the database. You need to wake up the device so that the binding can communicate with it. I guess there will be a specific button that will either wake up the device, or send the NIF frame - the manual should tell you how to do this.
Thanks for the reply.
I have tried waking up the devices several times but they are still unknow. I tried waking up the Fibraro KeyFob several times now and I get these entries in the log:
2018-09-29 10:47:30.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Application Command Request (ALIVE:REQUEST_NIF)
2018-09-29 10:47:30.299 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0
2018-09-29 10:47:30.300 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: SECURITY not supported
2018-09-29 10:47:30.302 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 36: Received COMMAND_CLASS_CENTRAL_SCENE V0 CENTRAL_SCENE_NOTIFICATION
2018-09-29 10:47:30.303 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 36: Received scene 1 at key 0 [Single Press]
2018-09-29 10:47:30.305 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-29 10:47:30.307 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CENTRAL_SCENE, value = 1.0
2018-09-29 10:47:30.309 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Commands processed 1.
2018-09-29 10:47:30.311 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d24872.
2018-09-29 10:47:30.313 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 10:47:30.314 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 10:47:30.316 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-09-29 10:47:30.318 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
None of this looks like the device is waking up though - what button are you pressing?
