[dlink]

I'm trying to capture the opening and closing of a door with a 2845-222 hidden door sensor. The device does not appear to be directly supported in HAL and I've been only able to detect the "Open" condition with other device configurations. So now I'm looking at acting on the raw insteon commands. I've been able to capture the codes through the debug process as:

For opening the door, The HALultra System Monitor is reporting:
Rcvd Insteon 2B02E6 Cmd1:11 Cmd2:1
Rcvd Insteon 2b02E6 Cmd1:6 Cmd 2:1

For closing the door, the HALultra System Monitor is reporting:
Rcvd Insteon 2B02E6 Cmd1:11 Cmd2:2
Rcvd Insteon 2b02E6 Cmd1:6 Cmd 2:2

Using the debug process, I have identified these codes:
02 50 2B 02 E6 00 00 01 CF 11 01 for open

and
02 50 2B 02 E6 00 00 02 CF 11 02 for close

I have set a rule to flip a flag, but that isn't working.

Any ideas what I might be missing here?

[TimShriver]

Hi Dennis,

We sent an email to you about this. Can you send or post a screen capture of your rule logic?

Thanks,

Tim

[JimMcGowanInlet]

I looked at the developer notes, for the raw command it should be


02 50 2B 02 E6 00 00 01 CF 11 01 for opening
02 50 2B 02 E6 00 00 01 CF 13 01 for closing


02 50 2B 02 E6 00 00 04 CF 11 04 for heartbeat
02 50 2B 02 E6 00 00 03 CF 11 03 for battery low


To use the heartbeat and battery low you must have a group 3 and group 4 link.


I will have this added to the device list for the next release. If you have any problems please send me a DebugView log (See the Sticky Post on how to do that)

[dlink]

screen shot attached.

Looks like there might be a problem with saving the entire command.

[DevenLF]

I have three of these exact items setup and in use. I set them up as a "triggerlinc" in HAL, and have not had any difficulty with them working for both 'open' and 'close' HAL recognizes both state changes.

[dlink]

Thanks for the advice on using a triggerlinc.

Could you share some additional details as to your set-up?

Are you able to create just one device to cover the open/close or do you need two sensors: Open = group1 and Close = group2?

Are you able to use the battery low indicator?

could you share some screen shots of rules involving these devices?

I have struck out on the insteon raw commands. It doesn't appear HAL is saving the command.

[DevenLF]

Sorry for the delay. Just now seeing your questions. I only have one device setup per sensor.

I have not tried to use the battery low indicator.

I've tried to attach some screen shots, but the size limit and dimension limit is ridiculous, and it won't let me attach a 200kb file. Good grief. Want me to email them to you? Private me your email address and I'll send them.

Originally Posted by dlink

Thanks for the advice on using a triggerlinc.

Could you share some additional details as to your set-up?

Are you able to create just one device to cover the open/close or do you need two sensors: Open = group1 and Close = group2?

Are you able to use the battery low indicator?

could you share some screen shots of rules involving these devices?

I have struck out on the insteon raw commands. It doesn't appear HAL is saving the command.

[dlink]

Thanks for the screenshots. After looking at them, I remembered that this device has a special "2 group" mode so that it can send different commands for open than close. So I turned off the "2 group" mode and found HAL to report the open/close as on/off as expected, but that doesn't work for me because without the 2 group mode, I can't turn on the lights when the door closes and turn them off when the door opens. The light control pretty much doesn't work without "2 group"

Is there any chance of HAL supporting the "2 group" mode of this device any time soon?

*OR* I guess I can let HAL do the light control rather than the device, but that is delayed...hmmmm