maxnorth

For starters, I would at least restart it and make sure it is performing normally. Mine is working fine now with Pi-Hole running.

Hopefully final update: Safari now has a portal tab after logging out and back in. According to Benoit, certain features are disabled in eisy-ui when there is no internet access. I guess that means they disappear completely from the UI, which is a bit confusing. So, now that my portal access is restored, the feature is back, but it required a logout.

Update: The portal page shows in Chrome, but not Safari.

Here is how this resolved for me. At first, they wanted me to disable IPv6 on my router (it was never enabled, so not the issue). Did a long remote session with Benoit, who was very helpful. Noticed slowness from the eisy in web calls. Calls to the portal continued to fail even after extending the retry to 20 seconds. Did a bunch of diagnosis via SSH. Thought there might be DNS issues. I decided to take a look at my Pi-Hole instance on my NAS. It was hung. I stopped the docker container for that and the portal instantly started working. Restarted Pi-Hole and it still works. So, that being hung was the issue. No, I still do not have a portal tab in eisy-ui. I will have to focus on that another day. Thanks for the input, everyone.

Interesting. I'm not sure what to make of the IPv6 comment. I have never had IPv6 addresses on my network. My portal connection broke spontaneously on 5/2 when I was doing nothing on the system. I find it very odd that neither us has a "portal" page in eisy UI Settings. To me, that seems like a failed upgrade. I did just notice that the Configuration->Network Settings are grayed out on my Admin Console. DHCP is checked, but it is grayed out and nothing can be changed. I don't recall if that is normal after initial setup, but it does not seem right. I've got a ticket in and will report back.

I have the exact same problem (on an eisy). What was the resolution @someguy ?

In my case, I already had a single wire into the Liftmaster, from the Ratdgo. the 880LM was wired into the Ratdgo in pass through mode. My problem was false, spontaneous "lock" signals. This was confirmed because the 800LM would display "locked." The question is whether the spurious lock signal came from the 880LM, which is 12 years old, or the ratdgo itself. I disconnected the 880LM completely. At this point, I only have the ratdgo and wireless remotes communicating with my Liftmaster. It's been four days and I have not had a recurrence of the problem. My plan for now is to live with only wireless remotes plus the ratdgo. It that proves to be a problem, I'll install a new wired controller in pass through mode to the ratdgo. I am tossing the old 880LM. I am also trying to add the ratdgo "lock" control to my Home Assistant instance, but am having some difficulty. I can see the control in the ratdgo ESPHome instance and control it from my HA dashboard, but when I add it to HomeKit, it does not appear in HomeKit.

I seem to be experiencing this same symptom now. As a test, I have disconnected my 880LM completely and will see what happens. Did you ever track down a diagnosis or solution @SHM ?

My recollection is that the IP for the M1xep is set in the Elk settings. I use ElkRP software for that. It is located in the Account Details tab.

# Store in /usr/home/admin/ # No SSH required, Command to copy file FROM cd current directory (e.g., Mac desktop) to eisy # Replace with your own IP and user name and dev file name scp 2025-10-10-devfile.yaml admin@10.20.30.xxx:/usr/home/admin/

I believe the best approach is to create a scene including your relay. Then use programs to have the scene turned on and off (including by the KPL). For the light on the KPL button, that is another story. Create another scene including the KPL button. In the program controlling the relay, add an entry to turn off the KPL button scene when the relay is turned off.

I, too, would like to know if there is anything in process to fix the Elk problems related to the upgrade. I am holding off on the upgrade to 6/7 until this is more stable. I am unclear if this is a node server issue or something else. Clarification on that would be helpful.

I don't live in an area affected by lightening, but we do have periodic power outages during the winter months. I had several Insteon devices fried during outages like this. After installing a single whole house suppressor, I have not had any.

I have used darwin.kenyonralph.com successfully.

Ah, yes, "TelePeriod 20" does in fact set this to 20 seconds. Nice to be able to set this on a per-device basis! Thank you!