Insteon not pulling db from new modem

Add-ons Bindings
1

My old modem died so I bought a new one, this time a 2245-222 I wiped my house and reprogrammed ALL 117 devices (moved so to Z-Wave so I have less now), but I can’t pull db at all. Any ideas?

2017-04-22 13:20:36.183 [InsteonPLMActivator ] - Insteon PLM binding has been started.
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - poll interval set to 1800000 per config file
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - setting modem db retry timeout to 40s
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - dead device timeout set to 18000s
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - config: poll_interval -> 1800000
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - config: modem_db_retry_timeout -> 40000
2017-04-22 13:20:36.998 [InsteonPLMActiveBinding ] - config: port_0 -> /hub2/Rebellio:vv7AU6Ug@10.88.64.100:25105,poll_time=1000
2017-04-22 13:20:37.002 [InsteonPLMActiveBinding ] - devices: 0 configured, 0 polling, msgs received: 0
2017-04-22 13:20:37.009 [InsteonPLMActiveBinding ] - config: service.pid -> org.openhab.insteonplm
2017-04-22 13:21:17.049 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:21:34.439 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:21:34.439 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:21:34.439 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:21:57.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:22:37.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:23:17.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:23:57.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:24:37.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:25:17.050 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:25:57.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:26:37.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:27:01.785 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:27:01.785 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:27:02.599 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:27:17.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:27:57.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:28:37.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:29:17.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:29:32.923 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:29:32.923 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:29:32.923 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:29:57.051 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:30:37.003 [InsteonPLMActiveBinding ] - devices: 117 configured, 0 polling, msgs received: 855
2017-04-22 13:30:37.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:31:17.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:31:37.341 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:31:37.341 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:31:37.341 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:31:57.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:32:37.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:33:17.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:33:57.052 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:34:37.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:35:17.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:35:57.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:36:16.242 [MsgFactory ] - got unknown command code 0x6A
2017-04-22 13:36:16.242 [Port ] - bad data received: got unknown command code 0x6A
2017-04-22 13:36:16.242 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:36:37.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:37:17.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:37:57.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:38:37.053 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:38:51.566 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:38:51.566 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:38:51.566 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:39:17.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:39:17.683 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:39:17.683 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:39:17.683 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:39:57.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:40:37.003 [InsteonPLMActiveBinding ] - devices: 117 configured, 0 polling, msgs received: 805
2017-04-22 13:40:37.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:41:17.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:41:57.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:42:37.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:43:17.054 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:43:57.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:44:37.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:45:13.680 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:45:13.681 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:45:13.681 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:45:17.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:45:48.303 [MsgFactory ] - incoming message does not start with 0x02
2017-04-22 13:45:48.303 [Port ] - bad data received: incoming message does not start with 0x02
2017-04-22 13:45:48.916 [Port ] - got bad data back, must assume message was acked.
2017-04-22 13:45:57.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:46:37.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:47:17.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:47:57.055 [ModemDBBuilder ] - modem database download unsuccessful, restarting!
2017-04-22 13:48:37.056 [ModemDBBuilder ] - modem database download unsuccessful, restarting!

2

What’s the entry in your openhab.cfg look like? The number you give there (2245-222) is for a hub, no? If so, then you need a different syntax to connect to the hub, see documentation in openhab.cfg.

3

Sorry, I got the sku wrong, its a 2014 HUB, the issue was that I was not allowing enough time to download the db. On the old hub I could pull the db in 30 seconds so a retry of 40 seconds worked, but on the new 2014 HUB it takes much longer. I changed the retry to 5 min and it works fine.

4

BTW, if you have so many devices, it’s almost easier to repair the modem than to replace it, see

http://pfrommer.us/home-automation

In particular if you have saved the modem database beforehand so you can restore it. The modem failures are a well-known problem with the power supply. Replacing the capacitors should give you a more reliable device.

Bernd