Jablotron JA-80 series and JA-100 series alarm integration

Marcel1 · February 19, 2023, 6:25pm

Yes it does. Everything else works like a charm, but only when the alarm is tripped (loud siren), the integration displays that as armed_away

mattsaxon · February 19, 2023, 7:13pm

Which interestin are we talking, this thread covers a number of them. I’d suggest raising an issue on the relevant GitHub repo for the specific integration. This is deffo a bug!

Marcel1 · February 20, 2023, 7:24pm

Yes sure. Thanks.

DamianB · May 20, 2023, 5:22pm

Hi,
Is it possible to use the integration with the use of a USB/RS485 converter connected directly to the HA? The olink software easily connects through the convent with the alarm control panel over the A/B lines.
Unfortunately, the integration does not connect.
I will only add that I have a jablotron 83k, maybe there is a problem here?

mattsaxon · May 20, 2023, 5:50pm

If olink connects via same connector this seems feasible. However what USB driver are you using?

Ja-83k I don’t think should be an issue. Can you send a debug trace from the integration using the info from the GitHub repo and post an issue there?

DamianB · May 20, 2023, 7:36pm

I use drivers from HassOS, I tested with two converters:

waveshare FT232RL and SP485EEN chip
RS485 CH340 Modbus Profibus PLC

Hardware view from HA:

DEVLINKS: >-
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A10LSIEJ-if00-port0
/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0
DEVNAME: /dev/ttyUSB2
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB2/tty/ttyUSB2
ID_BUS: usb
ID_MODEL: FT232R_USB_UART
ID_MODEL_ENC: FT232R\x20USB\x20UART
ID_MODEL_ID: ‘6001’
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_1_0
ID_REVISION: ‘0600’
ID_SERIAL: FTDI_FT232R_USB_UART_A10LSIEJ
ID_SERIAL_SHORT: A10LSIEJ
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ‘:ffffff:’
ID_USB_INTERFACE_NUM: ‘00’
ID_USB_MODEL: FT232R_USB_UART
ID_USB_MODEL_ENC: FT232R\x20USB\x20UART
ID_USB_MODEL_ID: ‘6001’
ID_USB_REVISION: ‘0600’
ID_USB_SERIAL: FTDI_FT232R_USB_UART_A10LSIEJ
ID_USB_SERIAL_SHORT: A10LSIEJ
ID_USB_TYPE: generic
ID_USB_VENDOR: FTDI
ID_USB_VENDOR_ENC: FTDI
ID_USB_VENDOR_ID: ‘0403’
ID_VENDOR: FTDI
ID_VENDOR_ENC: FTDI
ID_VENDOR_ID: ‘0403’
MAJOR: ‘188’
MINOR: ‘2’
SUBSYSTEM: tty
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘3600546941’

Log after trying to add integration (cable 82t):

2023-05-20 21:10:29.134 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call system_status

2023-05-20 21:10:29.135 INFO (MainThread) [custom_components.jablotron80] Connecting to JA80 via HID using /dev/ttyUSB2…

2023-05-20 21:10:29.141 DEBUG (MainThread) [custom_components.jablotron80] Sending startup message

2023-05-20 21:10:29.143 DEBUG (MainThread) [custom_components.jablotron80] Successfully sent startup message

2023-05-20 21:10:29.144 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-20 21:10:29.145 INFO (MainThread) [custom_components.jablotron80] JA80CentralUnit(N/A): initializing mode to Unsplit

2023-05-20 21:10:29.150 INFO (MainThread) [custom_components.jablotron80] initializing

2023-05-20 21:10:29.154 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Loop endlessly reading serial

after a while also the message: (I have disabled aiohttp.server debugging due to hikvision integration problem)

ERROR (MainThread) [aiohttp.server] Error handling request

mattsaxon · May 21, 2023, 7:25am

Have you tried the Ja80T choice instead? Looks like no data is flowing fro the debug logs . But if olink works, must just be the way it’s being interpreted.

DamianB · May 21, 2023, 7:44am

It’s a partial log, then HA falls into an endless loop of these errors, only restarting HA helps:

2023-05-21 09:33:43.692 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call system_status

2023-05-21 09:33:43.693 INFO (MainThread) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:33:43.699 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-21 09:33:43.700 INFO (MainThread) [custom_components.jablotron80] JA80CentralUnit(N/A): initializing mode to Unsplit

2023-05-21 09:33:43.700 INFO (MainThread) [custom_components.jablotron80] initializing

2023-05-21 09:33:43.702 DEBUG (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Loop endlessly reading serial

2023-05-21 09:33:44.177 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:44.976 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:45.216 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:45.234 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:45.506 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:45.745 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:46.048 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:46.272 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:47.282 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:33:48.285 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:33:48.287 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:33:48.896 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 900, in _read_data

self._connection.read_until(b’\xff’) # throw away first record as will be corrupt

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:49.185 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:49.407 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:49.951 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:50.239 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:50.767 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:51.773 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:33:52.776 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:33:52.779 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:33:52.862 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 900, in _read_data

self._connection.read_until(b’\xff’) # throw away first record as will be corrupt

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:53.867 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:33:54.871 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:33:54.874 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:33:55.182 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 900, in _read_data

self._connection.read_until(b’\xff’) # throw away first record as will be corrupt

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:55.200 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:55.470 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:55.486 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:56.526 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:56.766 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:57.038 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:57.281 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:57.294 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:57.566 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:33:58.571 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:33:59.573 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:33:59.575 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:33:59.677 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 900, in _read_data

self._connection.read_until(b’\xff’) # throw away first record as will be corrupt

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:00.688 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:34:01.692 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:34:01.696 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:34:02.284 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 900, in _read_data

self._connection.read_until(b’\xff’) # throw away first record as will be corrupt

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:02.300 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:02.526 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 10 00 01 00 00 00 24 ff

2023-05-21 09:34:02.526 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 09:34:02.527 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 09:34:02.528 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 09:34:02.529 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 09:34:02.529 INFO (MainThread) [custom_components.jablotron80] JablotronLed(5): active changed from False to True

2023-05-21 09:34:02.530 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 09:34:02.531 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 09:34:02.532 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 09:34:02.532 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 09:34:02.535 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 09:34:02.535 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 09:34:02.536 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 09:34:02.537 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 09:34:02.537 INFO (MainThread) [custom_components.jablotron80] JablotronZone(3): status changed from Unknown to Disarmed

2023-05-21 09:34:02.539 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 09:34:02.540 INFO (MainThread) [custom_components.jablotron80] Zone C status changed from Unknown to Disarmed

2023-05-21 09:34:02.541 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Details

2023-05-21 09:34:02.541 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-21 09:34:02.542 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from to Triggered detector

2023-05-21 09:34:02.543 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 09:34:02.545 INFO (MainThread) [custom_components.jablotron80] initialization done.

2023-05-21 09:34:02.547 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=key sequence HIDDEN

2023-05-21 09:34:02.547 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Get settings

2023-05-21 09:34:03.526 WARNING (ThreadPoolExecutor-3_0) [custom_components.jablotron80] connection failed, reconnecting

2023-05-21 09:34:04.530 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Disconnecting from JA80…

2023-05-21 09:34:04.533 INFO (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 09:34:06.491 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:06.732 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:07.019 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:08.059 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 749, in read_send_packet_loop

records = self._read_data()

File “/config/custom_components/jablotron80/jablotron.py”, line 896, in _read_data

data = self._connection.read_until(b’\xff’)

File “/usr/local/lib/python3.10/site-packages/serial/serialutil.py”, line 663, in read_until

c = self.read(1)

File “/usr/local/lib/python3.10/site-packages/serial/serialposix.py”, line 595, in read

raise SerialException(

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

2023-05-21 09:34:08.315 ERROR (ThreadPoolExecutor-3_0) [custom_components.jablotron80] Unexpected error: %s

Traceback (most recent call last):

mattsaxon · May 21, 2023, 8:01am

can you send me a raw hex dump from the USB?

mattsaxon · May 21, 2023, 8:09am

I think the issue is that this integration expects either a HID device or a Serial Device. I think your adapter is presenting as a non HID USB device and so this integration does not know how to interpret this.

I don’t have such a device to test however.

DamianB · May 21, 2023, 8:20am

How do I do a hex dump? hexdump when trying to add integration shows only this:

[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0001 0000 ff16
0000008
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 00ff
0000001
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 00ff
0000001
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump

Edit:

[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0006 0804 0f0f 0000 0000 ff12 06e6 0400
0000010 0f09 000f 0000 5b00 e6ff 0006 0005 0f0f
0000020 0000 0000 ff77 06e6 0001 0101 0403 e6ff
0000030 0106 0200 0306 ff06 06e6 0001 0103 3f03
0000040 e6ff 0106 0400 0306 ff4b 06e6 0001 0605
0000050 0703 e6ff 0106 0600 0306 ff70 06e6 0001
0000060 0607 3c03 e6ff 0106 0800 0306 ff72 06e6
0000070 0001 0609 3e03 e6ff 0106 0001 0301 ff52
0000080 06e6 0101 0601 6b03 e8ff 530b e6ff 0106
0000090 0201 0306 ff1c 06e6 0101 0603 5003 e6ff
00000a0 0106 0401 0301 ff24 06e6 0101 0105 6803
00000b0 e6ff 0106 0601 0301 ff1f 06e6 0101 0107
00000c0 5303 e6ff 0106 0801 0301 ff1d 06e6 0101
00000d0 0809 6d03 e6ff 0106 0002 0308 ff40 06e6
00000e0 0201 0101 3003 e6ff 0106 0202 0301 ff47
00000f0 06e6 0201 0103 0b03 e6ff 0106 0402 0301
0000100 ff0a 06e6 0201 0105 4603 e6ff 0106 0602
0000110 0301 ff31 06e6 0201 0107 7d03 e6ff 0106
0000120 0802 0301 ff33 06e6 0201 0109 7f03 e6ff
0000130 0106 0003 0301 ff66 06e6 0301 0101 2a03
0000140 e6ff 0106 0203 0301 ff5d
000014a

mattsaxon · May 21, 2023, 9:09am

Can you send me a similar dump over 2 mins when everything is idle so I can see the heartbeat?

DamianB · May 21, 2023, 10:02am

Within 8 minutes I registered (I skip empty results):

[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 00ff
0000001
[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 ff43
0000002
[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 ff43
0000002
[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 0001
0000001
[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 1327
0000002
[core-ssh ~]$ cat /dev/ttyUSB3 | hexdump
0000000 00ed
0000001

I also changed the connection cable with the control panel, but no improvement.

DamianB · May 21, 2023, 10:19am

Another attempt to add integration - now the logs look different.
Beginning:

2023-05-21 12:03:07.864 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call system_status

2023-05-21 12:03:07.865 INFO (MainThread) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB3…

2023-05-21 12:03:07.874 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-21 12:03:07.875 INFO (MainThread) [custom_components.jablotron80] JA80CentralUnit(N/A): initializing mode to Unsplit

2023-05-21 12:03:07.876 INFO (MainThread) [custom_components.jablotron80] initializing

2023-05-21 12:03:07.879 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Loop endlessly reading serial

2023-05-21 12:03:07.884 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\x00\xff’

Traceback (most recent call last):

File “/config/custom_components/jablotron80/jablotron.py”, line 2596, in processing_loop

self._process_message(record)

File “/config/custom_components/jablotron80/jablotron.py”, line 2455, in _process_message

message_type = JablotronMessage.get_message_type_from_record(data,packet_data)

File “/config/custom_components/jablotron80/jablotron.py”, line 1126, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Unknown message type {hex(record[0])} with data {packet_data} received’)

File “/usr/local/lib/python3.10/logging/init.py”, line 1543, in log

raise TypeError(“level must be an integer”)

TypeError: level must be an integer

2023-05-21 12:03:08.078 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:08.079 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.081 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.082 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.083 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.084 INFO (MainThread) [custom_components.jablotron80] JablotronLed(5): active changed from False to True

2023-05-21 12:03:08.085 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 12:03:08.085 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.086 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:03:08.086 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:03:08.087 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.087 INFO (MainThread) [custom_components.jablotron80] JablotronZone(1): status changed from Unknown to Service

2023-05-21 12:03:08.088 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 12:03:08.089 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.089 INFO (MainThread) [custom_components.jablotron80] JablotronZone(2): status changed from Unknown to Service

2023-05-21 12:03:08.090 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 12:03:08.091 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.091 INFO (MainThread) [custom_components.jablotron80] JablotronZone(3): status changed from Unknown to Service

2023-05-21 12:03:08.092 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 12:03:08.092 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-21 12:03:08.093 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from to Maintenence, Codes, 65:None

2023-05-21 12:03:08.093 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 12:03:08.095 INFO (MainThread) [custom_components.jablotron80] initialization done.

2023-05-21 12:03:08.096 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Get settings

2023-05-21 12:03:08.365 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 12:03:08.367 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 12:03:08.380 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ff

2023-05-21 12:03:08.383 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:a0 ff

2023-05-21 12:03:08.384 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:08.386 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 12:03:08.387 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:08.389 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 12:03:08.390 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 12:03:08.492 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:08.494 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:08.496 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.496 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.497 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.498 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.498 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:08.499 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:03:08.500 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:03:08.500 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.501 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.501 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:08.605 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:08.892 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:09.132 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:09.437 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:09.660 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:09.948 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.173 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.174 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 12:03:10.174 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 12:03:10.178 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 12:03:10.194 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ff

2023-05-21 12:03:10.199 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:a0 ff

2023-05-21 12:03:10.202 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:10.202 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 12:03:10.207 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:10.207 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 12:03:10.208 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 12:03:10.299 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.564 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.565 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:10.565 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:10.565 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:10.566 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:10.566 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:10.566 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:03:10.567 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:03:10.567 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:10.568 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:10.568 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:10.621 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.700 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:10.988 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:11.323 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:11.622 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:11.755 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.043 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.045 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 12:03:12.047 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 12:03:12.051 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 12:03:12.059 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ff

2023-05-21 12:03:12.059 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:12.062 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 12:03:12.065 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:a0 ff

2023-05-21 12:03:12.066 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:12.069 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 12:03:12.070 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 12:03:12.188 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.190 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.191 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:12.193 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:12.194 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:12.194 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:12.195 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:12.196 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:03:12.196 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:03:12.197 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:12.197 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:12.198 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:12.299 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.605 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:12.795 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:13.084 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:13.323 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:13.611 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:13.851 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:13.851 WARNING (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 12:03:14.252 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:14.252 DEBUG (MainThread) [custom_components.jablotron80] Message of type Ping received c6 ff

2023-05-21 12:03:14.253 DEBUG (MainThread) [custom_components.jablotron80] Ping Message: 0xc6

2023-05-21 12:03:14.405 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:03:14.405 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:14.406 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:14.407 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:14.408 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:14.409 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:03:14.409 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:03:14.409 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:03:14.410 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:14.411 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:14.412 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:03:45.620 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:03:45.622 DEBUG (MainThread) [custom_components.jablotron80] Message of type Ping received c6 ff

2023-05-21 12:03:45.623 DEBUG (MainThread) [custom_components.jablotron80] Ping Message: 0xc6

Then this log repeats itself in a loop for 10 minutes now:

2023-05-21 12:12:07.912 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-21 12:12:07.913 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:12:07.915 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:12:07.917 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:12:07.918 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:12:07.919 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 12:12:07.920 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 12:12:07.921 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 12:12:07.924 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:12:07.925 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:12:07.926 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 12:12:38.993 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 12:12:38.994 DEBUG (MainThread) [custom_components.jablotron80] Message of type Ping received c6 ff

2023-05-21 12:12:38.997 DEBUG (MainThread) [custom_components.jablotron80] Ping Message: 0xc6

DamianB · May 21, 2023, 6:24pm

Another logs, from another converter:

2023-05-21 20:19:45.540 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call system_status

2023-05-21 20:19:45.541 INFO (MainThread) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-21 20:19:45.570 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-21 20:19:45.571 INFO (MainThread) [custom_components.jablotron80] JA80CentralUnit(N/A): initializing mode to Unsplit

2023-05-21 20:19:45.572 INFO (MainThread) [custom_components.jablotron80] initializing

2023-05-21 20:19:45.573 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Loop endlessly reading serial

2023-05-21 20:19:45.734 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:45.736 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:19:45.739 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:19:45.741 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:19:45.745 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:19:45.745 INFO (MainThread) [custom_components.jablotron80] JablotronLed(5): active changed from False to True

2023-05-21 20:19:45.747 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 20:19:45.747 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:19:45.749 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:19:45.758 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:19:45.760 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:19:45.763 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:19:45.764 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:19:45.765 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:19:45.773 INFO (MainThread) [custom_components.jablotron80] JablotronZone(3): status changed from Unknown to Disarmed

2023-05-21 20:19:45.775 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 20:19:45.775 INFO (MainThread) [custom_components.jablotron80] Zone C status changed from Unknown to Disarmed

2023-05-21 20:19:45.990 INFO (MainThread) [custom_components.jablotron80] initialization done.

2023-05-21 20:19:45.993 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=key sequence HIDDEN

2023-05-21 20:19:45.995 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Get settings

2023-05-21 20:19:46.007 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:46.012 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:46.025 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.058 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.071 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.079 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.088 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.101 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.131 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.144 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.163 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.174 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.175 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:19:46.176 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:46.180 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:46.191 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.218 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.256 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.318 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.432 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.450 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.459 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.483 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.605 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.645 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.649 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:19:46.650 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:46.651 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:46.669 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.703 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.711 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.774 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.781 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.801 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.810 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.826 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.871 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.913 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:46.915 WARNING (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:19:47.031 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:47.035 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:47.058 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.086 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.133 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.152 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.197 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.210 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.228 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.258 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.280 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.287 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.288 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:19:47.288 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:47.289 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:47.307 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.319 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.329 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.342 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.355 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.365 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.395 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.433 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.452 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.472 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.473 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:19:47.474 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-21 20:19:47.476 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-21 20:19:47.486 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.499 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.532 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.564 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.596 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.604 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.633 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.713 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.741 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.768 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:19:47.770 WARNING (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-21 20:20:08.845 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.846 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:08.846 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:08.852 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:08.853 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.853 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.855 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.856 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.856 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.857 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:08.857 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:08.858 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:08.858 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:08.860 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:08.861 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:08.861 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-21 20:20:08.862 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from to Complete entry

2023-05-21 20:20:08.862 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 20:20:08.863 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.864 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 20:20:08.866 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.867 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:08.868 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:08.873 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:08.874 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.874 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.875 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.875 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.876 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.876 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:08.877 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:08.877 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:08.878 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:08.878 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:08.880 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:08.939 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.940 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 20:20:08.944 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:08.945 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.945 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.946 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.946 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.947 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.947 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:08.948 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:08.948 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:08.948 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:08.949 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:08.949 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:08.958 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.958 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:08.960 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:08.966 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:08.968 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.970 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.972 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.975 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.975 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:08.976 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:08.977 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:08.977 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:08.978 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:08.979 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:08.980 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:08.982 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.982 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 20:20:08.991 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:08.992 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:08.992 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:09.000 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:09.002 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.003 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.003 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.004 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.004 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.005 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:09.006 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:09.007 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:09.008 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:09.008 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:09.009 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:09.011 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:09.011 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 20:20:09.017 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:09.017 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:09.019 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:09.022 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:09.023 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.024 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.024 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.026 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.026 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.027 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:09.027 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:09.029 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:09.029 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:09.030 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:09.031 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:09.037 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:09.038 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-21 20:20:09.042 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:09.042 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-21 20:20:09.043 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-21 20:20:09.049 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-21 20:20:09.050 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.050 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.051 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.051 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.052 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.052 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:09.053 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:09.054 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:09.054 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:09.055 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:09.055 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:09.134 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-21 20:20:09.135 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a4 ff

2023-05-21 20:20:09.135 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa4, 4 subtle (short) beeps triggered

2023-05-21 20:20:09.140 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 00 00 01 00 00 00 16 ff

2023-05-21 20:20:09.141 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.142 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.143 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.144 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.144 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.145 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:09.146 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:09.146 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:09.147 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:09.147 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:09.148 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:09.150 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-21 20:20:09.150 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from Complete entry to

2023-05-21 20:20:09.151 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-21 20:20:09.191 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 10 00 01 00 00 00 24 ff

2023-05-21 20:20:09.192 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.194 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.194 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.195 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.197 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-21 20:20:09.197 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-21 20:20:09.198 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-21 20:20:09.199 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-21 20:20:09.200 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-21 20:20:09.200 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-21 20:20:09.202 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-21 20:20:09.203 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Details

2023-05-21 20:20:09.204 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

mattsaxon · May 21, 2023, 7:00pm

So this last one looks like it is working. Let’s focus on the setup you have with that one and see what the issues are

DamianB · May 21, 2023, 7:08pm

Configuration as before, 80t cable: usb:

DEVLINKS: >-
/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0
/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0
DEVNAME: /dev/ttyUSB2
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB2/tty/ttyUSB2
ID_BUS: usb
ID_MODEL: USB2.0-Ser_
ID_MODEL_ENC: USB2.0-Ser\x21
ID_MODEL_ID: ‘7523’
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_1_0
ID_REVISION: ‘0254’
ID_SERIAL: 1a86_USB2.0-Ser_
ID_TYPE: generic
ID_USB_DRIVER: ch341
ID_USB_INTERFACES: ‘:ff0102:’
ID_USB_INTERFACE_NUM: ‘00’
ID_USB_MODEL: USB2.0-Ser_
ID_USB_MODEL_ENC: USB2.0-Ser\x21
ID_USB_MODEL_ID: ‘7523’
ID_USB_REVISION: ‘0254’
ID_USB_SERIAL: 1a86_USB2.0-Ser_
ID_USB_TYPE: generic
ID_USB_VENDOR: 1a86
ID_USB_VENDOR_ENC: 1a86
ID_USB_VENDOR_ID: 1a86
ID_VENDOR: 1a86
ID_VENDOR_ENC: 1a86
ID_VENDOR_ID: 1a86
MAJOR: ‘188’
MINOR: ‘2’
SUBSYSTEM: tty
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘87854533923’

The previous converter has a 120 ohm resistor, the current one does not. Probably due to this, in the case of a short distance of the rs485 cable (2m), it causes interference.
However, the O-link worked ok.

DamianB · May 21, 2023, 7:13pm

Hexdump while idle (you can see the difference right away):

[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16 40ed 0000 0001 0000
0000030 ff16 40ed 0000 0001 0000 ff16 40ed 0000
0000040 0001 0000 ff16 40ed 0000 0001 0000 ff16
0000050 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000060 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000070 0000 0001 0000 ff16 40ed 0000 0001 0000
0000080 ff16 40ed 0000 0001 0000 ff16
000008c
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 0000 0000 0000
0000010 0000 0000 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16 40ed 0000 0001 0000
0000030 ff16
0000032
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16 40ed 0000 0001 0000
0000030 ff16 40ed 0000 0001 0000 ff16 40ed 0000
0000040 0001 0000 ff16 40ed 0000 0001 0000 ff16
0000050 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000060 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000070 0000 0001 0000 ff16 40ed 0000 0001 0000
0000080 ff16
0000082
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 ffc6 40ed 0000 0001 0000 ff16 40ed 0000
0000010 0001 0000 ff16
0000016
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0000 0000 0000 0000 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16
0000028
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 ffc6
000000c
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16
000000a
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0000 0000 0000 0000 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16
0000028
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0000 0000 0000 0000 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16
0000028
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0000 0000 0000 0000 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16
0000028
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 0000 0000 0000 0000 0000 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16 40ed
0000020 0000 0001 0000 ff16
0000028
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 ffc6 40ed 0000
0000010 0001 0000 ff16
0000016
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16
0000014
[core-ssh ~]$ cat /dev/ttyUSB2 | hexdump
0000000 40ed 0000 0001 0000 ff16 40ed 0000 0001
0000010 0000 ff16 40ed 0000 0001 0000 ff16
000001e

mattsaxon · May 22, 2023, 6:35am

Ok, so you have a working setup now? If not what it the problem, don’t need hexdumps for this one now as the debug logs have the interpreted messages.

DamianB · May 22, 2023, 7:05am

Data is sent and received, you can see it in the logs. however, the problem has not changed, the integration cannot be added. While adding it freezes and the logs repeat endlessly. Only restarting HA helps.