Insteon binding takes several hours to connect to modem

Gunn · October 27, 2018, 4:51pm

I have been using the InsteonPLM binding for a couple of weeks now. I was having trouble getting it to download information from the modem (Insteon Hub, newest version) until I just left openHAB running overnight and then it connected. In looking at the logs, it took over two hours to get the information. And the other issue is that it isn’t downloading all of the information either.

When openHAB is started, I will see this messages in the log:

2018-10-23 22:48:35.448 [INFO ] [nding.insteonplm.InsteonPLMActivator] - Insteon PLM binding has been started.
2018-10-23 22:48:35.768 [DEBUG] [ding.insteonplm.internal.driver.Port] - clearing modem db!
2018-10-23 22:48:35.770 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - initialization complete, found 1 port!

Then these messages every 2 minutes...

2018-10-23 22:50:35.771 [WARN ] [onplm.internal.device.ModemDBBuilder] - modem database download unsuccessful, restarting!
2018-10-23 22:50:35.772 [DEBUG] [ding.insteonplm.internal.driver.Port] - clearing modem db!

until...

2018-10-24 13:08:54.157 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - modem database has 17 entries!

As you can see, in this latest log, it took 15 hours to connect! And every time it does eventually connect, it comes up with a different number of entries:

1st time: “modem database has 11 entries!”
2nd time: “modem database has 10 entries!”
This time: “modem database has 17 entries!”

Now I have 32 Insteon devices in my house, all configured using the Hub and my Android Insteon for Hub app, so the Hub should know about all 32.

So, two issues with questions: (1) What could be responsible for it taking multiple hours to get the database information? And (2) Why is it not downloading all of the entries when it does connect?

This makes it difficult to setup effectively.

Thanks!

Tom

Gunn · November 1, 2018, 1:31am

Oh boy…no one else is having this issue? Yikes!?! I’ll keep digging…

Thedannymullen · November 1, 2018, 1:57am

Hey one thing I don’t remember asking, I
in all of your work had you factory reset? I know it is a pain, but sometimes it gives a great starting point is all.

Burzin_Sumariwalla · November 1, 2018, 2:38am

Hi @Gunn,

I have a PLM, not a Hub, but I’ve seen and unable to download modem DB message.

2018-04-15 16:53:54.728 [WARN ] [onplm.internal.device.ModemDBBuilder] - modem database download unsuccessful, restarting!
2018-04-15 16:55:54.731 [WARN ] [onplm.internal.device.ModemDBBuilder] - modem database download unsuccessful, restarting!

My PLM died, but from outward appearances, it looked okay. I’m wondering if what you are seeing is a symptom of the Hub’s modem going out.

Just an (unfortunate) thought.

Regards,
Burzin

Gunn · November 2, 2018, 10:19pm

Thanks for the suggestion guys. I’m not doing a factory reset lol! I have 32 devices scattered all over the place. Blah.

I have been through the common issue of the Hub dying after about 2 years. I replaced this one and went through all that trouble about a year ago. I don’t think there’s any issue with it as I can use my phone app for Hub just fine, no problems at all.

btw, I just did a brand-new install of the snapshot build into a brand-new directory, reset everything up and…same issue. It took about two hours and then found 16 entries; some new, some old. The old ones I had setup in my sitemap that weren’t found this time cause errors in my items and sitemaps that I have to comment out.

Very frustrating; I really see great potential here, but I’m not getting very far!

Tom

Gunn · November 2, 2018, 10:22pm

Is there anything in the insteonplm config file that I could tweak…maybe I timeout setting or something? Maybe it’s just not waiting long enough to gather all of the information that the Hub is sending. I didn’t see anything, but maybe someone else knows of a setting like that.

Thedannymullen · November 3, 2018, 12:29am

Maybe try some network debug. Could be an issue besides openHAB.

Can you change the network port and cable that hub is plugged in?

Can you change the IP address?

Sometimes network issues cause things like you see. I have had router issues in the past that caused unbelievable issues. Maybe try a new router? My reason for saying this is… I had an old router once that worked for many computers, till I got a new one. This computer just would not run downloads at speed. Everything else appeared to work. I would try to download something bigger than 10mb and the speed would crawl. I played hell. Then I plugged directly into the cable modem and computer worked great. So I bought a new router and never looked back. Maybe the insteon hub doesn’t play well with router? Or your openHAB server?

This is a last ditch effort but had to suggest. This smells of something weird like that. Could you try borrowing a friend router for an hour? Or buy one and return if nothing changes. I know it is out there but…

Gunn · November 3, 2018, 12:36am

Ok, I will try all you suggest…

FYI, after another reboot, I noticed that some of my lights were activating/deactivating due to openHAB…even though it hadn’t yet successfully downloaded the modem database yet! Weird…here are some log events:

2018-11-02 19:50:51.336 [INFO ] [nding.insteonplm.InsteonPLMActivator] - Insteon PLM binding has been started.
2018-11-02 19:50:51.343 [DEBUG] [org.openhab.binding.insteonplm      ] - ServiceEvent REGISTERED - {org.openhab.model.item.binding.BindingConfigReader, org.openhab.binding.insteonplm.InsteonPLMBindingProvider}={service.id=352, service.bundleid=209, service.scope=bundle, component.name=org.openhab.binding.insteonplm.genericbindingprovider, component.id=209} - org.openhab.binding.insteonplm
2018-11-02 19:50:51.344 [DEBUG] [org.openhab.binding.insteonplm      ] - BundleEvent STARTED - org.openhab.binding.insteonplm
2018-11-02 19:50:51.510 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - activating binding
2018-11-02 19:50:51.511 [DEBUG] [org.openhab.binding.insteonplm      ] - ServiceEvent REGISTERED - {org.osgi.service.event.EventHandler, org.osgi.service.cm.ManagedService}={service.id=358, service.bundleid=209, service.scope=bundle, event.topics=openhab/command/*, service.pid=org.openhab.insteonplm, component.name=org.openhab.binding.insteonplm.activebinding, component.id=208} - org.openhab.binding.insteonplm
2018-11-02 19:50:51.512 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - global binding config has arrived.
2018-11-02 19:50:51.514 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - dead device timeout set to 3000s
2018-11-02 19:50:51.514 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - configuration update complete!
2018-11-02 19:50:51.514 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - initializing...
2018-11-02 19:50:51.515 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - config: port_0 -> /hub2/Terryn73:B3tBRrBF@192.168.1.4:25105,poll_time=2000
2018-11-02 19:50:51.631 [INFO ] [b.core.service.AbstractActiveService] - InsteonPLM has been started
2018-11-02 19:50:51.635 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - devices:   0 configured,   0 polling, msgs received:     0
2018-11-02 19:50:51.636 [DEBUG] [ng.insteonplm.internal.driver.Driver] - added new port: port_0 /hub2/username:password@192.168.1.4:25105,poll_time=2000
2018-11-02 19:50:51.637 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - config: service.pid -> org.openhab.insteonplm
2018-11-02 19:50:51.637 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - setting driver listener
2018-11-02 19:50:51.637 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - starting 0 ports
2018-11-02 19:50:51.637 [DEBUG] [ding.insteonplm.internal.driver.Port] - starting port /hub2/username:password@192.168.1.4:25105,poll_time=2000
2018-11-02 19:50:51.723 [DEBUG] [ng.insteonplm.internal.driver.Poller] - starting poll thread.
2018-11-02 19:50:51.845 [DEBUG] [ding.insteonplm.internal.driver.Port] - starting writer...
2018-11-02 19:50:51.873 [DEBUG] [ding.insteonplm.internal.driver.Port] - starting reader...
2018-11-02 19:50:51.873 [WARN ] [.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
2018-11-02 19:50:51.889 [DEBUG] [onplm.internal.device.ModemDBBuilder] - querying port for first link record
2018-11-02 19:50:51.889 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - ports started
2018-11-02 19:50:51.889 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - initialization complete, found 1 port!
2018-11-02 19:50:51.889 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - item lamplincChelseaWindowLights    binding changed: addr=2D.8F.D8|prodKey:F00.00.19|feature:dimmer
2018-11-02 19:50:51.913 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x60|
2018-11-02 19:50:51.917 [DEBUG] [ding.insteonplm.internal.driver.Port] - clearing modem db!
2018-11-02 19:50:51.927 [DEBUG] [plm.internal.device.DeviceTypeLoader] - loaded 45 devices: 

**then followed by a bunch of these, which seem like communication messages:**

2018-11-02 19:51:32.582 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:2A.25.65|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 19:51:32.602 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:34.590 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:2A.25.65|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:51:34.606 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:36.594 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x0B|LinkAddr:30.43.28|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 19:51:36.622 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:36.692 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x50|fromAddress:35.EA.78|toAddress:00.00.01|messageFlags:0xC7=ALL_LINK_BROADCAST:3:1|command1:0x13|command2:0x00|
2018-11-02 19:51:36.696 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - dropping message from unknown device with address 35.EA.78
2018-11-02 19:51:38.603 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x0B|LinkAddr:2A.25.65|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 19:51:38.607 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:38.609 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x50|fromAddress:35.EA.78|toAddress:39.B3.99|messageFlags:0x41=ALL_LINK_CLEANUP:1:0|command1:0x13|command2:0x01|
2018-11-02 19:51:38.613 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - dropping message from unknown device with address 35.EA.78
2018-11-02 19:51:38.633 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x50|fromAddress:35.EA.78|toAddress:13.01.01|messageFlags:0xCB=ALL_LINK_BROADCAST:3:2|command1:0x06|command2:0x00|
2018-11-02 19:51:38.635 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - dropping message from unknown device with address 35.EA.78
2018-11-02 19:51:40.607 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:2B.BB.EF|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 19:51:40.621 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:42.608 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:2B.BB.EF|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:51:42.612 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:44.613 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:14.22.6B|LinkData1:0x01|LinkData2:0x0E|LinkData3:0x3A|
2018-11-02 19:51:44.635 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:46.622 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:14.22.6B|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:51:46.630 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:48.624 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xEA|ALLLinkGroup:0x00|LinkAddr:14.2F.CF|LinkData1:0x01|LinkData2:0x0E|LinkData3:0x3A|
2018-11-02 19:51:48.626 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:50.628 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:14.2F.CF|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:51:50.628 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:52.631 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x01|LinkAddr:29.E0.03|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 19:51:52.631 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:54.636 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x0F|LinkAddr:14.2F.CF|LinkData1:0x01|LinkData2:0x0E|LinkData3:0x3A|
2018-11-02 19:51:54.640 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:56.642 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x0F|LinkAddr:14.22.6B|LinkData1:0x01|LinkData2:0x0E|LinkData3:0x3A|
2018-11-02 19:51:56.642 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:51:58.646 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:33.75.AA|LinkData1:0x01|LinkData2:0x20|LinkData3:0x44|
2018-11-02 19:51:58.650 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:52:00.651 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:33.75.AA|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:52:00.651 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:52:02.654 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:1D.36.9A|LinkData1:0x01|LinkData2:0x20|LinkData3:0x40|
2018-11-02 19:52:02.656 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:52:04.659 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xA2|ALLLinkGroup:0x01|LinkAddr:1D.36.9A|LinkData1:0x00|LinkData2:0x00|LinkData3:0x00|
2018-11-02 19:52:04.659 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:52:06.663 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x00|LinkAddr:33.83.16|LinkData1:0x01|LinkData2:0x20|LinkData3:0x44|
2018-11-02 19:52:06.667 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|

**But then the good 'ole failure message comes:**

2018-11-02 19:56:51.928 [WARN ] [onplm.internal.device.ModemDBBuilder] - modem database download unsuccessful, restarting!
2018-11-02 19:56:51.928 [DEBUG] [ding.insteonplm.internal.driver.Port] - clearing modem db!
2018-11-02 19:56:53.394 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 19:56:53.394 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x1B|LinkAddr:1E.04.61|LinkData1:0x01|LinkData2:0x1E|LinkData3:0x41|
2018-11-02 19:56:55.396 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|

**And it starts over.**

And here is where the command comes in and it successfully applied it, even though I don’t have a modem database loaded yet:

2018-11-02 20:29:07.748 [INFO ] [g.insteonplm.InsteonPLMActiveBinding] - Item: switchOffice got command 0
2018-11-02 20:29:07.757 [DEBUG] [eonplm.internal.device.InsteonDevice] - processing command 0 features: 7
2018-11-02 20:29:07.761 [DEBUG] [onplm.internal.device.CommandHandler] - changing level of 33.83.16 to 0
2018-11-02 20:29:07.784 [INFO ] [onplm.internal.device.CommandHandler] - PercentHandler: sent msg to set 33.83.16 to zero by switching off
2018-11-02 20:29:07.785 [DEBUG] [eonplm.internal.device.InsteonDevice] - gave up waiting for query reply from device 33.83.16
2018-11-02 20:29:07.787 [DEBUG] [eonplm.internal.device.InsteonDevice] - qe taken off direct: GenericDimmer(1:3:8) OUT:Cmd:0x62|toAddress:33.83.16|messageFlags:0x0F=DIRECT:3:3|command1:0x13|command2:0x00|
2018-11-02 20:29:07.788 [DEBUG] [eonplm.internal.device.InsteonDevice] - next request queue processed in 2000 msec, quiettime = 2000
2018-11-02 20:29:09.277 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x1A|LinkAddr:1E.04.61|LinkData1:0x01|LinkData2:0x1E|LinkData3:0x41|
2018-11-02 20:29:09.277 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (0): OUT:Cmd:0x6A|
2018-11-02 20:29:09.784 [DEBUG] [.internal.device.RequestQueueManager] - device queue for 33.83.16 is empty!
2018-11-02 20:29:11.278 [DEBUG] [ding.insteonplm.internal.driver.Port] - writing (500): OUT:Cmd:0x62|toAddress:33.83.16|messageFlags:0x0F=DIRECT:3:3|command1:0x19|command2:0x00|
2018-11-02 20:29:11.278 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x57|RecordFlags:0xE2|ALLLinkGroup:0x1A|LinkAddr:1D.C1.99|LinkData1:0x01|LinkData2:0x20|LinkData3:0x41|
2018-11-02 20:29:13.291 [DEBUG] [g.insteonplm.InsteonPLMActiveBinding] - got msg: IN:Cmd:0x50|fromAddress:33.83.16|toAddress:39.B3.99|messageFlags:0x20=ACK_OF_DIRECT:0:0|command1:0x01|command2:0xFE|
2018-11-02 20:29:13.295 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: FastOnOff
2018-11-02 20:29:13.295 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: RampRate
2018-11-02 20:29:13.295 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: LEDBrightness
2018-11-02 20:29:13.295 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: ManualChange
2018-11-02 20:29:13.297 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: ExtStatusGroup
2018-11-02 20:29:13.297 [DEBUG] [eonplm.internal.device.InsteonDevice] - ----- applying message to feature: GenericDimmer
2018-11-02 20:29:13.297 [DEBUG] [lm.internal.device.MessageDispatcher] - 33.83.16:GenericDimmer DIRECT_ACK: q:QUERY_PENDING cmd: 80
2018-11-02 20:29:13.297 [DEBUG] [lm.internal.device.MessageDispatcher] - changing key to 0x19 for msg IN:Cmd:0x50|fromAddress:33.83.16|toAddress:39.B3.99|messageFlags:0x20=ACK_OF_DIRECT:0:0|command1:0x01|command2:0xFE|
2018-11-02 20:29:13.299 [INFO ] [onplm.internal.device.MessageHandler] - DimmerRequestReplyHandler: set device 33.83.16 to level 100
2018-11-02 20:29:13.299 [DEBUG] [eonplm.internal.device.DeviceFeature] - 33.83.16:GenericDimmer publishing: 100
2018-11-02 20:29:13.299 [DEBUG] [lm.internal.device.MessageDispatcher] - defdisp: 33.83.16:GenericDimmer set status to: QUERY_ANSWERED
2018-11-02 20:29:13.299 [DEBUG] [eonplm.internal.device.DeviceFeature] - 33.83.16:GenericLastTime publishing: 2018-11-02T20:29:13

Weird 'eh?

Gunn · November 3, 2018, 2:54pm

So where can I find the source code for this binding? I may need to debug and figure this out, which I’m interested in doing…

notanatheist · December 20, 2018, 10:39pm

What version number is the sticker on the PLM? You want at least 2.1. Also, try another USB cable. I spent who knows how long troubleshooting a PLM that kept disconnecting and going from ttyUSB0 to ttyUSB1 just to find out it was the darn cable.

Gunn · February 8, 2019, 2:17am

Sorry for the late reply.

The sticker on the bottom of the Insteon Hub shows:

Rev 1.4 - 3114

I don’t have a USB cable on mine; it is just a power cord and an ethernet cable going to a router/switch. (And I did replace the ethernet cable, no change). I’m assuming you have a USB modem. I have the Hub…

Still have the same problem, but recently purchased a new Hub. But I’m not looking forward to replacing it. Insteon makes it as hard as it could possibly be!

Thanks,