Insteon Hub 2245-222 and wireless motion sensor 2842-222

Trying to determine how to address or communicate with the Insteon wireless motion sensor model 2842-222 via the 2245-222 Insteon hub from the openhab items/confugurations. I guess to narrow it down - the bindingType???
{ insteonhub = “device=xx.xx.xx, bindingType=???” }
Have found zero reference to this anywhere I have looked so far.

Use the insteonplm binding:

and configure your openhab.conf for the hub 2014 aka “hub2”.

I have established the InsteonPLMActiveBinding, get other errors…

I am expecting to see the one configured device show up openhab.log, but
I am seeing this in the openhab.log -

2015-10-20 14:08:23.513 [WARN ] [.o.b.i.InsteonPLMActiveBinding] - device xx.xx.xx not found in the modem database. Did you forget to link?

  • I can see the device in iPad Insteon APP that I used to set up the 2842-222 motion sensor on this Insteon Hub 2245-222 with my matching HEX number device ID…

openhab.cfg associated lines

root@raspberrypi:/opt/openhab/configurations# grep ^insteo openhab.cfg

mysite.items: (now)
Contact MotionLivingRoom “motion sensor [MAP(]” {insteonplm=“xx.xx.xx:0x00004A#contact”}
Number MotionLivingRoomBatteryLevel “motion sensor battery level [%.1f]” {insteonplm=“xx.xx.xx:0x00004A#data,field=battery_level”}
Number MotionLivingRoomLightLevel “motion sensor light level [%.1f]” {insteonplm=“xx.xx.xx:0x00004A#data,field=light_level”}

Messages in openhab.log

2015-10-20 13:26:38.358 [INFO ] [.service.AbstractActiveService] - InsteonPLM has been started
2015-10-20 13:26:38.359 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - config: poll_interval -> 300000
2015-10-20 13:26:38.368 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - config: port_0 -> /hub2/MyInsteonUserName:MyInsteonPW@InsteonLANIP:25105, poll_time=1000
2015-10-20 13:26:38.387 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - devices: 0 configured, 0 polling, msgs received: 0

I am expecting to see at least the one device configured… pop up.



  1. Seems like somehow your hub2 is not linked as a responder. I’m surprised that it’s not. Would’ve expected the insteon software to do that for you. I don’t use that software, so can’t say for sure.
  2. Switch on DEBUG logging. The insteonplm wiki has instructions on how to do so.
  3. Post the debug log, in particular where it prints out the “modem database”. It will tell me for which devices your hub is configured as a responder.
  4. Do you have any other insteon devices that are less squirrely than a battery operated motion sensor? The thing is asleep most of the time.

Hi Bernd,
I got to thinking of how quiet the logs seemed for this Insteon hub. I even turned on the “TRACE” option … which looked
exactly the same as the generic “DEBUG” option… nada…
A major discovery by retracing my footsteps.
When I set up the application on the iPad - I had “created” username and password… which I was using
inside the openhab.cfg for the initial connection.

If you have a bad username:password … you have seen what that looked like… very quiet logs… NO ERROR!!!
(at least - not a visible one)

After making that adjustment - things blasted through… in openhab logs and such…

Got that log now… the “TRACE” option is so very verbose (after fixing that login) … dropped back to “DEBUG”

Here is the output.
root@raspberrypi:/opt/openhab/logs# tail -f insteonplm.log
2015-10-20 19:05:17 DEBUG o.o.b.i.internal.driver.Port[:320]- writing (0): OUT:Cmd:0x6A|
2015-10-20 19:05:17 DEBUG o.o.b.i.i.d.ModemDBBuilder[:64]- got all link records.
2015-10-20 19:05:17 DEBUG o.o.b.i.i.d.ModemDBBuilder[:89]- MDB ------- start of modem link records ------------------
2015-10-20 19:05:17 DEBUG o.o.b.i.i.d.ModemDBBuilder[:96]- MDB DD.DD.DD: RESP group: 01 data1: 00 data2: 00 data3: 00
2015-10-20 19:05:17 DEBUG o.o.b.i.i.d.ModemDBBuilder[:101]- MDB -----
2015-10-20 19:05:17 DEBUG o.o.b.i.i.d.ModemDBBuilder[:103]- MDB ---------------- end of modem link records -----------
2015-10-20 19:05:17 INFO o.o.b.i.InsteonPLMActiveBinding[:525]- modem database has 1 entries!
2015-10-20 19:05:17 DEBUG o.o.b.i.InsteonPLMActiveBinding[:530]- modem db entry: DD.DD.DD
2015-10-20 19:05:17 INFO o.o.b.i.InsteonPLMActiveBinding[:539]- device DD.DD.DD found in the modem database!
2015-10-20 19:05:17 DEBUG o.o.b.i.internal.driver.Poller[:64]- start polling device DD.DD.DD|data->MotionSensorData(2:1:4)|contact->WirelessMotionSensorContact(1:1:5)| lastheardfrom->GenericLastTime(0:0:0)

Just got up and moved around in that room where the sensor is… a bunch of meaningful data filling the logs!
The binding page had most of the deeper technical set up stuff that made the difference. My issue was initial
setup … USERNAME:PASSWORD (DUH)… found on the unit is small print by port and MAC address
Thanks for your attention here!


Will try to improve the error messages when login credentials are incorrect. You should get a clean error there.


Hi Bernd,
Thought I would mention that the Insteon 2245-222 hub downloaded application made it so very easy to initialize and setup on the LAN when using a smart phone or tablet, that you miss some valued information needed when using the openhab.

I used the camera to scan a bar code on the hub surface, and never even saw the username:password on the back of the device… (need glasses and magnifying glass)

When I used the application, it prompted me to create this username and password…

This is how I ended up using this “self created” username password that I was trying to use inside the openhab.cfg file to initialize this hub…

It is the username password on the hub - not the one you create using the app.
Was not sure how clearly this came out in my message.
thanks again.

That’s the key. Thanks a lot! Been trying to figure this one out for a while!

Submitted a pull request that adds documentation to openhab.cfg. Binding now prints out an error message that is easier to decipher.