HowTo: Aeon Labs MiniMote fully functional Scene Controller in UI5!

ionizer · August 6, 2015, 6:00pm

Ok, so I did this:

Upgraded firmware on remote
went to UI5 in Vera Lite and added handheld remote battery
went to vera lite device with remote and hit “JOIN” button (my bottom panel only has +/- Device, a blank button an a Join wifi looking button)
When i hit join, the remote blinked blue and the blinking orange button on the veralite went off. nothing seemed to be happening other than the remote kept blinking blue. thinking nothing was going on after 15 seconds, i hit join again.
After a very short time after that, the remote blinked orange and then went off.
The vera lite remained with the 2nd light not being on.

I went back to reload the UI5 GUI and i dont see anything added.

should i try again? did i do something wrong?

tec · October 6, 2015, 1:49am

With UI7 (1.7.690), It appears to have gotten simpler. I paired the the MiniMote per the instructions. I did need to refresh the Vera page after waiting a few minutes to get the MiniMote to show up. The steps regarding scene numbers were confusing and now appear to be unnecessary. I was able to create a scene with MiniMote as the trigger. Then ‘Devices->MiniMote->Select scenes for devices buttons’. I was given 8 choices, a tap and long press for each numbered button and the associated scene. Button 1 worked for both tap and long press.

I finally feel this z-wave stuff is starting to live up to its promise.

bratan · October 15, 2015, 10:34pm

I just got my second minimote and I think something is wrong with it…
I updated firmware to 1.19
It won’t reset when I hold blank and join buttons. When I hold them, blue light blinks once, then red one is blinking slowly…forever!
I tried adding it to my Vera Light per instructions, but it doesn’t see it… Is it defective?
There’s a tiny hole under Join button. Could it be hard reset switch? It can also be light sensor, in that case I don’t want to poke it with needle

EDIT: Figured it out. Looks like “join” button wasn’t making good contact. Instead of pressing both buttons simultaneously, I held “join” first and then “blank” and it worked. After reset it paired with Vera.

battars · November 1, 2015, 5:47am

Is there a way to keep the minimote in secondary mode, so that you can use its native dimming capabilities, and link one of the buttons to a ZRTSI? The problem I’m having on my ZRTSI II is that once a zwave node in it is linked to Vera, that particular node is missing from the list of nodes you can press to include.

bsteimel · January 6, 2016, 7:16pm

Has anyone got the MiniMote to report battery percentage? I just had a remote go out and realized that I don’t see it on the screen. It would be really nice.

akbooer · January 6, 2016, 9:15pm

No. It’s never worked for me. On the plus side, however, they do hold a charge for a few months at a time, I find.

NickTheGreat · January 7, 2016, 7:03pm

It would be nice to know in advance. You’re right though, I only have to charge mine a few times a year.

shallowearth · January 7, 2016, 7:38pm

Yes, I just set my polling to 0 on these devices. Since the Battery reporting doesn’t work, and they move arround in the mesh, seems no reason to have polling turned on, further conserving battery life.

kyb2012 · January 18, 2016, 12:04am

This is the best thread to get the minimote working. Didn’t realize that I had to use low power inclusion and hold the minimote close to vera during inclusion.
Everything worked.
Thank you, thank you, thank you!!!

zant · April 10, 2016, 9:18am

[quote=“oTi@, post:48, topic:169756”]Played with the Minimote (MM) a bit over the weekend to look into options related to controlling dimmers.

By default the MM acts as a scene controller, triggering 4x2 scenes in Vera, losing the ability to change the level of a dimmer from the MM, as previously discussed. There are some workarounds.

[size=12pt]Experimental / Beta[/size]
[size=8pt]Given this uses poorly or un-documented low-level Z-Wave commands and features, and has some delays that may be device dependent, we’ll need to see how well the stuff below works for folks. It was tested with a Leviton and a GE plug-in dimmer.[/size]

[size=11pt]Method A - Make it a regular secondary controller[/size]
Put the following in the Luup sandbox ([tt]Apps[/tt] > [tt]Develop Apps[/tt] > [tt]Test Luup code (Lua)[/tt]):

luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='<nodeID>',Data='x70 4 250 1 0'},1)

Then, while holding the top left button on the MM, click the [tt]Go[/tt] button on the Dashboard.
[size=8pt](The SendData command does not get put on the Wake-Up queue; hence the clunky method to keep the MM awake by holding a button and then sending the command.)
[/size]
This now controls dimmers the same way as when the MM is primary.

Notes:
[size=8pt]Having the MM control the lights directly is nice, but because Vera isn’t in the loop, the status of the dimmer is not updated in Vera until the next poll. So make sure to enable polling for any devices controlled by the MM that support instant status updates (e.g. Leviton), as by default Vera does not poll these devices. Also, for faster updates, you could write a scene on a periodic timer that polls all devices controlled by the MM, and see how it performs.

This method is easy to enable and may suffice if only controlling some lighting devices. If you also want the scene capability in Vera to do more complex things (with some of the buttons), then consider Method B.[/size]

To get back to the scene mode Vera normally configures the MM in (and required for Method B):

luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='<nodeID>',Data='x70 4 250 1 1'},1)

[size=11pt]Method B - Write scenes to control dimming[/size]
Write 2 scenes per button. One for activated and one for de-activated. Besides the appropriate trigger, put the following under the scene’s [tt]Luup[/tt] tab:

[tt]A scene is activated[/tt]:

[code]local DIMMER_DEVID =
local DIMMER_NODEID =
local DIMMER_ON_VALUE =
local MINIMOTE_BUTTON =
local MINIMOTE_DEVID =
local DIMMING_TIMEOUT = 4
local POLL_HOLDOFF = 3

local SC1_SID = ‘urn:micasaverde-com:serviceId:SceneController1’
local ZN1_SID = ‘urn:micasaverde-com:serviceId:ZWaveNetwork1’
local HD1_SID = ‘urn:micasaverde-com:serviceId:HaDevice1’
local D1_SID = ‘urn:upnp-org:serviceId:Dimming1’

local lastSceneTime = luup.variable_get(SC1_SID,‘LastSceneTime’, MINIMOTE_DEVID) or os.time()
local lastSceneDeactivated = luup.variable_get(SC1_SID,‘sl_SceneDeactivated’, MINIMOTE_DEVID) or 0
local loadLevelStatus = luup.variable_get(D1_SID,‘LoadLevelStatus’, DIMMER_DEVID)

lastSceneTime = tonumber(lastSceneTime)
lastSceneDeactivated = tonumber(lastSceneDeactivated)
loadLevelStatus = tonumber(loadLevelStatus)

if ((os.difftime(os.time(),lastSceneTime) < DIMMING_TIMEOUT) and (lastSceneDeactivated == MINIMOTE_BUTTON)) then
luup.call_action(ZN1_SID,‘SendData’,{Node=‘’…DIMMER_NODEID…‘’,Data=‘x26 5’},1)
luup.call_action(HD1_SID,‘Poll’,{},DIMMER_DEVID)
return true
else
if (loadLevelStatus > 0) then
luup.call_action(ZN1_SID,‘SendData’,{Node=‘’…DIMMER_NODEID…‘’,Data=‘x20 1 0’},1)
else
luup.call_action(ZN1_SID,‘SendData’,{Node=‘’…DIMMER_NODEID…‘’,Data=‘x20 1 ‘…DIMMER_ON_VALUE…’’},1)
end
luup.sleep(1000*POLL_HOLDOFF)
luup.call_action(HD1_SID,‘Poll’,{},DIMMER_DEVID)
return true
end[/code]
[size=8pt]Replace the following in the first 5 lines:
with the Device# from the dimmer’s [tt]Settings[/tt] tab.
with the ID from the dimmer’s [tt]Settings[/tt] tab.
with the level the dimmer should be set to (1-100, 255=previous).
with the number of the MM’s button (1-4).
with the Device# from the MM’s [tt]Settings[/tt] tab.[/size]

[tt]A scene is de-activated[/tt]:

[code]local DIMMER_DEVID =
local DIMMER_NODEID =
local DIM_THRESHOLD = 50

local ZN1_SID = ‘urn:micasaverde-com:serviceId:ZWaveNetwork1’
local D1_SID = ‘urn:upnp-org:serviceId:Dimming1’

local loadLevelTarget = luup.variable_get(D1_SID,‘LoadLevelTarget’,DIMMER_DEVID)

loadLevelTarget = tonumber(loadLevelTarget)

if (loadLevelTarget >= DIM_THRESHOLD) then
luup.call_action(ZN1_SID,‘SendData’,{Node=‘’…DIMMER_NODEID…‘’,Data=‘x26 4 x78 99’},1)
luup.variable_set(D1_SID,‘LoadLevelTarget’,‘1’,DIMMER_DEVID)
else
luup.call_action(ZN1_SID,‘SendData’,{Node=‘’…DIMMER_NODEID…‘’,Data=‘x26 4 x38 1’},1)
luup.variable_set(D1_SID,‘LoadLevelTarget’,‘100’,DIMMER_DEVID)
end

return true[/code]
[size=8pt]Replace the following in the first 2 lines:
with the Device# from the dimmer’s [tt]Settings[/tt] tab.
with the ID from the dimmer’s [tt]Settings[/tt] tab.[/size]

A short press of the button should now toggle the dimmer on or off. When turned on, it will be set at the provisioned level (DIMMER_ON_VALUE); you can use 255 to ‘go-to-previous’.

A long press of the button will start ramping up or down. The press only kicks it off, letting go of the button doesn’t stop it; to stop the ramping do a short press.

A poll is done after all state changes, so the status in Vera should update.

Notes:
[size=8pt]Because the short press double as on/off and stop action, you can not go to the off state immediately after changing the level; there is a time-out, currently set at 4 seconds.

Also, the poll after on/off is done with a delay, currently set at 3 seconds, to give the dimmer time to ramp up/down to the final state; otherwise the wrong value will be polled.

So when testing this, keep the slightly altered button behavior and the time-outs/delays in mind.[/size]

[size=11pt]Method C - Program buttons to send any command[/size]
The MM allows the buttons to emit any sequence of bytes to any group of nodes, making it a very customizable device. This could be leveraged, however there appear to be only 2 events per button, so combining on/off and dimming with just 1 button may not be possibe. Given that, plus the complexity to get it set up, as well as the partial implementation of some of the command classes, making it a one-time-only/first-time-right kind of exercise, I decided to consider this method out-of-scope.[/quote]

Hallo oTi@,

I’am new and don’t have enough knowledge to programm a scene as you mentioned above.
I have a VeraPlus a Minimite and a Fibaro FDG212 Dimmer. I want to dim the light with the Minimote.
The mentioned Metode B is the functionality a want to use.
I copied this in the scene luup tab as mentioned (and changed the id’s etc)
I use button 4 of the MM so i made one scene for activation and a other scene for de-activation.
Then in the device tab of my VeraPlus (UI7) I pick my Minimote and use for buton 4 short press the activation scene luup and buton 4 long press the de-activation scene luup.

All this did not result in a working dimming functionally.
Can you please help me to make this work for me.
Thanks in advance…

jjwatmyself · June 5, 2016, 2:59pm

I’m using a Vera 2 on UI5 version 1.5.673 and Minimote Firmware 1.19 (US)

Credits to
jasondag [url=http://forum.micasaverde.com/index.php/topic,29493.msg241697.html#msg241697]http://forum.micasaverde.com/index.php/topic,29493.msg241697.html#msg241697[/url]
cpmilaz [url=http://forum.micasaverde.com/index.php/topic,29493.msg218577.html#msg218577]http://forum.micasaverde.com/index.php/topic,29493.msg218577.html#msg218577[/url]
pmnb [url=http://forum.micasaverde.com/index.php/topic,29493.msg278848.html#msg278848]http://forum.micasaverde.com/index.php/topic,29493.msg278848.html#msg278848[/url]

To summarize “LastSceneID” is the only value being set correctly and modification are required to have use of all buttons. You’ll need a new .json and .xml file.

CAUTION: Do not overlay existing files. The process below results in new .json and .xml files on your Vera 2. The steps for UI7 do not require the use of the .xml file. The .json files for UI5 and UI7 ARE NOT THE SAME, DO NOT MIX AND MATCH!!

Step by step:

From UI5 Goto APPS
Click Develop apps
Click Luup Files
Download “D_SceneController1.json”, and save as “D_SceneControllerAeonMinimote.json”
On your PC, edit and change “sl_SceneActivated”, to “LastSceneID”
Download “D_SceneController1.xml”, and save as “D_SceneControllerAeonMinimote.xml”
On your PC, edit and change “D_SceneController1.json”, to “D_SceneControllerAeonMinimote.json” (fixed typo Jan 8 2017)
On UI5 upload files and check/tick reload luup engine.
Goto the device page and choose advanced options
Set ‘device_file’ to “D_SceneControllerAeonMinimote.xml”
Change NumButtons from 4 to 8 (you will now ignore the Deactivate buttons 1-8 after changing this)
Change PollSettings to 0 (because the Minimote never wakes up)
Go to Device Options, add configuration settings, Variable=250 Data size=1 byte Dec, Desired Value=1

To configure scenes:

On UI5 goto the device page and choose Scenes
Activate Scenes Button #1,3,5,7 are Short Press for Minimote buttons 1,2,3,4
Activate Scenes Button #2,4,6,8 are Long Press for Minimote buttons 1,2,3,4
(Ignore all Deactivate Scenes 1-8)

Here are a scene that is useful for thermostats that support heat and cool to set temp based on what mode the thermostat is currently set to. In my experience, during the summer, houses run warmer and in the winter houses run cooler. Having a single button that when pressed will set the comfortable temp is nice. I have this scene set for a short press and ESM set to a long press on same button.

local DevID_Therm = 11
local EnvStatus = luup.variable_get("urn:upnp-org:serviceId:HVAC_UserOperatingMode1", "ModeStatus", DevID_Therm)

luup.call_action("urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
                   "SetEnergyModeTarget", {NewModeTarget = "Normal"},DevID_Therm)

if (EnvStatus == "CoolOn") then
   luup.call_action("urn:upnp-org:serviceId:TemperatureSetpoint1_Cool",
                   "SetCurrentSetpoint", {NewCurrentSetpoint = "74"},DevID_Therm)
elseif (EnvStatus == "HeatOn") then
   luup.call_action("urn:upnp-org:serviceId:TemperatureSetpoint1_Heat",
                   "SetCurrentSetpoint", {NewCurrentSetpoint = "68"},DevID_Therm)
end


# Scene 2:
local DevID_Therm = 11

luup.call_action("urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
                   "SetEnergyModeTarget", {NewModeTarget = "EnergySavingsMode"},DevID_Therm)

Enjoy!!

Gogzy · December 28, 2016, 2:13pm

Hello all,

I would like to know is it possible to have the minimote or any other remote to use as a remote from a car?
I have the Vera Plus and UI7 latest firmware. I allways use the phone to change the mode (home/away), but that is not so practical. So can i use minimote to do that?
I dont know what will happen when the minimote iout of range is and then again in range? Does it work automaticaly? Can i just switch mode when i am in range of the Vera? Or do i need to include it every time i get in range again?

Thanks a lot

shallowearth · December 28, 2016, 3:37pm

If you set polling of the minimote to 0, you can take it out of range and bring it back in range, and you should be fine

jjwatmyself · January 8, 2017, 6:04pm

[quote=“Gogzy, post:152, topic:169756”]Hello all,

I would like to know is it possible to have the minimote or any other remote to use as a remote from a car?
I have the Vera Plus and UI7 latest firmware. I allways use the phone to change the mode (home/away), but that is not so practical. So can i use minimote to do that?
I dont know what will happen when the minimote iout of range is and then again in range? Does it work automaticaly? Can i just switch mode when i am in range of the Vera? Or do i need to include it every time i get in range again?

Thanks a lot[/quote]

If your phone is on Wifi and you have AnyMote Smart Remote installed on your phone, you can program HTTP GET Buttons and activate any Vera scene. I used the Notifications feature on this app in order to display buttons permanently on my Android pull down and lock screen. Turn on screen, press button. Done. This gives you a very convenient scene controller on the Android lock screen with up to 15 buttons. Personally I use the Anymote Notifications feature for IR and have some Vera scenes on the remotes within the app. But I like your idea about doing things from the car with easy to access buttons. That would save me from opening Home Buddy!

Here is the HTTP GET URL. Just change the scene umber on the end.

http://IP:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=15

dannieboiz · May 31, 2017, 4:37am