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
alarm keypad cannot arm disarm alarm 4.2.4
#1705
Comments
Could you please double check if you have set "Allow the device to make Home Assistant service calls"? |
Yes I have that set. |
So, can you see any error message related to this automation on your Home Assistant logs (Settings > System > Logs)? |
And could you please go to Developer Tools, tab States, find the entity related to this alarm and share it's state and attributes? |
I could not find anything in HA logs. code_format: number Later on I can try the nspanel_us landscape... maybe is a bug in the tft. |
Have you had any success from your side? I couldn't duplicate this issue. 😞 |
No same issue. I have five panels and none work with alarm code. I am not using encryption in ESPHome devices if this matters now? |
Do you know if that was working properly in a previous version? |
Sorry for late reply, have been busy. |
I believe this is solved in |
We just released a patch with solves this: v4.2.5 - Celebrating 1000 Stars with Enhanced Functionality and UI Improvements |
TFT Version
4.2.4
ESPHome Version
4.2.4
Blueprint Version
4.2.4
Panel Model
NSPanel US Model
What is the bug?
Cannot alarm or disarm from nspanel
Steps to Reproduce
Press alarm icon
Select arm (alarm is disarmed)
Press check mark nothing happens stays on keypad
Enter code and check nothing happens
(My alarm requires a code but previously I could arm without entering one)
Select disarm (alarm is armed)
Enter code and checkmark does not disarm panel.
nspanel does correctly show status of alarm when I ale disarm through HA.
Arming disarming with HA works as before - nothing seems to have changed in HA.
Your panel's YAML
No response
ESPHome logs
No response
Home Assistant logs
No response
The text was updated successfully, but these errors were encountered: