Pico Remotes wont respond until indicator light (tx) turns off

I’m not quite sure where the problem lies here (I can only assume me) but whenever I try to trigger an automation with the sensor.pico in hassio it takes two seconds to fire. I can confirm the automation will fire immediately when the green light on the pico stops flashing. If I keep pressing the button on the pico (to keep the light flashing) the automation will not fire until I stop and then the light stops. I had assumed that hassio was not seeing the state change until the light stopped flashing, however testing the button presses while watching the sensor in hassio shows immediate state changes. I’m stumped. Here is my automation code:

- id: '1548110829104'
  alias: Dining Room Pico On
  trigger:
  - entity_id: sensor.pico_remotes_dining_room_pico
    platform: state
    to: '1'
  action:
    entity_id: light.dining_room_main_lights
    service: light.turn_on

Running HA 84.3 and my lutron app reports 6.3

[mspace00]

One quick observation…when pressing the pico remote repeatedly I am unable to control other functions within home assistant. Once I stop pressing the pico repeatedly the actions fire. I will try to get some system resource info to post.

[gabe565]

I haven’t had time to look through the code, but it almost feels like the pico remote is blocking the interface with home assistant. If I do some sort of action within the native lutron app/eco system while the pico and homeassistant are doing their thing, it’s not blocked. Only when using home assistant.

It looks to me like this is a problem with the Lutron telnet interface and not with this project’s code. If I directly telnet in, push a button on the pico, then run a command, it still has this problem and the command isn’t immediately run.
It looks like the Lutron telnet spec supports disabling output per-connection, so maybe we could open multiple telnet connections and have one for input and one for output? Don’t know if it would actually help, but I am experimenting with it right now and will see if I can get around it.

Edit: I think the delay is on purpose for whatever reason. After posting this comment, I realized that the delay is also in the Lutron app. If I press a button on a pico remote, then immediately try to change a light’s state in the app, there is a delay just like with this HA component.
Found a reddit thread that has some possible explanations. The OP of that post emailed Lutron about it so we will see if anything comes of it.