Indigo Domotics

Hi Matt, I excluded, re-included and performed a define/sync with the new node ID. No dice even with turning on debug logging. The buttons on the remote illuminate and it includes and excludes fine so it doesn't seem like a hardware issue... Other thoughts?

Here are the results of the define/sync process:

Code: Select all

  Z-Wave                          Syncing - started for device "Minimote"
  Z-Wave                          Syncing - retrieved module neighbors list: - none -
  Z-Wave                          Syncing - retrieved manufacture and model names: Aeon Labs - 0086, Minimote (DSA03202x) - 00010003
  Z-Wave                          Syncing - retrieved protocol version 2.78, app version 1.19
  Z-Wave                          Syncing - retrieved class hierarchy: Controller : Portable Controller : Portable Remote Controller (01 : 01 : 01, base 00)
  Z-Wave                          Syncing - retrieved command classes: 20v1 70v1 72v1 9Bv1 86v1
  Z-Wave                          Syncing - device "012 - Minimote" Enable scene mode for all buttons changed to true
  Z-Wave                          Syncing - complete

I'm seeing 2 differences with your sync results than mine. One is that my Minimote's appVers is older (1.17) and the other is that mine claims to support association command class (85v1) and yours does not. The latter shouldn't really matter since Indigo isn't using associations with this module (it enables the global scene broadcast config parm 250), but it is interesting because it shows yours is definitely behaving differently.

Did your purchase your Minimote from MacHomeStore (now Indigo Store)? If so, I'll see if Norm can send me a loaner since it will probably have your appVers. I can then test it here to see if it works. If it has the same vers number and works, then I think you just have a malfunctioning unit. If it doesn't work, then I'll have to work with Aeotec developers to see what they changed..

Hi Matt, Apologies for the delay in responding. I actually purchased this Minimote from zwaveproducts.com. Maybe the MacHomeStore is selling this newer software version too? If not, maybe there's a way to downgrade the firmware? It seems Aeotec has made firmware tools available in the past... Thanks!

We've emailed Aeotec to ask them if there was a firmware change that effects how the scene mode (config parm 250) works. We'll let you know once we hear back from them.

I heard this back from Aeotec:

Aeotec wrote:

The change in firmware from 1.17 to 1.19 that does not effect the scene mode. Just if the customer has configured the parm 241~248, which will lead to the 4 buttons not being able to use the function of scene mode. So there are some suggestions: please removed the minmote from the Z-Stick and then include it again.

After that, choose the new node ID in the define dialog and resync it with Indigo. Make sure Indigo re-enables the scene command, parm 250 (should show it in the Event Log).

If that doesn't help then I would try to get it replaced to see if it was just a bad module.

I have my minimote set up in scene mode Below is the button notifications in the log. It shows as only 1 device and I can't create a trigger on a button push. I must be missing something. Thanks for you help in advance.


RCVD sceneActivateCmd: 01 0A 00 04 00 08 04 2B 01 01 00 D6
Z-Wave Debug . . sceneActivateCmd: node 008, scene: 1
Z-Wave received "008 - Minimote (DSA03202x)" button 1 pressed
Z-Wave Debug RCVD sceneActivateCmd: 01 0A 00 04 00 08 04 2B 01 01 00 D6
Z-Wave Debug . . sceneActivateCmd: node 008, scene: 1
Z-Wave received "008 - Minimote (DSA03202x)" button 1 pressed
Z-Wave Debug RCVD sceneActivateCmd: 01 0A 00 04 00 08 04 2B 01 01 00 D6
Z-Wave Debug . . sceneActivateCmd: node 008, scene: 1
Z-Wave received "008 - Minimote (DSA03202x)" button 1 pressed

Ok I figured out my issue. Have to do following

1. in Trigger define as z-wave event.
2. then select z-wave command.
3. then select minimote
4. Then select the button you want to trigger on.

It works yea!!!!!!!!

I've just bought a second minimote and I'm facing the exact same issue. I've excluded/re-included etc. Have turned on debug, but nothing comes through on the logs when I press any buttons or hold down any buttons.

So this is where it gets interesting.

My first minimote never worked no problem.

So I check the device info for both.

Here is the device info for the minimote that works:

Code: Select all

Indigo Z-Wave Version: 1.0.281
Node ID: 14
Model: Minimote (DSA03202x)
Model ID: 00010003
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 2.78
Application Version: 1.19
Model Definition Version: 3
Library Type: 2
Class Name: Portable Remote Controller
Class Hierarchy: 01 : 01 : 01
Command Class Base: 00
Command Versions: 20v1 70v1 72v1 9Bv1 86v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: beaming
Neighbors: - none -
Associations: - none -
Config Values: 250:1


And here is the device info for the new one, that does NOT work.

Code: Select all

Indigo Z-Wave Version: 1.0.281
Node ID: 20
Model: Minimote (DSA03202x)
Model ID: 00010003
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 2.48
Application Version: 1.14
Model Definition Version: 3
Library Type: 2
Class Name: Portable Remote Controller
Class Hierarchy: 01 : 01 : 01
Command Class Base: 00
Command Versions: 20v1 85v1 86v1 70v1 72v1 9Bv1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: beaming
Neighbors: - none -
Associations: - none -
Config Values: 250:1


Apart from the node ID, here are the changes that I see

Working remote:
Protocol Version: 2.78
Application Version: 1.19
Command Versions: 20v1 70v1 72v1 9Bv1 86v1

Non-working remote:
Protocol Version: 2.48
Application Version: 1.14
Command Versions: 20v1 85v1 86v1 70v1 72v1 9Bv1

One thing I'm going to try is to upgrade the firmware, which is currently 1.19. But have to go and find a bloody Windows machine to do it. Will post an update.

Matt, Jay, thoughts on anything else I should try? As I said, the include/exclude/re-include worked no problem. And the logs with debugging turned on do not show any command being received by Indigo. But Indigo does see this as a device on Z Stick and lets me configure/sync it etc.

I upgraded the firmware to the currently available 1.19 after getting hold of a Windows machine (as the firmware ships only as a Windows executable).

And SUCCESS!

Pressing the keys are triggering the all the actions I have setup on Indigo!

I had to just re-sync the device by holding down the 'Learn' key and selecting "Define/Sync" for the minimote again.

Now the minimote config is the same as that of the working minimote I have.

Code: Select all

Indigo Z-Wave Version: 1.0.281
Node ID: 20
Model: Minimote (DSA03202x)
Model ID: 00010003
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 2.78
Application Version: 1.19
Model Definition Version: 3
Library Type: 2
Class Name: Portable Remote Controller
Class Hierarchy: 01 : 01 : 01
Command Class Base: 00
Command Versions: 20v1 70v1 72v1 9Bv1 86v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: beaming
Neighbors: - none -
Associations: - none -
Config Values: 250:1


Hope this helps anyone looking to get it to work.

Hey Indy,

Great info. Thanks for the report and I'm glad the new firmware is working for you.

I recently purchased a Minimote. I was able to sync the device without issue and configured it for scene mode. When the buttons are pressed, I don't think Indigo is detecting it. I've run in debug mode to confirm this. The firmware appears to be a newer version than the recommended 1.19. Aeon website has the 1.19 firmware for download. I don't see any other version on their website. Should I install the older(?) 1.1.9 firmware version? Or is there another "trick" for this version of the minimote. The details of my device are pasted below.

Indigo Z-Wave Version: 1.0.355
Node ID: 10
Model: Minimote (DSA03202x)
Model ID: 00010003
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 2.48
Application Version: 3.10
Model Definition Version: 3
Library Type: 2
Class Name: Portable Remote Controller
Class Hierarchy: 01 : 01 : 01
Command Class Base: 00
Command Versions: 20v1 84v1 85v1 86v1 70v1 72v1 9Bv1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: beaming, waking
Neighbors: - none -
Associations: - none -
Config Values: 250:1

I'm not sure what is going wrong with the particular version you have. Is it a "Gen5" version of the module?

Try toggling the Enable scene mode for all buttons checkbox OFF, then save the settings to the module. Check to see if anything is debug logged, then try re-enabling it and saving the settings again to see if that gets it working. Note between changing the settings you'll have to wait for the module to wake for it to be written to the device.

Matt,

Thanks for your response and sorry it took me so long to try it. It didn't work. But the good news is by upgrading to firmware version 1.19 my problems are solved.

I have been using an Aeotec minimote successfully for a long time. Today, I got an additional one but cannot get it to work. If I hold the join button down during sync, the sync complete successfully. Output below. However, none of the four buttons are heard by Indigo. I tried turning debug on and still nothing is being heard. I would appreciate any suggestions.

Dec 11, 2016, 4:56:34 PM
Z-Wave Syncing - started for "MBR - Minimote 2"
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Syncing - retrieved manufacture and model names: Aeon Labs - 0086, Minimote (DSA03202x) - 00010003
Z-Wave Syncing - retrieved protocol version 2.48, app version 3.10
Z-Wave Syncing - retrieved class hierarchy: Controller : Portable Controller : Portable Remote Controller (01 : 01 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 84v1 85v1 86v1 70v1 72v1 9Bv1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: beaming, waking
Z-Wave Syncing - retrieved wake interval of 5 minutes
Z-Wave Syncing - device "018 - MBR - Minimote 2" wake interval changed to 5 minutes
Z-Wave Syncing - device "018 - MBR - Minimote 2" parameter 250 "Enable scene mode for all buttons" changed to true
Z-Wave Syncing - complete

Did it include a manual, and if so does it still say that parameter #250 is used to enable the global scene mode?

Try excluding and re-including it as well, if you haven't already.