elvisimprsntr

I don't have an eISY (MeLE Quieter3Q), but do have a MeLE Quieter3C running Ubuntu with Homebridge. The cooling fins on the top of the unit are plastic, not aluminum. I simply mounted it to the back of a monitor with a VESA mount. Hasn't been a problem after 2.56 years. root@mele-ud22:~# sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +49.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +41.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +41.0°C (high = +105.0°C, crit = +105.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +119.0°C) nvme-pci-0200 Adapter: PCI adapter Composite: +41.9°C (low = -0.1°C, high = +84.8°C) (crit = +94.8°C) Sensor 1: +41.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +46.9°C (low = -273.1°C, high = +65261.8°C) Sensor 8: +41.9°C (low = -273.1°C, high = +65261.8°C) root@mele-ud22:~# nvme smart-log /dev/nvme0 Smart Log for NVME device:nvme0 namespace-id:ffffffff critical_warning : 0 temperature : 42 C (315 Kelvin) available_spare : 100% available_spare_threshold : 5% percentage_used : 11% endurance group critical warning summary: 0 data_units_read : 1,495,531 data_units_written : 41,693,437 host_read_commands : 21,305,919 host_write_commands : 1,899,017,040 controller_busy_time : 1,898 power_cycles : 36 power_on_hours : 22,418 unsafe_shutdowns : 12 media_errors : 0 num_err_log_entries : 1,098 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 42 C (315 Kelvin) Temperature Sensor 2 : 46 C (319 Kelvin) Temperature Sensor 8 : 42 C (315 Kelvin) Thermal Management T1 Trans Count : 0 Thermal Management T2 Trans Count : 0 Thermal Management T1 Total Time : 0 Thermal Management T2 Total Time : 0 Not sure if the eISY comes with the original warning label on it, but here is a pic from a 3Q review.

Correction: "... older products that did not have a subscription based business model are now e-waste." Thats the dilemma. Adopt a new product/technology that does not have a sustainable business model and you get left holding the bag. Just ask anyone who purchased Sonos gear.

Skills working again as of 21:00 EDT

All skills are not working. https://downdetector.com/status/amazon-alexa/

@apostolakisl Serial PLM uses non-standard pinout. The one UDI sells is a modified off the shelf cable. https://www.universal-devices.com/product/serial-plm-kit/ Or you can make your own.

I have an adjustable inductive current sense relay on my doorbell transformer to detect when a video doorbell is pressed, which is wired to an Elk input zone. Note: The ELK-930 doorbell/ring detector only works on traditional mechanical doorbell chimes and is not user adjustable. I use the Elk zone to trigger the exterior lights on for 30 seconds when a doorbell is pressed. I also have an ISY program to continuously flash the exterior lights if the Elk alarm is set off or one of the keypad panic buttons is pressed to help emergency responders quickly narrow down which house.

Apparently, Notifyre touts its self as an alternative. I tried to register, but apparently you need an employer EIN. I think it is geared more towards enterprise. Pushover seems to be the best and most cost effective alternative. 30-day free trial and $4.99 one time license per platform. Already updated my ISY and Elk to use Pushover.

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.

@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.

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/

I spun up my own instance of Homebridge and connected it to my ISY, Elk, and cameras. Works automatically! Theoretically is should work with the eISY.