I also open my garage door using a voice command with my iPhone and Home Assistant Companion but I don’t see how to arm or disarm the alarm?
With latest HA version, 2024.6.x, something has changed in alarm panel where you cannot arm or disarm without a code, while it was possible until 2024.5.x
This post is full of people with same error from various alarm integration or addon.
While when you defne a manual, template or mqtt alarm panel you can add a code_arm_required option set to false to bypass it, in the integration/addon alarm panel, you cannot.
My question is if this is something that has to be solved by HA team or not…
Or if there is a workaround
Thanks
@woody4165 I have just tried and yes I got the same. So that messes up my watch and CarPlay actions!
However disarm doesn’t require a code. And I have noticed if you use the mushroom alarm card, when you arm, it comes up with a keypad to enter the code and that works for some reason.
@woody4165 I found this:
I can confirm it works! Go to your partition (s) and enter the code! That’s it!
1 Like
Thanks!
Very easy, but not easy to find.
Is there a way to have the code inserted every time, instead of updating the Default code field?
Thanks
@woody4165 If you mean you want to enter the code every time to arm and disarm, then use the mushroom alarm panel. But then you would have to remove the code in default that was just entered.
Now that the code has been entered in the default, the mushroom card does not give the keypad option and doesn’t require a code.
I am not sure how do it through mqtt way.
1 Like
Hi everyone,
I have integrated Paradox EVO192/Mosquito to HA on my RPi and wondering if there is any way to make more fast, more responsive.
Any suggestion would be appreciated.
There are tips how to do this in the wiki.
Thanks for your answer,
I looked at wiki before, but I only found “Transmit zone status on serial port” and I’m actual using only IP with IP150 interface. Do I have to look somewhere else specific? I have the thought that is all about MQTT.
I have at least a 5sec delay.
Found it,
Just for the reference,
I changed this from 6 to 1 and now I have the same delay as the panel with the Paradox display (1sec)
That is located in PAI Addon configuration.
Thanks anyway!
Hey Jevgeni,
Thank you, I have read the wiki and set the boud rate to 57600 with babywre and add-on side. Although that doesn’t make any deference.
Did you configure this? «Transmit zone status on serial port»
Let me check and get back later.
Actually not,
I haven’t check this box… I should I guess… 
Now is working great, also I set the “KEEP_ALIVE_INTERNAL” back to 10 as it was before.
Thank you @yozik04
Hi, I was amazed when I tested this, connects to my old IP100 (and MG5000) absolutely stable and everything works, controlling, statuses and so on. Big thanks!
However, not getting Pushover to work. If I insert the lines
PUSHOVER_ENABLE: true
PUSHOVER_KEY: <pushover_app_api_key>
PUSHOVER_BROADCAST_KEYS:
- user_key: <UserKey>
devices: '*'
to my AddOns → Paradox → Config → Yaml in the end and press “Save” the added lines are removed.
What am I doing wrong here?
(Pushover from HA works on other things so connections etc are ok)
Doh. Realized there was duplicate key, removing
PUSHOVER_BROADCAST_KEYS: []
before new lines fixed this. Pushover now works.
Hi!
I’m using this addon with an IP100 module and an EVO192 alarm panel, but I’ve noticed that the connection between the panel and the home automation system frequently drops. There are days when I see over 100 reconnections in the log.
Is anyone else experiencing this issue?
The error log (I deleted the serial number):
2024-10-17 13:27:50,602 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2024-10-17 13:27:50,602 - INFO - PAI.paradox.paradox - Clean Session
2024-10-17 13:27:50,602 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection
2024-10-17 13:27:50,604 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None
2024-10-17 13:27:50,605 - ERROR - PAI.paradox.connections.connection - Connection was lost
2024-10-17 13:27:50,607 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel
2024-10-17 13:27:50,608 - INFO - PAI.paradox.paradox - Connecting to interface
2024-10-17 13:27:50,609 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2024-10-17 13:27:50,702 - INFO - PAI.paradox.connections.connection - Connection established
2024-10-17 13:27:50,703 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module
2024-10-17 13:27:50,833 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP100) Module version 101, firmware: 5.10, serial: xxxxxxxx
2024-10-17 13:27:51,203 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2024-10-17 13:27:51,203 - INFO - PAI.paradox.paradox - Connecting to Panel
2024-10-17 13:27:56,218 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active?
2024-10-17 13:27:56,218 - ERROR - PAI - Unable to connect to alarm
2024-10-17 13:28:03,223 - INFO - PAI - Starting...
2024-10-17 13:28:03,223 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2024-10-17 13:28:03,224 - INFO - PAI.paradox.paradox - Clean Session
2024-10-17 13:28:03,224 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection
2024-10-17 13:28:03,226 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None
2024-10-17 13:28:03,226 - ERROR - PAI.paradox.connections.connection - Connection was lost
2024-10-17 13:28:03,227 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel
2024-10-17 13:28:03,228 - INFO - PAI.paradox.paradox - Connecting to interface
2024-10-17 13:28:03,228 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2024-10-17 13:28:03,402 - INFO - PAI.paradox.connections.connection - Connection established
2024-10-17 13:28:03,403 - INFO - PAI.paradox.connections.ip.commands - Authenticating with IP Module
2024-10-17 13:28:03,534 - INFO - PAI.paradox.connections.ip.commands - Authentication Success. IP(IP100) Module version 101, firmware: 5.10, serial: xxxxxxxx
2024-10-17 13:28:03,903 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2024-10-17 13:28:03,903 - INFO - PAI.paradox.paradox - Connecting to Panel
2024-10-17 13:28:04,075 - INFO - PAI.paradox.paradox - Panel Identified EVO192 version 6.90 build 5
2024-10-17 13:28:04,075 - INFO - PAI.paradox.paradox - Initiating panel connection
2024-10-17 13:28:04,259 - INFO - PAI.paradox.hardware.evo.panel - Installer login
2024-10-17 13:28:04,414 - INFO - PAI.paradox.hardware.evo.panel - Authentication Success
2024-10-17 13:28:04,414 - INFO - PAI.paradox.paradox - Connection OK
Edit:
Another log entry:
2024-10-17 13:37:14,954 - ERROR - PAI - Unable to connect to alarm
2024-10-17 13:37:19,093 - ERROR - PAI.paradox.lib.handlers - No handler for message 7
Detail: Container:
fields = Container:
data = b'r\xff\x04\x02\x00\x00\xa1Z\x01\x06\x90\x05\x05\x02y\xda'... (truncated, total 36)
value = Container:
po = Container:
command = 7
message_center = 2
new_protocol = 255
protocol_id = 4
protocol = Container:
version = 2
revision = 0
build = 0
family_id = (enum) (unknown) 161
product_id = (enum) (unknown) 90
talker = (enum) CONTROLLER_APPLICATION 1
application = Container:
version = 6
revision = 90
build = 5
serial_number = b'\x05\x02y\xda' (total 4)
hardware = Container:
version = 0
revision = 16
bootloader = Container:
version = 1
revision = 0
build = 15
day = 39
month = 16
year = 32
processor_id = 16
encryption_id = 48
reserved0 = b'\xffW' (total 2)
label = b'EVO192\x00\x00' (total 8)
offset1 = 0
offset2 = 36
length = 36
checksum = b'\xfb' (total 1)
2024-10-17 13:37:22,960 - INFO - PAI - Starting...
Hi Guys, i am evaluating security alarm options and MG5050+ with IP150 and wireless PIR is one of the 3 options i’m considering.
are there are issues or gotchas to be aware of before committing to the purchase?
anything that does not work or requires a hacky workaround?
Running an mg5050+ with an IP50.
Everything working fine, but how can I determine in home assistant when the alarm is in “entry delay” mode and “exit delay” mode?
I want to be able to notify myself when the alarm has been triggered and in entry delay mode separately to when it’s actually fully triggered and a siren is going off.
1 Like
Nevermind, figured it out.
For anyone else … add these into your config file:
HOMEASSISTANT_PUBLISH_PARTITION_PROPERTIES = [
‘target_state’,
‘current_state’,
‘entry_delay’,
‘exit_delay’
]
You’ll then get separate entities in home assistant which you can do whatever you want with.