Insteon Binding (Beta) [3.3.0;3.5.0)

[jeshab (Jeremy)]

@LORDUDE

For the devices OFFLINE in Openhab it says the devices are not int he database however they are linked

Could you please provide the product reference from your offline device? What do the new binding logs show when the modem database is getting downloaded?

@LORDUDE

All the devices with config pending are old devices that are not dual band, that is the only thing in common.

Same question for this one. The binding seems to not be able to get the product info from these devices.

Also, do you have both modems configured in openHAB at the same time? Are you running another third party application while the binding is connected to your PLM or Hub modems?

[LORDUDE (Harry Gomez)]

@jeshab

Could you please provide the product reference from your offline device? What do the new binding logs show when the modem database is getting downloaded?

Is there a way to get this from the old binding? I just spent all the morning switching to the old binding? I can restore from backup and test bot not today - below is what HA list

CONFIG:PENDING
15.63.AF KeypadLinc On/Off 2486SWH6 (0x02, 0x0f)
17.96.4A Keypad Countdown Timer 2484DWH8 (0x01, 0x05)
24.F0.F1 KeypadLinc On/Off 2487S (0x02, 0x2c)
14.6D.A6 SwitchLinc Relay with Sense 2476S (0x02, 0x15)

Not found in database - i have 4 of them the other two work without issues
15.97.4D OutletLinc Relay 2473SWH (0x02, 0x08)
15.97.5A OutletLinc Relay 2473SWH (0x02, 0x08)

@jeshab

Same question for this one. The binding seems to not be able to get the product info from these devices.

Also, do you have both modems configured in openHAB at the same time? Are you running another third party application while the binding is connected to your PLM or Hub modems?

No other software is talking to the PLM/HUB- when I test Home Assistant or use insteon-terminal I shut down OpenHab

[jeshab (Jeremy)]

@LORDUDE

Is there a way to get this from the old binding?

If you are referring to logs, you should have rolled over logs from this binding. Otherwise you would have to test again.

[LORDUDE (Harry Gomez)]

@jeshab You mentioned you are working on a newer rev with improved communication, let me know when you have that version ready for download and I will give it a try. I have another PLM I was going to try playing with OH4.0M1

[Tim_Davis]

Good work @jeshab Got my first Insteon Smoke Bridge → Battery Low Channel ON today !, I wouldn’t have known due to the First Alert fire detector randomly speaking at 3:30 AM, my wife heard it but I was sound asleep, I checked the Smoke Bridge and it’s Low Battery Channel is ON as expected, now a notification via openHAB → Alexa will work awesome !.. I kinda forgot to make an Alexa Reminder but am right now !

FYI: I purchased a NEW USB PLM from Insteon a few weeks ago to play with, just haven’t plugged it in yet

[CRC (Charles Cowan)]

Jeremy:

Are you still working on this binding? Will it be included in the OH4 release?

Thank you.
Charles

[jeshab (Jeremy)]

Sorry for the delay. I finally got around and pushed a new version for OH 4.1 and above which includes a lot of new improvements. Feel free to test it out. No new version will be released for OH 3.x.

Insteon Binding (Beta) [4.1.0.0;4.3.0.0)

[logo] This is a rewrite of the Insteon binding adding some much needed improvements. Apart from simplifying the user experience by retrieving all the configuration directly from the device when possible, and improving the way the Insteon things are configured in MainUI, here is an exhaustive list of the changes: Introduced device configuration automated determination Converted mode-based number items to string type with descriptive states Added number items uom support Added scenes and X10 …

[CRC (Charles Cowan)]

Jeremy:

That’s great news! Any recommendations on the best way to migrate to the new binding?

Thanks, and I appreciate the hard work.

Charles

[jeshab (Jeremy)]

@CRC

Any recommendations on the best way to migrate to the new binding?

In terms of deployment, assuming you are running OH 4.1 and above, you would have to first uninstall the official Insteon binding and then install the new version from the marketplace.

As far as configuration, if you are looking to take a peek at the new binding, you can leave your existing Insteon-related things untouched (they would appear in unhandled status).

Once you setup the relevant bridge and the binding is able to connect to your modem, it will automatically discover the devices and product information configured in your modem database. Any battery operated devices will need to be woken up (by pressing on set button or forcing an event trigger) to speed up the discovery process.

At that point, you should be able to add the discovered device things and start linking the relevant channels to your existing items. Keep in mind, that the binding downloads the link database for each device you will add. However, that process only happens once as the binding caches all this information including the initial modem database download. You can manage all this through the OH console if necessary such as forcing a given device or modem to reload its database for example.

For more details, I would recommend going over the updated documentation. The link is in the new thread I posted above.

[CRC (Charles Cowan)]

Thank you so much for your reply. I’ll do a backup and give it a try!

[LORDUDE (Harry Gomez)]

I see the new binding rolled out with OH 4.3 is there an advantage to converting everything from device-legacy to new device? Is there an easy way to do it using config files?

[jeshab (Jeremy)]

@LORDUDE

is there an advantage to converting everything from device-legacy to new device?

If you want to take advantage of the latest enhancements, you can refer to the migration guide.

@LORDUDE

Is there an easy way to do it using config files?

I would recommend using MainUI to discover and configured your Insteon things.

That being said, if you only want to use config files, you would link your existing Insteon bridge to one of the new ones based on your environment, and the associated device things under that bridge should migrate automatically (except the modem device which is now attached to the bridge).

Keep in mind only the address parameter is needed for the (new) device thing type. The binding will determine the rest.

For scenes, you would have to use the new scene thing type.

Finally, you will need to update your items and rules configuration with the updated channel names and, for some, item types.

[LORDUDE (Harry Gomez)]

Thanks - I will git it a try - BTW - Great job on the seamless implementation!!!

One last item, I do get an error once in a while when I reboot my server (not often) with one of my keypad’s switches that show online but without channels. I have not reported because I cannot reproduce it consistently - it does not happen on every reboot.

[jeshab (Jeremy)]

@LORDUDE

One last item, I do get an error once in a while when I reboot my server (not often) with one of my keypad’s switches that show online but without channels.

Could you provide the error details and the keypad model in question? Have you tried to remove it and recreate the thing possibility using a different ID?

[LORDUDE (Harry Gomez)]

Device is a On/Off Keypad configure as productKey=“F00.00.14”. The errors I see in the logs is

2024-12-15 14:11:01.025 [WARN ] [.core.thing.binding.BaseThingHandler] - Attempt to update thing 'insteon:device:homeusb:frontlghtkp' with a thing containing invalid configuration 'Configuration[{key=address; type=String; value=24.F0.F1}, {key=productKey; type=String; value=F00.00.14}]', blocked. This is most likely a bug.

I’m in the process of converting everything from device-legacy I’ll let you know if I see the issue again. It only happens randomly when I reboot and I reboot my server about once a month.

regards
harry

[jeshab (Jeremy)]

As I mentioned above, only the address parameter is needed for the (new) device thing configuration. You would need to remove the productKey parameter from your thing config file.

However, this error wouldn’t explain why your keypad shows online with no channels.

Could you run the below console commands and provide the output?

insteon device listFeatures 24.F0.F1
insteon device listProductData 24.F0.F1

[LORDUDE (Harry Gomez)]

Here is the output

openhab> insteon device listFeatures 24.F0.F1
The features for device 24.F0.F1 are:
beep: type=Beep state=NULL isHidden=false
buttonA: type=KeypadButton state=OFF isHidden=false
buttonB: type=KeypadButton state=OFF isHidden=false
buttonBeep: type=OpFlags state=OFF isHidden=false
buttonC: type=KeypadButton state=OFF isHidden=false
buttonConfig: type=KeypadButtonConfig state=BUTTON_6 isHidden=false
buttonD: type=KeypadButton state=OFF isHidden=false
databaseDelta: type=DatabaseDelta state=NULL isHidden=true
insteonEngine: type=InsteonEngine state=NULL isHidden=true
lastHeardFrom: type=GenericLastTime state=2024-12-20T23:10:34.366-0800 isHidden=false
ledBrightness: type=LEDBrightness state=NULL isHidden=false
ledOnOff: type=OpFlags state=ON isHidden=true
ledTraffic: type=OpFlags state=OFF isHidden=false
offMaskButtonA: type=KeypadButtonOffMask state=NULL isHidden=true
offMaskButtonB: type=KeypadButtonOffMask state=NULL isHidden=true
offMaskButtonC: type=KeypadButtonOffMask state=NULL isHidden=true
offMaskButtonD: type=KeypadButtonOffMask state=NULL isHidden=true
onMaskButtonA: type=KeypadButtonOnMask state=NULL isHidden=true
onMaskButtonB: type=KeypadButtonOnMask state=NULL isHidden=true
onMaskButtonC: type=KeypadButtonOnMask state=NULL isHidden=true
onMaskButtonD: type=KeypadButtonOnMask state=NULL isHidden=true
ping: type=Ping state=NULL isHidden=true
programLock: type=OpFlags state=OFF isHidden=false
switch: type=GenericSwitch state=OFF isHidden=false
toggleModeButtonA: type=KeypadButtonToggleMode state=NULL isHidden=false
toggleModeButtonB: type=KeypadButtonToggleMode state=NULL isHidden=false
toggleModeButtonC: type=KeypadButtonToggleMode state=TOGGLE isHidden=false
toggleModeButtonD: type=KeypadButtonToggleMode state=NULL isHidden=false
openhab>

openhab> insteon device listProductData 24.F0.F1
The product data for device 24.F0.F1 is:
deviceCategory:0x02
subCategory:0x2C
description:KeypadLinc On/Off Switch 6-Button
model:2487S
vendor:Insteon
deviceType:SwitchedLightingControl_KeypadButton6
firmwareVersion:0x41
hardwareVersion:0x69
openhab>

[jeshab (Jeremy)]

These look good. So it might be an issue with the thing type. How did you configure this device thing? As I mentioned above, have you tried to remove it and recreate it possibility using a different ID?

[John_Siemon]

@jeshab nice job on the binding update. I’m still using an UD ISY994i for my Insteon installation, but I am looking to move to using openHAB and your binding. I have no issue using the updated binding but I was wondering if there is any way to do a backup and/or restore of the PLM using the UI or console from within openHAB. This is a critical feature for me given how in past the PLM’s were prone to failures. I’ve looked at using the insteon-terminal for this feature, but was not able to get a connection to the 2413S PLM even after multiple tries and adding the device.py. I have no issue connecting with your binding, so is the a current or planned feature for the Insteon binding?.

[jeshab (Jeremy)]

@John_Siemon

I was wondering if there is any way to do a backup and/or restore of the PLM using the UI or console from within openHAB.

There is no direct feature to do so as of yet but I certainly can add console commands to backup/restore a modem and device database to/from a file in the future.

The only way currently would be to list the existing records using this console command:

insteon modem listDatabase --records

and, after you reset your PLM, re-add each record depending on their type using this command after your PLM is reset:

insteon modem addDatabaseController <address> <group> <devCat> <subCat> <firmware>
insteon modem addDatabaseResponder <address> <group>