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

Third party integrations
464

Ok, I’ll take a look at the logs, please highlight the exact debug log that is using this setup and that looped endlessly. I’m not in front of computer at moment, but will take look when I have time

465

Currently it looks like this:

2023-05-22 18:11:36.013 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call system_status

2023-05-22 18:11:36.014 INFO (MainThread) [custom_components.jablotron80] Connecting to JA80 via Serial using /dev/ttyUSB2…

2023-05-22 18:11:36.023 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-22 18:11:36.024 INFO (MainThread) [custom_components.jablotron80] JA80CentralUnit(N/A): initializing mode to Unsplit

2023-05-22 18:11:36.026 INFO (MainThread) [custom_components.jablotron80] initializing

2023-05-22 18:11:36.031 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Loop endlessly reading serial

2023-05-22 18:11:36.041 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.041 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:36.042 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:36.043 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:36.044 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:36.045 INFO (MainThread) [custom_components.jablotron80] JablotronLed(5): active changed from False to True

2023-05-22 18:11:36.045 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-22 18:11:36.049 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:36.050 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 18:11:36.050 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 18:11:36.051 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-22 18:11:36.052 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-22 18:11:36.055 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-22 18:11:36.059 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 18:11:36.060 INFO (MainThread) [custom_components.jablotron80] JablotronZone(3): status changed from Unknown to Disarmed

2023-05-22 18:11:36.062 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-22 18:11:36.064 INFO (MainThread) [custom_components.jablotron80] Zone C status changed from Unknown to Disarmed

2023-05-22 18:11:36.072 INFO (MainThread) [custom_components.jablotron80] initialization done.

2023-05-22 18:11:36.073 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=key sequence HIDDEN

2023-05-22 18:11:36.074 DEBUG (MainThread) [custom_components.jablotron80] Adding command Command name=Get settings

2023-05-22 18:11:36.102 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.104 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.113 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.117 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.130 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.141 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.144 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.152 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.164 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.168 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.171 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.175 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.177 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:36.179 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.183 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.188 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.192 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.197 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.203 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.208 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.214 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.222 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.228 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.231 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.237 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.238 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:36.238 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.240 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.282 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.288 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.294 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.297 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.301 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.304 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.307 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.310 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.315 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.318 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.319 WARNING (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:36.336 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.339 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.344 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.350 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.354 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.358 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.361 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.364 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.368 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.371 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.375 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.378 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.379 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:36.380 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.381 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.388 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.391 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.394 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.398 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.401 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.404 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.408 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.411 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.414 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.418 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.418 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:36.420 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:11:36.422 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:11:36.426 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.430 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.433 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:2:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.442 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.452 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.456 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.459 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.462 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.465 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.469 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 00 00 01 00 00 00 16 ff

2023-05-22 18:11:36.470 WARNING (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:11:38.615 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.616 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-22 18:11:38.619 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.620 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-22 18:11:38.621 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-22 18:11:38.623 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.624 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-22 18:11:38.625 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.628 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-22 18:11:38.630 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

Then these lines repeat many times:

2023-05-22 18:11:38.807 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.810 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-22 18:11:38.814 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:38.816 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-22 18:11:38.817 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

In Loop:

2023-05-22 18:11:59.097 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 04 00 01 00 00 00 4b ff

2023-05-22 18:11:59.098 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:59.098 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:59.098 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:59.099 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:59.099 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 18:11:59.100 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 18:11:59.100 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 18:11:59.100 DEBUG (MainThread) [custom_components.jablotron80] Zone A action disarm

2023-05-22 18:11:59.101 DEBUG (MainThread) [custom_components.jablotron80] Zone B action disarm

2023-05-22 18:11:59.101 DEBUG (MainThread) [custom_components.jablotron80] Zone C action disarm

2023-05-22 18:11:59.102 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 18:11:59.102 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-22 18:11:59.102 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from to Complete entry

2023-05-22 18:11:59.103 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-22 18:11:59.103 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:59.103 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-22 18:11:59.104 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-22 18:11:59.104 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:59.104 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-22 18:11:59.106 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:59.106 DEBUG (MainThread) [custom_components.jablotron80] Message of type Beep received a0 ff

2023-05-22 18:11:59.107 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa0, 1 subtle (short) beep triggered

2023-05-22 18:11:59.118 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:11:59.119 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

This changes sometimes:

2023-05-22 18:19:01.632 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 40 10 00 01 00 00 00 24 ff

and:

2023-05-22 18:32:12.665 INFO (MainThread) [custom_components.jablotron80] Keypad Beep: 0xa4, 4 subtle (short) beeps triggered

Sometimes i see: (I think it’s my pir sensor in the room.)

2023-05-22 18:39:23.471 DEBUG (MainThread) [custom_components.jablotron80] Zone C action device_activated

2023-05-22 18:39:23.471 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-22 18:39:23.472 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from Triggered detector to Triggered detector, 4:device 4

2023-05-22 18:39:23.472 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-22 18:39:23.566 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:3:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:23.855 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:4:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:24.090 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:5:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:24.378 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:6:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:24.620 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:7:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:24.903 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:8:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:25.139 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:9:ed 40 10 04 01 00 00 00 1c ff

2023-05-22 18:39:25.140 INFO (ThreadPoolExecutor-2_0) [custom_components.jablotron80] no accepted message for sequence:0 received

2023-05-22 18:39:25.142 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] Sending keypress, sequence:0

2023-05-22 18:39:25.144 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress sent, sequence:0

2023-05-22 18:39:25.150 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:0:ff

2023-05-22 18:39:25.152 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 18:39:25.152 DEBUG (MainThread) [custom_components.jablotron80] Message of type Confirm received ff

2023-05-22 18:39:25.173 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] record:1:a4 ff

2023-05-22 18:39:25.174 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron80] keypress accepted, sequence:0

466

When i use in integration serial port by id:

/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0

I see other Log (log is longer, it only shows the part with errors):

2023-05-22 19:38:08.035 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.036 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 03 04 08 0f 0f 0f 0f 0f 0f 0f 0f 0a ff

2023-05-22 19:38:08.038 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 03 04 09 0f 0f 0f 0f 0f 0f 0f 0f 25 ff

2023-05-22 19:38:08.047 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 03 05 00 0f 0f 0f 0f 0f 0f 0f 0f 60 ff

2023-05-22 19:38:08.055 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 00 00 00 00 00 00 43 ff

2023-05-22 19:38:08.060 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 01 00 00 00 00 00 2d ff

2023-05-22 19:38:08.063 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 02 00 00 00 00 00 3c ff

2023-05-22 19:38:08.066 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 03 00 00 00 00 00 52 ff

2023-05-22 19:38:08.070 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 04 00 00 00 00 00 1e ff

2023-05-22 19:38:08.074 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 05 00 00 00 00 00 70 ff

2023-05-22 19:38:08.077 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 06 00 00 00 00 00 61 ff

2023-05-22 19:38:08.080 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 07 00 00 00 00 00 0f ff

2023-05-22 19:38:08.084 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 08 00 00 00 00 00 5a ff

2023-05-22 19:38:08.087 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 04 09 00 00 00 00 00 34 ff

2023-05-22 19:38:08.090 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 05 00 3a ff

2023-05-22 19:38:08.095 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 06 00 44 ff

2023-05-22 19:38:08.096 DEBUG (MainThread) [custom_components.jablotron80] JA80CentralUnit function call mode

2023-05-22 19:38:08.100 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 00 00 07 ff

2023-05-22 19:38:08.104 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 01 00 2d ff

2023-05-22 19:38:08.107 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 02 01 15 ff

2023-05-22 19:38:08.110 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 03 00 79 ff

2023-05-22 19:38:08.113 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 04 00 0c ff

2023-05-22 19:38:08.118 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 05 01 60 ff

2023-05-22 19:38:08.121 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 06 00 58 ff

2023-05-22 19:38:08.126 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 08 07 00 72 ff

2023-05-22 19:38:08.127 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 00 00 4b ff

2023-05-22 19:38:08.132 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 01 00 61 ff

2023-05-22 19:38:08.136 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 02 00 1f ff

2023-05-22 19:38:08.139 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 03 00 35 ff

2023-05-22 19:38:08.142 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 04 00 40 ff

2023-05-22 19:38:08.146 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 05 00 6a ff

2023-05-22 19:38:08.149 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 06 01 52 ff

2023-05-22 19:38:08.152 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 06 09 07 00 3e ff

2023-05-22 19:38:08.157 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 02 09 02 00 77 ff

2023-05-22 19:38:08.159 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e6 04 00 06 01 02 02 09 01 02 00 02 3d ff

2023-05-22 19:38:08.160 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.169 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e5 12 21 18 01 3d ff

2023-05-22 19:38:08.171 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 20 02 00 01 00 00 00 41 ff

2023-05-22 19:38:08.173 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.174 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.176 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.177 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.180 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.181 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 19:38:08.182 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 19:38:08.183 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.184 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.185 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.186 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.188 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x14\x14\xfa\xed \x02\x00\x01\x00\x00\x00A\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:08.195 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x12!\x18\x01)\xfa\xed \x02\x00\x01\x00\x00\x00A\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:08.202 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.204 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e5 12 21 18 01 3d ff

2023-05-22 19:38:08.207 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.219 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x12!\x18\xfa\xed \x02\x00\x01\x00\x00\x00A\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:08.298 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.396 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x14\x14\xfa\xe8\r"\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:08.691 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xc0\x14\x14\xfa\xed \x02\x00\x01\x00\x00\x00A\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-22 19:38:08.731 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 20 02 00 01 00 00 00 41 ff

2023-05-22 19:38:08.731 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.733 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.733 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.735 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.736 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:08.736 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 19:38:08.737 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 19:38:08.738 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.739 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.739 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:08.819 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:08.823 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e5 12 21 18 01 3d ff

2023-05-22 19:38:08.921 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:09.044 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x14\x14\xfa\xe8\r"\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:09.057 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e5 12 21 18 01 3d ff

2023-05-22 19:38:09.118 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:09.402 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\x85\xa2\x00\x10u\xfc\xa0\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:09.415 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-22 19:38:09.416 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.418 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.419 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.420 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.421 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.422 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 19:38:09.423 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 19:38:09.423 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:09.424 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:09.425 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:09.425 DEBUG (MainThread) [custom_components.jablotron80] JablotronStatusText function call message

2023-05-22 19:38:09.426 INFO (MainThread) [custom_components.jablotron80] JablotronStatusText(3): message changed from Maintenence to Maintenence, Codes, 65:None

2023-05-22 19:38:09.427 DEBUG (MainThread) [custom_components.jablotron80] publishing updates

2023-05-22 19:38:09.609 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:09.668 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x14\x14\xfa\xe8\r"\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:09.970 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b"\xc0\x14\xfa\xed’\x13A\x01\x00\x00\x00C\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-22 19:38:09.983 DEBUG (MainThread) [custom_components.jablotron80] Message of type State received ed 27 13 41 01 00 00 00 43 ff

2023-05-22 19:38:09.984 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.985 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.986 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.988 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.988 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:38:09.990 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 19:38:09.993 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 19:38:09.993 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:09.995 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:09.997 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:38:10.067 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:10.223 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe0\x14\x14\xfa\xe8\r"\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-22 19:38:10.310 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b"\xe5\x14\x14\xfa\xed’\x13A\x01\x00\x00\x00C\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:10.395 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:10.521 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b’\xe5\x14\x14\xfa\xe8\r"\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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-22 19:38:10.619 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:10.623 DEBUG (MainThread) [custom_components.jablotron80] Message of type Settings received e5 12 21 18 01 3d ff

2023-05-22 19:38:10.690 DEBUG (MainThread) [custom_components.jablotron80] Message of type StateDetail received e8 0d 22 ff

2023-05-22 19:38:10.829 ERROR (MainThread) [custom_components.jablotron80] Unexpected error processing record: b"\xe5\x14\x14\xfa\xed’\x13A\x01\x00\x00\x00C\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 1129, in get_message_type_from_record

LOGGER.log(expected_warning_level, f’Invalid CRC for {packet_data}')

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

And next in Loop:

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

2023-05-22 19:41:16.420 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:41:16.423 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:41:16.424 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:41:16.426 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:41:16.426 DEBUG (MainThread) [custom_components.jablotron80] JablotronLed function call active

2023-05-22 19:41:16.427 DEBUG (MainThread) [custom_components.jablotron80] JablotronAlert function call value

2023-05-22 19:41:16.428 DEBUG (MainThread) [custom_components.jablotron80] JablotronSensor function call value

2023-05-22 19:41:16.430 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:41:16.430 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:41:16.431 DEBUG (MainThread) [custom_components.jablotron80] JablotronZone function call status

2023-05-22 19:41:47.686 DEBUG (MainThread) [custom_components.jablotron80] Short packet, no CRC to check

2023-05-22 19:41:47.688 DEBUG (MainThread) [custom_components.jablotron80] Message of type Ping received c6 ff

2023-05-22 19:41:47.689 DEBUG (MainThread) [custom_components.jablotron80] Ping Message: 0xc6

467

Complete success.

Successfully added integration to HA.
The “USB RS485 CH340” device incorrectly read data from the RS485 bus, which caused errors - although it was possible to add integration 2 times, but only with 4 wired devices, I think it was an accident and at that moment the device read the data correctly.

The second device (more expensive) “Waveshare USB To RS485 Bidirectional Converter, Onboard Original FT232RL And SP485EEN” did not want to cooperate from the first connection.

After reading a lot of information on the internet, I came to the conclusion that the problem with Waveshare is the 120 ohm resistor placed directly on the board. This resistor, in the case of a short length of the rs485 bus (2m), prevented proper communication with the device. After removing the resistor from the pcb, the integration was successfully added after the first attempt.
The description of which resistor should be removed is available on the manufacturer’s website.

I will also add that GND has not been connected, I only use the A and B lines. According to the rs485 specification, lines A and B are connected on a twisted pair with one of the pairs of wires (in my case green and white-green).

At the moment I don’t have time to thoroughly test the whole thing, if I find any bugs, I’ll be sure to report them.

Regards.

468

Hi there,
I have connected my HA to my Jablotron 100 alarm installation and it has worked well for approx. 4 months.
Recently I noticed that arming for the night no longer work true HA. (maybe After an HA update, I’m not sure?)
However, fully arming and disarming the alarm works.
When I manually arm true the Jablotron keypad for the night, I can disable it via HA.
The options “arm_night” and “arm_away “are enabled in the UI Keypad of HA.
Cannot find what I should do, everything seems OK in the settings of the integration.

Is anyone facing the same problem?
Is there a fix?

Best regards,
Benny

469

Good morning,
First of all, your work is fantastic.

I’m new to HOME ASSISTANT and am absolutely not as competent as all of you, that’s why I need your advice to avoid making mistakes.

I have a JABLOTRON OASIS JA-83 alarm.

Is this module compatible? . Once the module is connected to port A and B, I plug the module into the LAN but how will HOME ASSISTANT, which is in a VM, see the module?

Another question, once the module is detected in HA, I install the hacs tahvane1and what else is there to do.

To be honest, I have read a lot of pages here but not all.

Sorry to ask stupid questions but I’m really a beginner and I don’t want the wrong equipment.

Thank you so much

this model

470

really no one to help me

471

JA-83 should work.

How you get HA running in a VM to see a USB is not really one for this thread, most people I feel run it on RPi, that’s certainly what i do, so there is no issue there. The solution will depend on the virtual machine manager you are using and possibly also which type of HA install you are using, eg if containerised I imagine there are other hurdles to jump through.

472

Thank you for taking the time to answer me.

I have an ASUSTOR NAS, I created a virtual machine where HA is in a vdi image.
For example, I have a ZIGBEE 2ZM network which works with a SONOFF dongle, this key is put directly into the USB port of the NAS and it goes up normally in HA (ttyACM0).

So I imagine that the module that I have already ordered (USR-TCp232-304) will be reassembled in the same way, well I really hope otherwise it will be of no use to me

473

OK if you are using USR-*, then connection is over IP, so no need for USB connection.

474

And you specify this using a device address of

socket://[ipaddress:socket]

as per readme instructions, you enter this on setup of the component.

You get the IP address and socket from your setup of the USR-*

475

Okay, this is the answer I was waiting for, so during configuration instead of giving it a serial port (EX: ttyACM0), I can just put the IP address of the USR, I must write in this form socket://[192.168.150.20:socket]?
THANKS

476

The final :socket is the port in USR-*, for for example socket://192.168.0.1:23

477

Okay, how do we find out the USR socket?
Excuse my stupid questions but I’m a beginner.
THANKS

478

All of this should be apparent when you USR arrives and you set it up, it comes with a manual that should explain.

All of this is the standard USR functionality.

479

actually there are drivers to configure the USR.

Thank you, when it is installed if I have any other questions I will ask you.

480

I wanted to ask again, on the USR there is an input A and an input B, input A goes on pole A of the jablotron card and input B on pole B.

THANKS

481

Yep, that’s right

1 Like
482

I need your help because I can’t do it, I set the USR as recommended but I can’t connect.

Capture4
Capture4597×695 15.3 KB

Capture3
Capture3933×737 70.2 KB

Capture2
Capture2953×731 82.5 KB

Capture1
Capture1876×729 84.6 KB

Capture
Capture962×782 82.7 KB

483

There should be no square brackets in that