Sending service code?

Question

Sending service code?

lambertvenema opened this issue 5 years ago · 7 comments

Hi

Thanks for your initiative for this project.
I have a JA80T cable and tried to connect my cable to the PI after installing your components.
After restarting Home assistant it imediatly activated my alarm ( Sirene).

In the logs i see:

2019-06-02 13:33:11 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for jablotron which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-06-02 13:33:11 DEBUG (ThreadPoolExecutor-0_2) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:11 DEBUG (ThreadPoolExecutor-0_2) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message
2019-06-02 13:33:13 WARNING (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Data has not been received for 2 seconds, retry startup message
2019-06-02 13:33:13 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:13 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message
2019-06-02 13:33:15 WARNING (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Data has not been received for 2 seconds, retry startup message
2019-06-02 13:33:15 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:16 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message
2019-06-02 13:33:18 WARNING (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Data has not been received for 2 seconds, retry startup message
2019-06-02 13:33:18 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:18 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message
2019-06-02 13:33:20 WARNING (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Data has not been received for 2 seconds, retry startup message
2019-06-02 13:33:20 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:20 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message
2019-06-02 13:33:22 WARNING (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Data has not been received for 2 seconds, retry startup message
2019-06-02 13:33:22 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Sending startup message
2019-06-02 13:33:22 DEBUG (ThreadPoolExecutor-0_1) [custom_components.jablotron.alarm_control_panel] Successfully sent startup message

any idea how to solve this?
Should i send some service code as part of the configuration ?

Thanks, Lambert

Answer 1 · 2019-06-02T19:58:44.000Z

This is the first time I've had info on the JA-80T. I had assumed it would work, but it's clearly not for you.

I can help you try to diagnose the situation if you are game?

Can you first tell me what control panel model you have, for example I have a JA-82K.

Can you also paste here you configuration that you have added to configuration.yaml

Answer 2 · 2019-06-02T20:36:11.000Z

One thing to mention is that, depending on your experience level, you may find reviewing this thread useful. https://community.home-assistant.io/t/jablotron-ja-80-series-and-ja-100-series-alarm-integration/

On it you can see various people with different configurations trying to get this to work. I note that recently there is someone with a JA-80 system who also has this working (thoky), its not clear what cable he is using though. This is quite early days and there are lots of different configurations, so this may take a few goes to get things working for you.

Answer 3 · 2019-06-05T13:08:00.000Z

Hi Matt, Thanks for your fast respons. I guess i also have the JA 82K allthough i can not find that number . At least my control box looks the same and has the same size. my config is: alarm_control_panel: - platform: jablotron serial_port: /dev/serial/by-id/usb-Silicon_Labs_JABLOTRON_serial_interface_1-if00-port0 I didnt define a "code" yet as i didnt know which code to use ( service code, user code or ...). And we didnt make any chenge in "alarm_control_panel.py". The fact that i get a tamper alarm immediately after restart of HA ( and sending the startup code: self._sendPacket(b'\x00\x00\x01\x01') )tells me the port seems the right one:). It would be nice to help with debugging, but unfortunately i will not be available next 4 weeks. If you have some first idea please let me know. regards, Lambert

…

On Sun, Jun 2, 2019 at 9:58 PM mattsaxon ***@***.***> wrote: This is the first time I've had info on the JA-80T. I had assumed it would work, but it's clearly not for you. I can help you try to diagnose the situation if you are game? Can you first tell me what control panel model you have, for example I have a JA-82K. Can you also paste here you configuration that you have added to configuration.yaml — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AIOQKZNM3GFSKNZEU5GXWG3PYQQ7JA5CNFSM4HSCRTLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWX42YY#issuecomment-498060643>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIOQKZOC7J36GG3YE5SRMCTPYQQ7JANCNFSM4HSCRTLA> .

Answer 4 · 2019-06-05T18:40:56.000Z

Can I suggest you contact 'thoky' on this thread https://community.home-assistant.io/t/jablotron-ja-80-series-and-ja-100-series-alarm-integration/113315/85. They are using the same type cable as you. Whilst the /dev/ path you are using might be the 'right' device, it may not the the right way to address it, I'd expected to address it using something more like /dev/ttyUSB0

Answer 5 · 2019-06-05T19:42:45.000Z

Hi Matt, Thanks for your respons. Sure, I will check with Thoky after my vacation. In the mean time new info might be available also. The reason we use this address to link to the device is that we are not sure the other address (like /dev/ttyUSB0 or 1) will never change. regards, Lambert

…

On Wed, Jun 5, 2019 at 8:40 PM mattsaxon ***@***.***> wrote: Can I suggest you contact 'thoky' on this thread https://community.home-assistant.io/t/jablotron-ja-80-series-and-ja-100-series-alarm-integration/113315/85. They are using the same type cable as you. Whilst the /dev/ path you are using might be the 'right' device, it may not the the right way to address it, I'd expected to address it using something more like /dev/ttyUSB0 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AIOQKZKHCJG3CGRRM75DEVDPZACDTA5CNFSM4HSCRTLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXAUOBQ#issuecomment-499205894>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIOQKZIVNWQRCRVHXGH4WWTPZACDTANCNFSM4HSCRTLA> .

Answer 6 · 2019-06-05T19:49:58.000Z

@lambertvenema Could you test it with /dev/ttyUSB0 or 1, even if you're not sure if this device will be available with this address in the future?

If you still want to test it with your customized address (of which I even didn't know or expect this should/could work), could you try a couple of things in order to be sure you're even seeing data?

if you type lsusb, do you see a USB device?
Expected results:

$ lsusb
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 008: ID 16d6:0008 JABLOCOM s.r.o.
Bus 001 Device 005: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Please mind the 2nd line with the JABLOCOM device. In my case, I just used a simple USB cable and not some kind of Jablotron cable. The lsusb command is detecting automatically a Jablotron device.

If you unplug and plug back in the cable and then type dmesg | grep hid, do you see any output?
Expected results:

[1815337.418852] hid-generic 0003:16D6:0008.0001: hiddev96,hidraw0: USB HID v1.11 Device [Jablotron ltd JA-100 Flexi] on usb-3f980000.usb-1.2/input0

This output will show me it recognizes a JA-100 system on a USB device, assigned to hidraw0.

Now if you type sudo cat /dev/hidraw0 | hexdump -C or any other device you saw in step 2, does it stay connected?
Expected results:

$ sudo cat /dev/hidraw0 | hexdump -C
<nothing showing here, just waiting for data>

or does it give you an error message like 'cat: /dev/hidraw1: File or directory doesn't exist'?

Or if all of the above works for you, is there a way we could replicate your issue?

Answer 7 · 2019-08-11T15:02:19.000Z

No response for 2 months on this thread so closing