doctorjerry

Thanks for the quick reply. This seems to be a section of the UDI forums where others using HA and Insteon have commented on the same issue. Hopefully someone with familiarity with both systems will pick up on my request for help.

I have an Insteon network of about 30 devices and a few Z-wave switches. I had solely used Insteon devices for years (99i and then 994i) until my PLM died and I couldn't find a replacement. With an Insteon Hub I was able get back into my network. I didn't know where Insteon was going and started looking for alternatives. I started using HA and added some Z-wave switches. The Z-wave switches are integrated directly in HA. Now with a new PLM I've retired the Hub and integrate Insteon into HA with ISY/IOX. I do like the HA front end for access to my setup by computer and mobile, but I'm unfamiliar with the programming. I use the accessory buttons of a Keypad to control other Insteon devices with scenes without a problem. Now I want to use a button to control a Z-wave switch. When I was using the Hub the accessory buttons showed up as devices and could easily be programmed as a trigger. But with ISY they are sensors and I have not been able to figure out how to use them as a trigger.

I haven't been able to get the additional buttons in a KeypadLinc to trigger. I tried to follow the suggested Isy994_control event example which in my case looks like this. - id: '1703200515964' alias: Shop Lights description: '' trigger: - platform: event event_type: isy994_control event_data: entity_id: sensor.basement_stairs_keypad_a control: DON value: 255 condition: [] action: - type: turn_on device_id: 73a0d20f1fa7802377822ce38c54a63f entity_id: 0ebda1d0dded7ce1564efdd14b7e8046 domain: light mode: single

I wound up factory resetting all my devices (one at a time), reinstalling and re-creating links and scenes. Well worth the effort as I now have a clean ISY setup that responds as expected. Also, ISY/Iox integration into Home Assistant is much better than the Insteon Hub integration. I do like using Home Assistant as a front end though I plan to try UD Mobile again. I went almost 2 years without a working plm and had to use the Insteon Hub. Hopefully never again.

Restoring device doesn't work. I'm not aware of an SD card in a 994i.

Tried to restore PLM with event viewer open at level 3. I've attached a copy of the log. I don't see errors, but there was no functional change. I have been successful restoring full function device by device by: 1. deleting all links to a device 2. deleting device 3. performing a factory reset on device 4. reinstalling device 5. reinstating all previous links Considering how well Insteon and ISY have worked for me for many years it's still worth whatever time it will take to do this. If someone can offer anything to simplify the process it is welcome. ISY-Events-Log.v5.3.4__Tue 2023.10.31 06.46.38 PM - Restore PLM.txt

I'm am experiencing the same problem. I have finally obtained a replacement for a failed PLM attached to an ISY994i. I followed the described procedure for replacing the PLM and restored ISY from the last good backup. All my devices are present and function from the AC but the AC does not update status when the devices are activated locally unless I do a Query. I have about 70 devices (only Insteon) and my PLM link database shows only 56 links. As suggested I will try both adding a new device and see if it functions properly and deleting and existing one and reinstalling and see how that works out.

Hope I don't annoy you MrWorf but having no experience with linux I'm not sure how to implement all the instructions as written. The changes to config.txt and cmdline.txt - I assume they are they made directly to the files on the SD card. Once this is done, the systemctl commands. Are they entered at the command line after the Rpi has booted and I log in? If so, do I have to re-enter them every time I reboot the Rpi.

I did miss that. Once installed I got this message This was with the serial console disabled and "dtoverlay=disable-bt" inserted at the end of config.txt. I then removed the line (just to see if it made a difference and got this: But when I rebooted the PLM it still went into Safe Mode :

After setting up an Rpi0 and TTL converter as described and connecting it to the ISY and PLM(2413U)I get this Any help would be appreciated. Jerome

I'll be attempting to build this. I have a PowerLinc V2 USB #2424U plm that I think came with my first ISY 99i. Do you think this will work like a 2413U the presently available USB PLM? Jerome

I've been using my old 99i controller without a problem until I tried to add a new 2477D dimmer version 8.2. Version 7.8 units were recognized but the 8.2 v units give a "cannot determine insteon engine error. Is this simply a matter of old and new incompatibility? Just want to be sure before purchasing a newer 994i. Jerome

I'm impressed with all the quick responses my simple question elicited. I'll take advantage and ask a followup. In 10 or more years using insteon modules/ISY this is the first time I've had to replace a module. Actually 16 switchlincs were fried after a momentary power outage/surge. This after what had to be hundreds of similar occurrences over the the years. Never thought about a whole house surge protector, but I am ready to install one. Can I expect this to make a difference?

Lee, I found that the new switch name disappeared and only the original switch name remained. It was preceded by an (!) exclamation. but with the new switch address and all the original links. After a write update the replacement was complete with no further need to change names.

A power surge has fried a few switchlincs. How do I substitute the replacement module to assume all the links of the bad switchlinc.

MFBra, Thanks, you got me over the hump and I've come up with a pair of programs that accomplish my goal. Most of the time I get only the one open message. But if I get two more open messages I can then close the door manually using Mobilinc. Program 'Garage ® Open1' If Control 'Wireless Sensors / Garage Door Sensor®-Opened' is switched On Then Send Notification to 'Text Message' content 'Garage Door Open' Wait 5 minutes Run Program 'Garage ® Open2' (If) Wait 15 minutes Run Program 'Garage ® Open2' (If) Send Notification to 'Text Message' content 'Diane's Garage Door Open' Wait 15 minutes Run Program 'Garage ® Open2' (If) Send Notification to 'Text Message' content 'Diane's Garage Door Open' Else - No Actions - (To add one, press 'Action') Program 'Garage ® Open2 If Status 'Wireless Sensors / Garage Door Sensor®-Opened' is Off Then Stop program 'Garage ® Open1' Else - No Actions - (To add one, press 'Action')

I have my program to notify me when the garage door opens and closes working well. But I'd like to refine it. When I enter or leave I get two messages, door opened then door closed. I'd like to avoid the door closed message unless it doesn't close within 5 minutes. Perhaps a timer that starts when the door opens and waits 5 minutes before sending a door open message. If the door closes within that time the timer stops and no message is sent. I have the idea, but no clue how to program it. Any help is appreciated.

I'll quote my favorite movie (Cool Hand Luke) ' What we got here is a failure to communicate'

I decided to try email to Smarthome tech support and did get a quick response as follows: Thank you for contacting Insteon. UDI did not get the update in time to add to the latest firmware release. The ability to set that will be in the next beta firmware release that they make. In the mean time, you can use programs to accomplish what you are trying to do until the update is pushed out.

Smarthome said the jumper has been eliminated and the change in mode is now done through software. They offered no help whatsoever in how to accomplish this. The phone rep seemed to know nothing himself, but relayed the message from someone else in "tech support". He did say that the Insteon Hub could not do it and knew nothing about the ISY. Then he quickly excused himself and said goodbye. I must say it was a miserable experience. Hopefully the savvy guys here can get further than I can.

Yes, the terminals are there. It looks just my other unit except for the missing jumper pins.

And the interesting thing is it seems to be registered in the default mode. I would have expected the multi-scene mode if the pins were just missing, because that would be like taking off the jumper. This is the event log for on and off 1. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] DOF 1 2. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] ST 0 3. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] DON 1 4. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] ST 255 And for future reference Lee, could you explain the 4 lines to me?

Unit say 4614REV 1.B In ISY v.43 No pins at all. Just the two empty holes in the board where they should be.

I just received a new 2843-222 open/close sensor. It has no jumper pins whatsoever. Is this some new version, or did I receive a bad unit? I called smarthome, but I got no answer. I thought I'd ask here before returning it.

Thanks