JablotronPy
Jablotron Cloud API client written in Python that allows you to retrieve data from Jablotron systems as well as control them.
Installation
The package is published to PyPi, to install it run the following command:
pip install jablotronpy
Usage
This is an example of initializing a client and getting all sections from the first available service:
import os
from jablotronpy.jablotronpy import Jablotron
# Initialize client and perform login
client = Jablotron(
username=os.environ["JABLOTRON_USER"],
password=os.environ["JABLOTRON_PASS"],
pin_code=os.environ["JABLOTRON_PIN"]
)
client.perform_login()
# Get service and its sections
service_id = client.get_services()[0]["service-id"]
sections = client.get_sections(service_id=service_id)
print(sections)
Methods
The client offers a variation of data, here is a table of the methods and data it returns:
| Method | Description |
|---|---|
| perform_login | Performs initial login to Jablotron Cloud API |
| get_services | Returns list of available services for specified Jablotron Cloud account |
| get_service_information | Returns additional information about specified service |
| get_sections | Returns available sections for specified service |
| get_thermo_devices | Returns list of available thermo devices for specified service |
| get_keyboard_segments | Returns list of available keyboards and their segments for specified service |
| get_programmable_gates | Returns available programmable gates and their states for specified service |
| get_service_history | Returns list of historical events for specified service (see note below) |
| get_access_token | Returns a bearer token for the GraphQL API |
| get_events | Returns event history (incl. arm/disarm) via the GraphQL API |
| get_events_page | Returns a single page of event history plus a cursor for the next page |
| control_section | Sets specified section of specified service to desired state |
| control_programmable_gate | Sets specified programmable gate of specified service to desired state |
| control_thermo_device | Sets heating mode and/or temperature of specified thermo device |
Thermostat control and 502 Bad Gateway
Jablotron Cloud often answers controlThermoDevice.json with 502 Bad Gateway after a few
seconds, while the thermostat still applies the change 20-50 seconds later.
control_thermo_device and control_thermo_device_with_response therefore treat a 502/504
as "not confirmed yet": they poll get_thermo_devices every confirm_interval seconds
(default 3) for up to confirm_timeout seconds (default 60) and return as soon as the
thermostat reflects the requested mode/temperature. If it does not, the original
BadGatewayException (a subclass of JablotronApiException) is raised. Pass
confirm_timeout=0 to raise immediately instead. Note that the call can block for up to
confirm_timeout seconds.
Detecting active alarms
The Jablotron Cloud API does not push notifications to third-party clients, so detecting an
active alarm requires polling. The signal lives in the sectionsGet response, not in
serviceListGet or in the section state itself (a section in alarm continues to report state
ARM). While an alarm is live, data["service-states"] contains an events list:
{
"service-states": {
"service-name": "Home",
"events": [
{
"type": "ALARM",
"message": "Alarm - Periphery PIR hallway (wifi), Section House",
"date": "2026-04-26T10:24:16+0200"
}
]
},
"states": [{"cloud-component-id": "SEC-...", "state": "ARM"}],
"sections": [...]
}
Notes:
- The
eventskey is only present while an event is active. If the alarm ends before the next poll, you will miss it. - Observed
typevalue:"ALARM". Other types (tamper, sabotage, fault) likely exist but are not yet documented here. - The
JA100/eventHistoryGet.jsonendpoint exposed viaget_service_historynow returns400 METHOD.NOT-SUPPORTEDregardless of parameters, for every panel type. Useget_eventsinstead (see below).
Minimal poller:
sections = client.get_sections(service_id=sid)
for event in sections["service-states"].get("events", []):
if event["type"] == "ALARM":
... # handle alarm
Event history (arm/disarm, etc.)
get_service_history (the eventHistoryGet.json REST endpoint) has stopped working. The
official app instead fetches event history through a separate GraphQL API
(https://graph.jablotron.cloud/graphql), authenticated with a short-lived bearer token.
get_events implements that flow and returns the same kind of data (including which
section was armed/disarmed, by whom, and when):
service = client.get_services()[0]
events = client.get_events(service_id=service["service-id"], service_type=service["service-type"])
for event in events:
if event["type"] in ("SECURITY_SYSTEM.CONTROL.SECTION_ARM", "SECURITY_SYSTEM.CONTROL.SECTION_DISARM"):
section = next((s["name"] for s in event["subjects"]), None)
invoker = next((i["name"] for i in event["invokers"]), None)
print(event["occurredAt"], event["type"], section, invoker)
Notes:
service_typeis required here and must be the panel type from theservice-typevalue ofget_services()(e.g.JA100F). It is used to build the GraphQL entity id and is unrelated to theservice_typeparameter on the REST endpoints (which defaults toJA100).- The API rejects page sizes above roughly 20-24 (
Request validation failedwith no further detail), sopage_sizeis limited to 20 andget_eventspaginates internally. It stops aftermax_pagespages (default10, i.e. up to 200 events); passmax_pages=Nonefor the complete history, or useget_events_pageand itsend-cursorto paginate yourself. - The bearer token is cached and renewed automatically.
get_access_tokencan be called on its own if you need to talk to the GraphQL API directly for something this library doesn't wrap yet.
Metadata
Release files for JablotronPy 0.7.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jablotronpy-0.7.5.tar.gz | 35.0 kB | Without provenance | Details for jablotronpy-0.7.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jablotronpy-0.7.5-py3-none-any.whl | Python 3 | none | any | Details for jablotronpy-0.7.5-py3-none-any.whl |
Total release size: 52.0 kB
Release files / jablotronpy-0.7.5.tar.gz
| Download URL | jablotronpy-0.7.5.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bb3a700c4923b9b4012c1afaeb6961b87fa615cd61687997f3c4cd828f9f04c
|
|
BLAKE2b-256 checksum How to use checksums |
9583095174b0941140b2ca33b22b99bf0a0d0a85c489669dbbc9bc8dec6cf9f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / jablotronpy-0.7.5-py3-none-any.whl
| Download URL | jablotronpy-0.7.5-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
194775e6c22e6054e72c5a443920e90d998360fb3e8bbf8cd6f098d38659dc13
|
|
BLAKE2b-256 checksum How to use checksums |
5030a31a3063d558173453b2275c65313633191f4b2a7b86f3269f1f75dacff5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for JablotronPy 0.7.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.