Any plans to support HomeSeer HSM200 Repeater/MultiFunction?

When I create an 'Action to Set LED Color and On/Off State (HomeSeer)', the HSM200 Motion Sensor always goes to the State 'on'.

I would like a Trigger to change the LED Color and state to reflect other information (In this case the LED is off between 6:00am to 8:00pm, Red if any deadbolt is unlocked from 8:00pm to 6:00am and Green if all deadbolts are locked from 8:00pm to 6:00am) without changing the Motion Sensor's State...

The HSM200's state is linked to the dimmer in the room and currently the lights are turning on with every LED Action.

Does anyone have a solution for this?

[matt (support)]

Can you capture what is showing in the Event Log when you execute the action?

The HSM200's state is linked to the dimmer in the room and currently the lights are turning on with every LED Action.

Is this a direct link via a Z-Wave Association, or is this indirectly via an Indigo Trigger watching the device state change?

matt

Here is the event log when excepting the action....

Code: Select all

Feb 22, 2022 at 8:45:21 PM
   Trigger                         Change LEDs to red
   Z-Wave                          sent "047 - HomeSeer HSM200 Motion Sensor - Kitchen" raw command [20 01 FF]
   Z-Wave                          sent "047 - HomeSeer HSM200 Motion Sensor - Kitchen" raw command [33 05 03 02 FF 03 00 04 00]
   Z-Wave                          received "047 - HomeSeer HSM200 Motion Sensor - Kitchen" status update is on

I am using indirect links via an Indigo trigger on the device state as the dimmers are Insteon.

[matt (support)]

Can you enable Indigo's Z-Wave debug logging (via the Interfaces->Z-Wave->Configure... menu item), then capture the Trigger sequence again? Include several lines before the Trigger so I can see what incoming command is causing Indigo's device state change.

Here you go:

Code: Select all

Feb 26, 2022 at 8:50:32 AM
   Action Group                    Turn On Blue LED - Ensuite HSM200
   Z-Wave Debug                    SENT sendRawZwaveCommand: 01 0A 00 13 30 03 20 01 FF 25 3A 14
   Z-Wave Debug                    RCVD sendRawZwaveCommand: 01 07 00 13 3A 00 00 03 D2 (node ACK)
   Z-Wave                          sent "048 - HomeSeer HSM200 Motion Sensor - Ensuite" raw command [20 01 FF]
   Z-Wave Debug                    SENT sendRawZwaveCommand: 01 10 00 13 30 09 33 05 03 02 00 03 00 04 FF 25 3B 14
   Z-Wave Debug                    RCVD sendRawZwaveCommand: 01 07 00 13 3B 00 00 02 D2 (node ACK)
   Z-Wave                          sent "048 - HomeSeer HSM200 Motion Sensor - Ensuite" raw command [33 05 03 02 00 03 00 04 FF]
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 12 00 04 00 30 0C 71 05 00 00 00 FF 07 07 03 77 06 00 2C
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 048, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 7, classSubKeyExt 7100000707
   Z-Wave Debug                    . .  requestAlarmSensorStatus: defnStatusByte 255
   Z-Wave                          received "048 - HomeSeer HSM200 Motion Sensor - Ensuite" status update is on


[matt (support)]

Sorry for the slow reply on this one.

Unfortunately, when Indigo is sending the command to turn on the LED the HSM200 is replying back with the motion sensor tripped command. Indigo doesn't have control over this behavior; to Indigo it looks identical to the motion sensor tripping. You can try sending a raw command (action Send Raw Z-Wave Command) that only sets the LED color but doesn't turn it on, but that may not give you the result you want.

In this case the raw command to set the LED color would be this sequence for red:

Code: Select all

0x33 0x05 0x03 0x02 0xFF 0x03 0x00 0x04 0x00

or this for blue:

Code: Select all

0x33 0x05 0x03 0x02 0x00 0x03 0x00 0x04 0xFF