Stop working after update to HA OS 5.11

Question

Stop working after update to HA OS 5.11

sicarriere opened this issue 3 years ago · comments

Eric Carriere commented 3 years ago

Alarm system

SP6000 with IP100

Environment

RPI 4
HA core-2021.2.1
HA supervisor-2021.02.5
Home Assistant OS 5.11

Git branch

Prod 2.2.5

Describe the bug

After updating from HA OS 5.10 to 5.11, PAI stop working. I'm using IP Connection type. Was working without problem with HA OS 5.10.

To Reproduce

Logs

2021-02-08 15:27:40,477 - INFO - PAI - Starting...
2021-02-08 15:27:40,477 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2021-02-08 15:27:40,478 - INFO - PAI.paradox.paradox - Clean Session
2021-02-08 15:27:40,479 - INFO - PAI.paradox.paradox - Connecting to interface
2021-02-08 15:27:40,480 - INFO - PAI.paradox.connections.serial_connection - Connecting to serial port /dev/ttyS1
2021-02-08 15:27:40,481 - INFO - PAI.paradox.connections.serial_connection - /dev/ttyS1 is not readable/writable. Trying to fix...
2021-02-08 15:27:40,482 - ERROR - PAI.paradox.connections.serial_connection - Failed to update file /dev/ttyS1 permissions
2021-02-08 15:27:40,484 - ERROR - PAI.paradox.paradox - Failed to connect to interface
2021-02-08 15:27:40,486 - ERROR - PAI - Unable to connect to alarm

Here my config :
LOGGING_FILE: null
LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
LOGGING_DUMP_PACKETS: false
LOGGING_DUMP_MESSAGES: false
LOGGING_DUMP_STATUS: false
LOGGING_DUMP_EVENTS: false
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 192.168.xxx.xxx
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: xxxxxxxxxx
IP_CONNECTION_SITEID: null
IP_CONNECTION_EMAIL: null
IP_CONNECTION_PANEL_SERIAL: null
IP_CONNECTION_BARE: false
LIMITS:
pgm: []
partition:
- 1
SYNC_TIME: false
PASSWORD: 'XXXX'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: xxxxxxxxxx
MQTT_PASSWORD: xxxxxxxxxx
MQTT_RETAIN: true
MQTT_BIND_ADDRESS: 127.0.0.1
MQTT_BIND_PORT: 0
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: false

gjanarthan commented 3 years ago

👍

Gunth · Answer 1 · Tue Feb 09 2021 04:50:18 GMT+0800 (China Standard Time)

I have the same issue but note sure if it is the upgrade of HA OS or HA Supervisor to 2021.02.5.
I'm seeing a lot of add-ons upgading with the change log "Update add-on configuration for Supervisor 2021.2"

Gunth · Answer 2 · Tue Feb 09 2021 04:54:18 GMT+0800 (China Standard Time)

In the supervisor log there is this :

21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_FILE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_LEVEL_CONSOLE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_LEVEL_FILE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_PACKETS
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_MESSAGES
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_STATUS
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_EVENTS
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options CONNECTION_TYPE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options SERIAL_PORT
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options SERIAL_BAUD
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_HOST
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PORT
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PASSWORD
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_SITEID
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_EMAIL
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PANEL_SERIAL
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_BARE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options LIMITS
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options SYNC_TIME
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options PASSWORD
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_ENABLE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOST
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PORT
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_USERNAME
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PASSWORD
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_RETAIN
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_ADDRESS
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_PORT
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE
21-02-08 20:36:01 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PUBLISH_STATUS
21-02-08 20:36:03 WARNING (MainThread) [supervisor.addons.options] Unknown options port

Claudiu Bucur · Answer 3 · Tue Feb 09 2021 05:12:09 GMT+0800 (China Standard Time)

Same issue here. After HassOS and Supervisor upgrades.

Jevgeni Kiski · Answer 4 · Tue Feb 09 2021 05:21:00 GMT+0800 (China Standard Time)

@Gunth I'm seeing a lot of add-ons upgading with the change log "Update add-on configuration for Supervisor 2021.2"

What are these addons?

Claudiu Bucur · Answer 5 · Tue Feb 09 2021 05:25:11 GMT+0800 (China Standard Time)

See this one for example: hassio-addons/addon-ssh@5f8a384

Gunth · Answer 6 · Tue Feb 09 2021 05:53:06 GMT+0800 (China Standard Time)

VS Code : hassio-addons/addon-vscode@ce707ad
Node Red : hassio-addons/addon-node-red@a870641

All with the same kind of commit

Jevgeni Kiski · Answer 7 · Tue Feb 09 2021 06:09:22 GMT+0800 (China Standard Time)

I also updated that but it does not solve the problem.

tvl9ops · Answer 8 · Tue Feb 09 2021 11:15:20 GMT+0800 (China Standard Time)

Same here, HA OS 5.11 broke the integration.

Rus Ti · Answer 9 · Tue Feb 09 2021 16:05:12 GMT+0800 (China Standard Time)

Ditto for me - updated both HASS and Core and now PAI is dead - same errors in my logs as posted above.

ukrolelo · Answer 10 · Tue Feb 09 2021 16:26:38 GMT+0800 (China Standard Time)

same here with
ERROR - PAI.paradox.connections.serial_connection - Failed to update file /dev/ttyS1 permissions

marius-venter · Answer 11 · Tue Feb 09 2021 16:38:40 GMT+0800 (China Standard Time)

I have updated to the latest but still getting the errors:
21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_FILE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_LEVEL_CONSOLE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_LEVEL_FILE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_PACKETS 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_MESSAGES 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_STATUS 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LOGGING_DUMP_EVENTS 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options CONNECTION_TYPE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options SERIAL_PORT 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options SERIAL_BAUD 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_HOST 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PORT 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PASSWORD 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_SITEID 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_EMAIL 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PANEL_SERIAL 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_BARE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options LIMITS 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options SYNC_TIME 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options PASSWORD 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_ENABLE 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOST 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PORT 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_USERNAME 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PASSWORD 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_RETAIN 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_ADDRESS 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_PORT 21-02-09 07:38:18 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE

ukrolelo · Answer 12 · Tue Feb 09 2021 16:39:48 GMT+0800 (China Standard Time)

Why it does even need /dev/ttyS1 if its over LAN ?!

Jevgeni Kiski · Answer 13 · Tue Feb 09 2021 16:41:12 GMT+0800 (China Standard Time)

Because Supervisor maintainers love to break things.

marius-venter · Answer 14 · Tue Feb 09 2021 16:41:13 GMT+0800 (China Standard Time)

Why it does even need /dev/ttyS1 if its over LAN ?!

I'm guessing it is falling back to defaults if it can't read the configuration

ukrolelo · Answer 15 · Tue Feb 09 2021 16:42:50 GMT+0800 (China Standard Time)

Why it does even need /dev/ttyS1 if its over LAN ?!

I'm guessing it is falling back to defaults if it can't read the configuration

Yeah sound logic

ukrolelo · Answer 16 · Tue Feb 09 2021 16:43:03 GMT+0800 (China Standard Time)

Because Supervisor maintainers love to break things.

xD

ukrolelo · Answer 17 · Tue Feb 09 2021 16:45:19 GMT+0800 (China Standard Time)

Why it does even need /dev/ttyS1 if its over LAN ?!

I'm guessing it is falling back to defaults if it can't read the configuration

2021-02-09 09:44:40,956 - INFO - PAI - Starting Paradox Alarm Interface 2.2.5
2021-02-09 09:44:40,956 - INFO - PAI - Config loaded from /data/options.json
2021-02-09 09:44:40,957 - INFO - PAI - Console Log level set to 20
2021-02-09 09:44:40,959 - INFO - PAI - Starting...
2021-02-09 09:44:40,959 - INFO - PAI.paradox.paradox - Connecting to interface
2021-02-09 09:44:40,960 - INFO - PAI.paradox.paradox - Using Serial Connection
2021-02-09 09:44:41,000 - INFO - PAI.paradox.connections.serial_connection - Connecting to serial port /dev/ttyS1
2021-02-09 09:44:41,000 - INFO - PAI.paradox.connections.serial_connection - /dev/ttyS1 is not readable/writable. Trying to fix...
2021-02-09 09:44:41,001 - ERROR - PAI.paradox.connections.serial_connection - Failed to update file /dev/ttyS1 permissions
2021-02-09 09:44:41,003 - ERROR - PAI.paradox.paradox - Failed to connect to interface
2021-02-09 09:44:41,004 - ERROR - PAI - Unable to connect to alarm

Its loaded correctly so saying

ukrolelo · Answer 18 · Tue Feb 09 2021 16:46:51 GMT+0800 (China Standard Time)

I wanted to delete
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
But it come back :-O

Jevgeni Kiski · Answer 19 · Tue Feb 09 2021 16:48:57 GMT+0800 (China Standard Time)

No. I am 90% that all addons that did not specified configuration schema are now out of luck.
Their documentation tells that addons may not specify schema.

From: https://developers.home-assistant.io/docs/add-ons/configuration/

I think this change in supervisor broke it:
https://github.com/home-assistant/supervisor/pull/2510/files

ukrolelo · Answer 20 · Tue Feb 09 2021 16:51:17 GMT+0800 (China Standard Time)

So what can we do? :-D my knowledge is limited to banana,potato,python :-D

Jevgeni Kiski · Answer 21 · Tue Feb 09 2021 17:06:00 GMT+0800 (China Standard Time)

Can please someone give me output of ha info. I am filing a bug in supervisor repo.

ukrolelo · Answer 22 · Tue Feb 09 2021 17:08:15 GMT+0800 (China Standard Time)

Can please someone give me output of ha info. I am filing a bug in supervisor repo.

Can you tell me where? like server logs? or PAI logs?

Jevgeni Kiski · Answer 23 · Tue Feb 09 2021 17:10:49 GMT+0800 (China Standard Time)

in ssh plugin.

Gunth · Answer 24 · Tue Feb 09 2021 17:11:16 GMT+0800 (China Standard Time)

arch: aarch64
channel: stable
docker: 19.03.13
features:
- reboot
- shutdown
- services
- network
- hostname
- hassos
hassos: "5.11"
homeassistant: 2021.2.2
hostname: homeassistant
logging: info
machine: raspberrypi4-64
operating_system: Home Assistant OS 5.11
state: running
supervisor: 2021.02.6
supported: true
supported_arch:
- aarch64
- armv7
- armhf
timezone: Europe/Brussels

ukrolelo · Answer 25 · Tue Feb 09 2021 17:15:21 GMT+0800 (China Standard Time)

Interesting i have same but supervisor: 2021.02.5 not supervisor: 2021.02.6
wtf :O
And in dashboard no option to update

Gunth · Answer 26 · Tue Feb 09 2021 17:16:56 GMT+0800 (China Standard Time)

I update it this morning, maybe it will come later for you.
But i have the same issue with the supervisor 2021.02.5 and 2021.02.6

Jevgeni Kiski · Answer 27 · Tue Feb 09 2021 17:19:31 GMT+0800 (China Standard Time)

I have filed a bug report. Let's wait for a response.

Woody · Answer 28 · Tue Feb 09 2021 17:19:56 GMT+0800 (China Standard Time)

same here.

Hassos in a Proxmox VM, was working fine before this update

arch: amd64
audio_input: None
audio_output: None
boot: true
image: homeassistant/qemux86-64-homeassistant
ip_address: 172.30.32.1
last_version: 2021.2.2
machine: qemux86-64
port: 8123
ssl: false
update_available: false
version: 2021.2.2
version_latest: 2021.2.2
wait_boot: 600
watchdog: true

Jevgeni Kiski · Answer 29 · Tue Feb 09 2021 18:04:11 GMT+0800 (China Standard Time)

If somebody has time please fill schema in https://github.com/ParadoxAlarmInterface/hassio-repository/blob/master/paradox_alarm_interface/config.json
from https://github.com/ParadoxAlarmInterface/pai/blob/master/config/pai.conf.example

Some documentation of format: https://developers.home-assistant.io/docs/add-ons/configuration/#options--schema

I will accept pull request. I do not have time to work on it this week.

ukrolelo · Answer 30 · Tue Feb 09 2021 18:46:51 GMT+0800 (China Standard Time)

Is this str? :-O
"map": [
"share:rw",
"config:ro"
],

proasnet · Answer 31 · Tue Feb 09 2021 19:23:31 GMT+0800 (China Standard Time)

The same problem after one week good working :(
Now not working.
2021-02-09 12:18:00,238 - ERROR - PAI.paradox.connections.serial_connection - Failed to update file /dev/ttyS1 permissions
2021-02-09 12:18:00,240 - ERROR - PAI.paradox.paradox - Failed to connect to interface
2021-02-09 12:18:00,242 - ERROR - PAI - Unable to connect to alarm
2021-02-09 12:18:30,275 - INFO - PAI - Starting...
2021-02-09 12:18:30,276 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2021-02-09 12:18:30,277 - INFO - PAI.paradox.paradox - Clean Session
2021-02-09 12:18:30,278 - INFO - PAI.paradox.paradox - Connecting to interface
2021-02-09 12:18:30,279 - INFO - PAI.paradox.connections.serial_connection - Connecting to serial port /dev/ttyS1
2021-02-09 12:18:30,280 - INFO - PAI.paradox.connections.serial_connection - /dev/ttyS1 is not readable/writable. Trying to fix...

Jevgeni Kiski · Answer 32 · Tue Feb 09 2021 19:43:40 GMT+0800 (China Standard Time)

Is this str? :-O
"map": [
"share:rw",
"config:ro"
],

No it is an array or stings.

@proasnet It is not my fault =) Blame HA devs.

tvl9ops · Answer 33 · Tue Feb 09 2021 19:56:27 GMT+0800 (China Standard Time)

Do you guys happen to know how I could revert to 5.10 for the time being?

marius-venter · Answer 34 · Tue Feb 09 2021 19:58:46 GMT+0800 (China Standard Time)

Do you guys happen to know how I could revert to 5.10 for the time being?

It's not the operating system causing the issue, but rather supervisor. It also auto updates every time I downgrade it :(

jontofront · Answer 35 · Tue Feb 09 2021 22:00:16 GMT+0800 (China Standard Time)

Same problem :( at Home Assistant OS 5.11
21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options SERIAL_BAUD 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_HOST 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PORT 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PASSWORD 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_SITEID 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_EMAIL 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_PANEL_SERIAL 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options IP_CONNECTION_BARE 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options LIMITS 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options SYNC_TIME 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options PASSWORD 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_ENABLE 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOST 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PORT 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_USERNAME 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_PASSWORD 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_RETAIN 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_ADDRESS 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_BIND_PORT 21-02-09 13:45:44 WARNING (MainThread) [supervisor.addons.options] Unknown options MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE

tvl9ops · Answer 36 · Tue Feb 09 2021 22:37:33 GMT+0800 (China Standard Time)

Is there any workaround we could use? My whole system depends on automations with Paradox, now nothing works, it is painful.

Claudiu Bucur · Answer 37 · Tue Feb 09 2021 23:30:14 GMT+0800 (China Standard Time)

If somebody has time please fill schema in https://github.com/ParadoxAlarmInterface/hassio-repository/blob/master/paradox_alarm_interface/config.json
from https://github.com/ParadoxAlarmInterface/pai/blob/master/config/pai.conf.example

Some documentation of format: https://developers.home-assistant.io/docs/add-ons/configuration/#options--schema

I will accept pull request. I do not have time to work on it this week.

I'll try to make a PR this evening. Let's see how it goes.

ukrolelo · Answer 38 · Tue Feb 09 2021 23:59:28 GMT+0800 (China Standard Time)

Is this str? :-O
"map": [
"share:rw",
"config:ro"
],

No it is an array or stings.

@proasnet It is not my fault =) Blame HA devs.

Ohh i see it now :>

Johann Kellerman · Answer 39 · Wed Feb 10 2021 03:51:05 GMT+0800 (China Standard Time)

I created a PR ParadoxAlarmInterface/hassio-repository#12

I do not think that Limits is supported yet... they only seem to support a list [] and not a dict {}

Johann Kellerman · Answer 40 · Wed Feb 10 2021 03:53:16 GMT+0800 (China Standard Time)

I tried to downgrade by SSHing into HASS OS, without success

ha > supervisor update --version 2021.01.8

artismiezitis · Answer 41 · Wed Feb 10 2021 05:28:31 GMT+0800 (China Standard Time)

Same for me on SP65 panel.
ssh

Johann Kellerman · Answer 42 · Wed Feb 10 2021 20:57:07 GMT+0800 (China Standard Time)

@yozik04 in the less than 4 minutes ago version, you had to specify everything in LIMITS, I guess you should also check, if this is empty then include ALL (in the past the key was omitted)

Jevgeni Kiski · Answer 43 · Wed Feb 10 2021 21:24:04 GMT+0800 (China Standard Time)

if you want to include all you should put auto

Jevgeni Kiski · Answer 44 · Wed Feb 10 2021 22:40:08 GMT+0800 (China Standard Time)

2.3.0 released with the fix. @clau-bucur is working hard to add more settings to addon schema.

Gunth · Answer 45 · Wed Feb 10 2021 23:21:01 GMT+0800 (China Standard Time)

It's back again for me, I had to merge my config with the default one because the validation failed, i don't know why maybe a missing property...

Thanks for the hard work !

danch99 · Answer 46 · Wed Feb 10 2021 23:52:30 GMT+0800 (China Standard Time)

How do you update to 2.3.0 ?
It doesn't show up on my end.

Thanks

Gunth · Answer 47 · Thu Feb 11 2021 00:04:05 GMT+0800 (China Standard Time)

For me the update has been available automatically, but if i remember remove / re-add the repository force HA to check the last update

Gordon · Answer 48 · Thu Feb 11 2021 00:25:59 GMT+0800 (China Standard Time)

Kudos for the amazing fix!
Anyone missing the function to arm/disarm in the latest 2.3.0? And, the alarm status e.g. arming/disarmed/triggered isn't there as well?

tvl9ops · Answer 49 · Thu Feb 11 2021 01:19:11 GMT+0800 (China Standard Time)

Cannot start 2.3, now it says: Missing required option 'LOGGING_FILE'. This is what @clau-bucur is working on, right?

Claudiu Bucur · Answer 50 · Thu Feb 11 2021 01:36:05 GMT+0800 (China Standard Time)

That should already be working in 2.3.
What I was working on (already finished) but not yet merged, was to add all available PAI config entries to addon config page.

DanieOD · Answer 51 · Thu Feb 11 2021 02:03:39 GMT+0800 (China Standard Time)

Same here. Getting "Cannot start 2.3, now it says: Missing required option 'LOGGING_FILE'. and i have upgraded supervisor and everything including PAI to 2.3.0

kobusdbr · Answer 52 · Thu Feb 11 2021 02:05:59 GMT+0800 (China Standard Time)

Same here. Getting "Cannot start 2.3, now it says: Missing required option 'LOGGING_FILE'. and i have upgraded supervisor and everything including PAI to 2.3.0

shayneob · Answer 53 · Thu Feb 11 2021 02:59:05 GMT+0800 (China Standard Time)

2.3 won't start for me either. Error from logs "21-02-10 18:29:39 ERROR (MainThread) [supervisor.addons.addon] Add-on e92a3241_paradox_alarm_interface has invalid options: Missing required option 'LOGGING_FILE'. Got {'LOGGING_LEVEL_CONSOLE': 20, 'LOGGING_LEVEL_FILE': 40, ..... "
Great to see this in the progress of being fixed, thanks heaps!

Claudiu Bucur · Answer 54 · Thu Feb 11 2021 03:33:26 GMT+0800 (China Standard Time)

Guys, I'm not sure what the problem is here that you're experiencing with Missing required option 'LOGGING_FILE'.
You could add this to your configuration: LOGGING_FILE: log_file.log

I've installed a clean HA instance, and installed PAI release 2.3.
It starts without any problems.
Here's the config I have set. I made changes only to connect to IP and set the correct MQTT credentials:

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: xxx
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: xxx
KEEP_ALIVE_INTERVAL: 10
LIMITS:
  zone: auto
  user: 1-2
  door: ''
  pgm: 1-5
  partition: auto
  module: 1-2
  repeater: ''
  keypad: 1-2
  key-switch: 1-3
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 60
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: xxx
MQTT_PASSWORD: xxx
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
COMMAND_ALIAS:
  arm: partition all arm
  disarm: partition all disarm
MQTT_COMMAND_ALIAS:
  armed_home: arm_stay
  armed_night: arm_sleep
  armed_away: arm
  disarmed: disarm
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHOVER_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
IP_INTERFACE_ENABLE: false
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []
MQTT_PUBLISH_COMMAND_STATUS: true
MQTT_PUBLISH_RAW_EVENTS: false

Claudiu Bucur · Answer 55 · Thu Feb 11 2021 03:48:40 GMT+0800 (China Standard Time)

It might be required to recreate PAI addon configuration, since the schema needed to change...
So try:

to copy your existing PAI configuration to some text editor
reset the PAI addon configuraton to defaults (addon Configuration tab / 3 dots ar Top Right / Reset to defaults)
recreate the configuration based on your old one saved in the text editor

shayneob · Answer 56 · Thu Feb 11 2021 03:57:30 GMT+0800 (China Standard Time)

Perfect, that fixed it - thanks so much!!!

kobusdbr · Answer 57 · Thu Feb 11 2021 04:08:52 GMT+0800 (China Standard Time)

Also. Fixed!! Thanks so much to everyone involved with this project. Really since I enabled this integration I instantly gained access to so many sensors and capabilities. Really fantastic work and thank you.

wondernomore · Answer 58 · Thu Feb 11 2021 09:14:27 GMT+0800 (China Standard Time)

Everything on my HA was working perfectly, until like everyone else, updating to core-2021.2.2/supervisor-2021.02.6.
After updating to PAI 2.3.0 (thank you!), I seem to be having a new issue.

Firstly, I reset the config to defaults, and then recreated the configuration based on my old one.

The error I receive is:
2021-02-11 11:51:46,516 - INFO - PAI - Starting...
2021-02-11 11:51:46,517 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2021-02-11 11:51:46,517 - INFO - PAI.paradox.paradox - Clean Session
2021-02-11 11:51:46,518 - INFO - PAI.paradox.paradox - Connecting to interface
2021-02-11 11:51:46,518 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2021-02-11 11:51:46,519 - ERROR - PAI.paradox.connections.ip.connection - Connect failed (try 1/3): [Errno 111] Connect call failed ('127.0.0.1', 10000)
2021-02-11 11:51:46,520 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 2/3
2021-02-11 11:51:46,521 - ERROR - PAI.paradox.connections.ip.connection - Connect failed (try 2/3): [Errno 111] Connect call failed ('127.0.0.1', 10000)
2021-02-11 11:51:46,521 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 3/3
2021-02-11 11:51:46,521 - ERROR - PAI.paradox.connections.ip.connection - Connect failed (try 3/3): [Errno 111] Connect call failed ('127.0.0.1', 10000)
2021-02-11 11:51:46,522 - ERROR - PAI.paradox.paradox - Failed to connect to interface
2021-02-11 11:51:46,522 - ERROR - PAI - Unable to connect to alarm

Here's my config:

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 127.0.0.1
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: paradox
KEEP_ALIVE_INTERVAL: 10
LIMITS:
  zone: auto
  user: 1-3
  door: ''
  pgm: 1-3
  partition: auto
  module: ''
  repeater: ''
  keypad: ''
  key-switch: ''
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 60
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: xxx
MQTT_PASSWORD: xxx
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
COMMAND_ALIAS:
  arm: partition all arm
  disarm: partition all disarm
MQTT_COMMAND_ALIAS:
  armed_home: arm_stay
  armed_night: arm_sleep
  armed_away: arm
  disarmed: disarm
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHOVER_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
IP_INTERFACE_ENABLE: false
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []

Hopefully something really simple that I have overlooked? Just to reconfirm, PAI was working perfectly before the updates.
Thanks in advance for any help :)

Eric Carriere · Answer 59 · Thu Feb 11 2021 09:21:11 GMT+0800 (China Standard Time)

Hi @wondernomore

Are you sure that your IP100/IP150 is at 127.0.0.1 (localhost). Check your setting for IP_CONNECTION_HOST and the others setting also.

wondernomore · Answer 60 · Thu Feb 11 2021 09:37:02 GMT+0800 (China Standard Time)

Thank you! I updated 127.0.0.1 to the LAN IP of my IP150 and it's connecting again now.
Strange as my previous config had the same 127.0.0.1 is everything connected perfectly.

Now that I'm connected, another small issue has popped up that I haven't seen before now.

I noticed the Gold app was sending alerts saying "Panel Trouble Restore Area 1 by Unknown'.
When I checked the PAI log, it's showing:

2021-02-11 12:25:15,578 - INFO     - PAI.paradox.paradox - Running
2021-02-11 12:25:16,153 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 76.153609 seconds
2021-02-11 12:25:16,269 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:26:07,502 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.502624 seconds
2021-02-11 12:26:07,610 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:27:07,502 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.502007 seconds
2021-02-11 12:27:07,628 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:28:07,551 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.551274 seconds
2021-02-11 12:28:07,661 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:29:07,641 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.641034 seconds
2021-02-11 12:29:07,766 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:30:07,665 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.665111 seconds
2021-02-11 12:30:07,774 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:31:07,707 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 67.707402 seconds
2021-02-11 12:31:07,817 - INFO     - PAI.paradox.paradox - Panel time synchronized

Is there a way to fix or disable this?

Final question, is there a way to associate the connection with a panel user, so that it doesn't say '* by Unknown' in Gold, etc?

Thanks again for all your help and hard work!

gjanarthan · Answer 61 · Thu Feb 11 2021 13:07:02 GMT+0800 (China Standard Time)

Thank you! for the update. My paradox system is connected and all entities active. But couldn't are or disarm through the HA security panel card. Any advice would be really helpful, thanks

When I tried to Arm Home
2021-02-11 12:54:46,411 - INFO - PAI.paradox.paradox - Running
2021-02-11 12:54:59,201 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=arm_stay
2021-02-11 12:54:59,202 - INFO - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=arm_stay user: None
2021-02-11 12:54:59,519 - WARNING - PAI.paradox.paradox - Missing property exit_delay in partition/Area 1
2021-02-11 12:54:59,830 - WARNING - PAI.paradox.paradox - Missing property squawk in partition/Area 1
2021-02-11 12:55:10,058 - INFO - PAI.paradox.paradox - Time drifted more than allowed: 70.058352 seconds
2021-02-11 12:55:10,783 - INFO - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:55:43,757 - WARNING - PAI.paradox.paradox - Missing property arm in partition/Area 1
2021-02-11 12:55:44,030 - WARNING - PAI.paradox.paradox - Missing property arm_stay in partition/Area 1
2021-02-11 12:55:44,257 - WARNING - PAI.paradox.paradox - Missing property arm_force in partition/Area 1
2021-02-11 12:56:00,734 - INFO - PAI.paradox.paradox - Time drifted more than allowed: 60.734604 seconds
2021-02-11 12:56:00,860 - INFO - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:56:04,586 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=disarm
2021-02-11 12:56:04,587 - INFO - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=disarm user: None
2021-02-11 12:56:04,933 - WARNING - PAI.paradox.paradox - Missing property arm_sleep in partition/Area 1
2021-02-11 12:56:04,934 - WARNING - PAI.paradox.paradox - Missing property alarm in partition/Area 1

wondernomore · Answer 62 · Thu Feb 11 2021 13:38:57 GMT+0800 (China Standard Time)

Upon checking, mine is doing the same thing:

2021-02-11 12:48:21,535 - INFO     - PAI.paradox.paradox - Running
2021-02-11 12:49:02,655 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 62.655363 seconds
2021-02-11 12:49:02,764 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:50:02,680 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 62.680776 seconds
2021-02-11 12:50:02,881 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:51:02,727 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 62.727821 seconds
2021-02-11 12:51:02,836 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 12:52:02,774 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 62.774535 seconds
2021-02-11 12:52:02,885 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 14:50:00,044 - INFO     - PAI.paradox.paradox - Time drifted more than allowed: 60.044608 seconds
2021-02-11 14:50:00,154 - INFO     - PAI.paradox.paradox - Panel time synchronized
2021-02-11 16:34:22,773 - INFO     - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=arm_sleep
2021-02-11 16:34:22,774 - INFO     - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=arm_sleep user: None
2021-02-11 16:34:23,054 - WARNING  - PAI.paradox.paradox - Missing property exit_delay in partition/Area 1
2021-02-11 16:34:23,351 - WARNING  - PAI.paradox.paradox - Missing property squawk in partition/Area 1
2021-02-11 16:35:02,603 - WARNING  - PAI.paradox.paradox - Missing property arm in partition/Area 1
2021-02-11 16:35:02,762 - WARNING  - PAI.paradox.paradox - Missing property arm_sleep in partition/Area 1
2021-02-11 16:36:14,858 - INFO     - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=disarm
2021-02-11 16:36:14,859 - INFO     - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=disarm user: None
2021-02-11 16:36:15,195 - WARNING  - PAI.paradox.paradox - Missing property arm_stay in partition/Area 1
2021-02-11 16:36:15,195 - WARNING  - PAI.paradox.paradox - Missing property alarm in partition/Area 1
2021-02-11 16:37:18,238 - INFO     - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=disarm
2021-02-11 16:37:18,239 - INFO     - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=disarm user: None
2021-02-11 16:37:23,390 - INFO     - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Area_1, payload=disarm
2021-02-11 16:37:23,391 - INFO     - PAI.paradox.interfaces.mqtt.basic - Partition command: Area_1=disarm user: None

marius-venter · Answer 63 · Thu Feb 11 2021 13:41:55 GMT+0800 (China Standard Time)

Try to specify:
partition: '1'

Worked for me

wondernomore · Answer 64 · Thu Feb 11 2021 13:47:51 GMT+0800 (China Standard Time)

@marius-venter

That worked for me. Thank you!

gjanarthan · Answer 65 · Thu Feb 11 2021 14:09:44 GMT+0800 (China Standard Time)

Great. Worked for me as well. Thank you very much.

gjanarthan · Answer 66 · Thu Feb 11 2021 14:27:35 GMT+0800 (China Standard Time)

found a new issue. Insite Gold is not connecting while HA is connected. any solution to this?

wondernomore · Answer 67 · Thu Feb 11 2021 14:35:12 GMT+0800 (China Standard Time)

@gjanarthan

It's my understanding that only one connection can be made at a time. This appears to be a limitation of Paradox.
If PAI is connected in Home Assistant, you will not be able to access the system via Insite Gold.
If you stop PAI in Home Assistant, you will be able to access the system via Insite Gold again.

I am using an iPhone, and even though am using PAI via Home Assistant, I still receive arm/disarm/error notification alerts via the Insite Gold app. I just can't open the app to access the system.

ukrolelo · Answer 68 · Thu Feb 11 2021 14:56:20 GMT+0800 (China Standard Time)

Try to specify:
partition: '1'

Worked for me

Greetings, Where it should be specified?

wondernomore · Answer 69 · Thu Feb 11 2021 15:02:32 GMT+0800 (China Standard Time)

@ukrolelo

In PAI add-on, click Configuration.
In the configuration, look for the line 'partition: auto' under the 'LIMITS:' heading.
Replace:
partition: auto
with
partition: '1'

marius-venter · Answer 70 · Thu Feb 11 2021 15:02:53 GMT+0800 (China Standard Time)

Try to specify:
partition: '1'
Worked for me

Greetings, Where it should be specified?

For me it was in the addon configuration page

ukrolelo · Answer 71 · Thu Feb 11 2021 15:04:33 GMT+0800 (China Standard Time)

Try to specify:
partition: '1'
Worked for me

Greetings, Where it should be specified?

For me it was in the addon configuration page

Thx <3

ukrolelo · Answer 72 · Thu Feb 11 2021 15:04:48 GMT+0800 (China Standard Time)

@ukrolelo

In PAI add-on, click Configuration.
In the configuration, look for the line 'partition: auto' under the 'LIMITS:' heading.
Replace:
partition: auto
with
partition: '1'

Thx <3

proasnet · Answer 73 · Thu Feb 11 2021 15:40:48 GMT+0800 (China Standard Time)

Hi, I am probably banana. I have an updated PAI to last release, 2.3.0 with new config scheme. I have a connector as ESP32 via telnet. I have PAI configured as follow:

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 57600
IP_CONNECTION_HOST: 192.168.0.180
IP_CONNECTION_PORT: 23
IP_CONNECTION_PASSWORD: paradox
KEEP_ALIVE_INTERVAL: 10
LIMITS:
zone: auto
user: 1-10
door: ''
pgm: 1-5
partition: auto
module: ''
repeater: ''
keypad: ''
key-switch: ''
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 60
PASSWORD: '****'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: pai
MQTT_PASSWORD: ***************
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
COMMAND_ALIAS:
arm: partition all arm
disarm: partition all disarm
MQTT_COMMAND_ALIAS:
armed_home: arm_stay
armed_night: arm_sleep
armed_away: arm
disarmed: disarm
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:

'live,alarm,-restore'
'live,trouble,-clock'
'live,tamper'
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
'live,alarm,-restore'
'live,trouble,-clock'
'live,tamper'
PUSHOVER_EVENT_FILTERS:
'live,alarm,-restore'
'live,trouble,-clock'
'live,tamper'
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
'live,alarm,-restore'
'live,trouble,-clock'
'live,tamper'
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
'live,alarm,-restore'
'live,trouble,-clock'
'live,tamper'
IP_INTERFACE_ENABLE: true
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []

but PAI is still not connected as next log:

2021-02-11 08:39:28,340 - INFO 2021-02-11 08:39:28,341 - INFO 2021-02-11 08:39:28,343 - INFO 2021-02-11 08:39:28,344 - INFO 2021-02-11 08:39:28,345 - INFO 2021-02-11 08:39:28,447 - INFO 2021-02-11 08:39:28,449 - INFO 2021-02-11 08:39:28,456 - ERROR 2021-02-11 08:39:28,457 - ERROR 2021-02-11 08:39:30,458 - ERROR 2021-02-11 08:39:30,459 - INFO 2021-02-11 08:39:30,496 - INFO 2021-02-11 08:39:30,498 - INFO 2021-02-11 08:39:30,505 - ERROR 2021-02-11 08:39:30,507 - ERROR 2021-02-11 08:39:32,508 - ERROR 2021-02-11 08:39:32,509 - INFO 2021-02-11 08:39:32,543 - INFO 2021-02-11 08:39:32,546 - INFO 2021-02-11 08:39:32,554 - ERROR 2021-02-11 08:39:32,555 - ERROR 2021-02-11 08:39:34,557 - ERROR 2021-02-11 08:39:34,559 - ERROR 2021-02-11 08:39:34,560 - ERROR - PAI - Starting...
- PAI.paradox.paradox - Disconnecting from the Alarm Panel
- PAI.paradox.paradox - Clean Session
- PAI.paradox.paradox - Connecting to interface
- PAI.paradox.connections.ip.connection - Connecting. Try 1/3
- PAI.paradox.connections.connection - Connection established
- PAI.paradox.connections.ip.commands - Authenticating with IP Module
- PAI.paradox.connections.protocols - Connection was closed: None
- PAI.paradox.connections.connection - Connection was lost
- PAI.paradox.connections.ip.connection - Timeout while establishing connection (try 1/3):
- PAI.paradox.connections.ip.connection - Connecting. Try 2/3
- PAI.paradox.connections.connection - Connection established
- PAI.paradox.connections.ip.commands - Authenticating with IP Module
- PAI.paradox.connections.protocols - Connection was closed: None
- PAI.paradox.connections.connection - Connection was lost
- PAI.paradox.connections.ip.connection - Timeout while establishing connection (try 2/3):
- PAI.paradox.connections.ip.connection - Connecting. Try 3/3
- PAI.paradox.connections.connection - Connection established
- PAI.paradox.connections.ip.commands - Authenticating with IP Module
- PAI.paradox.connections.protocols - Connection was closed: None
- PAI.paradox.connections.connection - Connection was lost
- PAI.paradox.connections.ip.connection - Timeout while establishing connection (try 3/3):
- PAI.paradox.paradox - Failed to connect to interface
- PAI - Unable to connect to alarm

Can me somebody help please?

gjanarthan · Answer 74 · Thu Feb 11 2021 16:04:14 GMT+0800 (China Standard Time)

Change the IP_CONNECTION_PORT: 23 to IP_CONNECTION_PORT: 100000

Claudiu Bucur · Answer 75 · Thu Feb 11 2021 16:22:52 GMT+0800 (China Standard Time)

Hi, I am probably banana. I have an updated PAI to last release, 2.3.0 with new config scheme. I have a connector as ESP32 via telnet. I have PAI configured as follow:

Can me somebody help please?

Share your old configuration that worked, if you still have it.
But please use the "Insert code" feature to properly format the configuration text.

Change the IP_CONNECTION_PORT: 23 to IP_CONNECTION_PORT: 100000

Maybe his ESP32 runs on the standard telnet port, in which case 23 would be correct.
Anyways, it should be port 10000, one 0 less 😀

Jevgeni Kiski · Answer 76 · Thu Feb 11 2021 17:23:42 GMT+0800 (China Standard Time)

Time drifted more than allowed: 62.655363 seconds

Fixed in default settings.

Set SYNC_TIME_MIN_DRIFT to 120. SP/MG can not sync to a second precision.

Woody · Answer 77 · Thu Feb 11 2021 18:01:14 GMT+0800 (China Standard Time)

Thanks for the really fast fixing!

With this new version, when I arm the alarm, I get only the arming message, but I don't get the armed one and in the alarm panel I get a continuous blinking Watiting icon.

What can I check?

Thanks

marius-venter · Answer 78 · Thu Feb 11 2021 18:04:34 GMT+0800 (China Standard Time)

Thanks for the really fast fixing!

With this new version, when I arm the alarm, I get only the arming message, but I don't get the armed one and in the alarm panel I get a continuous blinking Watiting icon.

What can I check?

Thanks

Replace:
partition: auto
with
partition: '1'

Claudiu Bucur · Answer 79 · Thu Feb 11 2021 18:20:01 GMT+0800 (China Standard Time)

partition: auto should work usually, in which case PAI will load all active partitions from your panel.
If it's not working, until it's gonna be fixed, it should be replaced with partition: 1-n where n is the number of parititions you currently have.
If you have more than one partition, as I do (3), by saying 'partition: 1 you'll instruct PAI to only load the first partition from your panel.

Woody · Answer 80 · Thu Feb 11 2021 19:01:16 GMT+0800 (China Standard Time)

@clau-bucur my configuration was
partition: 1-2
and it was not working fine.
Now with
partition: '1'
It's working fine

Claudiu Bucur · Answer 81 · Thu Feb 11 2021 19:08:08 GMT+0800 (China Standard Time)

I see, then to me it looks like another bug in the limits parsing.
What do you think @yozik04 ?

proasnet · Answer 82 · Thu Feb 11 2021 22:58:34 GMT+0800 (China Standard Time)

Hi, I am probably banana. I have an updated PAI to last release, 2.3.0 with new config scheme. I have a connector as ESP32 via telnet. I have PAI configured as follow:
Can me somebody help please?

Share your old configuration that worked, if you still have it.
But please use the "Insert code" feature to properly format the configuration text.

Change the IP_CONNECTION_PORT: 23 to IP_CONNECTION_PORT: 100000

Maybe his ESP32 runs on the standard telnet port, in which case 23 would be correct.
Anyways, it should be port 10000, one 0 less 😀
Paradox EVOHD 7.51
This is my old config:
LOGGING_FILE: /config/paradox.log LOGGING_LEVEL_CONSOLE: 20 LOGGING_LEVEL_FILE: 40 LOGGING_DUMP_PACKETS: true LOGGING_DUMP_MESSAGES: true LOGGING_DUMP_STATUS: false LOGGING_DUMP_EVENTS: false CONNECTION_TYPE: IP SERIAL_PORT: /dev/ttyUSB0 SERIAL_BAUD: 57600 IP_CONNECTION_HOST: 192.168.0.180 IP_CONNECTION_PORT: 23 IP_CONNECTION_PASSWORD: paradox IP_CONNECTION_SITEID: null IP_CONNECTION_EMAIL: null IP_CONNECTION_PANEL_SERIAL: null IP_CONNECTION_BARE: true LIMITS: {} SYNC_TIME: true PASSWORD: **** MQTT_ENABLE: true MQTT_HOST: core-mosquitto MQTT_PORT: 1883 MQTT_USERNAME: pai MQTT_PASSWORD: ****************** MQTT_RETAIN: true MQTT_BIND_ADDRESS: 127.0.0.1 MQTT_BIND_PORT: 0 MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true

Jevgeni Kiski · Answer 83 · Thu Feb 11 2021 23:40:07 GMT+0800 (China Standard Time)

@clau-bucur my configuration was
partition: 1-2
and it was not working fine.
Now with
partition: '1'
It's working fine

what if you enter '1-2' with quotes?

Jevgeni Kiski · Answer 84 · Thu Feb 11 2021 23:41:14 GMT+0800 (China Standard Time)

I see, then to me it looks like another bug in the limits parsing.
What do you think @yozik04 ?

LIMITS parsing it is 100% covered with tests. Can't be. No idea yet.

Johann Kellerman · Answer 85 · Thu Feb 11 2021 23:49:34 GMT+0800 (China Standard Time)

what if you enter '1-2' with quotes?

No difference. only partition: 1 works 100% for me

The user interface immediately validates '1-2' as a string and removes the quotes (it's still a valid yaml string as 1-2)

nardusleroux · Answer 86 · Fri Feb 12 2021 02:48:17 GMT+0800 (China Standard Time)

I have 2 partitions on panel and have tried partition: 1-2 , partition: 1,2 and partition: auto and at least both partitions labels are loaded from panel. Seeing same thing, if I sleep_arm partition 2, I never get armed icon, just keep on flashing arming, but can disarm. There after I cannot sleep_arm again, since still just flashing arming. The partition gets sleep_armed and disarmed succesfully on panel. Here is logs during sleep_arm and disarm. Seems the "Missing Property" is problematic? Partition 2 label is Perimeter.

2021-02-11 20:29:07,569 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Perimeter, payload=arm_sleep
2021-02-11 20:29:07,572 - INFO - PAI.paradox.interfaces.mqtt.basic - Partition command: Perimeter=arm_sleep user: None
2021-02-11 20:29:07,840 - WARNING - PAI.paradox.paradox - Missing property exit_delay in partition/Perimeter
2021-02-11 20:29:08,134 - WARNING - PAI.paradox.paradox - Missing property squawk in partition/House
2021-02-11 20:29:37,598 - WARNING - PAI.paradox.paradox - Missing property arm in partition/Perimeter
2021-02-11 20:29:37,715 - WARNING - PAI.paradox.paradox - Missing property arm_sleep in partition/Perimeter
2021-02-11 20:30:30,505 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Perimeter, payload=disarm
2021-02-11 20:30:30,506 - INFO - PAI.paradox.interfaces.mqtt.basic - Partition command: Perimeter=disarm user: None
2021-02-11 20:30:30,788 - WARNING - PAI.paradox.paradox - Missing property arm_stay in partition/Perimeter
2021-02-11 20:30:30,789 - WARNING - PAI.paradox.paradox - Missing property alarm in partition/Perimeter

JeanDiv14 · Answer 87 · Fri Feb 12 2021 03:24:48 GMT+0800 (China Standard Time)

+1 for the issue. Had been working brilliantly for months. Annoying loop now is that Paradox wont start because it wont take a blank PASSWORD (this was the only way it was working before), and every time I try to change anything in the config file I get this same error...

Failed to save addon configuration, not a valid value for dictionary value @ data['options']. Got {'LOGGING_LEVEL_CONSOLE': 20, 'LOGGING_LEVEL_FILE': 40, 'CONNECTION_TYPE': 'IP', 'SERIAL_PORT': '/dev/ttyUSB0', 'SERIAL_BAUD': 9600, 'IP_CONNECTION_HOST': '192.xx.xx.xx', 'IP_CONNECTION_PORT': 10000, 'IP_CONNECTION_PASSWORD': 'xxxx', 'KEEP_ALIVE_INTERVAL': 10, 'LIMITS': {}, 'SYNC_TIME': True, 'SYNC_TIME_MIN_DRIFT': 60, 'PASSWORD': None, 'MQTT_ENABLE': True, 'MQTT_HOST': 'core-mosquitto', 'MQTT_PORT': 1883, 'MQTT_KEEPALIVE': 60, 'MQTT_USERNAME': 'xxxx', 'MQTT_PASSWORD': 'xxxx', 'MQTT_...

So not able to boot :-(

Any advice, pls?

Tx,
Jean

Brendan Ward · Answer 88 · Fri Feb 12 2021 04:17:36 GMT+0800 (China Standard Time)

As someone said before, in the configuration page, copy your old configuration to a text file on your computer. Then press the three dots above your configuration and 'Reset to defaults'. Defaults should work. Then go line by line adding your own settings, saving each time. The limits settings were usually what threw an error in my config.

Claudiu Bucur · Answer 89 · Fri Feb 12 2021 04:41:12 GMT+0800 (China Standard Time)

I could say that these issues appear because the addon configuration is not correctly being translated to PAI configuration json.
@yozik04 correct if I'm wrong. But nothing else changed, just the way the config data gets to PAI.
So, I think the following information would be helpful (I did this too during schema creation process):

what panel are you using (EVO/SP/whatever) and the firmware;
the addon configuration as you have it under PAI addon Configuration tab;
the generated options.json file that the addon creates based on 2.. This is the actual configuration file that PAI is using. This might not be properly generated!

Of course, remove any sensitive data from the attached data, and include it using the "include code" feature.
Now, the hardest part is getting the options.json file. Here's how I did it, using Portainer addon:

by default Hassio addons are hidden in Portainer, so you have to unhide them
open Portainer and go to Settings and under the Hidden containers section, remove the row with value addon
go to Containers, find your PAI addon, and under the Quick actions section click on Exec console
under Command select /bin/sh then click Connect
after connection type in: more /data/options.json
it will show most of the file. Press R to show the rest of the file
select the text from the console and paste it here

Here's my example:
Panel: EVO192

Addon config:

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: xxx
IP_CONNECTION_PORT: xxx
IP_CONNECTION_PASSWORD: xxx
KEEP_ALIVE_INTERVAL: 10
LIMITS:
  zone: auto
  user: 1-2
  door: ''
  pgm: 1-5
  partition: auto
  module: 1-2
  repeater: ''
  keypad: 1-2
  key-switch: 1-3
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 60
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: xxx
MQTT_PASSWORD: xxx
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
COMMAND_ALIAS:
  arm: partition all arm
  disarm: partition all disarm
MQTT_COMMAND_ALIAS:
  armed_home: arm_stay
  armed_night: arm_sleep
  armed_away: arm
  disarmed: disarm
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
PUSHOVER_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
  - 'live,alarm,-restore'
  - 'live,trouble,-clock'
  - 'live,tamper'
IP_INTERFACE_ENABLE: false
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []
MQTT_PUBLISH_COMMAND_STATUS: true
MQTT_PUBLISH_RAW_EVENTS: false

options.json:

{
  "LOGGING_LEVEL_CONSOLE": 20,
  "LOGGING_LEVEL_FILE": 40,
  "CONNECTION_TYPE": "IP",
  "SERIAL_PORT": "/dev/ttyUSB0",
  "SERIAL_BAUD": 9600,
  "IP_CONNECTION_HOST": "xxx",
  "IP_CONNECTION_PORT": xxx,
  "IP_CONNECTION_PASSWORD": "xxx",
  "KEEP_ALIVE_INTERVAL": 10,
  "LIMITS": {
    "zone": "auto",
    "user": "1-2",
    "door": "",
    "pgm": "1-5",
    "partition": "auto",
    "module": "1-2",
    "repeater": "",
    "keypad": "1-2",
    "key-switch": "1-3"
  },
  "SYNC_TIME": true,
  "SYNC_TIME_MIN_DRIFT": 60,
  "PASSWORD": "0000",
  "MQTT_ENABLE": true,
  "MQTT_HOST": "core-mosquitto",
  "MQTT_PORT": 1883,
  "MQTT_KEEPALIVE": 60,
  "MQTT_USERNAME": "xxx",
  "MQTT_PASSWORD": "xxx",
  "MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE": true,
  "COMMAND_ALIAS": {
    "arm": "partition all arm",
    "disarm": "partition all disarm"
  },
  "MQTT_COMMAND_ALIAS": {
    "armed_home": "arm_stay",
    "armed_night": "arm_sleep",
    "armed_away": "arm",
    "disarmed": "disarm"
  },
  "HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS": [
    "live,alarm,-restore",
    "live,trouble,-clock",
    "live,tamper"
  ],
  "PUSHBULLET_CONTACTS": [],
  "PUSHBULLET_EVENT_FILTERS": [
    "live,alarm,-restore",
    "live,trouble,-clock",
    "live,tamper"
  ],
  "PUSHOVER_EVENT_FILTERS": [
    "live,alarm,-restore",
    "live,trouble,-clock",
    "live,tamper"
  ],
  "SIGNAL_CONTACTS": [],
  "SIGNAL_EVENT_FILTERS": [
    "live,alarm,-restore",
    "live,trouble,-clock",
    "live,tamper"
  ],
  "GSM_CONTACTS": [],
  "GSM_EVENT_FILTERS": [
    "live,alarm,-restore",
    "live,trouble,-clock",
    "live,tamper"
  ],
  "IP_INTERFACE_ENABLE": false,
  "IP_INTERFACE_PASSWORD": "paradox",
  "DUMMY_EVENT_FILTERS": [],
  "MQTT_PUBLISH_COMMAND_STATUS": true,
  "MQTT_PUBLISH_RAW_EVENTS": false
}

Jevgeni Kiski · Answer 90 · Fri Feb 12 2021 05:33:47 GMT+0800 (China Standard Time)

@JeanDiv14 0000 equals ``

Jevgeni Kiski · Answer 91 · Fri Feb 12 2021 07:08:15 GMT+0800 (China Standard Time)

2.3.1 released. Hurry to be first and get it nice and shiny with latest bug fixes.

Closing this issue as this is now fixed. Create new issues if you have problems.

Jevgeni Kiski · Answer 92 · Fri Feb 12 2021 07:08:46 GMT+0800 (China Standard Time)

@clau-bucur Thanks for taking care while I was away.

JeanDiv14 · Answer 93 · Sun Feb 14 2021 11:26:34 GMT+0800 (China Standard Time)

As someone said before, in the configuration page, copy your old configuration to a text file on your computer. Then press the three dots above your configuration and 'Reset to defaults'. Defaults should work. Then go line by line adding your own settings, saving each time. The limits settings were usually what threw an error in my config.

I missed it above, but it worked for me!

I went line-by-line, and weirdly it looks like the 1 that was causing the pain was the MQTT Username & Password.. If I pasted the value from notepad, it failed with the dictionary error. When I re-typed it.. it worked. I'm using a MacBook, if that means anything.

Thanks to all for the advice, and for fixing this :-)

gmow1 · Answer 94 · Wed Feb 17 2021 23:47:06 GMT+0800 (China Standard Time)

I'm getting the following error, I do not have the Installer code as my installer disappeared...any suggestions?

2021-02-17 08:44:48,804 - INFO - PAI.paradox.connections.ip.commands - Session successfully established with IP Module
2021-02-17 08:44:48,804 - INFO - PAI.paradox.paradox - Connecting to Panel
2021-02-17 08:44:48,907 - INFO - PAI.paradox.paradox - Panel Identified SP6000 version 4.54 build -1
2021-02-17 08:44:48,908 - INFO - PAI.paradox.paradox - Initiating panel connection
2021-02-17 08:44:49,038 - INFO - PAI.paradox.hardware.spectra_magellan.panel - Installer login
2021-02-17 08:44:49,138 - ERROR - PAI.paradox.paradox - Got ERROR Message: Invalid PC Password
2021-02-17 08:44:49,140 - ERROR - PAI.paradox.lib.handlers - Exception caught during message handling
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/paradox/lib/handlers.py", line 112, in handle
await handler(data)
File "/usr/local/lib/python3.7/site-packages/paradox/lib/handlers.py", line 61, in call
result = self._handle(data)
File "/usr/local/lib/python3.7/site-packages/paradox/paradox.py", line 638, in handle_error_message
raise AuthenticationFailed()

Jevgeni Kiski · Answer 95 · Thu Feb 18 2021 16:28:33 GMT+0800 (China Standard Time)

@gmow1 =) Just 0000-9999 to try. Every 5 wrong it locks for I think 15 minutes. I let you do the math.

gmow1 · Answer 96 · Thu Feb 18 2021 22:19:58 GMT+0800 (China Standard Time)

Got it figured out, so far so good. Key issues with my setup was PC Password and no 0(zero's) in the PC Password. FYI My setup is MG6000, IP150+ with latest firmware