The remote is not recognized by OH: “Unknown Device”. This is how it looks in PaperUI:
Z-Wave Node 028 (0330:0300:B302:1.26)
If I understand it correctly, the “B302”-Part is the difference.
These are the properties:
zwave_beaming
true
zwave_class_basic
BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic
GENERIC_TYPE_WALL_CONTROLLER
zwave_class_specific
SPECIFIC_TYPE_BASIC_WALL_CONTROLLER
zwave_deviceid
45826
zwave_devicetype
768
zwave_frequent
false
zwave_listening
false
zwave_manufacturer
816
zwave_neighbours
zwave_nodeid
28
zwave_plus_devicetype
NODE_TYPE_ZWAVEPLUS_NODE
zwave_plus_roletype
ROLE_TYPE_SLAVE_PORTABLE
zwave_routing
true
zwave_secure
false
zwave_version
1.26
Side note:
I tried to update OH to a snaphot-release, to see if that changes recognization:
sudo runtime/bin/update 2.5.4-SNAPSHOT
#########################################
openHAB 2.x.x update script
#########################################
Making Temporary Directory
Downloading openHAB 2.5.4-SNAPSHOT…
curl: (22) The requested URL returned error: 404 Not Found
Download failed, version 2.5.4-SNAPSHOT does not exist.
And if i just use “update” it announces a version far beyond the current one:
sudo runtime/bin/update
#########################################
openHAB 2.x.x update script
#########################################
Making Temporary Directory
Downloading openHAB 2.6.4…
curl: (22) The requested URL returned error: 404 Not Found
Download failed, version 2.6.4 does not exist.
Thank you very much @chris Works just fine with 2.5.5, build 107.
For others maybe interesting, how this remote works, and what / how much commands it can send:
The remote has just two channels, one for it’s battery state, and one for the scenes. Depending on which of the 12 buttons is pressed it sends a “scene number” value from 1.0 - 12.0
• If a button is held, the value becomes 2 after the decimal, like 12.2
There is no dimm-command, and it does not send continuously it’s held state (like it is with my FS20 remotes), so a dimm logic must be rule-scripted by hand.
According to the manual it is possible to send dim commands, if used with Association groups (five goups, each can have up to five devices), but I didn’t try, as this makes the remote to inflexible (for me).
• If the button is released, it sends the value 1 after the decimal, like 12.1
• There’s no double-click functionality, but it should be doable via rule.
My test rule (and my very first OH rule, no complaints please ):
rule "Remote GA"
when
Item zwave_device_a0cc5df2_node28_scene_number received update // funzt, aber bei gedrücktem Button feuert nur ein Event
then
logWarn("Rules", "Node 28 changed: " + zwave_device_a0cc5df2_node28_scene_number.state)
switch zwave_device_a0cc5df2_node28_scene_number.state {
case 12 : { logWarn("Rules", "Node 28: button clicked short")
zwave_device_a0cc5df2_node22_switch_binary.sendCommand(ON) }
case 12.2 : logWarn("Rules", "Node 28: button held")
case 12.1 : { logWarn("Rules", "Node 28: button released") // fires if 12.2 occurred before, not after a normal click.
zwave_device_a0cc5df2_node22_switch_binary.sendCommand(OFF) }
}
end
Works just fine with 2.5.5, build 107.
):
