Stop working after update to HA OS 5.11 #199
Comments
sicarriere
added
bug
|
I have the same issue but note sure if it is the upgrade of HA OS or HA Supervisor to 2021.02.5. |
|
In the supervisor log there is this : |
|
Same issue here. After HassOS and Supervisor upgrades. |
What are these addons? |
|
See this one for example: hassio-addons/addon-ssh@5f8a384 |
|
VS Code : hassio-addons/addon-vscode@ce707ad All with the same kind of commit |
|
I also updated that but it does not solve the problem. |
|
Same here, HA OS 5.11 broke the integration. |
|
Ditto for me - updated both HASS and Core and now PAI is dead - same errors in my logs as posted above. |
|
same here with |
|
I have updated to the latest but still getting the errors: |
|
Why it does even need /dev/ttyS1 if its over LAN ?! |
|
Because Supervisor maintainers love to break things. |
I'm guessing it is falling back to defaults if it can't read the configuration |
Yeah sound logic |
xD |
2021-02-09 09:44:40,956 - INFO - PAI - Starting Paradox Alarm Interface 2.2.5 Its loaded correctly so saying |
|
I wanted to delete |
|
No. I am 90% that all addons that did not specified configuration schema are now out of luck. I think this change in supervisor broke it: |
|
So what can we do? :-D my knowledge is limited to banana,potato,python :-D |
|
Can please someone give me output of |
Can you tell me where? like server logs? or PAI logs? |
|
in |
|
|
Interesting i have same but supervisor: 2021.02.5 not supervisor: 2021.02.6 |
|
I update it this morning, maybe it will come later for you. |
|
I have filed a bug report. Let's wait for a response. |
|
In PAI add-on, click Configuration. |
For me it was in the addon configuration page |
Thx <3 |
Thx <3 |
|
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
but PAI is still not connected as next log: 2021-02-11 08:39:28,340 - INFO - PAI - Starting... Can me somebody help please? |
|
Change the IP_CONNECTION_PORT: 23 to IP_CONNECTION_PORT: 100000 |
Share your old configuration that worked, if you still have it.
Maybe his ESP32 runs on the standard telnet port, in which case 23 would be correct. |
|
👍 |
Fixed in default settings. Set |
|
Thanks for the really fast fixing! With this new version, when I arm the alarm, I get only the
What can I check? Thanks |
Replace: |
|
|
|
@clau-bucur my configuration was |
|
I see, then to me it looks like another bug in the limits parsing. |
|
what if you enter '1-2' with quotes? |
LIMITS parsing it is 100% covered with tests. Can't be. No idea yet. |
No difference. only The user interface immediately validates '1-2' as a string and removes the quotes (it's still a valid yaml string as 1-2) |
|
I have 2 partitions on panel and have tried 2021-02-11 20:29:07,569 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Perimeter, payload=arm_sleep |
|
+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...
So not able to boot :-( Any advice, pls? Tx, |
|
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 could say that these issues appear because the addon configuration is not correctly being translated to PAI configuration json.
Of course, remove any sensitive data from the attached data, and include it using the "include code" feature.
Here's my example: Addon config: options.json: |
|
@JeanDiv14 |
|
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. |
|
@clau-bucur Thanks for taking care while I was away. |
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 :-) |
|
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 |
|
@gmow1 =) Just |
|
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 |
and others
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
The text was updated successfully, but these errors were encountered: