OK. This is the third time this is happened. I have the Elk control an electronic gate via an M1Kam module. It normally works fine, except on several occasions. Today was one of them, and it was raining. The symptoms are: The gate doesn't open either through the Elk or the remote control, which directly toggles the gate controller. Rebooting the eisy always frees up the problem. What seems to be happening is that the Elk plugin is polling the Elk all the time, keeping the Elk from doing it's job and causing the M1KAM to prevent the gate from opening. I never had this happen with the ISY994 and the Elk module.

I don't know where the problem is, so I have put this on the Elk forum and submitted a ticket.

I have attached a zip file containing the error logs from both the eisy and the PG3.

I hope someone can figure this out soon, or I will be putting back my old ISY994.

I would PM the developer of the Elk plugin, but I don't know how to PM the developer.

Steve

eisy-Elk troubles.zip

Edited Monday at 03:37 PM3 days by SJacobson

The ELK Plugin does not poll the Elk, it connects to the Elk the exact same way the old ISY Elk module did, so it can't make the Elk to busy to do it's job.

From your description this does not involve the Eisy and/or Elk Plugin at all, and reviewing your logs there is nothing of interest.

I am the developer so you can PM me at anytime, but usually better to post on the forum to allow other users to answer if possible.

If you go to the PG3x plugin page for the Elk Plugin and change logging mode to Debug+Modules it will log more information, then if you experience the issue again note the time and download log package before midnight the same day and send that to me with the time. I'll review the log and see if it happened to be going crazy.

On 10/27/2025 at 7:45 PM, Jimbo.Automates said:

The ELK Plugin does not poll the Elk, it connects to the Elk the exact same way the old ISY Elk module did, so it can't make the Elk to busy to do it's job.

From your description this does not involve the Eisy and/or Elk Plugin at all, and reviewing your logs there is nothing of interest.

I am the developer so you can PM me at anytime, but usually better to post on the forum to allow other users to answer if possible.

If you go to the PG3x plugin page for the Elk Plugin and change logging mode to Debug+Modules it will log more information, then if you experience the issue again note the time and download log package before midnight the same day and send that to me with the time. I'll review the log and see if it happened to be going crazy.

If the plugin does not poll the Elk, how does it find the state changes in the inputs and output? Also, why are there polling parameters in the PG3X configuration page of the plugin?

Also, why does rebooting the eisy solve the problem (for a few days, anyway)?

I changed the log parameters as you suggested.

Again, this worked flawlessly on the ISY994 with the Elk module, so something is amiss.

Steve