elvisimprsntr

Thanks ATT. This is how I send notifications on certain events (alarm, doorbell, left garage door open at night, etc.) effectively acting like push notifications.

For the record page 386 (PDF sheet 399) has the schematic and pin-out. https://cache.insteon.com/developer/developer-guide-022009-en.pdf

Use an ohm meter to compare the pinout of the two sets of DE9 to RJ45 cables. I suspect the new cables are a standard Cisco serial console cable, which is not compatible with the serial PLM, and our mutual friends at the new Insteon don't know or assumed users would know. In which case, you can continue to use the old cables or cut off the RJ45 and re-terminate with the correct pin-out.

Likely related to Alexa+ rollout, Amazon's new AI powered assistant. I suspect the existing platforms are not powerful enough to do it locally. https://www.amazon.com/dp/B0DCCNHWV5

@Rapidway Excellent job. Just be careful what you use to control a GD. In my experience, the IO Linc reliability was not sufficient to connect to a GD controller, especially with a wall transformer right next to the IO Linc

Have you confirmed you previously configured the ISY to use a static IP? If so, your ISY has a static IP on a completely different subnet from your new ISP gear. You need to use one of the methods above to change the ISY to use DHCP, or set a static IP, subnet mask, gateway, and DNS aligned with your new ISP gear. If not, have you performed a network scan or logged into your new ISP gear to see what IP address was assigned? Or you may need to clear your Java cache to force the ISY launcher to stop looking for the old IP address.

Or connect up the serial console cable. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Quick_Start_Guide Then you can check/change the IP configuration. Personally, I prefer DHCP and use static reservations in my pfSense firewall. Another option would be to connect the ISY99 LAN connection directly to a computer, then assign the computer a fixed IP address on the same subnet. Then you can log into the admin console and make a backup and change IP settings.

Inductive current sense relay. They come in two flavors. NO and NC. https://www.amazon.com/dp/B07SFWWPP7 I have one wired to an Elk zone to detect when my video doorbells are pressed

@Brian H As stated, 2412S PLM. No changes to Insteon device is 5+ years. Nor any additional noisy PWM power bricks.

It’s powered by the PLM.

I’ve had my ISY99 then ISY994 in service for more than a decade connected to a serial 2412S Insteon PLM. The ISY is powered by the PLM. Except for Insteon in wall and plug in module high failure rates [emoji3525], the ISY and PLM duo have been seemingly rock solid until recently. In the past weeks the ISY randomly stops responding and the activity lights are off even when the power light is on. When I disconnect and reconnect power it starts working again for a few days. I don’t think it’s due to a power glitch on my mains since I get instant notification from my UPS when a glitch occurs. Many moons ago, I bought a second hand ISY-994 with a ZW 500 module, since those were no longer available for purchase, so I could upgrade to the latest firmware. I know UDI no longer provides support for the ISY, but I am not ready to migrate to the eISY. I just don’t have the desire or bandwidth. I was wondering if someone else has experienced similar symptoms and/or what they did to resolve it, or any suggestions. I did make a recent backup of my ISY config JIC. 1. Is the SD card going bad? If so how can I replace? 2. Is the PLM suspect? 3. Is the ISY itself going bad? My recollection is the second hand ISY I purchased does not have all the module licenses activated. I recall at one time UDI would migrate licenses to a different device for a small fee. Not sure if that is an option anymore.

Spammers were using bulk email to sms/mms. My guess is ATT is trying hard to detect and block this sort of abuse, which may have the unintended consequence of blocking legitimate use of the feature. We can all thank ATT for releasing all our sensitive information. https://www.bleepingcomputer.com/news/security/att-now-says-data-breach-impacted-51-million-customers/

The jury is still out, but from everything I read it is legit.

BACKGROUND There are some major projects that actively contribute to FreeBSD, which are moving from FreeBSD to Linux. 1. iXsystems is already recommending TrueNAS SCALE for new deployments, as new features will likely only be developed for SCALE. https://www.truenas.com/compare/ 2. Netgate posted a blog about the future of pfSense. Initial reactions were this was an Aprils Fools joke, but turns out they are serious. https://www.netgate.com/blog/pfsense-software-embraces-change-a-strategic-migration-to-the-linux-kernel There also seems to be a decline in large doners. https://freebsdfoundation.org/our-donors/donors/?donationYear=2024 QUESTION With the rapid industry shift away from FreeBSD, and likely less contributions to FreeBSD, what are the long term prospects of a FreeBSD based EISY?

I am not familiar with details of the E27. You would have to reach out to UDI or Elk directly for that.