Aeon Minimote Configuration OH 1.8.2?

Yep, I get the red and blue lights when I press a button.

Just out of curiosity, did you ever get this to work?

I did not. I just migrated everything except ZWave to OH2, so Iā€™ll config that and try again soon.

Ahhh. I was going to say from your description it sounded as though option 250 never got set. If itā€™s not set then the minimote will try and talk to associated devices directly (ā€¦of which there are none) rather than send scene info to the controller.

I have zwave up and running on 2.0 and still having the same difficulty. I agree that it sounds like 250 is not getting set. Iā€™ve tried multiple times, and OH seems to be trying to send it, but the behavior doesnā€™t change.

Put the zwave binding in debug mode and see if it sees the remote waking up. (NIFs)

Make sure youā€™re running the latest firmware on the minimote. I think itā€™s 1.19. I struggle with the minimote for about a month originally but @TheKornā€™s method worked for me.

Iā€™m back, after some time away from this project. The good news is that in DEBUG mode, I can see that the binding is seeing the button presses:

2017-02-14 22:05:38.957 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 08 04 2B 01 01 00 D6 
2017-02-14 22:05:38.958 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-14 22:05:38.958 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 04 00 08 04 2B 01 01 00 D6 
2017-02-14 22:05:38.959 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0A 00 04 00 08 04 2B 01 01 00 D6 
2017-02-14 22:05:38.959 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 04 2B 01 01 00 
2017-02-14 22:05:38.959 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:DONE)
2017-02-14 22:05:38.959 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Starting initialisation from DONE
2017-02-14 22:05:38.959 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@e6ba0de already registered
2017-02-14 22:05:38.959 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class SCENE_ACTIVATION
2017-02-14 22:05:38.959 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Received Scene Activation for Node ID = 8
2017-02-14 22:05:38.960 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene Activation Set
2017-02-14 22:05:38.960 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene activation node from node 8: Scene 1, Time 0
2017-02-14 22:05:38.960 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-02-14 22:05:38.960 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-02-14 22:05:38.960 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 1
2017-02-14 22:05:38.960 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Updating channel state zwave:device:159d39e5eee:node8:scene_number to 1 [DecimalType]
2017-02-14 22:05:38.960 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Transaction not completed: node address inconsistent.  lastSent=9, incoming=255

(the node number on the last message seems to vary based on other recent activity, but there is always a similar message after the group of Node 8 messages)

Here are two of my item definitions:

Switch Minimote1_Button1 (gMinimote) {zwave="8:command=SCENE_ACTIVATION,scene=1,state=1"}
Switch Minimote1_Button1_Long  (gMinimote) {zwave="8:command=SCENE_ACTIVATION,scene=2,state=1"}

and rule:

rule "Reset minimote switches"
when
        Item gMinimote received update
then
	logInfo("Alert", "Get a minimote button press")

        gMinimote.members.forEach[ button |
                if(button.state == ON) button.postUpdate(OFF)
        ]
end

When I press a button, I get nothing in either log (openhab.log or events.log), apart from the debug messages shown.

The logs log like zwave 2.0 binding logs but your items definitions are 1.x
style.

Switch Minimote1_Button1 (gMinimote)

{channel=ā€œzwave:device:159d39e5eee:node8:scene_numberā€}

Using what ever channel ID corresponds to the buttons. You can find the
channel IDs under the Thing in PaperUI.

Thanks. Yes, I am running 2.0, upgraded from 1.8 (1.9 ZWave). I missed that changes needed to be made to the ZWave item definitions; will give that a try now. My only other ZWave device (so far) is seasonal, and I havenā€™t missed it since the upgrade, so I didnā€™t know it too is broken.

Now looking for the URL to launch paperui. This is what frustrates me about OH - the docs keep taking you almost far enough. http://docs.openhab.org/addons/uis/paper/readme.html

ā€¦ and itā€™s working! Thanks!

Hello. I am unable to find the place to edit parameter 250 as described above.
I have OH2.3.0, and Habmin2.3.0 addon. Do I understand correctly that I should be able to view/edit thing parameters in Habmin under Configuration, Things? If so, I merely see read-only information, of which none are parameters. :frowning:

Please advise. Thank you.

In Habmin> Configuration> Things> your minimote> Configuration Parameters, do you see 250: Secondary Controller Mode (itā€™s the last one)?

Be aware that this setting is not read from the minimote, so will display with the default (Group Mode) next time you look at it.

@5iver, thanks, but no, I do not have that listing! Iā€™m confused as to why. This is all I see:
(I have a new installation of OH2.3 and Habmin2.3, running on Linux Debian jessie Raspberry Pi)

Unknown Device means your minimote is not initialized. Try waking it up (hold the join button for a few seconds).

@5iver, I didā€¦ several times. Also tried the other things this thread suggests, such as a full reset of the minimote via buttons 7 and 8 simultaneously, flashed to firmware 1.9, rebooted, etc.
Is there a simple step I missed? Iā€™m open to all thoughts and suggestions, please. Iā€™ve been probing around for many hours without success. Since this thread in context to OH1.8.2, Iā€™m wondering what has changed in OH2.3 that may be contributing to my issue here. :-/

When I press-and-hold the join button for several seconds to wake up the Minimote, here is what my logs say:

==> /var/log/openhab2/openhab.log <==
2018-06-24 17:59:46.660 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 23: Unsupported command class ASSOCIATION_COMMAND_CONFIGURATION

==> /var/log/openhab2/events.log <==
2018-06-24 17:59:46.684 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:f21702b0:node23' has been updated.

==> /var/log/openhab2/openhab.log <==
2018-06-24 17:59:46.691 [WARN ] [l.serialmessage.SendDataMessageClass] - NODE 23: Already processed another send data request for this callback Id, ignoring.

There was a recent report here about a minimote not initializing. Interesting that you are getting this with the 2.3 release zwave binding. @chris, is this possibly the same issue?

Update: I got it working. :slight_smile: No success unpairing and re-pairing while sitting in the same location the room relative to the the zwave controller. BUT if I move very close (1" away) from the Zwave controller, then unpaired and re-paired, and woke up the device, suddenly I see parameter 250 and the other jazz.

Credit to rlkoshak for realizing this. I had to read it a few times before I finally resorted to trying it. (duh me)

1 Like