Michaelco

So, how would I know if the Restore Modem(PLM) worked correctly when I relied on plugging in the PLM at the time of the EISY reboot? Is repeating Restore Modem(PLM) with unplugging the EISY, feasible and useful to correct any issues if I hadn't plugged in the PLM in time?

Thanks for the instructions. I just finished swapping out the the PLM, and checked the operation of a number of devices. So far, all devices are working correctly, and the EISY is logging in complete device communications. The only substitution I did to the procedure in the pdf you provided was to reboot the EISY instead of pulling power. I'm surprised the process suggest to remove power.

I have a spare on hand, and latest backup is current. Just want to make sure I swap out the PLM in a reasonable way.

It's more than 5 years old, probably closer to 10. I see instructions on replacing a PLM connected to an ISY. The guide for the EISY has a link pointing to the ISY instructions which starts by saying "Unplug ISY from the power outlet" - this works for an ISY, but is problematic with an EISY. So, I'm thinking of Disconnecting the old PLM from the EISY, Unplug old PLM Plug in the new PLM, but don't initially connect to EISY Reboot the EISY, Connect the EISY to the new PLM Restore Modem(PLM) from the Admin Console "File" menu Is there a better way to replace a PLM with EISY?

Thank you for the suggestion. Where is the setting to disable automatic write to battery devices? And, can I restore a single device. Thought I could have restored one of the devices not having the behaviors programmed, and not have to worry about the battery'd device issue. But, not sure a restore can be done on a single device - can it? My hesitation is because of the confirmation dialog. When I select "Restore Device" from the context menu (while on a device I want to restore), I get a confirmation dialog (attached) which says it will reprogram your INSTEON Devices using the settings stored in loX. Is it just the selected device, or all devices. I know I can select multiple devices and choose "Restore Device" from the menu - then the reference to Devices (plural) fits what I'd be doing - but.

Thank you. I had unplugged the PLM, but only waited couple seconds before plugging back in. The plm is old enough that it could be it, but wouldn’t I have had a problem with the EISY communicating with the Insteon devices via the console, or UD Mobile? I don’t know the internals of the PLM nor how the table is structured/used, but I can control the devices from the console. I just unplugged the plm and waited around 30 seconds - still no entries PLM Links Table. Before doing the plugging/unplugging I tried to control the kitchen lights via the console and noticed the device status didn’t show the lights being on, even though they had turned on. I retried this after plugging the PLM back in, and the status reflected correctly. So, I’ll try a new PLM - is it as simple as choosing “Restore Modem(PLM)” from the file menu?

Problem extends to a number of Insteon devices no longer working as they have for years. The first device which I noticed not working correctly yesterday was the Insteon 2455 I/O Linc. I'm using it on an entrance gate - the input monitors the safety and exit loops change of state, and the output controls opening and closing the gates remotely. I had thought it was failing, after seeing odd behavior - no longer getting indications when someone drives over the loops - I can open and close the gates using UD Mobile, but even the closing behavior is odd. The gates close, but a few minutes later they reopen. I was going to replace the I/O Linc today, until I saw other things not working correctly. Last night I turned on the outside lights. I use the Insteon 2477D SwitchLinc Dimmer, to turn on the Entry Porch lights. I have EISY code to turn on other outside lights if the Entry Porch light SwitchLinc is pressed two times within 3 seconds. This no longer works - the entry porch light turns on, however the other lights that would normally come on with a second tap of the rocker switch, ... don't. I have another switch that controls lights in the kitchen which uses the same function - i.e., a single tap of the switch rocker turns on the light that's connected to the switch, but the second tap is ignored. I looked at the event log, and the switch actions don't appear when operating either the porch switch, or the kitchen switch. The even log shows switch activity when I turn on the switch via UD Mobile. Another oddity occurs when I access menu item from the ISY Console "Show PLM Links Table". It's been a while since I've used it, so I may not be doing something correctly, but nothing is displayed when I click on the Start button. I could believe there is a problem with the PLM, but even this doesn't explain the situation - as, I have control of all the switches via UD Mobile. Any help on this would be appreciated.

Thank you

Thanks - made purchase - wish there was a quicker way to locate and change all of the vText lines of code - bit cumbersome to change 50+ vText notifications to push notifications. Is there a faster way to accomplish?

Thank you for the links/info - I changed a few of the places where I was using vText, to the push notifications with no - i.e., using the Notification plugin (free version). How do I purchase the standard version of the plugin? I thought possibly via the menu selection "Launch Polyglot V3", but when I selected the menu item, the "Connecting is Not Private" message made me doubt this was the way to make the purchase.

I started playing with the Notification Plugin to get away from issues using vText service. I can set a push notification when a device changes state, ... but can I set the notification when either a program is executed, or a variable changes state? Can the Notification Plugin handle this approach, or is it limited to trigger a notification when a device status changes? For example, I currently send a notification when someone stops at the gate for more than 20 seconds (code StoppedAtGate below). Recently delays using vText, occasionally fail to arrive on time - a few times, they arrived over 12 hours after the fact - not real useful. What's the best way to implement push notification for this type of situation? I didn't see a way to add a notification for variable change of value (like intTotStoppedAtGate), nor execution of a program (like StoppedAtGate(Then)). I would like to replace the "Send Notification" in the StoppedAtGate code, using a push notification. Is this possible? Michael ============ Example Code ========== StoppedAtGate - [ID 002B][Parent 0001] If 'Gate Operator Safety Loop Sen' Status is On Then Wait 20 seconds $intTotStoppedAtGate += 1 Send Notification to 'TextMichael' content 'Someone At the Gate' Run Program 'FlashLight' (If) Else - No Actions - (To add one, press 'Action') Increment the intTotStoppedAtGate counter if the Gate outside safety loop sensor is still "on"after 20 seconds. The 20 second filter ignores people turning around at entrance, and allows notifications when a delivery has been made ======================

Thanks, I'll give that a try

Ever since upgrading to the EISY, I have noticed a couple issues that happen from time to time. I have logic to send a text if an outdoor light is turned on during the daytime - this was to provide a warning if someone mistakenly turned on a light during daytime. After getting the EISY, around 15% of the time, I will get a text saying the path lighting was turned on during daytime. I will delay the time the path lighting comes on by a minute to avoid this message, but wonder whether the problem occurs now do to EISY's faster processing. A second situation which has cropped up since getting the EISY is where I use light switches to turn on more than a single gang of lights. For example, when I tap the porch light switch once, it turns on the porch light. Tapping it twice within a 3 second period turns on additional lights around the house, and the driveway lights. Similar type of approach to turn on the kitchen lights. I wonder if this is a contact bounce issue where the EISY is just fast enough to see any contact bounce as a separate switch press. Thinking of adding logic to ignore a second switch press if it occurs before 1/2 second since first press. Has anyone noticed similar situations, and have a more elegant solution?

Have you closed and restarted UD Mobile app after making the changes to Span? I just tried changing the Span to 4, and had to restart the app to have the change reflected in the Favorites view

I didn't make any changes to the Favorite's Span - went with whatever the default setting. I am using IOS devices, ... if that makes a difference.