Sending service code? about hass-jablotron80 HOT 7 CLOSED

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

from hass-jablotron80.

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.

from hass-jablotron80.

from hass-jablotron80.

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

from hass-jablotron80.

from hass-jablotron80.

@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?

1. 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.

2. 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.

3. 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?

from hass-jablotron80.

No response for 2 months on this thread so closing

from hass-jablotron80.