Now firmware 1.19 is available!
Get it at http://aeotec.com/small-z-wave-remote-c ... mware.html
and update your minimote.
I've found that minimote with this firmware passes interview successfully.
However the page itself lacks any config, so you need to do all the staff yourself.
There were a file in the start of this topic with config, but now it is gone!
However you can use the engineering spec (https://www.domotiga.nl/attachments/dow ... 20Spec.pdf
and the example config from another ha engine as the guide: https://www.domotiga.nl/attachments/dow ... nimote.xml
The main principle: each minimote button can work in different modes. The 'normal' (default) mode is described in the manual, nothing interesting for us
Also there are modes for 'include', 'remove', 'associate' and 'learn'. They are by default already assigned to the low 4 buttons (and you can just note that you can reassign these actions/modes to other buttons. For me sounds not so useful, expecially taking in mind thad default buttons for these actions are marked, and so, works well enough).
Most interest mode is 'scene'. This mode can't be assigned to lowest 2 buttons (so, you have only 6 buttons totally). But for each of these 6 there are 2 scenes available - 'short' press (tap) and 'long' press (hold about a second, untill it became blinking, then release).
You can use congigurations 241 to 248 to set the button's behavior (for 'scene' mode set them to 1, for 'default' - to 0. 2,3,4,5 are for include, remove, associate and learn).
Also somebody reported that it is necessary to set 250-th param to 0. I've not found so in the docs, and my minimote works well without a command. However - to let you know.
Each scene may contain up to 20 commands. They are numbered as configuration parameters. 0-19 affect button 1 tap, 20-39 - button 1 hold, 40-59 - button 2 tap, 60-79 - button 2 hold, and etc up to 220-239 for button 6 hold.
By default scenes send 'basic switch' commands. According to techs, you need to put nodeid and basic value into param. How to do that, if you have to enter only 1 number in expert UI? Well, just pack node (MSB) and value into big number and send it!
For example, if I want button 1 tap to switch light on node 3, I have to set in 'expert commands' this configuration value for my minimote
parameter : 1 (actually - any of 0..19)
Value: 1023 (that is: 3-th node *256 + 'on' value, which is 255)
size: 2 byte
And if I want same button long press to switch it off, I have to set:
Value: 768 (which is 3*256+0)
Size: 2 byte
Another example: I want tap on 2-nd button to set dimmer on node 32 to 50%:
value: 8242 (which is 32*256+50).
Don't forget to 'wake up' your minimote, in ordet to actually apply these values! (hold 'learn' for 3 seconds untill it blinking).
So, now you can assign any switches to minimote. However, what about other commands than simple 'basicset'?
Well, it is possible! You need to set same parameters (0..239), but not in 'configuration', but in 'assotiation command configuration'.
This command is not available in expert ui (it was available in z-wave cloud, but now it is gone).
However you can form and send the command manually. That may be done by executing and URL from your browser, like
The bytes after 'SendData' are first, the nodeid of minimote (in line above that is 4). And then - the blob.
First two bytes (0x9b, 1) mandatory (that is command class, and then command 'set').
next (61) - is the param to save. May be from 0 to 239. Note, that params saved by 'configuration' command share the same memory as command saved by 'association command configuration'. So, if you already have some setting, say, in parameter 20 - you have to chose either other number for same button (21..39), or the setting will be overwritten.
Next byte (3) is the node to which the saved command will be sent. In this case - node 3.
Then (7) - is just the len of the following blob (i.e., 7 more bytes after this '7' value).
And finally blob of the command - 0x60,13,1,2,0x25,1,0. Techs says that it is limited to 8 bytes max. I'd not checked it!
In this case the command is taken directly from the 'inspect queue' window, it appeared when I'd switched off the light on the second channel of fibaro double switch.
(The bytes in queue were:
3 7 60 d 1 2 25 1 ff 25 - when switched on,
3 7 60 d 1 2 25 1 0 25 - when switched off. Just guess the ascribed blob from here
Another example: let set short press on first button to send 'switch to scene 11' command to the controller!
The blob for it will be 4 bytes (0x2B, 1, 11, 0). (above in the thread PoltoS noted to use 3 bytes, but I've found that it doesn't work. However 4 bytes works ok.
The command will be sent to the controller (1), size is 4 bytes. Let us save it into 0 param (first for tap of 1-st button). My minimote lives on 5-th node. So, I have to do:
Well, why don't also assign the scenes to all the rest of the buttons? And to long pressings also?
1long - http://razberrypi/JS/Run/zway.SendData(5
2tap - http://razberrypi/JS/Run/zway.SendData(5
3tap - http://razberrypi/JS/Run/zway.SendData(5
4tap - http://razberrypi/JS/Run/zway.SendData(5
4long - http://razberrypi/JS/Run/zway.SendData(5
5tap - http://razberrypi/JS/Run/zway.SendData(5
5long - http://razberrypi/JS/Run/zway.SendData(5
6tap - http://razberrypi/JS/Run/zway.SendData(5
6long - http://razberrypi/JS/Run/zway.SendData(5
Finally wake up the minimote to apply all of this. That's all!