EVOHD fw 4.50: Got ERROR Message: Invalid record type #198

proasnet · 2021-02-01T10:21:11Z

Alarm system

EVOHD fw 4.50 over ESP32 serial telnet
described here
https://github.com/espressif/arduino-esp32/blob/master/libraries/WiFi/examples/WiFiTelnetToSerial/WiFiTelnetToSerial.ino
with UART level converter 5/3,3V ( without convert is not possible estabilish connection )

Environment

HA on RPI HASSIO

Git branch

HASSIO, docker, HAOS

Question

I found descriptions the same problem here
#127
but it not help me.
I can not find problem of this error.
And it seems there is no data on MQTT topics.
MQTT is Mosquitto broker
Current version: 5.1
`logins:

username: xxxxxx
password: xxxxxxx
anonymous: false
customize:
active: false
folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false`

Logs (if required)

I have configured logging as described in help, but in a location defined in conf is nothing.
LOGGING_FILE: /tmp/paradox.log

log from addon
2021-02-01 11:03:52,127 - INFO - PAI.paradox.paradox - Connection OK 2021-02-01 11:03:52,128 - INFO - PAI.paradox.paradox - Loading data from panel memory 2021-02-01 11:03:52,129 - INFO - PAI.paradox.hardware.panel - Loading definitions 2021-02-01 11:03:52,130 - INFO - PAI.paradox.hardware.panel - Updating Definitions from Panel 2021-02-01 11:03:52,682 - INFO - PAI.paradox.hardware.panel - Zone definitions loaded (0.55s) 2021-02-01 11:03:52,702 - INFO - PAI.paradox.hardware.panel - Partition definitions loaded (0.02s) 2021-02-01 11:04:02,627 - INFO - PAI.paradox.hardware.panel - User definitions loaded (9.92s) 2021-02-01 11:04:03,503 - INFO - PAI.paradox.hardware.panel - Loading labels 2021-02-01 11:04:03,503 - INFO - PAI.paradox.hardware.panel - Updating Labels from Panel 2021-02-01 11:04:03,727 - INFO - PAI.paradox.hardware.panel - Zone labels loaded (0.22s): xxxxxxxx 2021-02-01 11:04:04,478 - INFO - PAI.paradox.hardware.panel - Partition labels loaded (0.07s): xxxxxxxxx 2021-02-01 11:04:08,976 - INFO - PAI.paradox.paradox - Running 2021-02-01 11:04:10,572 - ERROR - PAI.paradox.paradox - Got ERROR Message: Invalid record type 2021-02-01 11:04:11,492 - ERROR - PAI.paradox.paradox - Got ERROR Message: Invalid record type
total 39 times
then
2021-02-01 11:04:54,220 - INFO - PAI.paradox.paradox - Disconnecting from the Alarm Panel 2021-02-01 11:04:54,222 - INFO - PAI.paradox.paradox - Clean Session 2021-02-01 11:04:54,223 - INFO - PAI.paradox.paradox - Cleaning previous session. Closing connection 2021-02-01 11:04:54,229 - ERROR - PAI.paradox.connections.protocols - Connection was closed: None 2021-02-01 11:04:54,231 - ERROR - PAI.paradox.connections.connection - Connection was lost 2021-02-01 11:04:54,235 - INFO - PAI.paradox.paradox - Disconnected from the Alarm Panel
and again again

The text was updated successfully, but these errors were encountered:

yozik04 · 2021-02-01T11:23:59Z

Most probably too old firmware.

proasnet · 2021-02-01T11:32:02Z

I thing too. I want upgrade fw, but in Infield (latest) I will connect via serial to panel, then in in the list, I open file browser, select puf file with never EVOHD firmware, and then I get error message that file is not for my panel..
downloaded from paradox.com

proasnet · 2021-02-02T06:05:47Z

Error SOLVED !
Used panel is EVOHD with 4.50 firmware, updated to 7.31
Firmware version 4.5 is not function with PAI. Must be never.
Latest version of Infield from paradox for update from version 4.50 can not be used. Not loading never puf files. I use older 4.26.4 Infield for update to 7.31 EVOHD puf file.
My older panel EVO192 with fw 2.80 is not possible update, puf file with never firmware is not loaded to Infield 4.26.4, is another hardware revision probably.

UART connector on EVO HD has this connection
Serial on Panel LM2956 ESP32
┌───────┐
│ Tx................┌╵ == > 5V== > LEVEL CONVERTER == > 3,3V == > == > == > RX2
│ Rx...............│ == > 5V == > LEVEL CONVERTER == > 3,3V == > == > == > TX2
│ GND..........│ == > IN(-) -> OUT(-) == > USB GND
│ AUX+........└╷ == > IN(+) -> OUT(+) == > USB 5V
└───────┘

Here is used level converter
https://i.stack.imgur.com/YMjIK.gif
You can use any universal NPN transistors, I used BC547
Now, all working fine and this Issue can be closed.

yozik04 · 2021-02-03T13:13:44Z

I have updated Compatibility and referred this ticket in Connection methods pages in the wiki.
If you have something to add regarding your setup with ESP32 feel free to edit this page: https://github.com/ParadoxAlarmInterface/pai/wiki/Connection-methods#serial-over-ip-esp32

yozik04 · 2021-02-03T13:14:11Z

And congrats for solving this. Enjoy.

proasnet · 2021-02-03T21:02:56Z

In future I remake esp32 interface to arduino uno with ethernet shield. Will ne connected over wired lan. Thank you for support.

ezequiellop · 2021-05-21T20:48:15Z

es LM2956 o LM2596?

ezequiellop · 2021-06-11T01:52:51Z

Hi, I'm trying to connect I get this error.
2021-06-10 22:48:46,938 - INFO 2021-06-10 22:48:46,938 - INFO 2021-06-10 22:48:46,939 - INFO 2021-06-10 22:48:47,181 - INFO 2021-06-10 22:48:47,184 - INFO 2021-06-10 22:48:47,191 - INFO 2021-06-10 22:48:47,193 - INFO 2021-06-10 22:48:47,194 - INFO 2021-06-10 22:48:47,195 - INFO 2021-06-10 22:48:47,776 - INFO 2021-06-10 22:48:48,200 - INFO 2021-06-10 22:48:57,327 - INFO 2021-06-10 22:48:57,329 - INFO 2021-06-10 22:48:57,429 - ERROR 2021-06-10 22:48:57,430 - ERROR 2021-06-10 22:48:58,338 - ERROR 2021-06-10 22:48:58,341 - ERROR 2021-06-10 22:49:01,347 - INFO 2021-06-10 22:49:01,347 - INFO 2021-06-10 22:49:01,348 - INFO 2021-06-10 22:49:01,350 - INFO 2021-06-10 22:49:01,351 - INFO 2021-06-10 22:50:08,327 - INFO 2021-06-10 22:50:08,329 - INFO 2021-06-10 22:50:08,335 - ERROR 2021-06-10 22:50:08,337 - ERROR my evo48 using ESP32, but I can't connect.
- PAI - Starting Paradox Alarm Interface 2.5.3
- PAI - Config loaded from /data/options.json
- PAI - Console Log level set to 20
- PAI.paradox.interfaces - Starting BasicMQTTInterface Interface
- PAI.paradox.interfaces.mqtt.core - MQTT loop started
- PAI.paradox.interfaces - Starting HomeAssistantMQTTInterface Interface
- PAI - Starting...
- PAI.paradox.paradox - Connecting to interface
- PAI.paradox.paradox - Using IP Connection
- PAI.paradox.connections.ip.connection - Connecting. Try 1/3
- PAI.paradox.interfaces.mqtt.core - MQTT Broker Connected
- PAI.paradox.connections.connection - Connection established
- PAI.paradox.paradox - Connecting to Panel
- PAI.paradox.connections.protocols - Connection was closed: [Errno 104] Connection reset by peer
- PAI.paradox.connections.connection - Connection was lost
- PAI.paradox.paradox - Failed to connect: Not connected
- PAI - Unable to connect to alarm
- 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.paradox - Connecting to Panel
- PAI.paradox.connections.protocols - Connection was closed: None
- PAI.paradox.connections.connection - Connection was lost

my configuration is the following

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 192.168.1.106
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: 120
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: 192.168.1.115
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: village
MQTT_PASSWORD: village6624
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
PUSHOVER_BROADCAST_KEYS: []
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: []
IP_CONNECTION_BARE: true

yozik04 · 2021-06-11T19:04:33Z

Panel blocks connection for some reason. Try to restart the panel. Remember you can have only one connection at a time.

danilodivaio · 2021-08-14T09:19:08Z

Good morning, I try to connect to alarm panel (paradox EVO 192 by serial over ip with a esp32) but I've a problem:

2021-08-14 11:11:11,871 - INFO - PAI.paradox.connections.ip.connection - Connecting. Try 1/3
2021-08-14 11:11:11,988 - INFO - PAI.paradox.connections.connection - Connection established
2021-08-14 11:11:11,990 - INFO - PAI.paradox.paradox - Connecting to Panel
2021-08-14 11:11:17,004 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active?
2021-08-14 11:11:17,006 - ERROR - PAI - Unable to connect to alarm

my configuration:

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 57600
IP_CONNECTION_HOST: 192...*
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: 120
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: *********
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
PUSHOVER_BROADCAST_KEYS: []
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: []
IP_CONNECTION_BARE: true

how can i solve? Thanks to all!

intensite · 2022-09-29T03:16:13Z

Sorry to revive this old thread, I just discovered this great interface to Paradox.

I have PAI installed in a docker container and it communicates successfully with the IP Module, the EVOHD Panel and even the MQTT Broker (see image bellow). However after a while, I get the "Invalid record type" messages.
I have the dreaded EVOHD version 4.50 with the IP150 module.

I read in @proasnet post that a Firmware upgrade solves the problem. Can you provide some pointers as to where I can get some instructions on how to perform the upgrade? What version of Firmware do you recommend ?

Have a good day!

yozik04 · 2022-09-29T11:44:38Z

Write in gitter. Maybe somebody will find you a link.

proasnet added the question Further information is requested label Feb 1, 2021

yozik04 changed the title ~~Got ERROR Message: Invalid record type~~ EVOHD fw 4.50: Got ERROR Message: Invalid record type Feb 1, 2021

yozik04 added evohd help wanted Extra attention is needed esp32 labels Feb 1, 2021

proasnet closed this as completed Feb 2, 2021

proasnet mentioned this issue Oct 11, 2021

Problem with serial over ip with a esp32. #259

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

EVOHD fw 4.50: Got ERROR Message: Invalid record type #198

EVOHD fw 4.50: Got ERROR Message: Invalid record type #198

proasnet commented Feb 1, 2021 •

edited

Loading

yozik04 commented Feb 1, 2021

proasnet commented Feb 1, 2021 •

edited

Loading

proasnet commented Feb 2, 2021 •

edited

Loading

yozik04 commented Feb 3, 2021

yozik04 commented Feb 3, 2021

proasnet commented Feb 3, 2021

ezequiellop commented May 21, 2021

ezequiellop commented Jun 11, 2021

yozik04 commented Jun 11, 2021

danilodivaio commented Aug 14, 2021

intensite commented Sep 29, 2022

yozik04 commented Sep 29, 2022

EVOHD fw 4.50: Got ERROR Message: Invalid record type #198

EVOHD fw 4.50: Got ERROR Message: Invalid record type #198

Comments

proasnet commented Feb 1, 2021 • edited Loading

Alarm system

Environment

Git branch

Question

Logs (if required)

yozik04 commented Feb 1, 2021

proasnet commented Feb 1, 2021 • edited Loading

proasnet commented Feb 2, 2021 • edited Loading

yozik04 commented Feb 3, 2021

yozik04 commented Feb 3, 2021

proasnet commented Feb 3, 2021

ezequiellop commented May 21, 2021

ezequiellop commented Jun 11, 2021

yozik04 commented Jun 11, 2021

danilodivaio commented Aug 14, 2021

intensite commented Sep 29, 2022

yozik04 commented Sep 29, 2022

proasnet commented Feb 1, 2021 •

edited

Loading

proasnet commented Feb 1, 2021 •

edited

Loading

proasnet commented Feb 2, 2021 •

edited

Loading