Closed palazzem closed 7 months ago
After another round of investigation, we discovered that the error is misleading (fixed in #133) as the underlying response error is:
2024-01-30 23:16:28.893 DEBUG (SyncWorker_14) [elmo.api.client] Client | Disarming response: [{'Poller': {'Poller': 1, 'Panel': 1}, 'CommandId': 1, 'Successful': False, 'ErrorMessages': ['Comando fallito totalmente o parzialmente']}]
A possible root cause (thanks @xtimmy86x for the insights!) is that the main unit is a model that still requires the userID
as part of the code to obtain the supervision (and so to send commands). In the first call payload (Panel API), there is a field we can use called LoginWithoutUserID
. If this field is false
, it means that the main unit is expecting a userID
, hence the API call should include userID
in the payload.
Given this investigation, we may need to:
econnect-python
to query the Panel APILoginWithoutUserID
to understand if userID
should be sent or notUSER_ID*CODE
(*
is the separator).Let's take another pass so we can support also these models!
Describe the bug The integration is installed and configured without errors. When the alarm is armed, everything works as expected but disarming is not possibile as it returns "selected sectors 1 don't exist" in the logs.
Error message
Expected behavior As users can arm the alarm, it's expected they can also disarm it.
Additional context User experiencing this issue has configured the alarm using 2 areas with 4 sectors each. The integration retrieves 8 sectors without distinguishing the areas.
To Reproduce Not reproduced yet locally.
Environment