Insteon status update issue

Hello,

I am getting issue with status update from an Insteon dimmer:

  • I am using openhab 1.8 with the hub 2014 (2245)
  • I can control properly the dimmer from the OpenHab app so it seems the binding works properly (see config under)
  • I am getting a status update when I physically press the dimmer (but with some important fail rate)
  • I do NOT get update when the dimmer is triggered by a scene or by the Insteon app.
  • The status gets recovered after a few minutes: would my poll time not be taken into account ?

My configuration:

.cfg:
insteonplm:port_0=/hub2/login:pwd@ip:port,poll_time=1000

.items:

Dimmer dimmer "dimmer [%d]" <slider> (myGroup) {insteonplm="42.A0.F3:F00.00.01#dimmer"}

What do you see in the log files? If you have it proplerly configured you should see something like:

2016-12-17 07:49:46.679 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - modem database has 61 entries!
2016-12-17 07:49:46.684 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - device 23.9F.C9 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].
2016-12-17 07:49:46.706 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - device 24.33.F7 found in the modem database and the modem controls groups [0xFE] and responds to groups [0x01].

Also, no need to comment out the device id’s.

The dimmer is 42.A0.F3. Here under logs I could find about Insteon
I noticed a dead device timeout set to 3000s: would it be the cause of my trouble ?

2016-12-17 13:23:37.453 [INFO ] [insteonplm.InsteonPLMActivator] - Insteon PLM binding has been started.
2016-12-17 13:23:37.551 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - dead device timeout set to 3000s
2016-12-17 13:23:37.563 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - config: port_0 -> /hub2/login:pwd@ip:port,poll_time=1000
2016-12-17 13:23:37.591 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - devices:   0 configured,   0 polling, msgs received:     0
2016-12-17 13:23:37.652 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - config: service.pid -> org.openhab.insteonplm
2016-12-17 13:23:56.502 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - modem database has 4 entries!
2016-12-17 13:23:56.510 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - device 40.CB.59 found in the modem database and the modem controls groups [0x00,0x02,0x08] and responds to groups [0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08].
2016-12-17 13:23:56.534 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - device 42.A0.F3 found in the modem database and the modem controls groups [0x00] and responds to groups [0x01].
2016-12-17 13:23:56.557 [INFO ] [.o.b.i.InsteonPLMActiveBinding] - device 41.AC.AA found in the modem database, but is not configured as an item and the modem controls groups [0x00] and responds to groups [0x01].
2016-12-17 13:23:57.517 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 2 switched to OFF
2016-12-17 13:23:57.535 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 3 switched to OFF
2016-12-17 13:23:57.538 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 4 switched to ON
2016-12-17 13:23:57.544 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 5 switched to OFF
2016-12-17 13:23:57.547 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 6 switched to OFF
2016-12-17 13:23:57.557 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 7 switched to OFF
2016-12-17 13:23:57.565 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 8 switched to OFF
2016-12-17 13:23:58.509 [INFO ] [.o.b.i.i.device.MessageHandler] - DimmerRequestReplyHandler: set device 40.CB.59 to level 0
2016-12-17 13:25:12.317 [INFO ] [.o.b.i.i.device.MessageHandler] - DimmerRequestReplyHandler: set device 42.A0.F3 to level 100
2016-12-17 13:28:57.666 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 2 switched to OFF
2016-12-17 13:28:57.668 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 3 switched to OFF
2016-12-17 13:28:57.670 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 4 switched to ON
2016-12-17 13:28:57.671 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 5 switched to OFF
2016-12-17 13:28:57.673 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 6 switched to OFF
2016-12-17 13:28:57.675 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 7 switched to OFF
2016-12-17 13:28:57.676 [INFO ] [.o.b.i.i.device.MessageHandler] - SwitchRequestReplyHandler: dev 40.CB.59 button 8 switched to OFF
2016-12-17 13:28:58.679 [INFO ] [.o.b.i.i.device.MessageHandler] - DimmerRequestReplyHandler: set device 40.CB.59 to level 0
2016-12-17 13:30:12.393 [INFO ] [.o.b.i.i.device.MessageHandler] - DimmerRequestReplyHandler: set device 42.A0.F3 to level 100

If you manipulate a dimmer by hand, it will send out a status update (really, a group broadcast message). It is this message that the openhab insteon binding is listening to.

If however a device changes its state due to receiving a message, no such broadcast is sent out, and the insteon binding will not know about it until it polls the device the next time.

There is a hack to work around this, such that if one device changes status, then automatically another device is polled. This cuts down on latencies. See the wiki page’s section:

3-way switch configurations and the “related” keyword

Bernd

Thank you for your help. I am not sure that I get it right. I found a previous post from you about 3 state switch: https://groups.google.com/forum/#!topic/openhab/gwYN8K1YGOA
Is that what I am supposed to do ?

Should I create multiple switch objects in openhab for any insteon controllers that would trigger my switch ? Then use a rule to sum up the different switches ? That would solve the problem of scene triggered by a physical device. But how would I do if the scene is triggered by the Insteon App ?

I also have an old version of hub (version 2012 or 2242): some people say it is more open and can do more: would I have a simple way to solve my problem with this hub ?

Please refer to https://github.com/openhab/openhab/wiki/Insteon-PLM-Binding#3-way-switch-configurations-and-the-related-keyword, this explains how to set up N-way switches with InsteonPLM.

This is a known limitation, This is from https://github.com/openhab/openhab/wiki/Insteon-PLM-Binding#known-limitations-and-issues:

Using the Insteon Hub 2014 in conjunction with other applications (such as the InsteonApp) is not supported. Concretely, OpenHab will not learn when a switch is flipped via the Insteon App until the next poll, which could take minutes.

I’ve been using openHAB with Insteon for a couple years now. I started with the 2014 hub and it works, but not that great. Issues aren’t due to openHAB compatibility, but intrinsic in the hardware itself. What you are experiencing (as explained in previous comments by others) is a known issue with trying to use the hub and other apps in conjunction with openHAB.

I HIGHLY recommend you buy a PLM and use that with openHAB. You can keep your hub for other things (like Amazon Echo or other similar devices), but it just isn’t nearly as fast or nice as a PLM. I solved many speed issues I had by buying a PLM.