Indigo Domotics

new2me07 wrote:

Yes Sir, thats exactly where. Theres simply no options available at all from those devices. All others populate with at least that option.

Interesting. Have to hear from Matt or Jay on this.

I started coding this for you yesterday; should have something by end of Weds.


Sent from my iPad using Tapatalk Pro

The device only supports sending (not receiving) On/Off/Dim commands which usually Indigo would never need to receive so I guess it's coded to hide those devices in that dialog.


Sent from my iPad using Tapatalk Pro

Ignore my last comment, it was utter rubbish.

I don't have any light switch devices other than Fibaro's which have load on them as well, so I wasn't thinking straight.

That said, I'm surprised you don't have On/Off/Dim triggers right in triggers > device state changed > becomes On. You shouldn't need to match raw Zwave...?


Sent from my iPad using Tapatalk Pro

I just tried for a device state change, no secondary selection window comes up. I just left it that way and nothing happens and nothing in event window. I'm extremely excited about the possibilites though on such an outstanding plug in and platform

We definitely need to get this one added as a device definition so it shows up like a normal dimmer.

You apparently have also encountered a bug, which is that if a module isn't identified (and also doesn't get automatically matched to any of the basic profiles) then it doesn't show in the Match Raw Packet event like it should. We'll get that fixed.

In the mean time if you select Any Device instead of your specific module you should then see the Match Raw Packet option. The full packets shown include the module's address (node ID), so the following should match an ON received from your node 041 (0x29 in hex):

0x01 0x09 0x00 0x04 0x00 0x29 0x03 0x20 0x01 0xFF*

and the following will match OFF:

0x01 0x09 0x00 0x04 0x00 0x29 0x03 0x20 0x01 0x00 *

matt (support) wrote:

We definitely need to get this one added as a device definition so it shows up like a normal dimmer.

You apparently have also encountered a bug, which is that if a module isn't identified (and also doesn't get automatically matched to any of the basic profiles) then it doesn't show in the Match Raw Packet event like it should. We'll get that fixed.

In the mean time if you select Any Device instead of your specific module you should then see the Match Raw Packet option. The full packets shown include the module's address (node ID), so the following should match an ON received from your node 041 (0x29 in hex):

0x01 0x09 0x00 0x04 0x00 0x29 0x03 0x20 0x01 0xFF*

and the following will match OFF:

0x01 0x09 0x00 0x04 0x00 0x29 0x03 0x20 0x01 0x00 *

So with * 0x29 0x03 0x20 0x01 0xFF * I was able to trigger an event. Thank you Matt

New2me07

Can you try the 1.0.34 beta at https://github.com/howartp84/ZWaveScene ... tag/1.0.34

It should support your switches without needing the manual ZWave matches you're currently using.

Even if you want to stay with those triggers, I'd appreciate it if you could test my update and report back.

Peter

Indigo 7.2.0 is now available for download and should add basic support for this Evolve module as well as fix the UI problem that prevented the Match Raw Packet trigger event UI from showing the device.

Anyone with an LTM-5 know how to get it to wake up? I've had one hard wired in for 5+ years and now that there's a definition for it, I don't see any reset button or anything aside from the on and off paddle. Having my wife press on/off repeatedly while I try to sync didn't work, and taking it out of the wall reveals no reset buttons.

I could kill power to it, but OF COURSE its on the same circuit as my entire network closet!