Events (EL:) Received But Not Parsed/Dispatched from InFusion Controller FW 3.0.62 #283
Description
Checklist
- This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
- This issue is not a duplicate issue of currently previous issues..
Describe the issue
Environment:
aiovantage: 0.22.5 (also tested 0.22.4)- Python: 3.13.2
- Controller: InFusion DIN (Hardware ID: E0), Firmware: 3.0.62
- Connection: No Auth, No SSL
Problem:
aiovantage connects and subscribes successfully. Debug logs show raw EL: messages (e.g., EL: 324 Button.GetState 1) are received on the port 3001 connection when a physical button is pressed. However, no registered Python event callbacks (ObjectUpdated, EnhancedLogReceived, etc.) are ever triggered.
Specific Symptom:
Often, only the very first EL: message after a fresh connection is seen in the debug logs. Subsequent physical button presses do not generate further EL: messages in the debug log until the script/connection is restarted.
Expected Behavior:
Callbacks registered via vantage.subscribe() or vantage.buttons.subscribe() should be triggered when corresponding EL: messages are received.
Actual Behavior:
Raw EL: messages are received by the library (visible in debug logs), but no Python callbacks are executed.
Log Snippet Example:
... Successful connection and subscription logs ...
main - INFO - [MAIN_LOOP] Subscribed to all specified events.
main - INFO - [MAIN_LOOP] Waiting for events...
--- Physical Button Pressed ---
aiovantage - DEBUG - Received message: EL: 324 Button.GetState 1
--- NO [CALLBACK] logs appear here or for subsequent presses ---
aiovantage - DEBUG - Sending message: ECHO
Note: A separate official Vantage diagnostic tool does receive events correctly from the same controller. This suggests an incompatibility between aiovantage and the event processing/parsing for this specific older firmware.
Reproduction steps
...