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

mattsaxon · May 29, 2019, 8:16am

Given all the great progress you’ve made on the JA-100 series, shall we take this opportunity to rename the repo to remove the 80 designation. I wanted to check as it might require you to reclone the repo (though somethings in GitHub are resilient to such name changes, last time I check clone repos weren’t)

plaksnor · May 29, 2019, 8:50am

Sure, great suggestion!
Another suggestion for new development: could we make it as a multiple platform? At the moment, it’s an alarm_control_panel platform, but I’d like to extend it with a sensor platform as it looks like we’re also getting sensor data.

Ps. I noticed I was using ‘state’ as variable in my last post, but that variable was already being used and could mess up your alarm state

plaksnor · May 29, 2019, 12:09pm

Progress on the sensor…

Concept of the multiple platform component, please let me know your thoughts:

configuration.yaml:

defines location of the serial port
reference to the alarm code (preferable by using !secret code in secrets.yaml)
specifies arm/disarm code requirements

__init__.py:

identifies the alarm system, for example: 80 or 100 series.
loads platforms:
– Is polling for the alarm state, for example b’\x80\x01\x01\x52\x01\x0E’ (in case of 100-series)
– Is polling for the sensor states, for example b’\x80\x01\x02’ (in case of 100-series). This should be done once, so regardless how many sensors your system has. Therefore it cannot be part of the binary_sensor.py script (right?)

alarm_control_panel.py

updates alarm state, based on triggers in the init.

binary_sensor.py

updates sensor states, based on triggers in the init.

Marcel1 · May 29, 2019, 8:55pm

@plaksnor: I have changed the startupcode and extended the _read function as suggested.
I triggered all my sensors, my log only shows unknown packages:

2019-05-29 22:48:48 DEBUG (Thread-25) [custom_components.jablotron.alarm_control_panel] Unknown packet: b'\x80\x01\x02\x00\x00\x00\x00\x00T)\x00\x10\xf4\x00\x00\x00\x00\x00\x00\x00\x0c)\x00\x10\x00\x00\x00\x00\x0c\x00\x00\x00\x01\x00\x00\x00\xd9\xd3\x00\x00\x00\x00\x00\x00d\x04\x00\x10\x0b\x00\x00\x00|E\x00\x10\x00\x00\x00\x00\x97R\x03\x00'

I will try to troubleshoot some time later.

Some quick remarks that I want to share. It might be helpfull to you.
In your code you commented that you are not sure what the 3rd byte is.
In my earlier post, i mentioned that my wired magnetic sensors send out messages starting with 550800 while my wireless magnetic sensors send out messages starting with 550901. Looks like both byte 2 and 3 are related to wirless vs wired.

Also i noticed that you assume that byte 4 is the sensor state.
This might be true, but i’ve noticed the value of the 4th byte is not consistent across sensors.

In my case:
wired magnatic sensor byte #4 open: 8c
wired magnatic sensor byte #4 close: 8e
wireless magnetic sensor-1 byte #4 open: 80
wireless magnetic sensor-1 byte #4 close: 82
wireless magnetic sensor-2 byte #4 open: 84
wireless magnetic sensor-2 byte #4 close: 86
For me the closed state is always open state +2

Out of curiosity: Is there a particular reason you are deciphering the 55 codes here? The 52 codes (only generated by wirless sensors) seem easier to decpipher. Or do you have all your sensors wired?

One quick probably stupid question (sorry for being a python noob )
I understand that packet[:2] means: first 2 bytes
But how do I exactly read: packet[10:12]?
Is it something like: start reading after byte 10, till byte 12? So that the actual result is that you catch byte 11 and 12?

plaksnor · May 29, 2019, 11:04pm

@marcel1: sorry, I had to mention you need to change some packet conditions, my bad!

The old script contains the following condition, but we actually need packet b\ ‘xd8’

elif packet[:1] == b'\xd0' or packet[:1] == b'\xd2' or packet[:1] == b'\xd8':
    pass # recognised, but as yet undeciphered JA-101 packets

So I changed this condition to

elif packet[:1] == b'\xd0' or packet[:1] == b'\xd2':
    pass # recognised, but as yet undeciphered JA-101 packets

And I added a new condition for the sensors only

elif packet[:2] == b'\x55\x09' or (packet[:2] == b'\xd8\x08' and packet[10:12] == b'\x55\x09'):

What it actually scans for is:

packets which start with 55 09 or
packets which start with d8 08 and have 55 09 on position 11 and 12 (this seems to be the only anomaly)

So packet[10:12] is from packet 11 (remember, start counting at 0) til 12 (not including). I also had to test this before I used it.

I checked your analysis before analyzing my data, but it seems to be different.

All sensors I tested were wireless and starting in the 55 09 range.
At the moment, I don’t have any messages starting with 52 or 55 08. I’ve added them in my script to keep an eye on them. Maybe I miss important data we could use

Things in common:

I have tested 2 doors with wireless magnetic sensors, but both seem to have different bytes for opening and closing it. But at least they seem to be consistent per device.
I also noticed 1 instead of 2 different bytes for PIR sensors. So for now I’ve build a time out after 1 sec.

This afternoon I’ve made some progress. Pretty hard with zero python skills, but there are some good examples online. It just takes a while to figure out how things work and how I think we could make this work for anyone, without sniffing packets.
So I decided to make a copy of @matt’s Jablotron component to build a multiple platform component in order to add binary sensors (on/off/opened/closed/etc.). Here you’ll see a working PIR sensor as a binary sensor:

Later on I thought, as a user you don’t want to define all your sensors one by one. And if you would, how would you even know how to identify them? You don’t want users to sniff their packets like we did, so we need to make something what’s more dynamic.
If HA finds a unknown packet starting with 55 09, it’s probably a device which hasn’t been triggered yet. So I used the 5th and 6th byte to give the binary sensor an ID. You could always give it a friendly name and a device class (door/window/motion):

Here you can see new binary sensors incoming as soon you trigger them. Sensor 40_01 is a wireless PIR, 00 02 is a wireless magnetic door sensor and 80_01 is another wireless magnetic door sensor I opened.
Please ignore the ‘binary_sensor.jablotron_door_sensor’ sensor. This was the original binary sensor catching all 55 09 packets regardless the device or state.

Pro’s: as a user you don’t need to setup all sensors manually in configuration.yaml. The script will currently create new binary sensors as soon as it receives the right packets.
Con’s: after a reboot, all your binary sensors are gone. Your history is still there, but sensors will be shown as soon as they report. Which could be never if you won’t open all windows, doors, etc.

So I guess we need to decide how we want to take this to another level.
@matt: do you have any idea what we should do? At the moment, I used set_state to create any binary sensor we want, but I’m not sure if this would cause any problems later on.

In the meanwhile, I’ll work on my python skills, try to add more functionality (icons, attributes) keep an eye on unknown packets and try to work a new release to publish/test.

Marcel1 · May 30, 2019, 7:28am

hi @plaksnor.
I had already removed b'\xd8 from the pass condition, that was not the problem.

I’ve noticed that whatever i do or try, my control panel is not generating any \x55\x09 codes, also not as part of a \xd8\x08 code even though i did measure those codes when i was connected to F-link.

I am starting to believe that what i’ve measured when conncted to F-link (\x55\x09, \x52\x09 and \xd8\x08 with an \x55\x09 in byte 10 and 11) is somehow for me only generated when connected to F-link.
I am a bit lost at this point and need time to investigate this.

thoky · May 30, 2019, 11:54am

I got the OEM usb serial cable yesterday and have quickly setup new RPi with Hassio for testing with my JA-80. Arm away was successful . When I Disarm back I realised the Alarm state goes to servis mode… In config I was using my master code. The Arm at home didn’t work. Any ideas ?

thoky · May 30, 2019, 3:01pm

I apologize . Just checked again and its working. Strange thing is that I can arm and disarm without actually entering the code even if I have in config:

alarm_control_panel:

platform: jablotron
serial_port: /dev/hidraw0
code: xxxx
code_arm_required: true
code_disarm_required: true

mattsaxon · May 30, 2019, 7:17pm

Yes, this looks sensible

mattsaxon · May 30, 2019, 7:24pm

The code uses those parameters to decide if to send the code that is entered in the UI to the alarm system. It does not configure the alarm system. I chose to do it this way as I didn’t really want to store my alarm code in HA which would be needed to validate the code.

The way it works at the moment, If you want a code to be required, you configure your alarm system to require the code and then this component.

Would that work for you?

plaksnor · May 30, 2019, 7:46pm

@Marcel1: Ok, I understand. Things are getting complicated, so let’s make things clear.
As far as I can see, we have two kind of topics going on:

Timeline for alarm state

In post 67 I discovered a packet to get the alarm state with a faster response.
You confirmed this in post 75

So far so good. This is the progress we got on the alarm_control_panel platform.

Timeline for sensor state

In post 58, I published my analysis on sensor data, while sniffing USB traffic on a host directly connected to the alarm system while running J/F-link in the background. I saw one 52 07 packet, but in general all sensors report states in a 52 09 packet (I was showing my data in decimal, where dec 82 == hex 52)
In post 60 you confirmed my analysis. You even noticed the 55 08 and 55 09 packets.

We were not able to retreive them without having J/F-link opened, because back then we only had a startup message in Matt’s Jablotron code which showed us the state of the alarm, not the state of the sensors.

In post 78 I discovered a specific startup message we could use in (a separate version of) Matt’s Jablotron code for retreiving sensor states, which won’t require us to have J/F-link opened. The concept of a binary sensor was born, yay \o/
In post 83 you tried to compare your analysis (based on J/F-link data) with my analysis (based on startup message responses). And in post 85 things got blurry for both of us I guess.

So there’s one way to get back on track: publish a new version of my code asap, in order to share and discuss test results. I’ll try to do this tonight.

thoky · May 30, 2019, 8:19pm

OK, and what part of the config should I change in order to arm and disarm the alarm from HA only with code entered? I don’t actually mind if the code will be stored somewhere in secret.yaml
Thank you

Marcel1 · May 31, 2019, 10:12am

hi @plaksnor. Thing are getting complicated, but i am still with you entirely.
I am not lost in terms of the steps we have taken so far, also it is entirely clear what our goals is.
It’s more that I am lost in terms of the codes generated (or not generated). I assumed we were on the right track with finding those codes, but now, with the new startup code and the modified _read function, i am not able to capture the codes anymore.

Even when trying to open one session, doing: echo -ne "\x80\x01\x02" > /dev/hidraw0 and opening a second where i do cat /dev/hidraw0 | hexdump -C | grep '55 09' i am not catching any 55 09 anymore.
I really can’t get my head around why this is.

Let me know once you posted your new version.

plaksnor · May 31, 2019, 11:07am

The code is here:

You could run this as a different custom_component. So you can use Matt’s repo with custom_component ‘jablotron’ for the alarm control panel and my repo with custom_component ‘jablotron_system’ for the binary sensors.

plaksnor · June 3, 2019, 3:03pm

To all 100-series owners: I just released an update which supports both alarm_control_panel as binary_sensor platforms. @mattsaxon and @Marcel1 : thanks for your support!
Of course, coding could have been better, but for a first release I’m already satisfied with the functionality

thoky · June 3, 2019, 6:39pm

Hi @plaksnor, I can confirm its working on my JA-80 too but without sensors. Arming_home have pending state (approx. 20 s) even if the physical alarm is set in “arm_home” immediately. Second, its arming even if I dont enter the code on alarm_control panel. If you could advice how to change these things I would appreciate and maybe I am not alone Sorry I not good in programming and trial and error may take me some time Thanks

thoky · June 3, 2019, 6:43pm

@plaksnor … sorry I forgot to mention that your previous code was showing me the sensors badge icon, but always in unknown state. I tried to watch States page but non of my sensors appear there

plaksnor · June 3, 2019, 7:24pm

@thoky thanks for testing!
Unfortunately, I’m not able to test the code on a JA-80 series system, only a JA-100 series. I already thought the binary_sensor was not working on a JA-80 series, because we haven’t analyzed that data for sensor purposes yet. So we need someone who’s able to sniff incoming data.
If you are able to help us by opening J/F/O-link and capture data with something like Device Monitoring Studio or USBPcap running in the background, I’d be happy to analyze your data. Please do keep in mind you’d better change your alarm code before putting data like this online.

For the alarm control panel code, you reported two issues:

pending state seems to have a delay

Could you show us some log while having logger enabled in configuration.yaml? Does it show an error, or does the output in the log gives you any more information which leads us to a specific kind of action?

code_arm_required and code_disarm_required doesn’t require you to use a code if set on True.
I think this has anything to do with post 91, right? @mattsaxon: Would you be able to respond on that?

thoky · June 3, 2019, 8:58pm

@plaksnor thanks for reply and here is the log. I will try to sniff the incoming data from usb but not today

2019-06-03 20:50:31 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] Send arm home command
2019-06-03 20:50:31 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] Sending keys
2019-06-03 20:50:31 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] sending *2
2019-06-03 20:50:31 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] Using keys for model Jablotron JA-80 Series
2019-06-03 20:50:31 DEBUG (MainThread) [custom_components.jablotron_system.alarm_control_panel] _sendKeys: Acquiring lock…
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:32 DEBUG (MainThread) [custom_components.jablotron_system.alarm_control_panel] _sendKeys: Lock acquired.
2019-06-03 20:50:32 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] sending packet 1, message: b’\x00\x02\x01\x8f’
2019-06-03 20:50:32 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:32 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] sending packet 2, message: b’\x00\x02\x01\x82’
2019-06-03 20:50:33 DEBUG (MainThread) [custom_components.jablotron_system.alarm_control_panel] _sendKeys: Releasing lock…
2019-06-03 20:50:33 DEBUG (MainThread) [custom_components.jablotron_system.alarm_control_panel] _sendKeys: Lock released.
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:33 INFO (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] Jablotron state changed: disarmed to pending
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:33 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:34 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:35 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:35 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:35 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:35 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:35 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:36 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:36 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:37 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:37 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:38 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:38 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:39 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:39 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:40 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:41 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:42 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:43 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:43 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:43 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:43 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:43 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:44 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:45 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:45 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:45 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:45 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:45 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:46 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:47 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:47 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:47 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:47 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:47 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:48 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:49 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:50 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:50 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:50 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:50 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:50 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:51 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:52 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:52 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:53 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:54 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:54 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:54 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:54 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:54 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:55 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:56 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:57 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:58 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:58 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:50:58 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:50:58 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: closed connection
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Releasing lock…
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock released.
2019-06-03 20:50:59 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:00 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:00 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Acquiring lock…
2019-06-03 20:51:00 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: Lock aquired.
2019-06-03 20:51:00 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: trying to read data
2019-06-03 20:51:00 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:01 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:01 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:02 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:02 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:03 DEBUG (ThreadPoolExecutor-1_1) [custom_components.jablotron_system.alarm_control_panel] Data is flowing, wait 1 seconds before checking again
2019-06-03 20:51:03 DEBUG (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] _read_loop: succesfully read data
2019-06-03 20:51:03 INFO (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] Jablotron state changed: pending to armed_home

plaksnor · June 3, 2019, 9:17pm

Thanks thoky. This is what I read from it:

2019-06-03 20:50:31 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] Send arm home command
2019-06-03 20:50:32 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] sending packet 1, message: b’\x00\x02\x01\x8f’
2019-06-03 20:50:32 INFO (MainThread) [custom_components.jablotron_system.alarm_control_panel] sending packet 2, message: b’\x00\x02\x01\x82’
2019-06-03 20:50:33 INFO (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] Jablotron state changed: disarmed to pending

Within 2 seconds, we got a new state from the alarm system. So the alarm system is responding within the expected amount of time on the arm action.

However, I also see that it will take exactly 30 seconds to get it armed:

2019-06-03 20:51:03 INFO (ThreadPoolExecutor-1_0) [custom_components.jablotron_system.alarm_control_panel] Jablotron state changed: pending to armed_home

To be honest, I really don’t have a clue why the system is reporting back this state only after 30 seconds, while the code has been reading data every second since it has the state ‘pending’. It looks like it’s not reporting back the right state any sooner.