Insteon PLM Binding Duplicate Info logs

[Kirk McCann]

Has anyone noticed duplicate transaction notices when using the Insteon PLM binding?

12:05:02.453 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:02.542 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:02.630 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:02.717 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:02.804 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.158 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.244 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.427 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.511 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.601 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.689 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:03.777 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:32.332 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.512 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.622 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.710 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.795 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.879 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:32.979 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.095 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.182 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.268 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.352 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.441 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.528 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.616 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:33.965 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.051 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.158 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.246 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.343 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.434 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:34.518 INFO  runtime.busevents[:26] - OFC_Motion state updated to CLOSED

12:05:51.010 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.158 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.245 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.333 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.420 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.510 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.604 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.817 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.905 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:51.992 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.077 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.162 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.249 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.337 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.555 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.639 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.738 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.825 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:52.912 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:53.007 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:05:53.093 INFO  runtime.busevents[:26] - OFC_Motion state updated to OPEN

12:06:42.331 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.390 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.449 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.506 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.561 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.620 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.675 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to OFF

12:06:42.731 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:42.802 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:42.938 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:42.992 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:43.056 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:43.111 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

12:06:43.169 INFO  runtime.busevents[:26] - Light_GF_Dining_Light state updated to 0

Thanks,

Kirk

[Bernd Pfrommer]

Kirk,

The binding will generate a bus event whenever an insteon message comes in that updates the state. Duplicates are not suppressed.

What I don't understand however is why  the messages come in back-to-back.

Could you switch on debugging and send us the log?

Also, what devices have you connected?

Bernd

[Bernd Pfrommer]

Alright, I see duplicates, too, but not nearly as many as you do.

The situation you are seeing arises when a device sends a notification because it has been toggled directly, i.e. a motion sensor is tripped, or somebody has pushed the rocker on a switch/dimmer.

My motion sensor sends out (at least) 3 messages when it detects motion, like so (with debugging switched on):

2014-07-17 16:19:13 DEBUG o.o.b.i.InsteonPLMActiveBinding[:466]- got msg: IN:Cmd:0x50|fromAddress:27.8C.A3|toAddress:00.00.01|messageFlags:0xC7=ALL_LINK_BROADCAST:3:1|command1:0x13|command2:0x01|

2014-07-17 16:19:14 DEBUG o.o.b.i.InsteonPLMActiveBinding[:466]- got msg: IN:Cmd:0x50|fromAddress:27.8C.A3|toAddress:1E.DB.41|messageFlags:0x41=ALL_LINK_CLEANUP:1:0|command1:0x13|command2:0x01|

2014-07-17 16:19:15 DEBUG o.o.b.i.InsteonPLMActiveBinding[:466]- got msg: IN:Cmd:0x50|fromAddress:27.8C.A3|toAddress:1E.DB.41|messageFlags:0x47=ALL_LINK_CLEANUP:3:1|command1:0x13|command2:0x01|

It would be enough to just use the ALL_LINK_BROADCAST message, but the binding parses and processes the subsequent cleanup messages as well, for redundancy.

To find out why you have so many duplicates, please switch on debugging in logback.xml, and post the output here.

Thanks!

Bernd

On Monday, June 30, 2014 1:08:31 PM UTC-4, Kirk McCann wrote:

[Kirk D Mccann]

I dont know if it was a memory leak or what but after pulling latest 1.6.0. I'm now seeing just three like you were talking about.  Sorry It took me so long to get to testing it.

Thanks,
Kirk

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/ffprIGqKMwo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Bernd Pfrommer]

About the water sensor and the fanlinc: yes, with the latest version of either 1.5 or 1.6 you only need to fiddle with the xml files.
Provided of course that the device is similar to existing devices.
If you can't get it to work, switch on debugging and post the insteonplm log.

[Joe Barneson]

curious - is the fanlinc supported? it's not listed on the insteon plm wiki page, but i have several fans i'd like to hook into

[Bernd Pfrommer]

FanLinc is currently not supported :(

Can be done of course, but looks like an odd device. Most likely will need coding, not just xml tweaking.

Do you have the FanLincs already or are you just thinking of getting them?

Bernd

[Joe Barneson]

just thinking of getting one - i have alternative options available, but was interested by this for my new install

[Kirk McCann]

He was able to add support for additional devices for me really quickly.

Sent from my iPad

--

[Mike Wilson]

I have a few FanLinc devices and now have a PLM. I'm very interested in getting these supported along with the 8 scene handheld remotes(2342-2). Is there something I can do to help?

[Bernd Pfrommer]

Mike,

Unfortunately the current master does not yet have the latest binding. The review is still pending.

Do you know how to build openhab from source? If yes you can grab the latest version of the binding from my branch.

Bernd

[Bernd Pfrommer]

As of yesterday, the latest version of the binding has been merged into the 1.6 master, and should be downloadable from cloudbees. The openHAB InsteonPLM binding wiki page has instructions on how to add devices. Try those, switch on debugging, and post the log here.

[Mike Wilson]

It does get much further and doesn't complain about the device type for the mutli-button remote. I'm getting status updates for the button presses, but it doesn't seem to work from openhab -> insteon. Here is the log:

2014-11-07 14:24:54 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:27.F9.86|LinkData1:0x00|LinkData2:0x12|LinkData3:0x37|

2014-11-07 14:24:54 DEBUG o.o.b.i.internal.driver.Port[:332]- writing (0): OUT:Cmd:0x6A|

2014-11-07 14:24:54 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x01|LinkAddr:27.F9.86|LinkData1:0x01|LinkData2:0x2E|LinkData3:0x41|

2014-11-07 14:24:54 DEBUG o.o.b.i.internal.driver.Port[:332]- writing (0): OUT:Cmd:0x6A|

2014-11-07 14:24:54 DEBUG o.o.b.i.i.d.ModemDBBuilder[:60]- got all link records.

2014-11-07 14:24:54 INFO  o.o.b.i.InsteonPLMActiveBinding[:531]- modem database has 2 entries!

2014-11-07 14:24:54 DEBUG o.o.b.i.InsteonPLMActiveBinding[:536]- modem db entry: 27.F9.86

2014-11-07 14:24:54 DEBUG o.o.b.i.InsteonPLMActiveBinding[:536]- modem db entry: 2E.86.67

2014-11-07 14:24:54 INFO  o.o.b.i.InsteonPLMActiveBinding[:545]- device 2E.86.67     found in the modem database!

2014-11-07 14:24:54 DEBUG o.o.b.i.internal.driver.Poller[:56]- start polling device 2E.86.67|lastheardfrom->GenericLastTime(0:0:0)|switch->MultiButtonRemote(9:0:4)

2014-11-07 14:26:01 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x11|command2:0x00|

2014-11-07 14:26:01 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 2 bclean: 0 bbcast: 2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: ON param button == 2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:01

2014-11-07 14:26:01 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x11|command2:0x00|

2014-11-07 14:26:01 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 2 bclean: 0 bbcast: 2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: ON param button == 2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light2

2014-11-07 14:26:01 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:01

2014-11-07 14:26:09 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x11|command2:0x00|

2014-11-07 14:26:09 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 1 bclean: 0 bbcast: 1

2014-11-07 14:26:09 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: ON param button == 1

2014-11-07 14:26:09 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light1

2014-11-07 14:26:09 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:09

2014-11-07 14:26:10 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x11|command2:0x00|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 1 bclean: 0 bbcast: 1

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: ON param button == 1

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light1

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:10

2014-11-07 14:26:10 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:2F.F8.EC|messageFlags:0x41=ALL_LINK_CLEANUP:1:0|command1:0x11|command2:0x01|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 1 bclean: 1 bbcast: 236

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: ON param button == 1

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light1

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:10

2014-11-07 14:26:10 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:11.01.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x00|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.d.MessageHandler[:110]- ignore msg 0x06: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:11.01.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x00|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:10

2014-11-07 14:26:10 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:11.01.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x00|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.d.MessageHandler[:110]- ignore msg 0x06: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:11.01.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x00|

2014-11-07 14:26:10 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:10

2014-11-07 14:26:12 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x13|command2:0x00|

2014-11-07 14:26:12 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 2 bclean: 0 bbcast: 2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: OFF param button == 2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:12

2014-11-07 14:26:12 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:00.00.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x13|command2:0x00|

2014-11-07 14:26:12 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 2 bclean: 0 bbcast: 2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: OFF param button == 2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light2

2014-11-07 14:26:12 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:12

2014-11-07 14:26:30 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:2F.F8.EC|messageFlags:0x41=ALL_LINK_CLEANUP:1:0|command1:0x13|command2:0x02|

2014-11-07 14:26:30 DEBUG o.o.b.i.i.d.MessageHandler[:86]- 2E.86.67 button: 2 bclean: 2 bbcast: 236

2014-11-07 14:26:30 DEBUG o.o.b.i.i.device.DeviceFeature[:225]- MultiButtonRemote publishing filtered: OFF param button == 2

2014-11-07 14:26:30 DEBUG o.o.b.i.i.device.DeviceFeature[:230]- MultiButtonRemote publishing to: MO_Light2

2014-11-07 14:26:30 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:30

2014-11-07 14:26:30 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:13.03.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x01|

2014-11-07 14:26:30 DEBUG o.o.b.i.i.d.MessageHandler[:110]- ignore msg 0x06: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:13.03.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x01|

2014-11-07 14:26:30 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:30

2014-11-07 14:26:31 DEBUG o.o.b.i.InsteonPLMActiveBinding[:504]- got msg: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:13.03.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x01|

2014-11-07 14:26:31 DEBUG o.o.b.i.i.d.MessageHandler[:110]- ignore msg 0x06: IN:Cmd:0x50|fromAddress:2E.86.67|toAddress:13.03.02|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x01|

2014-11-07 14:26:31 DEBUG o.o.b.i.i.device.DeviceFeature[:209]- 2E.86.67:GenericLastTime publishing: 2014-11-07T14:26:31

2014-11-07 14:26:49 INFO  o.o.b.i.InsteonPLMActiveBinding[:119]- Item: MO_Light1 got command OFF

2014-11-07 14:26:49 DEBUG o.o.b.i.i.device.InsteonDevice[:148]- processing command OFF features: 2

2014-11-07 14:26:49 WARN  o.o.b.i.i.d.CommandHandler[:58]- command OFF is not implemented yet!

2014-11-07 14:26:57 INFO  o.o.b.i.InsteonPLMActiveBinding[:119]- Item: MO_Light2 got command ON

2014-11-07 14:26:57 DEBUG o.o.b.i.i.device.InsteonDevice[:148]- processing command ON features: 2

2014-11-07 14:26:57 WARN  o.o.b.i.i.d.CommandHandler[:58]- command ON is not implemented yet!

I'll start poking around with the fanlinc. Do you have any suggestions as to what features to use for it? It has a simple light dimmer and then 3 speeds for fan control.

[Bernd Pfrommer]

Mike,

I don't know the FanLinc device at all, but I'd start like this:

1) copy one of the dimmer devices in device_types.xml. It should reference the GenericDimmer handler. See wiki on how to inject your own device types via my_own_devices.xml. Try sending it dimmer commands and post the debug log.

2) then start messing with the device_features.xml. To modify that file you'll need to set up the IDE (at some point I will hack in a hook to inject your own device features, just like for the device_types.xml, but that's not done yet).

About the remotes: you cannot send them any commands, which explains why there is no ON/OFF feature implemented. The remotes are wireless devices, they only broadcast when you press the button, then they go asleep to save battery. You can send the commands all day long, they will not respond. And besides, why should they? The confusion comes because they are represented as switches in openHAB, so you are tempted to flip them in the GUI, and expect them to change their state. Alas, they won't.

Please keep us posted on progress with the FanLinc, thanks!

Bernd

On Friday, November 7, 2014 2:32:14 PM UTC-5, Mike Wilson wrote:

It does get much further and doesn't complain about the device type for the mutli-button remote. I'm getting status updates for the button presses, but it doesn't seem to work from openhab -> insteon. Here is the log:

[Brian Tillman]

Hi Mike,

Did you manage to get the FanLinc device bound?

[Kirk D Mccann]

I don't think so but the I'm sure it can be done.  I moved not to long ago and mine isn't hooked up at the moment.  I'll try to get it hooked up this week.

--

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/ffprIGqKMwo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/9bd7e2bd-58a9-4f93-a780-7569bc22ff03%40googlegroups.com.

[Mike Wilson]

Not really, but to be fair I haven't spent much time on it at all. I did get the lights working as a dimmer, but I haven't gotten the fan to work.

[Brian Tillman]

I've got it working, but could probably use additional testing. Check out https://github.com/openhab/openhab/pull/3139. Binary attached to this message.