Home Assistant custom component for JABLOTRON 100+ alarm system.
Tested with JA-100K, JA-101K, JA-101K-LAN, JA-103K, JA-103KRY, JA-106K-3G, JA-107K and JA-14K.
- States are reported to Home Assistant.
- You can arm/disarm all sections. Supported states are
arm_away
(= armed) andarm_night
/arm_home
(choose in options what means "armed partially" for you). - Event
jablotron100_wrong_code
is triggered when wrong code is inserted in Home Assistant. - Problem in a section is reported in specific "problem" sensor.
- Devices with two states (on/off, active/inactive, open/closed etc.) are supported.
- Sabotage or problem of the device is supported in specific "problem" sensor.
- Temperature is reported for thermostats, thermometers and smoke detectors.
- Pulses are reported for electricity meters with pulse output.
- Signal strength is reported for wireless devices.
- Battery level is reported for devices with battery.
- States are reported to Home Assistant.
- It's possible to turn on/off all PG outputs.
- State of LAN connection is reported to Home Assistant for supported central units.
- Strength of GSM signal is reported for supported central units.
-
Connect the USB cable to Jablotron central unit
-
Restart the Home Assistant OS
-
Use the following command line to identify the port:
$ dmesg | grep usb $ dmesg | grep hid
The cable should be connected as
/dev/hidraw[x]
,/dev/ttyUSB0
or similar.
- If you use code with a prefix, insert the code with the asterisk, e.g.
12*3456
. - Use code of administrator to make devices work. If you cannot use code of administrator, or you don't want to use devices, set the number of devices to 0.
- You have to set devices in the same order as you see them in your J-Link/F-Link/mobile application. Ignore the central unit on position 0.
- If you want to use PG outputs, the user of the code has to have rights to control the PG outputs. Set the number of PG outputs to 0 to ignore them.
- Install the integration via HACS (Home Assistant Community Store)
HACS is a third party community store and is not included in Home Assistant out of the box. - Restart Home Assistant
- Jablotron integration should be available in the integrations UI
- Download integration
- Copy the folder
custom_components/jablotron100
from the zip to your config directory - Restart Home Assistant
- Jablotron integration should be available in the integrations UI
- Try to arm/disarm all sections
- Try to activate all devices if possible (open/close door/window, move ahead of motion sensor etc.) and check if Home Assistant see the state changes
- Check log - it should be empty when everything works
- Does any problem occur? Report issue or join Discord
Even if everything works for you, you can join the Discord. We would be happy:
- If you report model of you Jablotron central unit, so we know that integration works on another model
- If you can test some things (e.g. LAN), so we can make the integration more robust
The communication in Discord is mostly in Czech or Slovak but don't be afraid - you can use English as well.
- Enable debug logging for the Jablotron intergation via the logger integration by adding the following lines to the
configuration.yaml
file.
logger:
default: info
logs:
custom_components.jablotron100: debug
- Enable debug logging in the Jablotron integration. Go to the Integration page of your Home Assistant and click on the
Configure
button belonging to the Jablotron integration and then selectDebugging
to specify specific debugging options, such asLog all incoming packets
. Finish the configuration by pressing theSubmit
button. - After enabling 1. and 2., the home assistant log should contain debug log of the Jablotron integration, e.g.,
2022-02-17 10:57:19 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron100] Incoming: 801a0cffffffff010001002820010027ffffffffffffffffffffffff
2022-02-17 10:57:19 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron100] Incoming: 5203820113
- Restart Home Assistant
Big thanks to plaksnor, Horsi70 and Shamshala for their work on previous integration.