[SOLVED] Aeon Labs Minimote help

All,

I have my minimote working just fine (I’m using the 1.8 zwave binding, but it worked with the 1.7.1 as well).

You need to know that you will NEVER get it to show any parameters, or create a node.xml file in habmin - but as it’s a send only device - that doesn’t matter.

When you press any of the action buttons, an event will be generated in the Zwave binding, that you can trap in openhab and use. The question is - what are you trying to do?

My advice is, GIVE UP on trying to get the minimote to show parameters or create a node.xml file or even register in habim as anything other than nodeX. You don’t need this for anything. Focus on capturing the events.

The minimote has two modes of operation, dimmer mode (as shipped) and scene mode. I have mine in scene mode (so I get eight scenes that I can switch on and off). I put the minimote in scene mode using 3rd party tools (openzwave I think - google it) - you can’t do this in openhab, habmin, habmin2 or anything, you need a 3rd party tool to do it, and it can be difficult. I think I had to edit the openzwave database as they had the parameters for dimmer or scene mode reversed (ie it shows as scene mode by default, but it isn’t).

So you can use the minimote as a dimmer as is. If you have the items file configured correctly. If you can get it into scene mode (by hook or crook), then you can configure the items file as below, to trigger scene events:

Switch Minimote1 "Minimote Scene 1 [%d]" (Minimote) {zwave="17:command=scene_activation, scene=1, state=1"}

and so on up to eight.

Then in rules I have

rule "Minimote 1 received update ON"
when
    Item Minimote1 received update ON
then
    //do whatever
end

That’s how I use my minimote, (I have eight rules, eight items) nothing registered in habmin at all (beyond “Node 17”).

I’m not sure how you would use it in dimmer mode, but it has to be similar. look at the zwave binding log and see what events are generated when you press an action button (multilevel switch? basic?) then trap that event in the items file, and use a rule to trigger an action. It doesn’t matter about all the error messages (“not completed initialization”, “device is asleep” etc. etc)., if you can see events triggered when pressing a button, you can capture them.

best of luck!

2 Likes

I have my minimote in scene mode I used open zwave control panel to do that, but I still cannot get the rules to fire.

Here is what I have in my item file.
Switch Rem_A_b1m "Remote A Button 1 [%d]" {zwave="3:command=scene_activation,scene=1,state=1"}

Here is my rule.
rule "zwave test button 1"
when
Item Rem_A_b1m received update ON
then
sendCommand(Toggle_3,ON)
logDebug(“RULES”, “zwave button”)
end

and when I push the button here is what I get in the log but the Toggle_3 is never switched to ON.

2016-02-07 18:55:27.322 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1481]- Receive Message = 01 0A 00 04 00 03 04 2B 01 01 00 DD 
2016-02-07 18:55:27.324 TRACE o.o.b.z.i.p.SerialMessage[:136]- NODE 255: Creating new SerialMessage from buffer = 01 0A 00 04 00 03 04 2B 01 01 00 DD 
2016-02-07 18:55:27.324 TRACE o.o.b.z.i.p.SerialMessage[:179]- Calculated checksum = 0xDD
2016-02-07 18:55:27.324 TRACE o.o.b.z.i.p.SerialMessage[:141]- NODE 255: Checksum matched
2016-02-07 18:55:27.326 TRACE o.o.b.z.i.p.SerialMessage[:153]- NODE 255: Message payload = 00 03 04 2B 01 01 00 
2016-02-07 18:55:27.327 TRACE o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1390]- Message is valid, sending ACK
2016-02-07 18:55:27.331 TRACE o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1375]- Response SENT
2016-02-07 18:55:27.332 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1405]- Receive queue ADD: Length=1
2016-02-07 18:55:27.332 DEBUG o.o.b.z.i.p.ZWaveController[:1163]- Receive queue TAKE: Length=0
2016-02-07 18:55:27.335 TRACE o.o.b.z.i.p.SerialMessage[:179]- Calculated checksum = 0xDD
2016-02-07 18:55:27.336 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 0A 00 04 00 03 04 2B 01 01 00 DD 
2016-02-07 18:55:27.337 DEBUG o.o.b.z.i.p.ZWaveController[:1164]- Process Message = 01 0A 00 04 00 03 04 2B 01 01 00 DD 
2016-02-07 18:55:27.337 DEBUG o.o.b.z.i.p.ZWaveController[:192]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 03 04 2B 01 01 00 
2016-02-07 18:55:27.338 TRACE o.o.b.z.i.p.ZWaveController[:212]- Incoming Message type = REQUEST
2016-02-07 18:55:27.338 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:30]- Handle Message Application Command Request
2016-02-07 18:55:27.339 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:38]- NODE 3: Application Command Request (ALIVE:WAIT)
2016-02-07 18:55:27.339 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:56]- NODE 3: Incoming command class SCENE_ACTIVATION
2016-02-07 18:55:27.340 TRACE o.o.b.z.i.p.s.ApplicationCommandMessageClass[:79]- NODE 3: Found Command Class SCENE_ACTIVATION, passing to handleApplicationCommandRequest
2016-02-07 18:55:27.340 DEBUG o.o.b.z.i.p.c.ZWaveBasicCommandClass[:62]- Received Scene Activation for Node ID = 3
2016-02-07 18:55:27.340 DEBUG o.o.b.z.i.p.c.ZWaveBasicCommandClass[:66]- Scene Activation Set
2016-02-07 18:55:27.341 DEBUG o.o.b.z.i.p.c.ZWaveBasicCommandClass[:93]- Scene activation node from node 3: Scene 1, Time 0
2016-02-07 18:55:27.341 DEBUG o.o.b.z.i.p.ZWaveController[:635]- Notifying event listeners: ZWaveCommandClassValueEvent
2016-02-07 18:55:27.341 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2016-02-07 18:55:27.342 DEBUG o.o.b.z.i.ZWaveActiveBinding[:450]- NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 1
2016-02-07 18:55:27.342 TRACE o.o.b.z.i.c.ZWaveConverterHandler[:346]- Getting converter for item = Rem_A_b1m, command class = SCENE_ACTIVATION, item command class = scene_activation
2016-02-07 18:55:27.343 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:85]- Transaction not completed: node address inconsistent.

Any help you may be able to provide would be great.

Does anyone no if the ‘Transaction not completed: node address inconsistent’ is normal?

Thanks,
Dan

Dan,

Yes the ‘Transaction not completed: node address inconsistent’ is a normal message, you can ignore it.

This is what I get in the zwave log when I press button 1:

2016-02-08 10:38:27.169 [DEBUG] [ApplicationCommandMessageClass:38  ]- NODE 17: Application Command Request (ALIVE:PING)
2016-02-08 10:38:27.169 [DEBUG] [ApplicationCommandMessageClass:56  ]- NODE 17: Incoming command class SCENE_ACTIVATION
2016-02-08 10:38:27.169 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ]- NODE 17: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 1

if I press button 4 (short press)

2016-02-08 10:41:17.997 [DEBUG] [ApplicationCommandMessageClass:38  ]- NODE 17: Application Command Request (ALIVE:PING)
2016-02-08 10:41:17.997 [DEBUG] [ApplicationCommandMessageClass:56  ]- NODE 17: Incoming command class SCENE_ACTIVATION
2016-02-08 10:41:17.997 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ]- NODE 17: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 7

this is filtered on "NODE 17"
unfiltered it looks like:

2016-02-08 10:44:11.968 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 11 04 2B 01 01 00
2016-02-08 10:44:11.968 [DEBUG] [ApplicationCommandMessageClass:38  ]- NODE 17: Application Command Request (ALIVE:PING)
2016-02-08 10:44:11.968 [DEBUG] [ApplicationCommandMessageClass:56  ]- NODE 17: Incoming command class SCENE_ACTIVATION
2016-02-08 10:44:11.968 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:62  ]- Received Scene Activation for Node ID = 17
2016-02-08 10:44:11.968 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:66  ]- Scene Activation Set
2016-02-08 10:44:11.968 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:93  ]- Scene activation node from node 17: Scene 1, Time 0
2016-02-08 10:44:11.968 [DEBUG] [b.z.i.protocol.ZWaveController:635 ]- Notifying event listeners: ZWaveCommandClassValueEvent
2016-02-08 10:44:11.968 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ]- ZwaveIncomingEvent
2016-02-08 10:44:11.968 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ]- NODE 17: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 1
2016-02-08 10:44:11.968 [DEBUG] [ApplicationCommandMessageClass:85  ]- Transaction not completed: node address inconsistent.

(button 1 again)

in the openhab log I get:

10:46:13.172 [DEBUG] [m.r.internal.engine.RuleEngine:305  ] - Executing rule 'Minimote Scene 1'
10:46:13.173 [INFO ] [.openhab.model.script.Minimote:53   ] - Minimote Scene 1 Activation Received
10:46:13.173 [INFO ] [.openhab.model.script.Minimote:53   ] - ALL LEDs ON - turning them OFF

(button 1 again) - this turns my outside LED lights on and off (toggle).

This is my items entries:

/* Minimote configuration */
Group Minimote "Minimote Remote Control" <remote> (All)

Switch  Minimote1 "Minimote Scene 1 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=1,state=1"}
Switch  Minimote2 "Minimote Scene 2 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=2,state=1"}
Switch  Minimote3 "Minimote Scene 3 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=3,state=1"}
Switch  Minimote4 "Minimote Scene 4 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=4,state=1"}
Switch  Minimote5 "Minimote Scene 5 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=5,state=1"}
Switch  Minimote6 "Minimote Scene 6 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=6,state=1"}
Switch  Minimote7 "Minimote Scene 7 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=7,state=1"}
Switch  Minimote8 "Minimote Scene 8 [%d]" (Minimote) {zwave="17:command=scene_activation,scene=8,state=1"}

and this is my rule for Minimote1:

rule "Minimote Scene 1"
when
	Item Minimote1 received update ON
then
    logInfo("Minimote", "Minimote Scene 1 Activation Received")
    //This now (button 1) turns ALL LEDs on and off - short press on - short press OFF
    
    if(RGBSAll_pi.state == ON) {
      logInfo("Minimote", "ALL LEDs ON - turning them OFF")
      sendCommand(RGBSAll_pi,OFF)
      }
    else {
      logInfo("Minimote", "All LEDs OFF - turning them ON")
      sendCommand(RGBSAll_pi,ON)
    }
end

You look to have everything correct, you must be close …

This is using openhab zwave binding 1.8 (but as I say it has worked with previous bindings - 1.71).

What does your openhab log say? it may be as simple as a bug in another rule preventing your rule from executing properly. It looks like you have a separate file set up for rule debugging, maybe just pare it back to a basic logInfo message, see if you can see that in the regular openhab.log file.

Regards,
Nick

1 Like

@DMize

Are you able to launch this particular rule via the webinterface? Might be something wrong with the rule itself. The log says “Scene Activation set, scene activated from node 3”. That sounds about right.

I’m starting to wonder whether my remote works properly. I haven’t seen any feedback in the log files when I press any of the 4 buttons on the Minimote. After a bit of Googling I managed to get OpenZwave Control Panel up and running. However, I can’t find any setting that let’s me change the remote from normal to scene mode. Also, the log file doesn’t show any info coming from the remote (when a button is pressed). Can anyone compare my settings to theirs? Would be great…

@Nicholas_Waterton, I cannot thank you enough. I finally have my minimote operating correctly. I’m not sure exactly what the problem was but I used your exact item layout and your rule then modified to my needs. I also removed all other rules and turned on debugging since I wasn’t seeing much about the rule processing in the openhab log. It is now working, I’ve turned back on all the other rules and I’ve been testing for over an hour with no issues.

Thank you so much for your last post! It’s worth a beer or two if you’d like to collect.

@Qris, in your second screenshot there should be another option. Do you know what firmware your minimote is on? It needs to be on one of the latest in order to see this option and the most current is 1.19, which is what I’m using.

Once you update the firmware start the ozwcp again and click on ‘Configuration’ and you should see something to the effect of a mode. There you need to select ‘Scene Mode’. It will seem like it doesn’t do anything but it does. If you refresh it will go back to the default because the system doesn’t actually get the setting from the minimote.

Here’s how you can tell which mode the minimote is in using the minimote.
When pressing and holding any scene button:

Red + Blue LED light up and disappear (red LED may blink a little bit before no activity) = Scene Mode (Parameter 250 [1 byte] = 1)

Red + Blue LED light up, and then starts blinking the Blue LED rapidly = Group Mode (Parameter 250 [1 byte] = 0)

Once you get it in scene mode you should be good to go and if you have any trouble check post 23 above.

Let me know how you progress and I’ll try to help as much as I can.

Not sure what the procedure is for resolved topics here but I’m wondering if maybe you or @Nicholas_Waterton could help me out with my issue. I have a minimote and Gen5 stick, and I’ve tried to follow what you guys have said worked, but I might be stuck somewhere above where you started this thread. I am able to get the minimote to show up in habmin as a node and with parameter 250 showing up, but whenever I press a scene button on it, nothing seems to happen in the logs. The red and blue light flash once on the remote at the same time, and if I hold one, the red light will turn off and the blue light will flash quickly until I let it go. Is this what is supposed to happen on the remote, or could I possibly have a bad one? Is there a special way to include the minimote besides pressing the button on the z-stick then pressing the learn button on the minimote? Should they show up as neighbors in habmin? because they aren’t for me. These are the only 2 Z-wave devices I have. using openhab 1.8 and minimote firmware 1.19

Edit: just read the response from the remote so I guess my remote is actually in group mode so I’ll probably need to change that first

Having parameter 250 show up in habmin means nothing. You cannot use habmin to configure a minimote.

You have to use openzwave or some other configuration utility (not habmin or habmin2), to set parameter 250 to “scene” mode. After that, it will work. You can’t skip this step. You can’t do it in habmin.

Try openzwave, see if you can configure it there. They don’t come set for scene mode, you have to configure it.

Nick Waterton P.Eng.
National Support Leader - Nuclear Medicine, PET and RP
GE Healthcare

M+1 416 859 8545
F +1 905 248 3089
E nick.waterton@med.ge.commailto:nick.waterton@med.ge.com

2300 Meadowvale Boulevard
Mississauga, ON L5N 5P9 Canada

GE imagination at work

From: Dakiem Ellis [mailto:bot@community.openhab.org]
Sent: February-18-16 12:47 PM
To: Waterton, Nick (GE Healthcare)
Subject: [openHAB] [Add-ons/Bindings] Aeon Labs Minimote help (Resolved)

[https://community.openhab.org/letter_avatar_proxy/v2/letter/d/e274bd/45.png]

dakoellishttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_dakoellis&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=9y4soyaTIEcIHPpROZa-CF6HCcOhWmCSI-AAJvEHu0M&e= Dakiem Ellishttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_dakoellis&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=9y4soyaTIEcIHPpROZa-CF6HCcOhWmCSI-AAJvEHu0M&e=
February 18

Not sure what the procedure is for resolved topics here but I’m wondering if maybe you or @Nicholas_Watertonhttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_nicholas-5Fwaterton&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=Dt_kMLqMssLTFsL28VfmQW61-Su74uhMh_FFkTCbhIQ&e= could help me out with my issue. I have a minimote and Gen5 stick, and I’ve tried to follow what you guys have said worked, but I might be stuck somewhere above where you started this thread. I am able to get the minimote to show up in habmin as a node and with parameter 250 showing up, but whenever I press a scene button on it, nothing seems to happen in the logs. The red and blue light flash once on the remote at the same time, and if I hold one, the red light will turn off and the blue light will flash quickly until I let it go. Is this what is supposed to happen on the remote, or could I possibly have a bad one? Is there a special way to include the minimote besides pressing the button on the z-stick then pressing the learn button on the minimote? Should they show up as neighbors in habmin? because they aren’t for me. These are the only 2 Z-wave devices I have. using openhab 1.8 and minimote firmware 1.19

Visit Topichttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_t_aeon-2Dlabs-2Dminimote-2Dhelp-2Dresolved_5714_27&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=dIs3HpjIuCOrMpyJDFelLde-4vOuCNc0bo-JqokLyIA&e= or reply to this email to respond.

I just had to go through this all again (my Z-Wave controller got wiped – don’t ask).

This is how you get the minimote into scene mode. Default is “Group” mode.

Get hold of openzwave, and open-zwave-control panel. You may have to install and complie from source.

Make sure your minimote is included on your z-wave controller (in my case a Z-Stick Gen 5)

Run ozwcp –p 9900 (or another port).
Open a browser, and point to the ip you are running ozwcp on, port 9900 (ie http://ip:port)

Enter the device name of your zwave controller (eg /dev/ttyACM0), and press “initialize”

Your devices should show up in the list now. Wait until all the properties are filled in, waking up you minimote periodically until it’s configuration shows. This can take a while.

Select “configuration”. You should see the current “mode” as “group”. If you don’t see anything, the configuration download hasn’t finished, and you need to keep waking up your minimote until it does.

When you see the configuration mode show up, select “Scene” and wake your minimote up again.

This is the bit that confuses people, when the mimimote is reconfigured, the “mode” switches back to “group” as if it didn’t do anything. But it did!

Now exit openzwave, go back to openHAB (start-up, wait, wait, wait…), and you should be able to see responses from your minimote in the zwave debug log when you press one of the 4 buttons.

Hope this helps.

Nick Waterton P.Eng.
National Support Leader - Nuclear Medicine, PET and RP
GE Healthcare

M+1 416 859 8545
F +1 905 248 3089
E nick.waterton@med.ge.commailto:nick.waterton@med.ge.com

2300 Meadowvale Boulevard
Mississauga, ON L5N 5P9 Canada

GE imagination at work

From: Dakiem Ellis [mailto:bot@community.openhab.org]
Sent: February-18-16 12:47 PM
To: Waterton, Nick (GE Healthcare)
Subject: [openHAB] [Add-ons/Bindings] Aeon Labs Minimote help (Resolved)

[Image removed by sender.]

dakoellishttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_dakoellis&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=9y4soyaTIEcIHPpROZa-CF6HCcOhWmCSI-AAJvEHu0M&e= Dakiem Ellishttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_dakoellis&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=9y4soyaTIEcIHPpROZa-CF6HCcOhWmCSI-AAJvEHu0M&e=
February 18

Not sure what the procedure is for resolved topics here but I’m wondering if maybe you or @Nicholas_Watertonhttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_users_nicholas-5Fwaterton&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=Dt_kMLqMssLTFsL28VfmQW61-Su74uhMh_FFkTCbhIQ&e= could help me out with my issue. I have a minimote and Gen5 stick, and I’ve tried to follow what you guys have said worked, but I might be stuck somewhere above where you started this thread. I am able to get the minimote to show up in habmin as a node and with parameter 250 showing up, but whenever I press a scene button on it, nothing seems to happen in the logs. The red and blue light flash once on the remote at the same time, and if I hold one, the red light will turn off and the blue light will flash quickly until I let it go. Is this what is supposed to happen on the remote, or could I possibly have a bad one? Is there a special way to include the minimote besides pressing the button on the z-stick then pressing the learn button on the minimote? Should they show up as neighbors in habmin? because they aren’t for me. These are the only 2 Z-wave devices I have. using openhab 1.8 and minimote firmware 1.19

Visit Topichttps://urldefense.proofpoint.com/v2/url?u=https-3A__community.openhab.org_t_aeon-2Dlabs-2Dminimote-2Dhelp-2Dresolved_5714_27&d=CwMCaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=U_-uBTyQDj4ifd00J7nSYtwgRmrVu_2vacy9QbRAMDQ&m=NU-UatEINokpUw6uyRcnEvGrDovE2XKUX815N1g3k48&s=dIs3HpjIuCOrMpyJDFelLde-4vOuCNc0bo-JqokLyIA&e= or reply to this email to respond.

@dakoellis, Nick’s last post pretty much sums it up. I was getting hung up on things that don’t matter.

1 Like

Yeah I’ll go through it later. I guess I thought I was in scene mode for a couple of reasons. First, a post on another site said that the newest firmware will set your minimote in scene mode by default, and that coupled with the post here that had the minimote info except for the 250 param made me think that since I had the 250 param in my list that I was in scene mode.

This is the way that Aeotec told me to check which mode it is in. In neither application will it say that it is in Scene Mode.

Awesome stuff @Nicholas_Waterton That worked perfectly. Thanks for the help I now have a working minimote

Still no go for me, helas. I tried @Nicholas_Waterton his advise using Openzwave to configure my Minimote. The mode settings just don’t show up in my configuration tab. I keep hitting the Learn button to keep the Minimote alive, but no new configurations are loaded into the Control Panel. I can only chose between Button #1 Programmable On or Off.

@DMize I’m using the latest firmware from the Aeon Labs website: EU 1.19.

What oh what could it be :slightly_smiling:

Anything to do with a low battery? I’m guessing no, since I keep getting log readings when I long press the Learn button.

Can you post a screenshot? The configuration is a radiobutton you select (may depend on what version of ozwcp you are using – I have done this with new and old versions). Might shed some light on what you are seeing.

Maybe learn isn’t the right button to wake it up? I can’t remember what I was pressing, but the list of devices should say (asleep) or (awake), unless you get it to wake up (several times) it won’t finish downloading the configuration, and the options don’t appear.

It’s always a problem getting these Aeon labs things to stay awake long enough to download the configuration (I have the same problem with the MS6), you just have to keep pressing until presto! It completes without a time out. Sometimes several rapid presses are better than one long press. I’ve done this so many times now I just go into “keep the Aeon labs thing awake until it downloads” mode, and I can usually get it in a couple of minutes. It may be a timing thing I have just “got the hang of”.

It does take minutes for ozwcp to read everything, depending on how many devices you have, it’s not fast….

Nick Waterton P.Eng.
National Support Leader - Nuclear Medicine, PET and RP
GE Healthcare

M+1 416 859 8545
F +1 905 248 3089
E nick.waterton@med.ge.commailto:nick.waterton@med.ge.com

2300 Meadowvale Boulevard
Mississauga, ON L5N 5P9 Canada

GE imagination at work

Can someone enlighten me as to why this is? Is there a logfile or something available? It would be good to resolve this - if it’s just a case of setting a parameter, then it should work fine in HABmin unless the database is incorrect. If there’s a problem, we should really try and resolve it, and your help would of course be greatly appreciated…

Chris,

The answer is that the minimote never seems to complete initialization when connected to the openHAB zwave binding. I’ve tried using 1.7, 1.8, 1.8.1, git latest etc. You can get through static values, to the point where the configuration values show up in habmin, but it never completes dynamic initialization, and so never serializes to an xml file. No matter how many times you wake it up, it always times out and eventually restarts the initialization process again with too many retries.

Until it completes initialization, and serializes to a file, you can’t change any values. My minimote simply shows up in habmin as “Node 17”. If I wake it up enough times, it will fill in the description and configuration table, but it never completes, so the next time you restart, it’s back to “Node 17”.

I think it’s an Aeon labs thing, it just takes too long to initialize, and the wake-up timeout is too short.

You can still use it, as it’s a “send only” type of device (in scene mode anyway), so when you press a button, the zwave binding sees it, and acts on it, even though it hasn’t completed initialization.

Nick Waterton P.Eng.
National Support Leader - Nuclear Medicine, PET and RP
GE Healthcare

M+1 416 859 8545
F +1 905 248 3089
E nick.waterton@med.ge.commailto:nick.waterton@med.ge.com

2300 Meadowvale Boulevard
Mississauga, ON L5N 5P9 Canada

GE imagination at work

Thanks Nicolas.

It would be good to get a log. Often this is caused by an error in the database, but in any case, if we can identify it, then we can fix it. If you can get a debug log during the initialisation, it should be possible to resolve this.

Really - I didn’t think this was the case? It’s certainly possible in OH1 to send commands to devices that haven’t initialised - the initialisation runs in parallel to the operation. I just had a quick look at the code and can’t see anything that would stop commands being sent during initialisation.

I think it would be good if we can identify this issues and see if they can be resolved - any help you can provide on this would really be appreciated :slightly_smiling:

Cheers
Chris

Chris,

Did you take a look at my log from the post above… Aeon Labs Minimote help (Resolved) This should show you what I was getting when I was trying to do this the first time. I finally got the minimote working and my wife and kids use it now but if you really need me to I can “break” it to get a log again but I’ll be quite busy for the next week or so.

@Qris - have you tried to factory reset your minimote and start it over? Also, your screenshot of ozwcp looks quite different than mine did when I did this so I wonder if maybe you are using a different version. I did have an instance when I was testing this where I couldn’t get the options to come up correctly on a machine running ozwcp but then I tried on another computer and it did come up. I’m not sure what the difference was though.

Nope - I didn’t spot it - sorry. I didn’t read through the complete thread, but just had a look through the log. It looks like the device might not be responding to one of the STATIC messages as mentioned earlier - it might just be a one off, but it would be good to see if it stops in the same place each time.

Given this is a battery device, this continual timeout might then be the reason it’s not possible to set the configuration parameter. Can you provide a new log from startup until it stops again - I want to see a few other things, as well as where it stops… If it shows the same issue, I can look at adding something in the database to configure this.