RKenny02

So I finally got everything resolved, it seems in the switch over the old PLM module died, I setup the new PLM on the old e-isy and was able to do a backup again and start the migration process, everything is now working. A few switches had to be reset as well but after a few days now everything seems to be properly communicating.

I actually tried that first moving the PLM without a factory reset but the new eisy v2 consistently reported 'PLM not connected'. I tried multiple reboots and different USB ports, but since nothing worked, I assumed a PLM factory reset was the best path forward. I’m now at the point where I’ve tried three different PLMs, performed hard resets on the switches, and ran the restore commands inside the Admin Console, yet the issues persist. I’m almost ready to just screenshot all my device settings, factory wipe the eisy v2 and the PLM, and manually rebuild the entire network from scratch. It sounds like a massive pain for 40–50 devices (with another 15 still to add), but I'm running out of ways to diagnose this. I previously migrated from the ISY-994 to the first eisy version without any issues by just swapping the controller, but that same scenario clearly isn't working this time around. now my next question is do i go back to my orignal PLM with the ethernet to USB adapter since i have 2... or do i swap right to the new USB model, not sure there's an advantage over the new USB one besides it being newer...

hen migrating from my eisy v1 to the v2, I initially performed a factory reset on my original PLM. However, after multiple reboots and troubleshooting steps, the eisy v2 would not recognize the original module. I then connected a brand-new USB PLM (2413U), which the v2 detected immediately. I proceeded to restore my v1 backup onto the eisy v2 and ran a PLM Restore. While everything initially seemed to work, I noticed after a few days that several switches were failing to sync status back to the eisy. Commands and scenes triggered from the interface work fine, but it has become a "one-way" communication issue. Watching the Level 3 Event Viewer diagnostics while manually toggling a switch shows no activity, and the eisy status does not update. I have already tried factory resetting several switches and running the Restore Device command within the eisy, but the issue persists.

looking for some input if anyone has run into this issues with any of there migrations, i opened a ticket with support and got the generic link to the wiki... which i've tried in my orignal migrations and still not having any success, hoping that someone here might be able to share there experiences if they were similar Issue Summary: I recently migrated from an eisy v1 (which was stable for years) to a new eisy v2. Since the migration and backup restore, I have been unable to achieve stable two-way communication, despite testing three different PLM units and moving the controller to multiple physical locations. Detailed Timeline: Initial Migration: Upon the first restore to the eisy v2, the original PLM (2413S with the serial-to-USB adapter) was not recognized at all. Despite multiple reboots and full factory resets of the PLM (holding the set button until the beep stopped), the eisy v2 would not acknowledge the hardware. New Hardware (2413U): I purchased a brand-new USB PLM (2413U). The eisy v2 discovered this unit immediately. I performed a Restore Modem, and while the system appeared to function initially, I began experiencing "one-way" communication issues. Linking Failures: Multiple existing switches stopped reporting status updates to the interface. Furthermore, when attempting to add a new KeypadLinc, I consistently received the error: "Cannot determine device link table address". Isolation Testing: I attempted to "Restore Device" on several switches; however, the communication was too unstable to complete the writes. I physically moved the eisy v2 and PLM to a different part of the house to rule out local interference, but the "Reason 9" timeouts and status update failures persisted. Regression Test: I attempted to revert to the original PLM and even a third, brand-new-in-box 2413S unit. The eisy v2 continues to fail in recognizing the older serial units and maintains unstable communication with the USB unit. Request: Because this mesh was 100% stable on the eisy v1 and the issues persist across multiple PLMs on the v2, I suspect a hardware defect in the eisy v2's USB bus or a corruption in the migrated link database.

This situation is extremely frustrating. My eISY has been operating without portal access for a long time, and I’ve always used it internally. I technically have portal access, but I never use it. For the past week or two, the device has been prompting me to update, so today I finally went through with the update. After doing so, I was suddenly required to log in through the portal. I normally access my device using the ISY Finder Java application, so I wasn’t even sure what my portal login was. I tried resetting the password multiple times. Since it’s tied to a Gmail address, it took almost an hour and several “forgot password” attempts before I finally received a PIN code. Why is the company forcing users to log in through the portal? I didn’t purchase this device to rely on a cloud service or to incur additional subscription costs. I bought it specifically to manage my Insteon switches locally. It now feels like users are being pushed into needing a portal subscription.Is there any way to downgrade the firmware back to a version prior to 6.x? I used to recommend this product to all my customers with Insteon systems, but that will change if this direction continues. At this point, it feels no different from the companies we’ve tried to avoid.

Thanks for all your help this is a weird one I've never reached out for help on any other issues before but this one is strange for sure. Thanks

static ip or reservation I've tried both no difference, reservation is giving out 9.9.9.9 and 8.8.8.8 for primary and secondary DNS. if i set the static ip I've also set both of them and no difference, no Suricata or pfBlocker, pfsense hasn't been updated in that time frame.

one is pfsense the other one is the ubiquiti dream machine pro. the odd part is it works for the first 2-3 hours i can open/close doors and get notifications or can hammer the test email button and also consistently get the email notifications. There's no outbound blocking on either firewall.

the 2 GWs don't make a difference, this has worked for years with this setup i have a router at .1 (iwith ISP ip)and and router at .2(with different ISP ip) i flipped the isy over from .2 to .1 to see if it was the router/GW causing issues and no difference.

logs seem to be useless based on the last few entries B-SHWM-F Status Off Thu 2020/07/09 11:40:05 AM System Log B-SHWM-F On Level 100% Thu 2020/07/09 11:40:05 AM System Log B-SHWM-F Ramp Rate 28 Thu 2020/07/09 11:40:05 AM System Log Get NodeDef ZWave 0 Thu 2020/07/09 11:48:26 AM System Log Front - Door Sensor Status On Thu 2020/07/09 02:13:07 PM System Log Front - Door Sensor Status Off Thu 2020/07/09 02:13:11 PM System Log Front - Door Sensor Status On Thu 2020/07/09 02:18:48 PM System Log Front - Door Sensor Status Off Thu 2020/07/09 02:19:05 PM System Log Front - Door Sensor Status On Thu 2020/07/09 02:36:29 PM System Log Get NodeDef ZWave 0 Thu 2020/07/09 02:38:00 PM System Lo the front door sensors is what i have triggering emails on open and on close

in the from feild: ISY Controller:email@gmail.com upon the last reboot it worked for appox 2 houts and just now i tried the test email again and its giving the TLS errors again

I've looked at this post previously it seems related to domains and not the generic gmail accounts. all the info related to gmail accounts still uses the smtp.gmail.com with 587 port for TLS

have been using the google DNS of 8.8.8.8 since i set it up years ago, and it worked for years only in the last 2-3 months has this issue come up, i've flipped it just now to 9.9.9.9 just because and it works after the reboot but it always works after a reboot so i'll have to give it some time

I've tried everything except a new account, i have multiple gateways and have even switched it to a totally different gateway same issue, if i try port 465 i get no response 465 being SSL vs TLS port is 587. I've also rebooted the GWs and don't have any 2FA turned on on this account, rebooting the ISY it starts to work again its working now but not sure for how long before it stops again. i'll try to setup another account but it seems its something more related to the device, i'm wondering if i factory rest the ISY and restore from my backup, i read that a factory reset is the absolute last step but if i have a valid backup and it restores all my config why it wouldn't hurt, just makes no sense that after a reboot on the isy it functions normally for a period of time then stops

I've tried that in all my testing no difference

I currently use gmail for my email notifications, everything was working for years, all of a sudden the notifications stopped, i cheeked all the settings on the gmail side and nothing has changed,, if i reboot the ISY994i the email notifications will work again for a few hours, but after that they stop working another reboot and they work again so all of the settings are correct just not sure why after a few hours of up-time on the isy he emails stop, if i run the email test i get the following error. I've tried to increase the timeout on the smtp settings to 5000 as others had suggested that in the fourm but same issue here is a picture of my email settings *** being a valid email address isy info... Thanks