Insteon Open/Close 2444-222 Support


Insteon has this module to open/close roller shutters and covers.
It’s not seem to be supported with the Insteon bindings (also in the new Insteon Official BETA app they choose to stop support it).
I wonder why? it’s working well from the old app and from the keypad.
Any workaround or plan to support this? I can’t imagine a smart house without the ability to control the blinds…


Perhaps choose a standard like Z-Wave? :wink:

Well, I just found the developer’s notes for this device here:

It appears to use the same command other modules use. OPEN == ON and CLOSE == OFF.

Do you already have a working openhab insteon setup? If so, I’d suggest trying to set it up as:

2442-222 Micro Dimmer F00.00.06

Let me know if that works.

1 Like

The only reason I chose Insteon is because they have keypads that you can link to the blind module, so you don’t need many switches on the same wall,

2-3 lights + blind + curtain —> that’s 6 switches, and that’s only 1 setup, I have 4 windows in my living room and 6 lights

Will give it a try, thanks !

@obenreph - I’d agree this is probably the best way to go with native Insteon buttons linked direct to the blind module. That being said, the beauty of openHAB is that you can use your Insteon Keypad to tell openHAB to control whatever make/model (Insteon, Zwave, Zigbee, Anything else OH can control) blind control you want. So you can mix/match items that offer the best features/price/whatever.

For example, I used to use an Insteon motion sensor in my bathroom to kick the lights (via a rule to control brightness dependent on time of day, other lights that are on, etc) . I got tired of that junky hardware and changing batteries, so I bought a standard motion activated switch to hardwire into a switch box and, wired it to an Insteon micro-module to kick on the lights (via same rule). Later I got sick of problems with bandwidth on the Insteon Network causing issues, so I bought a hardwired ZWave motion sensor to kick on the lights (via same rule) and now it works perfectly!

1 Like

I love the idea very much, if that won’t work I’ll try a different module for the blinds!

I’ve tried to setup it as you suggested but it still doesn’t work. I can see the following DEBUG messages:

2020-05-30 22:06:12.934 [ome.event.ItemCommandEvent] - Item ‘InsteonDevice4DC52D_FastOnOff’ received command 0

2020-05-30 22:06:12.937 [nt.ItemStatePredictedEvent] - InsteonDevice4DC52D_FastOnOff predicted to become 0

2020-05-30 22:06:12.948 [vent.ItemStateChangedEvent] - InsteonDevice4DC52D_FastOnOff changed from 100 to 0

2020-05-30 22:06:13.366 [ome.event.ItemCommandEvent] - Item ‘InsteonDevice4DC52D_FastOnOff’ received command 0

2020-05-30 22:06:13.369 [nt.ItemStatePredictedEvent] - InsteonDevice4DC52D_FastOnOff predicted to become 0

Hold On!

something has just happened, I have configured the item type as ‘Switch’ and it started working (it responds MUCH FASTER than any insteon app :slight_smile: )

However, when I configure the type as Dimmer or RollerShutter it doesn’t work which takes out all the joy because I do want to be able to tell my automation system to open only half of the blind etc.

any idea how to make it work?

Type 'Switch:

2020-05-30 22:15:16.337 [DEBUG] [nternal.handler.InsteonDeviceHandler] - channel insteon:device:4DC52D:fastOnOff was triggered with the command OFF

2020-05-30 22:15:16.341 [DEBUG] [nsteon.internal.device.InsteonDevice] - processing command OFF features: 4

2020-05-30 22:15:16.345 [DEBUG] [steon.internal.device.CommandHandler] - FastOnOffCommandHandler: sent fast off to switch 4D.C5.2D

2020-05-30 22:15:16.345 [DEBUG] [nsteon.internal.device.InsteonDevice] - qe taken off direct: FastOnOff(1:1:2) OUT:Cmd:0x62|toAddress:4D.C5.2D|messageFlags:0x0F=DIRECT:3:3|command1:0x14|command2:0x00|

2020-05-30 22:15:16.347 [DEBUG] [ding.insteon.internal.InsteonBinding] - found binding config for channel insteon:device:4DC52D:fastOnOff

2020-05-30 22:15:16.347 [DEBUG] [nsteon.internal.device.InsteonDevice] - next request queue processed in 2000 msec, quiettime = 2000

2020-05-30 22:15:16.349 [DEBUG] [binding.insteon.internal.driver.Port] - writing (500): OUT:Cmd:0x62|toAddress:4D.C5.2D|messageFlags:0x0F=DIRECT:3:3|command1:0x14|command2:0x00|

2020-05-30 22:15:16.363 [DEBUG] [teon.internal.driver.hub.HubIOStream] - getting

2020-05-30 22:15:17.245 [DEBUG] [ding.insteon.internal.InsteonBinding] - got msg: IN:Cmd:0x50|fromAddress:4D.C5.2D|toAddress:49.DE.C2|messageFlags:0x20=ACK_OF_DIRECT:0:0|command1:0x14|command2:0x00|

2020-05-30 22:15:17.248 [DEBUG] [nsteon.internal.device.InsteonDevice] - ----- applying message to feature: FastOnOff

2020-05-30 22:15:17.252 [DEBUG] [on.internal.device.MessageDispatcher] - 4D.C5.2D:FastOnOff DIRECT_ACK: q:QUERY_PENDING cmd: 80

2020-05-30 22:15:17.255 [DEBUG] [on.internal.device.MessageDispatcher] - changing key to 0x19 for msg IN:Cmd:0x50|fromAddress:4D.C5.2D|toAddress:49.DE.C2|messageFlags:0x20=ACK_OF_DIRECT:0:0|command1:0x14|command2:0x00|

2020-05-30 22:15:17.258 [DEBUG] [steon.internal.device.MessageHandler] - DefaultMsgHandler ignoring unimpl message with cmd1:0x14

2020-05-30 22:15:17.265 [DEBUG] [on.internal.device.MessageDispatcher] - defdisp: 4D.C5.2D:FastOnOff set status to: QUERY_ANSWERED

2020-05-30 22:15:17.269 [DEBUG] [nsteon.internal.device.DeviceFeature] - 4D.C5.2D:GenericLastTime publishing: 2020-05-30T22:15:17.268+0300

2020-05-30 22:15:18.345 [DEBUG] [.internal.device.RequestQueueManager] - device queue for 4D.C5.2D is empty!

Type ‘RollerShutter’:

2020-05-30 22:19:08.494 [ome.event.ItemCommandEvent] - Item ‘InsteonDevice4DC52D_FastOnOff’ received command DOWN

2020-05-30 22:19:08.499 [nt.ItemStatePredictedEvent] - InsteonDevice4DC52D_FastOnOff predicted to become DOWN

2020-05-30 22:19:08.507 [vent.ItemStateChangedEvent] - InsteonDevice4DC52D_FastOnOff changed from NULL to 100

Try it as a dimmer. The device I suggested is actually a dimmer switch.

it works !

1 Like

Glad this is working for you! Curious what kind of blinds you are controlling with this?

These are actually blinds my uncle manufacture, you can see them here:

You’ll have to translate from Hebrew though

It uses somfy linear motors and I connected it to the insteon module.

Looks nice. I’m looking for a blind inside of the house to control. Haven’t found a good one yet that I like.

Going back to that discussion, now that I have a nice slider that controls my blinds using OH I wanted to spoof the switch with a roller shutter item, this way I have the UP, DOWN and STOP buttons.
I used a rule that trigger the dimmer item for UP (dimmer.sendCommand(100)) and DOWN (dimmer.sendCommand(0)).
Then I changed the DIMMER item visibility to off so it’ll be hidden.
It works very well !

however, I can’t make the STOP button to work, do you know what command should I use for the dimmer to stop ?

I thought about trying to use the “Manual Change” feature of a dimmer that has a manual change up, manual change down, and manual change stop to try to do this but I cannot seem to make it work with a dimmer.

@ranielsen - do you know how the manual change feature works? I see in the docs this example:

 Switch item=keypadSwitchManualChange label="manual change" mappings=[ 0="DOWN", 1="STOP",  2="UP"]

but commanding the manual change channel to 0, 1, or 2 didn’t do anything to me dimmer. Then I thought maybe this is a read only channel, but manually dimming my dimmer up or down did not show a state change to my item.

@tommycw10, this works for me both manually and via the UI:


Number manualChange {channel="insteon:device:home:239F82:manualChange"}


Switch item=manualChange label="manual change" mappings=[ 0="DOWN", 1="STOP", 2="UP"]


2020-06-04 08:40:18.691 [.ItemChannelLinkAddedEvent] - Link 'manualChange-insteon:device:home:239F82:manualChange' has been added.
2020-06-04 08:40:40.919 [vent.ItemStateChangedEvent] - manualChange changed from NULL to 0
2020-06-04 08:40:42.668 [vent.ItemStateChangedEvent] - manualChange changed from 0 to 1
2020-06-04 08:40:55.052 [vent.ItemStateChangedEvent] - manualChange changed from 1 to 2
2020-06-04 08:40:56.991 [vent.ItemStateChangedEvent] - manualChange changed from 2 to 1
2020-06-04 08:41:12.498 [vent.ItemStateChangedEvent] - manualChange changed from 1 to 2
2020-06-04 08:41:17.499 [vent.ItemStateChangedEvent] - manualChange changed from 2 to 1
2020-06-04 08:44:26.792 [ome.event.ItemCommandEvent] - Item 'manualChange' received command 2
2020-06-04 08:44:26.882 [nt.ItemStatePredictedEvent] - manualChange predicted to become 2
2020-06-04 08:44:26.958 [vent.ItemStateChangedEvent] - manualChange changed from 1 to 2
2020-06-04 08:44:30.782 [ome.event.ItemCommandEvent] - Item 'manualChange' received command 1
2020-06-04 08:44:30.808 [nt.ItemStatePredictedEvent] - manualChange predicted to become 1
2020-06-04 08:44:30.930 [vent.ItemStateChangedEvent] - manualChange changed from 2 to 1
2020-06-04 08:44:34.185 [ome.event.ItemCommandEvent] - Item 'manualChange' received command 0
2020-06-04 08:44:34.219 [nt.ItemStatePredictedEvent] - manualChange predicted to become 0
2020-06-04 08:44:34.286 [vent.ItemStateChangedEvent] - manualChange changed from 1 to 0
2020-06-04 08:44:37.493 [ome.event.ItemCommandEvent] - Item 'manualChange' received command 1
2020-06-04 08:44:37.513 [nt.ItemStatePredictedEvent] - manualChange predicted to become 1
2020-06-04 08:44:37.559 [vent.ItemStateChangedEvent] - manualChange changed from 0 to 1
1 Like

Thank you Rob, any chance to map this to RollerShutter so I get to use Up, Down icons as opposed to mappings labels?

Give it a try, maybe some sort of profile will let you send a 0, 1, and 2 to the device.


Thanks for looking into this. Error was me, I linked my item to the wrong damn device… thanks!

1 Like