paulbates

There are AArch64 / Arm64 versions of Java for Macs.

If your router has logs I would look there. You might have to raise the log level to see each DHCP address assignment. Wait for it to happen again and go look there. The answer should be there. The factory MAC address for the EISY should be on it's case for reference.

No. The YoLink app is how you configure your devices. The app and the plugin point to the same YoLink cloud services You're certain that YoLink devices are active, updating and/or controllable from the polisy or UDM? What happens with the YoLink app? You can log in? Are there errors? What about the error log or event viewer, what do they say? Describe in more detail what's going on

Key pads are complex beasties. Mine would have odd behaviors sometimes and I'd have to reset every once in a long while. There was one 8 key that everything worked, other than sometimes the middle 4 buttons would blink in unison. Like 5 - 6 times. I don't think was it following traffic because it should have been doing it a lot more. It was rare and in a place hard to catch it doing it. Not even factory resettle totally made it stop.

If it's WiFi, is there a chance that the thermostat itself has WiFi/networking that locked up or has a problem? Can you reach it with an app if it uses that? (Or ping it or see it in your router) Can you restart it somehow (eg remove from its mount and reseat) to eliminate that as a possible cause?

The only time Insteon tried this was with the Smoke Bridge... many years ago. First Alert sold Smoke detectors under the Onelink logo that were proprietary RF and worked with the Smoke bridge, I had 3 of them. While there still are people using both products, neither is offered any longer. The Insteon Smoke Bridge was single band. I think First Alert sells under the onelink brand but for matter sensors and maybe zwave now. FWIW I moved my wireless sensors from Insteon to YoLink a few years ago. YoLink has Smoke & Smoke CO sensors. The YoLink hub can be connected to the Virtualarm service for central station monitoring.

One thing I know for certain, the responding to the dreaded "All On" function was removed from these devices. I tested it several times with the "All On" button on the bottom of iox's network view. All other devices came on and i3's did nothing. Things I did find about the i3's Like all Insteon devices, that can come with links already in them. I had to factory reset several of ~35 i3 paddles I installed over initial behavioral problems. Each i3 has a separate flags node with even more settings in them and sometimes they are set the opposite of what you think. As an example I have is an i3 paddle that was as far away as it can be in my house in terms of wire feet from the panel. It wouldn't respond 100%. Looked at the flags, and there is setting to turn OFF its RF??? Bizarre feature, but changing that solved it. I would pick one. Factory reset it, restore device. Check the Flags node and see if any settings look counter what they should be. Wait and watch.

If haven't opened them up, there's a fuse in there. They could have been used over their spec'd rating, possibly inrush current turning them on

There's complexity here in apple home publishing things to eisy and matter is still a little early on IMO. You could try unplugging and replugging. I'd start with apple home, and once its clearly back up, plug in eisy so it sees the running Apple Home Alos, eisy-UI now backs up everything including PG3X, where plugins like matter are defined. Had you made a backup recently? If yes, did you try a restore, which will bring that backup's pg3x back? I haven't tried it, but the latest release docs say you can do a selective restore; choosing to bring back plugins (pg3x) only and not other eisy components (iox, zwave, eisy-ui settings)

A year or more ago UDI removed the detail device activity database from the backup, and you are seeing the results. Its all good.

Me, being me, might try to create 'Rube Goldberg' version 🤪😂

Interested in this too. If the yolink hub and mouse trap are subtracted from the picture, the remaining device looks like the yolink vibration sensor, which makes sense that's how it would work; vibration from the trap snapping. The git for the plugin says the vibration sensor is supported.

Its waiting to pair new insteon devices when you go to them and press the set button. I'm not sure what the exact prompt is, but there is a button for Finish or somethign like that. Just click it.

I've had this too in the distant past but don't remember specific steps. Things I think it can be: Java is already installed – a conflicting or corrupted existing version - Try to hunt down and delete its files including the temp folder Not running the installer on an Administrator account - right click on the installer pick the install as admin Antivirus soft blocking the installation - but I would think you'd get a pop-up

I have experience moving the plm from one system and back to another. Have to be careful not to change anything. I'd find a way, a time to make the conversion one time DO NOT TRY TO USE 2 PLMs with the same Insteon network. "There can be only one" controller owner of an Insteon network

That is a sign of fading away. I've had cases where a device worked fine until I went to manage, like change a scene it was in, and it would beep and not cooperate. I'm guessing it's dying. You could open the event viewer level 3, exercise it from the switch and then try what ever is failing from iox and post it. There are members that are good are deciphering those that might help validate the dying assertion.

I think you recently migrated from a 994?. That's a sign that the SD card in the 994 you came from was failing and the file was damaged. In that case symptoms like these are plausible, and remove/reset/rebuild is the answer Glad you got it working.

Don't remove! This is easy to do: Pull the tab on the bottom out Push all the way in for ~10 seconds and beeping starts or it stops This part can be different by switch, but waiting ~10 seconds until a sound change generally works Go to iox, right click on the device and pick restore device

I skimmed the other tread and it seems more than coincidence that this happened after you migrated. I didn't see that you tried the factory reset and restore device? For switches that old, losing its memory marbles is "a thing" due to running a long time or electrical events like brown/black outs, I've had luck with this wokring on my older, long time running insteon devices.

Air gap is n Air gap is not a factory reset if I take that statement literally. The button that does the air gap has to be pushed and held 10 seconds-ish until until the sound changes.

That sounds like they mistakenly got set to 0% for "On" for the device. That happens sometimes. When you reinstalled them, the default is 100% on

To follow @MrBill 's line of reasoning, Insteon devices are not designed to have 2 masters. Either the PLM owns link management or the devices own link management. You'll have to do the record keeping to keep it straight and doing both simultaneously is inviting problems like you are experiencing. There is zero performance advantage to device to device linking versus iox link management. The Insteon management functions of iox push device-to-device links into the devices and they don't require the PLM for operation; they just have the advantage of iox programming. My set up does that. Device-to-device performance is excellent.. and I can pull the PLM out of the wall and they continue to work that way.

Maybe something is wrong with the unit. Have you factory reset it? I had 2 of these I bought a couple of years ago and the on level could be set by scene and remotely faded up and down from another switch.

Yes, give that a try. I wasn't sure if you had done this, since their continued presence in the config of the iox Insteon db is a plausible explanation. Nothing else to do for this one if the switches don't appear in your device/network view I meant if the devices were still there and you could delete them, do that, it would have cleared them from the iox Insteon db.. and restoring should have removed those links from the device that is exhibiting the problem. First: Try a restore device on the problematic switch. Second: If that doesn't do it, the next steps are more technical In iox, go to Tools/Diagnostics/Event viewer At the bottom of the window, set it for the most detailed tracking - highest level Go turn on the problem switch and the event viewer will capture what's going on Post the related Event Viewer entries back here I'm not the best at deciphering those, but there are members here who are and can hopefully join the discussion to help keep it moving

The blinking can mean it can't contact old invalid links, either other devices or the PLM. If you used the i3s to replace other Insteon switches, my guess is its on or both of the older ones. Things to try: In iox, try right-clicking and Restore Device If that doesn't work, try deleting the old switches from the eisy If they're still in iox but you uninstalled them this could explain it If this still didn't get it, Restore Device again after deleting You can add them back later for a future project