ISY994 automation delays

I have my isteon network going through a polisy and using the ISY994 integration to control it.

All my manual controls via HA are instant. Turning on lights are instant and reports from door sensors
and the local control of devices are instant.

However, once I add an insteon device to an automation in the action, there is almost always a 2 second delay before the insteon command. I for the life of me can’t figure out to even debug it to see where the delay is or why it’s happening. It doesn’t appear to be in the trigger because I have some events with non-insteon devices that those devices trigger fine with no delay and when it hits the insteon device, there is a 2 second delay.

Here you can see a simple example trace timeline. The automation is just 2 triggers with trigger ids for the door sensor (open/close) and then a choice action to either turn the utility room light on/off based on the trigger.

I tried the debugging and I trigged the event and then triggered the device from HA…When calling from the automation, I get a 1.5-2 second delay in the request response…

2023-07-29 22:12:30.246 DEBUG (MainThread) [homeassistant.components.isy994] Sensor None turning On via the Primary node sending a DON command
2023-07-29 22:12:30.248 DEBUG (MainThread) [homeassistant.components.isy994] Heartbeat timer starting. Now: 2023-07-30 02:12:30.247908+00:00 Then: 2023-07-31 03:12:30.247869+00:00
2023-07-29 22:12:30.248 DEBUG (MainThread) [pyisy] ISY Node Control Event: NodeProperty(control='DON', value=1, prec='0', uom='', formatted=None, address='32 86 20 1')
2023-07-29 22:12:30.249 DEBUG (MainThread) [pyisy] ISY Updated Node: 32 86 20 1
**2023-07-29 22:12:30.262 DEBUG (MainThread) [pyisy] ISY Request: http://10.0.0.172:8080/rest/nodes/50%20D1%207F%201/cmd/DON**
**2023-07-29 22:12:31.873 DEBUG (MainThread) [pyisy] ISY Response Received: /nodes/50%20D1%207F%201/cmd/DON**
2023-07-29 22:12:31.873 DEBUG (MainThread) [pyisy] ISY command on sent to 50 D1 7F 1.
2023-07-29 22:12:32.186 DEBUG (MainThread) [pyisy] ISY Updated Node: 50 D1 7F 1

However when I call from the UI the response is almost immediate

**2023-07-29 22:21:17.173 DEBUG (MainThread) [pyisy] ISY Request: http://10.0.0.172:8080/rest/nodes/50%20D1%207F%201/cmd/DON**
**2023-07-29 22:21:17.181 DEBUG (MainThread) [pyisy] ISY Response Received: /nodes/50%20D1%207F%201/cmd/DON**
2023-07-29 22:21:17.182 DEBUG (MainThread) [pyisy] ISY command on sent to 50 D1 7F 1.
2023-07-29 22:21:17.496 DEBUG (MainThread) [pyisy] ISY Updated Node: 50 D1 7F 1

this makes no sense to me. My intuition is telling me that the automation is merely “scheduling” the request to be called and for some reason it is delayed by 1.5 seconds or so.

thisi s not the only automation that does this. It is any automation I have that has an insteon device/scene in it where it calls the polisy.

OK, well, I simplified my Automation to only 1 trigger and 1 action and it’s the same.

Now, both trigger and action are insteon. Could HA have some kind of throttling in place to prevent calling it too often (or maybe the integration does?) I tried controlling a switch manually in quick succession and it didn’t seem to have any delays, again pointing me to something special in the automation.

I triggered my more simple automation manually via the UI (hence no incoming signal) and there was no delay… which again seems odd to me.

So I think this is on the ISY (Polisy) side. I’ve run a few tests and from what I can tell it is self throttling or it just can’t handle this type of traffic, which I find disappointing. The Polisy should be able to handle multiple requests at once. I don’t think it’s the PLM as I had a similar setup with HomeSeer (but HS controlled/talked to the PLM directly) and I never had these types of delays.

So I went with built in Insteon using an insteon Hub and I get the same results. I don’t get why I would get this delay. that actual “update” in HA is near instant, but the response to that trigger is delayed by 1.5-2s. I guess I will take this to the integrations section as I don’t think it’s the automation configuration.