Code arm required about risco-mqtt-local HOT 21 CLOSED

hey @markxroberts .... I updated indeed to 2026.6
and the alarm panel was failing, since no code was setup, i had to define a default code, maybe an option to turn of the code_arm_required in your addon?

from risco-mqtt-local.

Well spotted. I didn't notice that it was a breaking change.

There's no facility to validate the code against the panel. The easiest option is for me to specify code_alarm_required: false in the registration packet.

If I put it in as an option, I'll have to validate it in the add-on, which doesn't seem right. Is that OK? If you say yes, I'll try to release an update later.

from risco-mqtt-local.

indeed, code_alarm_required: false, is perfect :-)
i have now setup a default code in the alarm panel, otherwhise it wasnt working anymore

from risco-mqtt-local.

Should be closed by #47, release 2024.6.1

from risco-mqtt-local.

Great! :-)

from risco-mqtt-local.

Hey, i saw some updates, thnx
@markxroberts , any idea why the lovelace alarm panel card is now presenting a keycode pad?

Never had this before :-(

from risco-mqtt-local.

Which add-on version is that?

from risco-mqtt-local.

I'm running latest version, updated yesterday, but not sure if it's addon related

from risco-mqtt-local.

2024.6.2 only released this morning. Could be an issue with the earlier version, but as no code specified in that one, seems less likely, especially as the configuration you shared is code_arm_required: false.

from risco-mqtt-local.

Yeah, nor sure what's going on :-(

from risco-mqtt-local.

Seems there is also "code_disarm_required" , maybe that one is needed to for "false" setting to hide the new keypad?
see here:

home-assistant/core#119443

from risco-mqtt-local.

Both "code_arm_required": false and "code_disarm_required": false are already present in the HA autodiscovery message for the partitions from 2024.6.1 onwards.

from risco-mqtt-local.

ah, but i only see this one: code_arm_required: false

from risco-mqtt-local.

You may need to update to the latest version. I can't remember when I noticed that both entries were required.

from risco-mqtt-local.

Just updated, but still a keypad, still notice only: code_arm_required

from risco-mqtt-local.

Can you pls share the MQTT autodiscovery message using MQTT explorer or equivalent

from risco-mqtt-local.

hmm, seems its there, but i dont see it, even after restarting the addon

{"name":"Pergola Quintens","object_id":"risco-alarm-panel-1","state_topic":"risco-alarm-panel/alarm/partition/1/status","unique_id":"risco-alarm-panel-partition-1","availability_mode":"all","availability":[{"topic":"risco-alarm-panel/alarm/status"},{"topic":"risco-alarm-panel/alarm/button_status"}],"payload_disarm":"disarmed","payload_arm_away":"armed_away","payload_arm_home":"armed_home","payload_arm_night":"armed_home","payload_arm_vacation":"armed_away","payload_arm_custom_bypass":"armed_home","code_arm_required":false,"code_disarm_required":false,"code":XXX,"device":{"manufacturer":"Risco","model":"LightSys/RP432","name":"Risco Alarm","sw_version":"2.70","identifiers":"risco-alarm-panel"},"command_topic":"risco-alarm-panel/alarm/partition/1/set"}

from risco-mqtt-local.

tried deleting the mqtt device and restarted addon, to start clean, but didnt make any difference
but i still dont know if it will fix the keypad issue at the end

from risco-mqtt-local.

This is interesting and I suspect might be an unanticipated front end issue. Here are some examples from my system. I have the alarm control panel card and the mushroom card to show the variation. The Risco Alarm Garage discovery message uses the new format autodiscovery message. The greenhouse dripper uses the old format autodiscovery message. Both show code_arm_required: true under Developer Tools ->states. Greenhouse dripper just gives an error message when you click the arm button. Risco alarm garage shows the keypad whether armed or disarmed. The mushroom card shows the same format for both types of autodiscovery message. You're right - I don't think we can fix this!

from risco-mqtt-local.

ok, yeah, it started happening since 2024.6.x , i try to keep away from custom cards if not needed :-)
maybe i can hide it with card-mod

from risco-mqtt-local.

found this on forum, working for now :-)

          - type: alarm-panel
            entity: alarm_control_panel.risco_alarm
            card_mod:
              style: |
                  #keypad {display: none !important;}
                  ha-textfield {display: none !important;}

from risco-mqtt-local.