Trying to make it work on a JA-82K with a "simple" USB to TTL converted based on CP2102 chipset
Closed this issue · 1 comments
Hi,
I'm trying to make it work on a JA-82K control panel with a "simple" USB to TTL converter based on CP2102 chipset (https://www.play-zone.ch/en/usb-zu-ttl-serial-kable-debug-console-cable-cp2102.html) as JA-82T is very hard to find as it's end of life.
I'm on latest ha (0.109), running on hassOS 3.13 on a raspberry pi 3. Device is properly recognized and mapped to /dev/ttyUSB0. I've configured your custom component accordingly but only get an "unavailable" state and only "disarm" action which does nothing.
No error visible in ha log, even in debug mode. I only get :
2020-05-03 21:30:23 DEBUG (MainThread) [custom_components.jablotron.alarm_control_panel] Sending startup message 2020-05-03 21:30:23 DEBUG (MainThread) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message 2020-05-03 21:30:23 DEBUG (MainThread) [custom_components.jablotron.alarm_control_panel] send_command_loop() enter
I tried hexdump /dev/ttyUSB0
but nothing is shown. Same after sending echo -ne “\x00\x00\x01\x01” > /dev/ttyUSB0
.
Using the same cable on Windows with Olink software, I'm able to see the current alarm state (which zone is set for instance) and see data in the "packets" view. Here is the data I get:
`Alarm triggered:
E8 02 0A FF
Not armed:
ED 40 40 00 31 ** ** ** ** FF
Arm ABC:
A1 FF
E3 10 01 16 26 08 30 4A FF
E8 0E 4B FF
ED 53 4C 00 3F 00 00 32 02 FF
E8 0E 4B FF
E8 0E 4B FF
B8 FF
B8 FF
ABC armed
ED 53 4C 00 3F 0D 00 00 1A FF
ARM A only:
A1 FF
E3 10 01 16 28 0D 2F 7F FF
A armed:
ED 41 40 00 09 0C 00 00 7E FF `
I'm a bit out of options, can you help ?
Nevermind, I managed to buy a JA-82T from Austria and it's working !