-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in alarm status night #108
Comments
VEDOS website console: http://192.168.1.30:6082/action.cgi?vedo=1&**p1**=32&_=1731569426448 |
Dev info: This does not work when I check the VEDO app. |
@gicamm Can you give an idea when you would have time for this issue pls. |
Still having problems with the latest release? Some changes have been introduced with PR 109. |
Hello @gicamm i checked in version 1.0.2 and still have the problem. I tried set state in developer but still not working. How can i help you further? |
@gicamm I activated the debug mode again, I pressed the 'Home' alarm button on my VEDOS device.
|
I disabled the alarm with OFF 4 minutes later:
|
@gicamm Armed: Disabling alarm changed 0 back to 0 instead of 1. Could it be that I need to change the configuration.yaml to something specific for Comelit like its the case for Aarlo? custom night mode name for example? |
Hi ward0, The issue seems to be limited to the Night mode. The Away mode works fine, but some adjustments are needed to enable support for Night mode. It’s likely a simple fix — we just need to identify and use the correct key in the URL parameters. Once added, we can test it to ensure everything functions as expected. Let me know if you’d like me to assist further! |
Hi @gicamm I have no idea how I can provide further information at this point. |
I tried to add this to my configuration.yaml, but has no effect. logger: |
Your configuration is not correct.
|
Configuration warnings Do I even had to add this to help you further? |
@gicamm i have enabled the debug logging, this is the result:
The night alarm is now active: 2025-01-28 22:44:11.078 DEBUG (Thread#BS) [custom_components.comelit.vedo] updated the alarm area I know this because these 2 values changed (also how my night alarm is configured: 2025-01-28 22:44:41.526 DEBUG (Thread#BS) [custom_components.comelit.vedo] Updating the zone {'index': 10, 'id': 10, 'name': 'Living', 'status': '0000'} So the p1_pres': 1 must be almost be the 'house' icon on physical keypad, that is configured to arm my night mode. |
integration version: 0.9.3
Action done:
Logging:
2024-11-09 14:08:23.297 DEBUG (Thread#BS) [custom_components.comelit.vedo] Updating the alarm area {'name': 'Woning', 'id': 0, 'p1_pres': 1, 'p2_pres': 0, 'ready': 0, 'armed': 0, 'alarm': 0, 'alarm_memory': 0, 'sabotage': 0, 'anomaly': 0, 'in_time': 0, 'out_time': 0}
2024-11-09 14:08:23.297 DEBUG (Thread#BS) [custom_components.comelit.vedo] updated the alarm area Woning
The text was updated successfully, but these errors were encountered: