Alarm_control_panel: manual_mqtt don't retain the state after reset HA or reboot Pi

Configuration
1

Hello, excuse me for my english. I need help for a problem with the alarm control panel Manual mqtt it don’t retain the state after reset Home Assistant or reboot Raspberry.

This is my System
arch: armv7l
os_name: Linux
python_version: 3.7.3
version: 0.97.2
virtualenv: true
mosquitto version 1.6.4

configuration.yaml

alarm_control_panel:
  - platform: manual_mqtt
    state_topic: home/alarm
    command_topic: home/alarm/set
    name: Allarme
    pending_time: 30
    delay_time: 20
    trigger_time: 4
    disarmed:
      trigger_time: 0
    armed_home:
      pending_time: 0
      delay_time: 0
    triggered:
      pending_time: 0
    qos: 2

mqtt:
  broker: 127.0.0.1
  port: 1883
  client_id: home-assistant
  username: !secret mqtt_user
  password: !secret mqtt_psw
  keepalive: 60
  discovery: true
  discovery_prefix: homeassistant
  birth_message:
    topic: 'hass/status'
    payload: 'online'
  will_message:
    topic: 'hass/status'
    payload: 'offline'

mosquitto.conf

pid_file /var/run/mosquitto.pid

persistence true
persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

allow_anonymous false
password_file /etc/mosquitto/pwfile
listener 1883

thanks to the availability

2

Did you get an answer to this please? Mine was retaining, but all of a sudden it has stopped. The Alarm goes to Disarmed after a reboot… which isn’t great

alarm_control_panel:
  - platform: manual_mqtt
    code: ****
    state_topic: home/alarm
    command_topic: home/alarm/set
    pending_time: 30
    trigger_time: 1800
    disarm_after_trigger: false
    delay_time: 20
#    armed_home:
#      pending_time: 0
#      delay_time: 0
    armed_away:
      pending_time: 30
      delay_time: 30
3

I have open a issue:

If you activate the alarm whit the app https://github.com/thanksmister/android-mqtt-alarm-panel the alarm retain the state after reboot of PI or HA

4

I’m still fighting this issue on 113.2

It looks to be as though the alarm state initializes to the command_topic state on boot.
Problem is the local mqtt manual alarm control panel doesn’t update this topic…

My workaround is

  1. automatons to update the command topic with mqtt.publish when the alarm control panel state changes. (This is messy and may cause issues with pending states in certain conditions?)
  2. use mqtt.publish with retain:true, rather than the alarm control panel services to change states where ever possible.
5

@wizmo Hey there!

I 've done the same thing using node red. The Manual MQTT Alarm saves the last state correctly if it is armed_home/away using an mqtt.publish with retain:true. The wierd thing is that i listened to the state topic of the alarm while i was arming it through HA and saw that the message is set as retain:true but if i restart HA it turns to disarmed again. Only if i publish an mqtt message with retain:true using Alarm Panel (android mqtt alarm app) the state of the Alarm remains in armed_home/away even after restart.
So i did the same thing as you did. Created two trigger nodes (armed_home , disarmed) on node red that they re-publish the state of the alarm to the topic using mqtt-out node with retain-true.
Till now it works fine!