Risco Alarm Panel not working, but my scripts do. What's happening??? about risco-mqtt-bridge HOT 6 CLOSED

Hey Luca, integration has been working well for a while, hence no update. I had made a mistake in the config file. Did a rebuild of my Pi4 recently. Used portainer to install the docker image and bingo, all working again without a hitch. I love docker!

from risco-mqtt-bridge.

what is that uniqie id? i dont have it

here is mine...

ps: the delay for arming / disarming is normal if you arm/disarm trough a hardware panel... if you test with the app, then its almost instant

alarm_control_panel:
 - platform: mqtt
   name: Risco Alarm
   state_topic: "riscopanel/armstatus"
   command_topic: "riscopanel/armstatus/SET"
   payload_disarm: "disarmed" 
   payload_arm_home: "partially"
   payload_arm_away: "armed"
   code_arm_required: false

from risco-mqtt-bridge.

Removing the unique_id and adding

  code_arm_required: false

simply created a second Risco alarm entity which still did not work. The second Risco alarm entity still reported that the Risco alarm was disarmed when it was armed and my sensor reported armed too.

I found the unique_id on the https://www.home-assistant.io/integrations/alarm_control_panel.mqtt/
unique_id (string)(Optional) An ID that uniquely identifies this alarm panel.
Which is why I added it. With or without this unique_id the panel does not work. All a bit odd.

Also, if I change

  code_arm_required: true

The alarm control panel does not request a code.

All a bit confusing!

from risco-mqtt-bridge.

inactivity

from risco-mqtt-bridge.

Hey Luca, integration has been working well for a while, hence no update. I had made a mistake in the config file. Did a rebuild of my Pi4 recently. Used portainer to install the docker image and bingo, all working again without a hitch. I love docker!

so can close it ?

from risco-mqtt-bridge.

Of course

from risco-mqtt-bridge.