Configuration of Insteon contact switch

Hardware: Intel Q9650 on Dell 0G261D motherboard
OS: Ubuntu 18.04.1 LTS
JRE: OpenJDK 1.8.0_192
OpenHAB 2.4
Insteon PLM
Issue: Cannot get contact switch to cause an action

I just picked up an Insteon 2843 open/close sensor and linked to my PLM. Initial indications are that the two linked, like my other Insteon devices did. The contact itself reacts to its magnet, the indicator LED flashes when the state of the contact changes as it should. But I can’t get any reaction within any test code.

I have the contact set up as:

Contact Garage_Door_1 "Garage Door Closed Switch" <contact> {insteonplm="4E.3F.BA:0x000049#contact"}

and some test code (to turn on a lamp):

rule "Test the contact switch"
when
    Item Garage_Door_1 changed to OPEN
then   
    Leviton_Test.sendCommand(ON)
end

And also have the contact set up on a sitemap to see it’s state

Text item=Garage_Door_1 label="Garage Car Door Contact [%s]"

The lamp (Leviton_Test) doesn’t switch and the state of the contact on my sitemap stays at NULL. It’s as if the contact isn’t in communication with the PLM.

First, any possible issues with my syntax? Second, is there a way to look to see if the PLM is actually linked to the contact, besides using Insteon-Terminal?

Thanks!

You can look at the openhab.log files, when the Insteon binding will output something like:

2019-01-14 11:39:35.363 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - modem database has 62 entries!
2019-01-14 11:39:35.386 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 23.9F.C9 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].
2019-01-14 11:39:35.438 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 24.33.F7 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].

Do you see your device listed there? You can then look in events and see something similar to:

2018-12-20 17:17:45.794 [vent.ItemStateChangedEvent] - garageDoor1 changed from NULL to CLOSED
2018-12-20 17:44:34.300 [vent.ItemStateChangedEvent] - garageDoor1 changed from CLOSED to OPEN
2018-12-20 17:45:10.501 [vent.ItemStateChangedEvent] - garageDoor1 changed from OPEN to CLOSED

Hi Rob.
Thinking maybe I didn’t reset the Insteon binding (I’m sure I did, but did it again after posting this, just to be sure) I got a set of log entries that lists all of the devices attached to the PLM. And there is my contact device. Nice. But the contact is still in the NULL state and won’t change. So I’m now confident it’s attached to the PLM, but maybe my coding is somehow incorrect?

Here’s how my item is configured:

Contact garageDoor1         "Main Garage Door [MAP(contact.map):%s]"                                              {insteonplm="31.6F.4B:0x00001A#contact,related=22.F8.B8+22.F6.88"}

And here’s what shows up in the openhab.log file:

$ grep 31.6F.4B openhab.log | head
2019-01-20 10:27:25.846 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 31.6F.4B found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].
2019-01-20 10:28:34.003 [INFO ] [onplm.internal.device.MessageHandler] - ContactRequestReplyHandler: set contact 31.6F.4B to: CLOSED
2019-01-20 10:28:36.110 [INFO ] [onplm.internal.device.MessageHandler] - SwitchRequestReplyHandler: set device 31.6F.4B to OFF
2019-01-20 10:33:34.468 [INFO ] [onplm.internal.device.MessageHandler] - ContactRequestReplyHandler: set contact 31.6F.4B to: CLOSED
2019-01-20 10:33:35.956 [INFO ] [onplm.internal.device.MessageHandler] - SwitchRequestReplyHandler: set device 31.6F.4B to OFF
2019-01-20 10:38:33.981 [INFO ] [onplm.internal.device.MessageHandler] - ContactRequestReplyHandler: set contact 31.6F.4B to: CLOSED
2019-01-20 10:38:35.479 [INFO ] [onplm.internal.device.MessageHandler] - SwitchRequestReplyHandler: set device 31.6F.4B to OFF
2019-01-20 10:43:34.303 [INFO ] [onplm.internal.device.MessageHandler] - ContactRequestReplyHandler: set contact 31.6F.4B to: CLOSED
2019-01-20 10:43:35.483 [INFO ] [onplm.internal.device.MessageHandler] - SwitchRequestReplyHandler: set device 31.6F.4B to OFF
2019-01-20 10:48:34.468 [INFO ] [onplm.internal.device.MessageHandler] - ContactRequestReplyHandler: set contact 31.6F.4B to: CLOSED

If it’s set up properly, it should transition from NULL to OPEN or CLOSED

I see that in your Item you’re using a map function. I’m not familiar with this and some searching regarding its use with a contact is not providing me with a lot of insight. Does a contact value need to be mapped to a separate Item before it can be read?

It’s a mapping file to provide different values in the UI. Here’s what’s in conf/transform/contact.map:

OPEN=Open
CLOSED=Closed
-=Unknown

Well, that should not matter. Still not working, I’m beginning to question the contact. I have another coming tomorrow, maybe I can get it to react.

1 Like

The second contact came in yesterday. It’s bound to the PLM, switch info is set up in OpenHAB, binding was reset and…nothing. Still no response! I think I need to start playing with Insteon product keys but that seems daunting.

What do you see in the log file? What Insteon device do you have?

I have a 2413U USB PLM and several miscellaneous devices, all which are working properly (a few switches and outlets). The contacts are 2843-222 Insteon devices.
I started out with the product key setting listed in the binding description (0x000049) which didn’t work. I tried using 0x00001A but it hasn’t worked either.
I don’t see much in the log files. If I reset my items file the PLM regathers the device information:

2019-01-22 21:41:06.844 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 36.6B.50 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.845 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4D.F2.C4 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.846 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4D.F6.64 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.847 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3F.BA found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.847 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3D.BE found in the modem database and the modem controls groups [0x01].

The contacts are the last two. Over the last day there weren’t many entries. Tonight I was getting messages that the PLM wasn’t hearing from the contact:

2019-01-22 21:40:22.759 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3F.BA|contact->IOLincContact(1:1:4)|lastheardfrom->GenericLastTime(0:0:0)|switch->IOLincSwitch(0:1:4) has not responded to polls for 14791 sec
2019-01-22 21:40:22.759 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3D.BE|contact->IOLincContact(1:1:4)|lastheardfrom->GenericLastTime(0:0:0)|switch->IOLincSwitch(0:1:4) has not responded to polls for 14805 sec

The error uses the word “switch,” not sure what that means…

Here is a snapshot of config. I pulled using ssh on my phone but I don’t have access to a computer right now.

Look for the contact switch part. 49 is the correct code. If you need more details let me know.

Thanks, Danny (and Rob). I’m not sure what else to ask at this point. I’ve been over everything 10 times and my setup is similar to yours. I know the PLM can see the contacts, they show up in the logs when I refresh my items file. I’ve tried every Insteon product key, as both a contact and a switch. The contacts themselves seems to be working, the lights blink when they change state. I just can’t get them to show in OpenHab.
The zwave contact I have, that works fine!

Ok let me backup a little and try to help.

First question.

Do you have other insteon devices? Do they work?

Second
After adding insteon did you stop openhab, clear cache, then restart. This only as a last effort I always try when things don’t work.

I had a problem initially setting up my insteon and after it worked it has always worked. I can’t explain what I was doing wrong. But it all works now and has for 10months!

Your devices are only configured as controllers so they will only send events to the PLM, the PLM can’t query it. Here’s what you have:

2019-01-22 21:41:06.844 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 36.6B.50 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.845 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4D.F2.C4 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.846 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4D.F6.64 found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.847 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3F.BA found in the modem database and the modem controls groups [0x01].
2019-01-22 21:41:06.847 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3D.BE found in the modem database and the modem controls groups [0x01].

Can you configure the contacts as a responders as well? You should see something like:

2019-01-14 11:39:35.386 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 23.9F.C9 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].
2019-01-14 11:39:35.438 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 24.33.F7 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].
1 Like

Good morning!

To start with Danny, I have a few other devices and they work, no problems. A few switches and a dinner, not an extensive network yet. My network is going to be spread out so I really like the powerline aspect of Insteon, but it’s definitely exponentially more difficult to manage.

I cleared the cache last night, then spent about 4 hours trying to figure out why the service wouldn’t restart! I had a permissions issue I needed to fix, back in business this AM. But the contacts are still not working. The balance of the Insteon devices (and the rest of the system) is working.

Rob, you pose an interesting question. Any idea how to alter the configuration as you describe? I’ve not done much beyond just setting up the thing as an item, as I’ve shown you before. I’ll be on Google again this AM lol…

@DaveL generally you can hold button on modem then press contact to link as one type, then press button on contact followed by the modem for the other type.

I always forget which is which responder or controller. You can also use insteon terminal to create the links.

1 Like

Danny, you’re a genius.
When I’d paired the contacts to the PLM, I’d first set the PLM into pair mode, then pressed the button on the contacts. The same procedure I’d used for my switches. I went back and attempted this in reverse; started with the contact, holding the button in until it was in pair mode, then pressed the PLM button. The contact in the logs went from:

2019-01-26 08:14:40.222 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3D.BE found in the modem database and the modem controls groups [0x01].

to:

2019-01-26 18:32:34.257 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - device 4E.3F.BA found in the modem database and the modem controls groups [0x01] and responds to groups [0x01].

The device IDs are different, these are my two contacts. They’re working great now, I’ll keep testing them to ensure there are no hiccups.

I do remember reading something about this but it hadn’t been an issue for me before.

2 Likes

Glad to hear!! I been in your shoes with insteon one slip up and you pull your hair out!

Ok, thought I was done, one more head scratcher! LOL

The contacts are working…ok. They don’t consitently change state every time, and that’s aggravating. But the biggest issue is connectivity. As long as they’re within range of the PLM, they connect. If I move them out of that range (but still within the range of another Insteon dual-band device, such as a a plug-in outlet or embedded dimmer) they lose connectivity. So they can communicate with the PLM but no other devices.

In troubleshooting this I tried pairing the contact switches directly to one of the other (non-PLM) devices, but that didn’t work. Unsure how to get them to talk across the Insteon wireless network?